-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
save and recall PID settings #3
Comments
I take it it wouldn't be easy to do this robot-side? Because this means your have to retune the PID for every device that wants to drive the robot, and that seems unfriendly/unintuitive at best. Edit: sorry I didn't read your whole post before commenting haha. I think it'd be best to just save the last PID settings in the robot's flash memory? |
I don't think it would be too bad to do it robot side, can I try that first? |
I'll update this issue with a description of how the robot sends recalled values, when I think of how. |
@joshua255 Maybe we could have the ds send an initial "hello" message to the robot (potentially with some special data, e.g. ip address or something like that), and the robot responds with its own "hello" message, containing PID values and other recalled constants. |
Would you mind having a save settings on robot button? |
done in v2, 4 years late! 😄 |
Being able to save and recall one set of PID constants to a file is important so the robot doesn't have to be retuned every time it is used. It would be even better if it can store different values for each robot and each configuration, and even cooler if these values could be synced between driverstations so we can switch robots and not have to retune (that could be a file manually copied between devices). Or, if you would prefer, we could try to have the robot store its PID values to its flash/eeprom memory, and transmit them to the driverstation on startup.
The text was updated successfully, but these errors were encountered: