HORST600 G2 offline preparation
The ROS component contains experimental local preparation for MoveIt 2 and Gazebo Harmonic. It uses the Model repository's detailed G2 visuals and a separate CAD-derived collision proposal. This is not hardware, production collision, calibrated planning, validated physics or a Runtime execution integration.
For a guided first run, follow MoveIt planning or Gazebo visualization. This page retains the full installation, configuration and verification details.
Windows start
From the workspace root, with WSL Ubuntu-24.04 and the built ROS overlay:
pwsh -File integrations/ros/env/launch-horst-rviz.ps1 -Mode MoveIt
pwsh -File integrations/ros/env/launch-horst-rviz.ps1 -Mode GazeboEach command keeps running in its terminal. The launcher verifies packages, reviewed model hashes, the overlay and OpenGL. It reuses or starts the existing authenticated VcXsrv on display :1. Offline modes need no Runtime endpoint or simulator supervisor. -CheckOnly checks readiness without launching the view. -Distribution, -VcXsrvPath and -XAuthority override the existing paths.
MoveIt uses ROS domain 78; Gazebo uses domain 79 and Gazebo partition plexa_horst600_g2_offline. Keep these domains separate from the live read-only view (default domain 74). Start only one instance of each offline mode.
MoveIt accepts -Pose zero, -Pose bent_a or -Pose bent_b for synthetic initial joint values. -Pose applies only to MoveIt. None of these values are sent to Robot Runtime. The default launcher mode remains the live read-only view.
Installation and model ownership
env/install-robotics-tools-ubuntu-24.04.sh pins MoveIt 2.12.4, ros_gz 1.0.24 and joint_state_publisher 2.4.3 against the signed Jazzy 2026-09-11 snapshot. env/robotics-tools.lock records observed versions, including Gazebo Sim 8.15.0. Use the persistent Python/SDK environment and overlay build from the main guide; temporary interpreters must not be baked into installed ROS executables.
Shared DAE/STL, planning URDF and SDF assets stay in models/robots/horst600/. Their LFS content must be materialized. The ROS loader checks the reviewed provenance, all derivative hashes and canonical joint consistency before loading. models/verification/OFFLINE-PREVIEW.md describes regeneration and validation. Model derivatives remain internal and require license review before redistribution.
MoveIt: plan and inspect
The offline launch starts robot_state_publisher, a synthetic joint_state_publisher, move_group and RViz. The arm group runs KDL and OMPL RRTConnect with CAD collision envelopes on all seven links. Only the six adjacent link pairs are exempted from self-collision. link_6 is a chain endpoint, not a calibrated TCP.
In the RViz Planning panel, select arm, start <current> and goal turned, then click Plan. Inspect the displayed trajectory. Execution is disabled by allow_trajectory_execution: false and no controllers are configured. The standard ExecuteTrajectory action remains available because RViz waits for it during initialization. Its disabled-execution guard aborts requests with CONTROL_FAILED; it does not provide a controller or Runtime path. There is no SDK client in this launch.
Planner timing uses provisional caps of 0.5 rad/s and 0.5 rad/s². These do not replace the robot's canonical limits or establish valid physical trajectory timing. The scene currently contains the robot only; there is no verified tool or cell.
After sourcing Jazzy and the overlay, run the independent service check from the workspace root:
ROS_DOMAIN_ID=78 "$HOME/.local/share/plexa/ros-venv/bin/python" \
integrations/ros/env/check-g2-planning.py --report integrations/ros/log/offline-acceptance.jsonIt checks zero and two bent poses, rejects a fixed self-colliding counterexample, plans zero to J1=15° and checks each returned sample through GetStateValidity. It publishes only a display trajectory, never an execution request.
The separate guard probe first checks that execution is explicitly disabled and then sends an empty local trajectory, with no joints, points or controllers:
ROS_DOMAIN_ID=78 "$HOME/.local/share/plexa/ros-venv/bin/python" \
integrations/ros/env/check-g2-execution-guard.py --report integrations/ros/log/execution-guard.jsonExpected result: ABORTED (status 6), CONTROL_FAILED (-4). No robot or simulator movement is requested. This test is limited to the isolated offline domain.
Gazebo: visual and status preparation
The launcher explicitly selects an SDF with unvalidated physics placeholders. It spawns horst600_g2_offline into the installed empty world with a fixed base, seven visual links and six revolute axes. Select this model in the Entity Tree to expose six local joint-position controls, in radians. These controls address only the isolated Gazebo model. Gravity and self-collision are disabled.
Masses, bounding-box inertias, centers of mass, effort and damping are provisional. Values and derivation are recorded in models/robots/horst600/gazebo-preview-parameters.json and the Model verification guide. Exact values can be reviewed and incorporated later; the current preparation is not usable as a physics reference.
The bridge runs Gazebo → ROS only:
ROS_DOMAIN_ID=79 ros2 topic echo /gazebo_preview/joint_states --once
ROS_DOMAIN_ID=79 ros2 topic echo /clock --onceGazebo publishes exactly joint_1…joint_6, radians, and simulation time. The ROS bridge exposes no command topic, Runtime client, actuator or hardware interface.
WSL and troubleshooting
With authenticated VcXsrv already running, use the shell entry point:
PLEXA_OFFLINE_MODE=MoveIt ROS_DOMAIN_ID=78 bash integrations/ros/env/launch-g2-offline.sh
PLEXA_OFFLINE_MODE=Gazebo ROS_DOMAIN_ID=79 bash integrations/ros/env/launch-g2-offline.shKeep the terminal open. Use Ctrl+C to stop the owned processes. Avoid saving an RViz configuration when merely inspecting a trajectory; an unsaved-configuration dialog can delay shutdown. MoveIt 2.12.4 produced a CallbackGroup-destructor segmentation fault during one shutdown in this WSL environment. Planning and the service checks succeeded; clean MoveIt shutdown is an unresolved tool issue. The launch supervisor eventually stopped its RViz process. Gazebo bounded runs cleaned up their own simulator and bridge processes.
Historical comparison: ExecuteTrajectory and WSL shutdown
Removing the ExecuteTrajectory capability caused a 30-second RViz startup wait, marker-update backlog and a crash in InteractiveMarkerClient::pushUpdates on this installation. The final configuration retains the action with execution disabled; the empty-trajectory guard probe verifies the refusal. The debugger was GDB 15.1-1ubuntu1~24.04.1; debug logs remain unversioned.
Expected preparation warnings include absent perception/octomap plugins and no controller_names. They reflect the configured scope. A model-hash mismatch requires regenerating, checking and reviewing derivatives, rather than bypassing validation.
Bounded headless shutdown diagnosis
The failure was reproduced without RViz on 14 October 2026 using the unchanged MoveIt 2.12.4 / rclcpp 28.1.22 packages. Readiness succeeded, the actual allow_trajectory_execution parameter was false, and SIGINT was sent once to the owned launch supervisor. That supervisor returned 0 while move_group exited −11 in rclcpp::CallbackGroup::~CallbackGroup(). Both state publishers exited cleanly. A zero launch return code therefore does not establish a clean shutdown; an RViz save dialog is not required to reproduce this failure.
After sourcing Jazzy and the existing overlay, run:
ROS_DOMAIN_ID=78 python3 integrations/ros/env/check-g2-shutdown.py --report .tmp/new-moveit-shutdown.jsonThe checker uses a new owned headless launch, localhost discovery, bounded timeouts and a read-only parameter request. It preserves an existing domain 78 MoveIt process, writes only new ignored outputs, and returns failure when any child crashes, readiness/readback is absent or forced cleanup is needed. Use the child-process results in the report to assess shutdown; launch return code 0 alone is insufficient for this failure mode. Related upstream reports 3680 and 3721 describe shutdown or destruction faults; they do not prove an identical root cause here.
The source and manifest remain in the ROS extension repository.
Configuration references: MoveIt configuration, Gazebo joint controllers, ROS 2 interoperability.