Hi all, I'm using the GSIOT classes from the fantastic e-book.
The problem I'm encountering is that if, say, the router or cable modem were to drop out for a second, meaning the netduino's GET requests could no longer get outside of the LAN, the Netduino seems to die.
Even if this outage is only for 30 seconds or so, it still happens.
I'm not sure if the board is locking up, or if the networking stack is getting stuck, I will investigate that further by setting up a process to blink a LED or something.
The only thing I could find through search was about lock ups when unplugging the cable, but in my case, the netduino never loses it's datalink layer connection to its local switch.
Is this something known? And/or, any suggestions on what docs to look up?
Thanks!
Networking fails to recover from unreachable hosts.
Started by cross6, Nov 08 2011 11:36 PM
2 replies to this topic
#1
Posted 08 November 2011 - 11:36 PM
#2
Posted 09 November 2011 - 02:52 PM
ThanksHi all, I'm using the GSIOT classes from the fantastic e-book.
I don't think I have heard about this problem yet. I assume you are using one of the HelloPachube examples? Does it work when the router has no outages?Is this something known? And/or, any suggestions on what docs to look up?
Is your Netduino still connected to Visual Studio, so that you see the debug output in the Output window, at least until an outage occurs?
Best regards
Cuno
#3
Posted 09 November 2011 - 03:54 PM
I too have the HelloPachube example running on a Netendo Plus powered by a wall-wart. It has been running continuously for a couple of weeks now. It runs fine and I can see the data on Pachube. I have definately had a few network hickups as well as outages lasting several minutes. The Netduino has not locked up once.
As they say, your mileage may vary .....
Also a big thank you for your great book, I highly recommend it!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users