Quote:
Originally Posted by furiousgeorge
the IO module on the robot is in working order, i was questioning the need for the IO module on the driver's station. when you say i need to click enable on the driver's station, does that mean i have to send the VI as a start up to the cRIO, then switch from the developer to the driver on the netbook so that i can test out my program? if so, is there any way that i can test my programming while still in labview so that i do not have to switch back and forth between the developer and driver user accounts on the netbook?
|
To answer your first question, the IO module does
not have to be hooked up to the driver station.
To answer your second question, at this point I'm assuming that you're also using your Classmate to program your robot in addition to using it as a driver station. While is this is possible, it's best to use a second laptop to do your development on.
That being said, it is possible to execute your code, and with LabVIEW still running, switch users and use the Driver account to enable the robot. I have run into issues with this, as when you try to switch back to the Developer account, the machine crashes. Switching users is not reccommended by FIRST.
You can also Deploy the code to the bot so that after the bot reboots, it retains the code. If you did this, then you could log out of the developer account, log in to the driver account, reboot the bot, and your code would still be loaded. Unfortunately I don't know how to deploy code from LabVIEW, so someone more versed in that should speak up. On that note, if anyone knows how to deploy code from the new java environment, I'm eager to find out. I've only done it using Windriver.
Hope this helps!
Jacob