|
Re: Pushing down LabView Code
You don't have to push the code through the Driver Station. It doesn't need to know.
You can also bypass the DS by connecting your laptop directly to the router rather than directly to the cRIO.
Typically though, you want to get used to connecting your laptop to the DS, because the router won't be available at competitions and it's so much easier to run over the wireless system when you're developing code at home, rather than to connect your PC directly to the cRIO.
The "No Code" means there's a disconnect between the DS and cRIO, but they have established basic communications. The code that sends the battery voltage is just not running on the cRIO.
--When you first flash the cRIO (with v7 from Update 2) there is code left to run and return the voltage.
--When you "Run as startup" to deploy new code, you need to reboot the cRIO afterwards to have it actually start.
--If you use the "Run" button to test code, under certain circumstances that will disable any pre-existing code on the cRIO set to run at startup. You will need to redeploy using "Run as startup" again.
It sounds as if you missed a step in deploying your code, so that it's on the cRIO but not set to run at startup.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Last edited by Mark McLeod : 18-01-2009 at 10:23.
|