|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: OPR after Week Three Events
Quote:
|
|
#2
|
||||
|
||||
|
Re: OPR after Week Three Events
Quote:
Put a trim pot on your bot. Read it with an analog input. Use that value to trim your autonomous shooter speed. You can easily make tweaks between matches in the heat of competition. No software changes or uploads. |
|
#3
|
||||||
|
||||||
|
Re: OPR after Week Three Events
Quote:
If you're worried about a trim pot getting bumped and screwing you up, you can put a very simple text file on the cRIO to adjust your speed. You can change the text file and FTP it to the cRIO in about 10 seconds. We call it our "fudge file" (as in the fudge factor to adjust or speed/angle/etc.). If anyone wants an example of how to do this in LabVIEW, let me know and I'll either post it here or e-mail it to you. |
|
#4
|
||||
|
||||
|
Re: OPR after Week Three Events
Yet another option:
If you have 3 free buttons on the operator console, you can use them to adjust values in the fudge file. Use button1 to cycle through the available fudge values in the file to select the one you want to adjust. Use button2 to bump the selected value up. Button3 to bump the selected value down. No need to connect a development computer. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|