[bomber7]

(I use windriver)
Untrue, I have often gotten "No Comms" with a code error. (Instead of saying "No Code")

(All values are approx)
What I have noticied about the debug light:
You start your robot at 00s
10s Light turns on and is blinking
40s dashboard/Driverstation responds
40s Light blinking slows down
80s Light goes solid, robot begins operating

Previously I've messed up a define in such a way I attempted to use an undefined variable in the init of the robot. At 80s the robot light would turn off and the driverstation/dashboard would report No Comms.

The robot would then proceed to restart continously always coming online for a period of a few seconds before resulting in No Comms. It would always report No Comms with the light blinking slowly.

I've also had this problem when I tried to send too many tcp/ip packets at once. (Turns out trying to send 100 packets in less than a second blows up the cRIO =P)