Quote:
Originally Posted by John_1102
I had so many errors it wasn't funny when i replaced Arcade Drive with tank drive. I tried Arcade and it still screwed up but the errors were gone. What i do is start a new Robot Project I build it and set it as the startup. I edited the tele-op File to use jostick, watchdog and Open motor references from the begin.vi, I changed the Arcade drive to Tank Drive and i set the 2 get axis's to Axis 2 and axis 5 because i'm using the Daul Action Gamepad. then i took axis 5 off and so nothing was to supposed to run the right motor. When i ran the program to see if the left motor worked on the left stick. Both motors ran they were not supposed to, when i took axis 2 off and tried axis 5 right y axis stick nothing happened. To run my code i save my teleop changes and Deploy it from the boot time thing at the bottom by right clicking and selecting deploy (I DO GET A MESSAGE BOX SAYING THAT CERTAIN VI's are real time vi's and that if i choose to continue all vi's on the device will close the vi's it lists are mostly camera realted though it sometimes shows the main vi as well). then i reboot and open the drivers station.
|
So you select deploy rather than 'Run as Startup' and then reboot the cRio once it's finished downloading? When you deploy, it just loads and runs your program on the cRio while the LabVIEW program is running, and if you turn off the cRio it will lose that code. The last program set as startup will then load when you reboot. Seems like you're loading the same arcade drive program each time you turn it off and back on. Right click on Build Dependencies in the project tree and select Build, then Run as Startup once that's done. Then you should be able to reboot without losing the program.