You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2022. It is now read-only.
Yep! The pid settings should be in their own yaml instead of in hardware.yaml, fixing this will involve using the yaml loader to load the seperate settings file when adjusting PID
The main reason for this, is that the hardware config is useful for in-the-pits work, but the pid is not.
Start under rio/constants and break the pid sections away, should look something like this:
robot_hardware.yaml
subsytem:
motor_id: 2another_motor_id: 69
robot_pid.yaml
subsystem:
motor_kp: 0motor_kd: 0motor_ki: 69
etc.
And to load them, you'll need another load command in python:
This is low priority but simple enough
The text was updated successfully, but these errors were encountered: