[bob.wolff68]

Hey Ron,
Your description of the problem tells me that possibly there is some confusion about the flashing of the crio versus uploading/deploying programs. Before going to a conversation about this, I figure I should say:
- cRio Imaging tool is usually done once at the beginning of the season to "catch up" with the latest flash version. This year, v47 is the version that should be on your cRio. You can verify this with the imaging tool. Just run it with the ethernet cable directly attached between the computer and the crio. The imaging tool is pretty good at discovering the crio and telling you on the UI what version is currently on the device. If it's v47, there's no need to re-flash again until FIRST says they have an update - which may or may not happen again this season.
- The cRio imaging tool has nothing to do with Windriver Workbench. Windriver workbench is the development environment for writing programs, compiling them, and 'uploading' or 'deploying' them to the crio. This is not the same as flashing the device. The deployment is simply ftp'ing a compiled program to the cRio so that it will be run the next time the cRio is rebooted.

With that couple of clarifications... let us know if you're on v47 or not and then let's talk about compilation, deploy, and reboot / diagnostic of whether things are healthy from there.

We'll get ya runnin'. I'm confident!

bob