Display state in RViz
Read the G2 simulator; check identity, six joints, TF and freshness.
Open the RViz tutorialThe read adapter exposes joint state to standard ROS 2 tools. The separate command adapter forwards all 48 Runtime RPCs and provides a FollowJointTrajectory action for explicit fixture/simulator proposals. Choose Runtime reads, local MoveIt planning, Gazebo preview or explicit Runtime proposals. Runtime modes use separate profiles for the HORST600 S5 test fixture and the HORST600 G2 HorstOS Neo simulator.
Read the G2 simulator; check identity, six joints, TF and freshness.
Open the RViz tutorial →Inspect three local poses and a collision counterexample; execution remains disabled.
Open the MoveIt tutorial →Inspect seven visual links, six joint states and simulation time with explicit physics placeholders.
Open the Gazebo tutorial →Use the command adapter for all 48 RPCs and FollowJointTrajectory with an explicit fixture/simulator source.
Open the command guide →
Use the fixture quickstart for an S5 testkit setup, or offline preparation for exact package pins, shared asset checks and full configuration limits. Keep Runtime reads and isolated offline synthetic state in separate ROS domains.
The adapter calls RobotStatusService.ListRobots and RobotStatusService.StreamCurrentRobotJoints. It accepts only a loopback endpoint. The S5 fixture and G2 simulator use separate profiles with checked identity, six-axis layout, model mapping and URDF before publication. No Runtime write API is exposed.
| Output | Meaning |
|---|---|
/joint_states | joint_1 through joint_6, positions in radians, with empty velocity and effort arrays |
/diagnostics | Stream health, data age, identity and sample validation failures |
/tf | base_link through link_6, calculated by robot_state_publisher from the reference URDF |
| RViz | S5 schematic collision geometry; G2 detailed source-derived visual meshes with optional collision and TF overlays |
Runtime joint values are logical J1...J6 values in degrees. The adapter maps them in order to URDF joint_1...joint_6, converts them to radians, and checks finite values and URDF limits before publication.
The Runtime payload has no measurement timestamp. ROS headers therefore use the ROS receipt time. A monotonic clock tracks freshness independently; the default stale threshold is 500 ms for the fixture's 100 ms sample interval. Stale or invalid samples are discarded, and the last state is never silently republished. High-rate intermediate samples are coalesced to the newest sample; /diagnostics counts the coalesced values.
Stream end, Runtime errors, malformed samples, and identity mismatches remain visible on /diagnostics. The pilot does not automatically reconnect after a terminal stream error. Publication may resume after a temporary delay when a new valid sample arrives.
The S5 fixture and G2 simulator setup contains the pinned Ubuntu/WSL environment, SDK/overlay builds and three-terminal sequence for a first read check.
The separate G2 simulator profile documents loopback forwarding, visual assets and the Windows RViz launcher. Use one ROS domain within a mode and separate domains for Runtime reads and synthetic offline planning.
Inspect synthetic G2 poses and local paths with MoveIt, or open the isolated Gazebo model with joint state and simulation time. Follow offline preparation for installation and launch. MoveIt execution remains disabled; Gazebo uses explicit physics placeholders.
The read adapter and offline simulator pilot do not prove interoperability with robot hardware. They provide no motion commands, ros2_control hardware interface, trajectory controller, realtime path, camera, I/O, gripper, calibrated visual model, or safety function. WSL testing is not a realtime or safety test.
The detailed G2 derivatives remain in the Model repository for internal use; this guide distributes no meshes or textures. External model-asset publication requires a separate license review. Explicit trajectory proposals use the new command adapter. Cyclic setpoints need their separately admitted streaming architecture; the southbound realtime contract is not an integration bypass.
The source, manifest, pinned environment, and tests are maintained in the PLEXA ROS extension repository.
Choose a canonical model ID for synthetic JointState/TF views. The catalog mode remains separate from Runtime reads and commands.
The additional catalog_offline.launch.py mode loads an exact source-checked model and publishes synthetic reference positions. It supports arbitrary articulated joint trees, multiple arms, fixed toolframes and mixed radians/meters; it opens no Runtime connection. The existing read and command modes retain their separately validated identities and bindings.
After rebuilding the SDK wheel and ROS overlay, start from the workspace root:
ROS_DOMAIN_ID=117 ros2 launch plexa_ros_read catalog_offline.launch.py models_root:="$PWD/models" model:=horst-1000-g2-s1 pose:=0Use model:=horst-1500-s1, model:=franka-panda, model:=unitree-g1 or another canonical catalog ID to select a different model. A portable Models visual-v1 export can be supplied through visual_urdf:=/absolute/path/to/model.urdf for RViz geometry; its source and output hashes are checked before loading. Without that export, the canonical source preserves kinematics and available primitives.
python -m plexa_ros_read.catalog --models-root models --model franka-panda --pose 1 prints the complete synthetic JointState/TF input packet. Panda fingers use meters, and its arm uses radians. The full mixed-unit model is not enabled in the existing degree-based Runtime command mapper. The AMR showroom visual has no joint-state mode. The available HORST1500 S1 source retains an unconfirmed G2 product mapping.
For an estimated collision/physics export, python -m plexa_ros_read.catalog_planning prepares group-complete SRDF and URDF files. Its --allow-estimated flag is required; --gazebo additionally invokes the installed native sdformat converter to produce a fixed-base, zero-gravity world with self-collision disabled. No collision pairs are automatically excluded from the MoveIt profile.
python -m plexa_ros_read.catalog_planning --models-root models --model horst-1500-s1 --profile-directory models/.generated/library/estimated-offline-v1/horst-1500-s1 --output .tmp/horst1500-planning --allow-estimated --gazebo
ROS_DOMAIN_ID=119 ros2 launch plexa_ros_read catalog_moveit_offline.launch.py models_root:="$PWD/models" model:=horst-1500-s1 profile_directory:="$PWD/models/.generated/library/estimated-offline-v1/horst-1500-s1" allow_estimated:=trueThese profiles provide offline scene preparation and joint-space groups. A native scene import is recorded separately from successful planning and clean shutdown; the existing native MoveIt shutdown failure remains an open dependency until a fresh lifecycle test passes. Trajectory execution remains disabled.