Motion Outputs disabled after cRIO reboot via DS

[Travis Hoffman]

It seems of late that whenever we deploy new code and reboot the cRIO from the Driver Station, the reboot appears to go well - all DS status lights return to green. However, upon enabling, the bot's PWM and relay outputs are non-responsive. We have to power cycle the bot once (and infrequently, twice) to get the program to execute, after which we have no problems. This is obviously very annoying, as you have to wait much longer to enable the bot following a power cycle than a reboot. I am wondering if there is a hidden issue somewhere in the code or with the Driver Station or cRIO that is causing this unwanted behavior.

Our code compiles and deploys with no apparent errors. We use the Classmate wireless adapter and the robot radio in AP mode. I haven't noticed any red dots on the DS or anything else that indicates wireless comms problems lately. We have the latest version of the DS installed, as well as the latest C++ update.

So does anyone have any initial thoughts on this matter? Debug steps to pursue? We'll have access to the bot once again on Monday afternoon, so we can try out any suggested debug operations then. Thanks in advance for the advice and help!