Open DangerousElectrician opened 8 years ago
http://wiki.ros.org/roboteq_driver http://wiki.ros.org/Motor%20Controller%20Drivers
Existing motor controller nodes
Talon srx transmits 4 status frames periodically General Status 10ms Feedback Status 20ms Quadrature Encoder Status 100ms Analog Status 100ms
Dynamixel node uses services to send commands to the motor and messages for motor state. roboteq node uses messages for both motor state and motor control. Roboteq node has fewer settings than Dynamixel.
Using services to control talon. Talon has lots of settings.
Maybe use lots of messages containing single values.
Control of talon srx is implemented as a bunch of messages can_talon_srx subscribes to.
talon status is published in a single message containing all unsolicited values. The way I implemented FRC_NetworkCommunication_CANSessionMux_receiveMessage is too slow.
Need to send ros messages to the can_talon_srx node to control the motor