Maybe you can post some of your code, the vision code is where I would start. (Post a snippet instead of just a screenshot.) Does this happen regardless of driver station mode?
I am guessing something is hogging all of the cRIOs CPU, and the RobotDrive.vi is not getting enough priority to run, or is never executed in the first place.
Quote:
|
One thing I'm not clear on is the proper way to upload a program to the cRIO. Do we just press run and wait for it to deploy? Somewhere else on CD I found instructions saying to right click the build target and click "build", then "run on startup". Which is the better way to do it, at least for development?
|
*For development, you can simply run the Main.VI, and LabVIEW will automatically deploy, and you still have all the debugging tools available. (It can use a lot of bandwidth.)
*Deploying sets your program to run without the laptop used to deploy. This is more useful for letting the drivers train, while more programming is going on. The code is however erased every time you reboot the cRIO. (That includes power cycles.) If your code is bad, the robot is easily recoverable by simply resetting the power.
*Deploying, and setting "run on start-up" will always run your code, even after power cycles. This is for competition and any time you need to use the robot without the computer used to program it. (EG. Drivers training on days without the programmers.) I typically wouldn't use this until I have tested it by simply deploying first. This will rule out issues with your code maxing out the cRIOs CPU.