MAGPIE Control ROS2 interface

Project notes

Build the interface and its messages together

The selected package metadata identifies version 2024.9 and Python 3.10 or later, with dependencies including Dynamixel SDK, ur_rtde and sensor/scientific packages. The README instructs users to build magpie_msgs and magpie_control together, then source the workspace-wide setup; a source import or one package's local setup is not equivalent to a complete ROS workspace. No dependency or workspace was installed. [1] [2]

The node selects auto_detect_port, port and use_eflesh; an explicit port takes effect only with auto_detect_port=false. The finger1theta_* and finger2theta_* calibration parameters are degree values, alongside moving-speed/torque settings. The inspected initializer raises on gripper initialization failure rather than treating that failure as a ready device. Match those values and the underlying gripper implementation to the actual unit; no serial port or sensor was accessed here. [3]

Separate interface units from calibrated contact force

The README describes aperture in millimeters and force-related services/state in newtons. The underlying gripper source converts between Dynamixel load values and force and contains model/calibration assumptions. A returned field or successful service callback is not an independently calibrated physical force or a completed grasp. The ROS set_force callback instead scales max_force by 10 and clamps it to 0–1023, leaving geometry-based conversion unfinished rather than using the underlying Gripper.set_force conversion. The newton-labelled interface therefore does not establish a calibrated physical limit. In the sampled state publisher, is_moving and contact_detected are hardcoded false, not measured motion/contact. A conditional DeliGrasp fallback reports success and copies requested initial force into final_force; the excerpt does not establish whether that fallback is reached with this Gripper implementation. Inspect these paths before relying on service/action results. No force, slip, contact, accuracy or action result was tested. [1] [3] [4]

The metadata contains an MIT license classifier, but a full root grant was not identified in the inspected tree. The source-available interface, external messages/dependencies and purchased sensors/servos retain separate rights questions; no blanket redistribution clearance is claimed. [2] [5]