There are a number of messages from the motor controllers we don't really use info from (Status 4, 8, 12, 14) especially not during a match - more for controllers that aren't ever running in closed loop mode (intake, hopper, indexer)
Same for the pigeon (e.g. magnetometer)
looks like followers will observe their leader & all statuses can be set to slowest values (255)
We probably don't need much from the pigeon IMU during teleop unless we're running the climb command but might be worth not having to add this additional complexity if not required
This should help reduce the probability of collisions on the bus, which may cause the PH to disable its outputs
Reduce frame periods on CTRE devices:
Some guidance here: https://docs.ctre-phoenix.com/en/stable/ch18_CommonAPI.html
There are a number of messages from the motor controllers we don't really use info from (Status 4, 8, 12, 14) especially not during a match - more for controllers that aren't ever running in closed loop mode (intake, hopper, indexer) Same for the pigeon (e.g. magnetometer)
This should help reduce the probability of collisions on the bus, which may cause the PH to disable its outputs