ROS troubleshooting
Check fresh data, middleware and QoS before changing a working setup.
If something does not work
No module named www_posim_ros: select the project's Python interpreter. For a website project, repeat the package-install command with that.venvPython.- No fresh telemetry: check that your world is running and the robot has appeared. A topic name alone does not mean data is arriving.
- Start your own workspace in ROS 2 direct-control mode: create a world with that control mode selected.
controller_busy: stop the other program controlling this world, then run your program again.- World or robot changed: stop the program and start it again to obtain the current connection profile.
- Installed ROS tools fail: check
~/.www-posim-ros/domain-76/client.loginside the prepared environment. Stop and reopen the ROS tools if needed.
DDS, camera QoS and WSLg troubleshooting
For a basic LiDAR/camera exercise, follow the challenge sensor tutorial. It saves a Matplotlib figure without opening a GUI window.
DDS is ROS 2's message transport. Fast DDS uses rmw_fastrtps_cpp; Cyclone DDS uses rmw_cyclonedds_cpp. Inspect the middleware in the prepared ROS shell:
python -c 'import rclpy; rclpy.init(); print(rclpy.utilities.get_rmw_implementation_identifier()); rclpy.shutdown()'
ros2 topic info /model/wamv/camera/compressed --verbose
The app-managed relay and programs in its prepared environment inherit the engine's middleware. Changing an environment variable in an already running shell does not change the relay process. Reliable subscriptions match the relay's Reliable camera and LiDAR publishers. Match the ROS domain, middleware and QoS when diagnosing large JPEG messages; a visible topic name alone does not prove delivery.
A Reliable publisher can also serve a Best Effort subscriber. A Best Effort publisher cannot serve a subscriber that requires Reliable delivery. Inspect the offered and requested QoS before changing it. For odometry, compare:
ros2 topic info /model/wamv/odometry --verbose
ros2 topic echo /model/wamv/odometry --once --qos-reliability best_effort
The website transports messages over WebSocket; its server and your local relay have separate DDS domains. See the ROS middleware guide for advanced configuration.
For a separately installed Ubuntu/WSL ROS environment, install the desired implementation and select it before starting both the connector and your sensor program:
sudo apt install ros-lyrical-rmw-cyclonedds-cpp
export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp
export ROS_DOMAIN_ID=76
export ROS_AUTOMATIC_DISCOVERY_RANGE=LOCALHOST
To use Fast DDS in that environment, install ros-lyrical-rmw-fastrtps-cpp and set RMW_IMPLEMENTATION=rmw_fastrtps_cpp instead. Stop your connector and ROS nodes before switching, run ros2 daemon stop, then restart them in terminals with the same settings. These manual commands apply to a separate ROS installation; use the app's prepared tools for the beginner exercise.
If RViz on WSLg fails with a Qt Wayland parent-window or xcb platform error, verify that WSLg and the GUI dependencies are available in the environment where RViz runs. Try X11 for that process:
QT_QPA_PLATFORM=xcb rviz2 -d session.rviz
Replace session.rviz with the connector's generated configuration path. Keep QT_QPA_PLATFORM scoped to the GUI command. The relay and headless Matplotlib script do not need it. Restarting RViz does not create a ROS connection; keep the matching connector running and check fresh message reception separately.