|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Here is the image of our setup... We're currently attempting to find the original default code to download, just in case we changed something by accident. As far as the joysticks, this is probably a stupid question, but other than battery usage, does the model matter? Meaning, do we have to select it somewhere within the code? We used V-Max 2013 flight joysticks for ps3/PC, nothing fancy, just generic joysticks... |
|
#2
|
|||
|
|||
|
Re: Reimaging the cRIO - Help!
From your screen, it seems that you have joysticks, code, and communication to your robot. It is disabled, and it isn't possible to know how the code was programmed.
My suggestion would be to enable the robot in teleop mode and carefully test it. Perhaps you should put the robot on blocks as you test. You should also be ready to disable or estop it by hitting the spacebar on the driver station if you need to. Another approach is to go to the dashboard and put the robot into test mode. This lets you read sensors and it lets you enable and test outputs just one at a time. Greg McKaskle |
|
#3
|
|||||
|
|||||
|
Re: Reimaging the cRIO - Help!
If you reimaged the cRIO, any user code was erased from it in the process. You must load your code onto the robot again before it will do anything.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|