kluger

I have been having issues with the network dying on my Netduino Plus. This poster seems to be having same/similar prob: http://forums.netdui...vailable-in-42/ -Being on a busy network is what is killing it (it seems). -I have found this on 4.1 and 4.2 firmware. -Seems independ of code. -When "dead", the rest of the Netduino still works. --If a debugger is running, the program can report things like network address. --onboard LED will continue to blink in a continuous loop. --Pinging the Netduino ceases to work. While on a busy network, it takes between 5minutes and an hour for the Netduino's net to stop responding. While on a very quiet network, the Netduino seems to live a great deal longer... I just started a test setup and will let it run for a day. My question: From within the C# program, can I detect when the network port is no longer responsive? I just had an idea!!!! maybe I could ping the localhost???? Anyways, I'd prefer to not have a watchdog. I prefer that the network port be dependable, or barring that, be able to detect in software when the network port had died and so have the software decide when to smartly do a reset. Any ideas? -kluger

Hello All, Here is a detailed five page guide for how to update the firmware on a Netduino Plus, and what to expect durring each stage. For example: some of the steps take less than a second while some take a great deal more time. I hope you find this document useful. -dusty