Doug gave us the same advice. We were having random sucess with our deployment, more failures than successes. IMO, the NoApp switch is a better solution than a cRIO re-image for a few reasons ... with the primary reason being the chance of lobotomizing the cRIO if the re-image goes bad.
Here are some steps I posted in the "Deployment Issues" thread ...
Quote:
1) on the cRIO, set the No App dipswitch to TRUE (this prevents user code from running when the cRIO boots, regardless of the SW settings)
2) reset the cRIO and feel free to deploy/run/build/set-as-startup, whatever ... As long as that dip-switch is set, it'll never run the startup apps when it boots, and the deployents (or just hitting RUN in the RobotMain.VI) works every time.
3) when you are done debugging and/or troubleshooting and want to try it out in a "realistic" fashion, do a final build and Set as Startup.
4) when the upload to the cRIO is complete, there's a window to close and then it asks you to reboot the cRIO. Before you click the Reboot button, UNSET that dip-switch
He said that they are looking into why this is occurring, but apparently they've got a pretty good workaround until we get a patch.
After I learned this trick, I never saw those errors again, and we were slinging code onto our 'bot all day today (Practice day at the AZ regionals)
|