See: https://cyberbotics.com/doc/reference/proto
The idea would be to create PROTOs that correspond to commonly used FRC parts (e.g. NEO, NEO550, Falcon, CIM, MiniCIM, GrayhillEncoder, AMT103Encoder) which provide fields for easy configuration (e.g. ticks per revolution, gear reduction, CAN ID, PWM port number, channel A, channel B). Once #22 is closed, each PROTO could use those fields to create the underlying sensors/actuators with names that contain the configuration info, so it can be used by the controller. Once #25 is closed, we can use the Supervisor API to configure the devices based on the values of the fields.
See: https://cyberbotics.com/doc/reference/proto
The idea would be to create PROTOs that correspond to commonly used FRC parts (e.g. NEO, NEO550, Falcon, CIM, MiniCIM, GrayhillEncoder, AMT103Encoder) which provide fields for easy configuration (e.g. ticks per revolution, gear reduction, CAN ID, PWM port number, channel A, channel B).
Once #22 is closed, each PROTO could use those fields to create the underlying sensors/actuators with names that contain the configuration info, so it can be used by the controller.Once #25 is closed, we can use theSupervisorAPI to configure the devices based on the values of the fields.