Package: roboflex.dynamixel
roboflex.dynamixelSupport for Robotis' Dynamixel motor product line. Some of it anyway (tested on XH430-V350-R, XH430-W350, XM540-W270, XL-330-M288-T, others may work as well).We provide two layers to controlling dynamixel motors:dynamixel_controller.h defines DynamixelGroupController: a controller for a group of dynamixels connected together (following Robotis' instructions), which uses no message passing or other roboflex functionality at all.dynamixel.h, which defines helper classes to control the above, using roboflex.DynamixelGroupController (seedynamixel_controller.h)Controls a group of dynamixel motors, connected together according to Robotis' instructions, to create robot arms, pan-tilt controllers, and other robots. The DynamixelGroupController abstracts the repetitive part of the communication with the motors, and provides a convenient class that can control a group of motors through a callback function: a 'ReadWriteLoop' function. It calls this function synchronously with communication with the dynamixel motors, as fast as the interface can manage, depending on configured baud rate (think > 100hz).This code is completely stand-alone; it uses nothing from roboflex.Each dynamixel can have its own independent operation mode (current, position, velocity, etc), but this class makes it particularly easy to control groups of motors all in the same mode; see the constructors and static methods of DynamixelGroupController indynamixel_controller.h.Unless using the PositionController or VelocityController methods to instantiate a controller, the client must decide which control table entries to read and which to write. In general, you can write to the control table entries that are named DXLControlTable::Goal*, and read everything else. Refer to Robotis documentation for details.Roboflex additions (seedynamixel.h)This layer defines additional functionality to integrate with roboflex-style message passing. It defines Messages that encapsulate State and Command types, and several useful nodes.The first of these is DynamixelGroupControllerNode. This Node sub-class adapts the non-roboflex 'business logic' of DynamixelGroupController to the roboflex paradigm by configuration - you give this Node an instance of a DynamixelGroupController. This Node performs three functions:Adapts DynamixelGroupController's control loop to the roboflex threading model: inchild_thread_fn, it callsrun_readwrite_loopon the controller. Whenstopis called on this Node, it stops the thread.Provides a simple, overrideable abstract method to actually perform the control: the user should subclass this class and override:virtual DXLIdsToValues readwrite_loop_function(
     const DynamixelGroupState& state,
     const core::MessagePtr last_msg) 
 {
     return DXLIdsToValues{ 
         5: {DXLControlTable::GoalVelocity: 12 },
         6: {DXLControlTable::GoalVelocity: 2 }
     }
 }

 # in python:

 def readwrite_loop_function(state, last_msg):
     # use state and last_msg as you wish
     return {
         5: {DXLControlTable.GoalVelocity: 12 },
         6: {DXLControlTable.GoalVelocity: 2 }
     }

 # In both of these cases, this means you want to set the goal velocity of
 # dynamixel motor with id 5 to 12, and motor 6 to 2.Provides basic message handling. It will:3.1. Save the most recent message. You can use this to send in, for instance, some new position or velocity you want to move the motors to. This Node's control loop might be operating at a different frequency that the incoming messages - it should still work.3.2. Broadcast the state and command (your command values) sent to the motor group at every loop cycle, in the form of aDynamixelCommandStateMessage.MessagesDynamixelCommandStateMessage:Encapsulates the a state and command of the dynamixel group. Used to communicate the last-known state of the motors, and last-known command sent to the motors. Serializes this schema to flexbuffers:{
...
"state": {                  # the present state of the group of motors:
5: {                    # motor with id 5
128: 2,             # has present velocity = 2
132: 204,           # has present position = 204
},
6: {                    # motor with id 6, etc.
128: 12,
132: 301,
}
}
"command": {                # the last-known command you sent
5: {104: 4},            # motor with id 5 should get goal velocity = 4
6: {104: 5}             # motor with id 6 should get goal velocity = 5
}
"t0": 170002032.2122312,    # time just before communication with motor
"t1": 170002032.2283432,    # time just after communication with motor
}For more 'distributed' operation:The second of these is DynamixelGroupNode. This node inherits RunnableNode; it is designed to be started and stopped. When instantiated, this node must be given an instance of a DynamixelGroupController. When started, it runs a ReadWriteLoopFunction on that instance inside its run_readwrite_loop method, using the last known GroupCommandMessage it has received, and then emits a GroupStateMessage.We also provided DynamixelRemoteController. This is an abstract base class that requires implementation of the 'readwrite_loop_function' virtual method. Here is where your custom control logic would go. The benefit of this approach is that the DynamixelGroupNode can run in its own thread, and keep up with the motors. This node, then, can be run from anywhere, and using transport classes, the controller can even run on a totally separate computer.We also provide DynamixelRemoteFrequencyController, which is exactly the same, but is driven at some frequency from a thread via inheritance from FrequencyGenerator.TroubleshootingYou might benefit from the Robotis Dynamixel Wizard program - just google for it.If you can't access /dev/ttyUSB0, try this:sudo usermod -a -G dialout $USER
sudo reboot