How woolfrey/server_serial_link works
Project type and purpose
• This is a ROS2 package (“serial_link_action_server”) that implements a set of action servers to control serial-link robot arms in real time.
• It builds on an external “interface_serial_link” message definitions package and uses “RobotLibrary” for kinematics, dynamics, and control algorithms.
File structure
• Top-level artifacts:
• CMakeLists.txt / package.xml → ROS2 build and package configuration
• /serial_link_action_server → templated headers for the ActionServerBase and derived control classes
• src/ → implementation .cpp files and nodes/ subfolder containing ROS2 node entrypoints
• README.md → project description, usage, architecture overview
• Key patterns:
• A base class (ActionServerBase) with several derived servers (FollowTransform, FollowTwist, TrackCartesianTrajectory, TrackJointTrajectory)
• A ModelUpdater node that updates the RobotLibrary::Model::KinematicTree from joint states
• Nodes launch executables that combine these classes into running ROS2 action servers
README for additional insights
• The “Classes” section provides a logical overview:
• KinematicTree ← sensor_msgs::JointState
• ModelUpdater → updates the model
• SerialLinkBase ← uses model to control an arm branch
• ActionServerBase<TGoal> ← templated glue with feedback, goal handling
• Derived classes implement specific control loops
• The “Nodes” section explains how each executable wires up:
• Arguments: URDF path, endpoint link, joint command topic, joint state topic, plus YAML parameters
Detail
• ModelUpdater as a distinct component
• Parameters flowing from YAML into SerialLinkBase
• External action clients or transform/twist publishers as separate actors if relevant