DEVELOPERS · ROS 2 EXPORT

TOOLCHAIN 0.1.1 · WORKING ALPHA

Generate static interoperability artifacts — not a running robot.

The active ROS 2 Synapse verifies a compiled OpenRGD bundle and generates deterministic configuration, limits and an explicit hardware-binding manifest.

IMPLEMENTATION BOUNDARY

ROS 2 static export is implemented and lifecycle-tested. It does not launch ros2_control, publish actuator commands, open device buses or grant physical execution authority. Isaac export is not implemented.

REQUIRED SEQUENCE

Verify, compile, export.

ROS 2 exportshell
rgd hash
rgd compile-spec
rgd export ros2 --out export/ros2

GENERATED ARTIFACTS

Every successful export explains what it produced.

01

ros2_control.yaml

Static controller / joint configuration.

02

rgd_limits.xacro

Deterministic exported joint limits and units.

03

export_manifest.json

Source root, bundle digest, robot identity, joint set and completeness status.

04

rgd_hardware.xacro

Generated only when every joint has complete explicit HAL interfaces and one system driver plugin.

EXPORT STATUS

Incomplete hardware evidence remains visible.

possible statusesshell
CONFIGURATION_ONLY
HARDWARE_BOUND

CONFIGURATION_ONLY is a successful static export with incomplete or intentionally withheld hardware bindings. It is not permission to execute.

IMPORTED BODY ISOLATION

Joint-name collisions cannot smuggle hardware mappings into an imported body.

binding ruleshell
source-derived joint topology + limits
              ↓
static configuration export

seed actuator / HAL bindings
              ✕ not inherited by name collision

UNAVAILABLE TARGET

Isaac export fails explicitly.

not implementedshell
rgd export isaac
# exits explicitly with code 2

The historical Isaac generator was a placeholder and is not advertised as an active target.

RELATED GUIDES

Continue through the verified toolchain.

CANONICAL SOURCE