I have 7 ND+2's talking to each other over ethernet and it works pretty well most of the time but I occasionally get a controller drop out and not even be pingable(using DOS command prompt) for no reason. The code is at a state where it is just waiting for incoming data so I can rule out the idea of the code causing the issue. All seven controllers are running the same code for the most part. I am controlling LED strands on a separate thread using SPI.
My first problem is that the ND will just be unresponsive to a ping at any random time. I have the socket option set to KeepAlive also. (If I have all the controllers working before I leave work around 5pm and return at 8am I will usually have around three controllers unpingable, the number will change from day to day) Is this a common issue with the ND+2? I tried firmware 4.2 and now I'm using 4.3 and it acts the same. The devices are all set to static and I have the router holding those addresses for the ND's
My second problem is when I try to do a socket.connect(RemoteEndpoint). If the endpoint is not responsive(i.e. cable unplugged) then the program just sits there waiting and will never throw an exception or move on; I have to reboot the device to get past this error. I've read some forums that this has been corrected on ver 4.3 but it did the same thing with ver 4.2.
Any help would be greatly appreciated,
Steve