Quote:
Originally Posted by apalrd
As for my autonomous example, I have found myself in many situations at competitions where there is a minor bug in autonomous, such as going a little bit too far or kicking a little too high, which is caused by a change in the reaction of something such as the kicker as it is worn in, and I must do a full deploy since it will be used on the field.
|
I can understand how this can be frustrating. However, you can solve this issue by taking advantage of one of the other big benefits for the cRIO: a real file system with plenty of file space.
To get around the problem you described, all of our autonomous parameters are stored in files on the cRIO. Upon boot-up the file system checks all of the files and loads the default. The drivers can cycle through all of the files from the driver station while in Disabled mode and the last selected file is what is used for the match. In order to add/change/delete files, we use FileZilla to FTP the files. It takes only a few seconds to do.
I would be more than happy to e-mail you our VIs that do all of this, if you want.