65tux

Huh. Got past it but I did 2 things and I'm not sure which one fixed it.  I tried the "remove all statics from Program" thing and, by itself that did not solve the problem.  I then changed my build to "release" and voila, it now boots.  Not sure if just the release would have fixed it, but it's working.

Me too - no answer?

We can mount it upside down but it would make access to the network jack a bit of a pain - and it's so pretty we don't want to hide it!  Plus the network lights are useful for troubleshooting.

Our circuit board is much bigger and the whole thing is going into an enclosure with customer-wired terminal blocks so if we don't switch the pin headers on the ND, we will either have to mount it under our circuit board or upside down.  Under again has the issue of accessing the network jack and we would have to have large standoffs to get the board high enough.

Just a thought - was hoping we weren't the only ones to have asked.

I assumed input interrupts were in a separate thread - is that not true?  If anything, it seems the other way around to me - the other logic is blocking the DataReceived.

The basic code is - when I get an interrupt, set a "waiting" flag and call a sub to send a command string to the display.  That sub has a whiile "waiting" loop.  The DataReceived will clear "waiting" when the response comes in.

Pretty sure I have all but proven it.  By putting all my code (send and receive) in one sub it works perfectly.  When using the DataReceived event handler receives are significantly delayed.