Ethernet W5100 gateway IP problem

[WMMHOME]

Hi, New to MySensors and I'm trying to figure out how to fix an IP addressing issue.
( apologies if this represents a double post, I attempted prior to validating my registration)
I'm using the latest IDE, Mysensors and etherenet gateway packages from here.

I put in my static IP address of 192,168,1,3 but can't ping it so I checked the logs and the address comes back as 0.0.0.0 or 127.127.127.127 or any other random set depending on what random nbr I use for the last digit. I tried a to go the DHCP route and it failed. Any ping attempts fail as well,

I have provided the 5100 with it's own 3.3v power, get good link and flashing tr/rx leds.

I'm using a NANO and have tried every build version down to about 10 where the old boot loader is not supported.

Strange thing is VERA seems to detect it but doesn't actually work ( start does noting) but if I disconnect the board, the ip address I entered disappears from the device.

Any ideas ?

Thanks
Wayne

[mfalkvidd]

Hi @wmmhome, welcome to the MySensors forum!

Could you post the debug log of the gateway and your entire sketch? The debug log will help see what is going wrong and a new set of eyes on the sketch might reveal some subtle difference.

[parachutesj]

power issue was my 1st thought. I had that before when it wasn't good enough.
I just experienced also an issue with a gateway, I had to specify the MAC address (change to whatever you like)

#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xAD

BR
SJ

[WMMHOME]

@mfalkvidd
Here is a dump of the log when using 192,168,1,3 I've used 1,250 and various in between and get random.

0 MCO:BGN:INIT GW,CP=RNNGA---,VER=2.3.0
11:32:45.228 -> 3 TSM:INIT
11:32:45.228 -> 4 TSF:WUR:MS=0
11:32:45.228 -> 11 TSM:INIT:TSP OK
11:32:45.228 -> 12 TSM:INIT:GW MODE
11:32:45.228 -> 14 TSM:READY:ID=0,PAR=0,DIS=0
11:32:45.228 -> 17 MCO:REG:NOT NEEDED
580 GWT:TIN:IP=120.0.0.0
1583 MCO:BGN:STP
11:32:46.834 -> 1585 MCO:BGN:INIT OK,TSP=1
51289 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
11:33:36.507 -> 51294 TSF:MSG:BC
11:33:36.507 -> 51296 TSF:MSG:FPAR REQ,ID=255
11:33:36.507 -> 51299 TSF:PNG:SEND,TO=0
11:33:36.547 -> 51301 TSF:CKU:OK
11:33:36.547 -> 51302 TSF:MSG:GWL OK
51444 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
53292 TSF:MSG:READ,255-255-0,s=148,c=3,t=3,pt=0,l=0,sg=0:
57296 TSF:MSG:READ,255-255-0,s=56,c=3,t=3,pt=0,l=0,sg=0:
59298 TSF:MSG:READ,255-255-0,s=10,c=3,t=3,pt=0,l=0,sg=0:

here is the sketch ( I have used static, no static commented and uncommented the my-ip-gateway and my-ip-static)

/**
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
 * Copyright (C) 2013-2015 Sensnology AB
 * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
 *
 * Documentation: http://www.mysensors.org
 * Support Forum: http://forum.mysensors.org
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * version 2 as published by the Free Software Foundation.
 *
 *******************************
 *
 * REVISION HISTORY
 * Version 1.0 - Henrik EKblad
 * Contribution by a-lurker and Anticimex,
 * Contribution by Norbert Truchsess <norbert.truchsess@t-online.de>
 * Contribution by Tomas Hozza <thozza@gmail.com>
 *
 *
 * DESCRIPTION
 * The EthernetGateway sends data received from sensors to the ethernet link.
 * The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
 *
 * The GW code is designed for Arduino 328p / 16MHz.  ATmega168 does not have enough memory to run this program.
 *
 * LED purposes:
 * - To use the feature, uncomment MY_DEFAULT_xxx_LED_PIN in the sketch below
 * - RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received
 * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
 * - ERR (red) - fast blink on error during transmission error or receive crc error
 *
 * See http://www.mysensors.org/build/ethernet_gateway for wiring instructions.
 *
 */

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_NRF24
//#define MY_RADIO_NRF5_ESB
//#define MY_RADIO_RFM69
//#define MY_RADIO_RFM95

// Enable gateway ethernet module type
#define MY_GATEWAY_W5100

// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4

// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif

// When W5100 is connected we have to move CE/CSN pins for NRF radio
#ifndef MY_RF24_CE_PIN
#define MY_RF24_CE_PIN 5
#endif
#ifndef MY_RF24_CS_PIN
#define MY_RF24_CS_PIN 6
#endif

// Enable UDP communication
//#define MY_USE_UDP  // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS below

// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,1,3

// If using static ip you can define Gateway and Subnet address as well
//#define MY_IP_GATEWAY_ADDRESS 192,168,1,1
//#define MY_IP_SUBNET_ADDRESS 255,255,255,0

// Renewal period if using DHCP
//#define MY_IP_RENEWAL_INTERVAL 60000

// The port to keep open on node server mode / or port to contact in client mode
#define MY_PORT 5003

// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254

// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Arduino examples use  "DEAD BEEF FEED" for the MAC address.
#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED

// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN  3

// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 7  // Error led pin
//#define MY_DEFAULT_RX_LED_PIN  8  // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN  9  // Transmit led pin

#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.h>
#include <MySensors.h>

void setup()
{
  // Setup locally attached sensors
}

void presentation()
{
  // Present locally attached sensors here
}

void loop()
{
  // Send locally attached sensors data here
}

[mfalkvidd]

Strange. Does the debug print always show 120.0.0.0 when you are using 192,168,1,3 or does the IP change for every reset or sketch upload?

My guess would be some sort of memory corruption.

Which version of the Ethernet library are you using? (The version will be printed at the end of sketch upload if the preference "Show verbose output during compilation/upload" is checked). The latest version seems to be 2.0.0.

[Karl-Heinz K]

@wmmhome

Hello,

could it be that your problem is related to the SPI issue which was discussed in this thread:

W5100 Ethernet gateway with RFM69 Radio fails at init

The suggested patches helped me a lot.

In addition: When I built my W5100 gateway I could not use the Arduino Nano, I had to switch to an Arduino Mega. The nano had not enough memory available for my project using an RFM69 AND the W5100 ethernet shield. The nano started to work, but after some 10 - 15 min the stack ran out of memory and the nano crashed. But it was not so obvious in the beginning when I started to debug the project at that time. Maybe you ran into a similar problem.

Sincerely

Karl-Heinz

[WMMHOME]

@mfalkvidd

The ethernet library I'm using is 2.0.0

The IP stays at 120.0.0.0 as long as I am using 192,168,1,3 through multiple complies and restarts. It changes to other numbers as I change the entered IP.

Karl-Heinz - thanks , I'll look through that and hopefully I'll begin to really understand it all.

Wayne

[WMMHOME]

@mfalkvidd

Good afternoon. I did some more research and found this sketch that works, in that I can get a pingable connection. I now am confident that the boards and wiring are correct. Problem now is I'm not smart enough yet to figure out how to incorporate the calls to initiate it. When I tried to put the code into SETUP, the compiler throws an error stating IPAddress is wrong. It appears that I'm not getting a reset in the stock gateway code?

const int W5100_RESET_PIN = 8;
#include <SPI.h>
#include <Ethernet.h>
#define MY_IP_ADDRESS 10,0,0,250
// Enter a MAC address for your controller below.
// Newer Ethernet shields have a MAC address printed on a sticker on the shield
byte mac[] = {
0x00, 0xAA, 0xBB, 0xCC, 0xDE, 0x02
};
void setup() {
Serial.begin(115200);
Serial.println();
Serial.println(F("node starting..."));
pinMode(W5100_RESET_PIN, OUTPUT);
digitalWrite(W5100_RESET_PIN, LOW);
delay(100);
digitalWrite(W5100_RESET_PIN, HIGH);
// give the Ethernet shield a second to initialize:
delay(3000);
#ifdef USE_DHCP
Serial.println(F("DHCP..."));
while (Ethernet.begin(mac) == 0) {
Serial.println(F("DHCP failed."));
delay(10000);
}
#else
Serial.print(F("static IP..."));
Ethernet.begin(mac, IPAddress(MY_IP_ADDRESS));
#endif
Serial.print(F("local IP:"));
Serial.println(Ethernet.localIP());
Serial.println(F("node started."));
}

void loop() {
// put your main code here, to run repeatedly:

}

[Karl-Heinz K]

Dear Wayne,

I copy my documentation for the Arduino Mega which I put in the header of my sketch (which means I did not think through all details again for this post, just wanted to help quickly) at the end of this post. It will help if you use an Arduino Mega. It might also help if you use an Arduino Nano.

During my experiments I also made the following note to myself (did not validate all details though):

" // final conclusion:
// ==============
// the Arduino Nano was not stable. Probably because it was low on SRAM.
// However, for the Arduino Nano test I did not use the SPI patched RFM69 Library -> could improve stability
// and I did not try to use an ethernet library with a smaller footprint -> could improve stability, too"

Currently I use these libraries:

#include <RFM69.h>
#include <SPI.h>
#include <Ethernet.h>

I hope this points to the right direction.

I currently use the Computourist RFM69 MQTT gateway sketch (get it here: https://github.com/computourist/RFM69-MQTT-client). But it is on my agenda to change all my code to MySensors. I just did not have time to do it. Anyway, long story short, if you send me a PM with an email address I could send you my sketch if you are interested. The code is not well structured currently, however, therefore I do not what to share it publicly.

Sincerely

Karl-Heinz

KH: quick and dirty documentation (end of 2017):

/*  Connect Arduino Mega:
 *  EthernetShield Labels = Mega Labels

 *  5V              = 5V
 *  GND             = GND
 *  IRQ = D2        = 2
 *  RST =           = 4	
 *  SCL = D13       = 52
 *  CS              = 8
 *  Miso = D12      = 50
 *  Mosi = D11      = 51
 */


/*This sketch only works under the following conditions:*/
/*============================================*/

/*1) An Arduino Mega must be used due to memory problems of Uno/Nano (SRAM)
   and it has to be an EthernetShield with W5100 chip, but it should be the newer 
  version of the EthernetShield, because older versions have the SPI
   interface permanently blocked by the EthernetShield. Only after a
   hardware modification at the SENS pin of the W5100 chip the blocking is no longer the case.
   
 2) the RFM69 Library of LowPowerLabs does not yet (end of 2017) contain all
    necessary adaptations, so that SPI conflicts between the Ethernet card
    and the RFM69 module can be solved.

    There is a patched version for this purpose:

       https://github.com/rrobinet/RFM69_Libary

  3) The original Ethernet Library of the Arduino IDE does not consider the Arduino IDE's 
     own current SPI library and must also be patched. 
     
     Copy from the Internet:

	"[Changes to the Ethernet Library](http://harizanov.com/2012/04/rfm12b-and-arduino-ethernet-with-wiznet5100-chip/)
	
	 I edited the Arduino Ethernet library file W5100.h so that it doesn’t
	allow RFM12b to interrupt while the SPI bus is busy handling Wiznet5100.
	I added a cli(); and sei(); as follows in the W5100 library."


	für Arduino Mega...
	[Reference](https://lowpowerlab.com/forum/moteino/moteino-w5100-ethernet-spi-support-spi_has_transaction/60/):

	In my case using an ATMEGA2560 changing the W5100.h library from:

	    #if defined(__AVR_ATmega1280__) || defined(__AVR_ATmega2560__)
	      inline static void initSS()    { DDRB  |=  _BV(4); };
	      inline static void setSS()     { PORTB &= ~_BV(4); };
	      inline static void resetSS()   { PORTB |=  _BV(4); };
	To
	    #if defined(__AVR_ATmega1280__) || defined(__AVR_ATmega2560__)
	      inline static void initSS()    { DDRB  |=  _BV(4); };
	      inline static void setSS()     { cli ();PORTB &= ~_BV(4); };
	      inline static void resetSS()   { PORTB |=  _BV(4); sei();};"*/```