Skip to content

Use with AI

Use with AI

ROS 2 fixture and simulator setup ​

Choose the profile that matches your source. The S5 fixture and G2 simulator have separate identities and model mappings. These setup commands belong to the read adapter. Use the separate offline preparation for local MoveIt/Gazebo modes.

Local fixture quickstart ​

The verified environment is Ubuntu 24.04 amd64, either native or under WSL 2, with ROS 2 Jazzy from the signed 2026-09-11 snapshot and Python 3.12. RViz needs a graphical server; the checked G2 Windows launcher uses authenticated VcXsrv. The repository contains the pinned environment setup and observed package versions.

From the ROS integration repository, install the pinned development environment:

sh
bash env/setup-ubuntu-24.04.sh

From the multi-repository workspace root, build the Python SDK wheel and the ROS overlay:

sh
python3 -m venv /tmp/plexa-sdk-build
/tmp/plexa-sdk-build/bin/python -m pip install build==1.3.0
cd sdks/python
/tmp/plexa-sdk-build/bin/python -m build --wheel
cd ../..

python3 -m venv --system-site-packages "$HOME/.local/share/plexa/ros-venv"
"$HOME/.local/share/plexa/ros-venv/bin/python" -m pip install -r integrations/ros/env/requirements.lock
"$HOME/.local/share/plexa/ros-venv/bin/python" -m pip install --no-deps sdks/python/dist/plexa_runtime_read-0.2.0-py3-none-any.whl

source /opt/ros/jazzy/setup.bash
cd integrations/ros
"$HOME/.local/share/plexa/ros-venv/bin/python" -m colcon build --packages-select plexa_ros_read
cd ../..

Start the deterministic HORST fixture in one terminal:

sh
cd testkit
npm run start -- --profile horst600s5 --scenario continuous

Launch the adapter from the workspace root in a second terminal:

sh
source /opt/ros/jazzy/setup.bash
source integrations/ros/install/setup.bash
ros2 launch plexa_ros_read horst600s5.launch.py \
  model_dir:="$(pwd)/models/robots/horst600s5"

Inspect the result from a third ROS-sourced terminal:

sh
ros2 topic echo /joint_states --once
ros2 topic echo /tf --once
ros2 topic echo /diagnostics --once

The RViz fixed frame is base_link. The displayed collision shapes are intentionally coarse, and link_6 is not a calibrated TCP.

Local simulator pilot ​

For an already active HorstOS Neo simulator advertising HORST with model ID horst-600-g2-pt1, the WSL 2 NAT setup can relay Windows port 9040 to WSL loopback port 19042 with bash integrations/ros/env/forward-windows-runtime.sh. From the workspace root, launch the separate G2 profile:

sh
source /opt/ros/jazzy/setup.bash
source integrations/ros/install/setup.bash
ros2 launch plexa_ros_read horst600g2_sim.launch.py \
  model_dir:="$(pwd)/models/robots/horst600" endpoint:=127.0.0.1:19042

Use the same ROS_DOMAIN_ID in each terminal if other local ROS graphs are running. The G2 view displays the read simulator state with its matching visual model. Use the separate offline preparation for local planning and Gazebo.

Visual assets, rendering and model limits

The G2 display uses seven link-local COLLADA meshes derived from the Model repository's GLB. The checked Visual-URDF preserves the canonical joints, limits and collision bodies. Source colors, materials and six normal-map images are retained; RViz uses geometry normals and a Phong approximation of the source PBR shading. Normal maps are preserved as source metadata and are not applied by the RViz Jazzy material loader. This does not establish calibrated geometry or pixel-identical rendering. The model lacks validated collision, inertial, calibration and TCP data for a robot-specific MoveIt or Gazebo acceptance. Installing those tools and opening their example windows does not establish a PLEXA planning or simulation integration.

On Windows, with the simulator supervisor and Robot Runtime already active, the workspace launcher checks WSL, the overlay, SDK and simulator, then reuses or starts the existing authenticated VcXsrv installation and opens RViz:

powershell
pwsh -File integrations/ros/env/launch-horst-rviz.ps1

The default distribution is Ubuntu-24.04, display :1, ROS domain 74. -CheckOnly checks prerequisites; the component README describes path overrides. The launcher verifies visual asset hashes and seven link mappings before RViz loads the description. Missing prerequisites are reported directly. It requires the model's LFS assets and the existing Xauthority file. Keep the terminal open while viewing. It does not send simulator or robot commands.