|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Different behavior in code when deployed vs run live
Hi all,
We are experiencing a difference in code behavior between when it is run live compared to being hard-deployed to the robot and then rebooting. We are running a shooter off of a PID loop in periodic tasks with feedback from a hall effect sensor. It runs perfectly when running from Robot Main, but when it is built and then deployed followed by a reboot it will initialize for one second and then stop. If we reinitialize autonomous, the shooter will run. Thanks for any and all help. |
|
#2
|
||||
|
||||
|
Re: Different behavior in code when deployed vs run live
You may not be calling the values correctly inside of the loop. Also are you saving the values as default after the build and deploy?
|
|
#3
|
|||
|
|||
|
Re: Different behavior in code when deployed vs run live
We set a global variable in autonomous which is read in by a loop in periodic tasks. This value is constant between the autonomous runs.
For your next question the values we are changing are constants not controls, so they are saved directly to disk and built from there. |
|
#4
|
||||
|
||||
|
Re: Different behavior in code when deployed vs run live
well if you could do a print screen of your code I can further help you with your situation.
When writing global variables you have to make sure the values in auto are written at the start of the VI then read them as needed. Since they are all constant you should be seeing no difference in the PID. You can also run indicators to see exactly what is going on. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|