[whitetiger0990]

That is strange..

Building and deploying does take awhile, but that is offset by the RAM deployment not taking long.

At least for us, the running from RAM is like 20 seconds. 30 seconds? something like that. It's not long at all.

You should be able to make things a lot faster if you make -everything- wired. That's how it'll be at competition.

You have your router with the 4 LAN ports on the back. Plug DS ETH1 into one. Plug cRIO port 1 into one. Plug computer into one. Everything on LAN means no interference and no wireless hops (like laptop to router to wireless bridge to robot, or laptop to DS to router to wireless bridge to robot). It's best to minimize hops and just do laptop to router to robot. Skip the wireless unless you need to.

The building is on the computer. It might take awhile if it's not a very fast computer. Keep that in mind.


If you're really worrying about last minute changes on the bot.. well. Sorry. Tell the people making the request how big your turn around time is, and/or don't make mistakes when programming =P

If you use some sort of scripting technique for autonomous, you could have the scripts separate from the main labview code, meaning you don't have to redeploy each time you want to change something in autonomous. You could also probably do something similer with variable initialization.. if the they want some sensitivity variable changed, change the script file, upload that to the cRIO, and have your program read that config file on start up... I'm planning this from memory and have not thoroughly tested it. I'll test it quickly tomorrow.

For those who don't know, it's possible to FTP to the cRIO (this is how deployment works I believe). I tried once, but I was able to FTP an image (for use for our target recognition calibration) to the bot and have the code read it. I just thought of using a text file for configuration. *makes a note to try*