wendo

Well this will be interesting. I have a project that was basically useless because of the network issues. Just updated one of my NP2's and we'll see how it goes. I was rebooting every hour as a really ugly work around but hopefully this will fix that

It has been in a try/catch the whole time, but it was still bombing out....

However, it's been happily running for something like 5 days now, and while it reports the stacktrace now, it's not locking up. I _think_ I either had a dodge network cable or is was the passive POE injector I was using (maybe a combination of both).

I've switched toa new network cable and removed the POE injector and it appears to be stable....

You'd think working in IT I would have looked at that earlier . I also think putting it in it's own thread and using autoreset has helped too but at the moment I'm leaning towards the cable. After I hit a week I'll put the injector back in and see what happens.

Thanks for all your help on this. 

Right, with ex.Stacktrace we have some success. I'm seeing 

It looks like it runs a custom command set so the drivers already written aren't likely to work. There is serial driver for the display written for the GHI hardware that should be fairly easy to port here. Obviously that doesn't get you I2C but it would at least get it going although it'd still take some porting work to remove all the GHI library requirements.

Failing that if an Arduino driver is available you could try porting it directly

So now I'm onto trying an AuroResetEvent since the delay in the main code just ended up crashing the main thread.

The weirdest thing is that I'm still not actually catching the exceptions in the catch block. I've added some text to the Debug.Print so now it looks like this

Debug.Print("SF: " + ex.Message);

and I get the occasional "SF:" printed, but no actual error. 

Still, we'll see if this is any more reliable...