[Ryan Reliford]

Thanks for the responses. Let me answer some of the questions asked...

How long does the power cut out? The power will completely cut out and the driver station will disable itself requiring us to re-enable to continue.

SLIJN, yes, this is all occurring while there are no wires connected to the output and while there is no cb connected on that particular port. We're not using the DLINK...we're connecting directly from the laptop to the cRIO with an Ethernet cable. I will check the voltage logs.

Does adding a fuse, 20A or 30A, rectify the problem? Do you push down onto the fuse itself, or somewhere else near the suspect slot? We started by trying to push the fuse all the way down and noticed that the light would flicker on and off. We then try to seat it just right so that the light would go off but it would only ever go off temporarily (no more than 20 seconds or so). Pressing on the PDB near where the fuse is also causes the light to go out but it's so touchy that it comes back on if you're not pressing in the "sweet spot".

The brief loss of communication was seen when we pressed down on the board, trying to keep the light off, and we witnessed what appeared to be a breaker tripping (the power cutting out). But, instead of the driver station disabling completely, the power would cut out but then come back on immediately (within a second or two). Again, this scenario only happened while we were actively trying to keep the light off by pressing on the board. Otherwise, the driver station would completely disable itself. So when I say it lost communication, what I'm really trying to convey is the fact that the driver station indicators all go to red, the robot communication indicator included.