WWW-POSIM v0.6.16Simulator documentation
Documentation menu
WWW-POSIM / Simulator documentation

Demo worlds

In the installed app, open Workspace → Demo worlds and select a vehicle. This catalogue groups runnable worlds by terrain, vehicle, sensors and operating conditions. Additional worlds can use the same sections. These personal workspace presets are separate from the shared Explore the live demo.

World Scene view
WAM-V · Hong Kong WAM-V · Hong Kong
BlueROV2 · KMOU BlueROV2 · KMOU

Native Gazebo scene previews. WAM-V is shown at the surface; the BlueROV2 overview shows the three-wreck terrain from an external scene camera.

WAM-V · Hong Kong

WAM-V is a twin-hull surface vehicle controlled by ArduRover. The world uses prepared Hong Kong harbour terrain: a 2 × 2 km centre and 6 × 6 km surroundings with elevation/depth data and aerial imagery. It starts at the surface (depth 0 m). A coral buoy is 16 m ahead and 5 m left; a lime buoy is 30 m ahead and 8 m right. Use them for camera, ranging and navigation practice.

Forward RGB camera: visible scene images. 360° lidar: surrounding obstacle ranges. IMU: angular velocity and acceleration for attitude estimation. GNSS: simulated geographic fixes for navigation, subject to antenna immersion and freshness checks.

BlueROV2 · KMOU

Select Demo worlds → BlueROV2 to start underwater at KMOU waterfront. The selected terrain bundle determines the inspection scene:

Check the Mission depth limits before planning a deeper inspection.

A dynamic physical support used only by this demo holds the vehicle while the selected cameras deliver their first frames and the IMU/DVL estimator initializes at rest. The initial latitude, longitude and altitude are a scenario-defined prior, not a GNSS measurement. Heading comes from the measured magnetometer signal with the scenario's magnetic-declination calibration. The estimator does not receive continuous simulator ground-truth positions.

After stationary initialization and normal pre-arm checks pass, the demo arms in ALT_HOLD. Support release requires the flight controller (FCU) to accept navigation source set 2 and confirm armed depth hold. The demo confirms actual joint detachment before reporting release complete.

The map places an estimated-position marker only after FCU acceptance and navigation freshness checks. It shows at most two status banners: GPS state and Estimated position / Estimate unavailable, without numeric coordinates. Support, anchor and initialization information is under the collapsed Navigation details section outside the map. When GNSS is lost underwater, GPS lost remains visible even with an available estimated position. This is local IMU/DVL position estimation; visual SLAM mapping is not started. See GNSS & navigation.

If initialization fails or the estimator loses tracking, including loss caused by stale sensor input, restart the demo. The session does not automatically reuse the starting coordinate to re-anchor. Stale or unaccepted estimates are unavailable for navigation.

The vehicle includes forward and downward RGB cameras and DVL. Multibeam sonar is selected when the runtime has a qualified sonar provider. Use Front lights in the joystick controls to turn the two forward lights on or off; the control shows their confirmed state.

On first use, the installed app downloads the pinned KMOU terrain and checks its SHA-256 hash. A valid cached bundle is reused. The demo starts only when terrain preparation is ready. A failed download, checksum mismatch or unavailable release asset leaves preparation failed. Restore the connection or wait until the required asset is available, then select the demo again.

The seabed uses generated colour materials with broad regional mixing and dark green areas around the three wrecks. See the Generate a seabed material atlas. Colour does not change geometry or prove sonar performance. The shallow alternative’s heightmap comes from MIT-licensed Orca5; retain the supplied reference notices. For shipwreck terrain/model sources and usage conditions, see the selected bundle’s attribution notice.

BlueROV2 is an underwater ROV using ArduSub. Forward/downward cameras observe targets and seabed texture. DVL supplies bottom-relative velocity when its simulated measurement is valid. IMU supports attitude estimation; GNSS is usable at the surface and can lose its fix underwater. Qualified multibeam sonar provides an acoustic image of underwater geometry; video frame rate is not a guarantee of independent physical sonar samples. Depth is derived from the simulation state relative to the water reference. See Sensor models & parameters, Physics-based sonar preview, and GNSS & navigation.

Scene and sensor views

The RGB and sonar examples come from fixed sensors in the same three-wreck scene. The sonar uses 256 beams and a 0.2–15 m range. Echo levels are displayed directly in dB over a 60 dB window; black marks no return or space outside the fan. This example uses CPU sonar processing. Installed-app operation, vehicle control and target-identification accuracy require separate validation.

The overall preview has underwater effects disabled. The RGB example uses underwater haze, absorption, seabed caustics and suspended particles, with depth-dependent sunlight fading disabled for clearer visibility.

The BlueROV2 KMOU demo starts with suspended particles on and depth-dependent sunlight fading off. Saved settings in the installed app take precedence over these demo defaults.

Fixed RGB camera

Fixed RGB camera

Multibeam sonar

Multibeam sonar

Search documentation