[byteit101]

I can't seem to find the good comprehensive documentation like in years past on the FIRST or NI site about crio, driver station, etc... I can only find basics getting started. If someone can point me in that direction, I'd be much appreciative.

(if you don't want to read story, questions are at end)

Yesterday I was working on re-downloading our old logomotion code compiled for 2012 on a v43 formatted crio for an upcoming school open house demo. First try I downloaded and rebooted successfully, but when I enabled, the jaguars (On CAN bus) did not enable, except the last one. I presses the space bar to disable, but to my shock, horror, and dismay, it is the new estop button AND the reboot robot button is disabled, so I had to power cycle the robot manually (not fun).
Upon the next boot up and enable, the can system worked, but no motor commands were being sent (strange, since it was our final working code on same robot from last year), so I added a few printfs and commented out unneeded code. Re-dowloaded a few times with more printfs, etc, and rebooted. Then the Symptoms started.
It was taking a while to come back up, so I checked Ethernet cables, and rebooted full robot stack. It still did not come up after 5 minutes, so I direct plugged into crio (bypassing switch), which still did not work. after unplugging unnecessary-to-drive systems, making sure necessary systems were plugged in, and battery was ok, I rebooted robot stack again.
Still nothing.
I flipped the safe mode dip switch (cRIO I) and rebooted, and it came up. I re-imaged it, turned off safe mode, and rebooted. Still nothing.
I watched the netconsole, which stayed empty (no pings either)
I watched the status lights above the dip switches, and found that the "Status" light was slow blinking yellow.


So,
#1 what is the key to disable the robot? (last year was spacebar)
#2 what does this yellow blinking "Status" (above "User" light) light mean?