Emonbase has stopped working

Hi everyone,

 

my emonbase has been happily communicating with emoncms.org for several months now. I've just built another emonTX for with a view to reading the Elster meter (which it does nicely). I modified my emonbase code to work with the my extra hardware and it no longer communicated with the emoncms server. 

I put my original sketch back in. This failed too. 

The network was upgraded to a Virgin Media superhub yesterday but the emonbase continued to communicate with the cms server until I added in my new code some six hours later. I'm fairly sure that this is not the reason.

If I try some of the standard sketches they dont work either.

 

I have the emon base (its the nanode RF SMT). I've checked the regulators. They have 5.12V and 3V. 

 

What seems to happen is that the sketches get as far as here:

 

if (ether.begin(sizeof Ethernet::buffer, mymac) == 0) { //for use with NanodeRF
    Serial.println( "Failed to access Ethernet controller");
    ethernet_error = 1; 
  }

and cannot get any further. It just hangs.

On the Nanode the ethernet connection has a green light and I can see the yellow light polling but nothing happens. 

 

If I comment out this section I can get further - I can receive RF data from the emonTX units but internet activity continues to time out.

I think I am using the same versions of the etherCard software as before but, in all honesty, I've gone around and around in circles so many times I cannot be 100% sure.

I can also program the unit with a "hello world" type of program. The issue seems to be in the ethernet part of the application... I'm just stumped and not sure where to go next.

 

Any thoughts are highly appreciated.

 

thanks

 

Ian

Robert Wall's picture

Re: Emonbase has stopped working

What sort of emonBase do you have? It looks exactly like the problem I have with an OKG I got to install for a friend. That worked fine for a time, now it refuses to communicate at all - except once, apparently by accident;  but a NanodeRF connected with the same cable to the same router works (not properly - while checking, I saw it take 450 tries of the initial DHCP Discover / Offer handshake before it reacted and accepted the IP address, but it got there eventually!)  Barring something stupid, I'd point the finger of suspicion at DHCP and your new router, or is there a firewall that needs setting up?

(I used Wireshark to find out the above - though it sees the initial broadcast query, it doesn't see the rest of the transactions once the path is set up.)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.