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

Autopilot missions

Plan a short route, check readiness, then run or stop the mission.

Run a short waypoint route

  1. Open Ground-control map and click to add waypoints. Right-click to delete; edit coordinates in the list.
  2. Select Check route at the top of the map panel and review waterways and detours.
  3. Select Run route beside it to arm and depart. Both buttons stay above the waypoint list.
  4. Use Stop to hold, Continue to resume and Abort to cancel and disarm.
  5. Return to the start and end the session.

Choose station keeping, inspection, survey or an underwater dive under ArduPilot → Preset scenario missions. Map waypoints take priority when present; clear them to use the preset. Map dragging and pinch zoom leave waypoints unchanged.

Arming and mission start check motion initialization, fresh navigation telemetry and the flight controller's pre-arm status. A streaming camera alone does not establish mission readiness. Read the reported blocker before retrying; changing the physics step does not clear other readiness checks. Navigation must remain ready continuously for two seconds before its settling check completes.

Route checks evaluate terrain and the space around the hull. Moving-vessel avoidance and full COLREG rules are unsupported. Begin underwater testing with a short dive, transit, return and surface mission.

Preset missions

The ArduPilot mission selector offers:

Pattern size is 1–25 m. Surface vehicles stay on the surface. Check route validates the route against terrain, then the same button becomes Arm & run mission. Changing a mission setting restores Check route. The route is validated again when starting. You can manually set mission waypoints and per-point depths in the Ground control panel; its waypoints take priority over presets. Clear those waypoints to select a preset again.

Autopilot parameters

  1. Stop the mission and disarm.
  2. Read values from the autopilot controller (FCU) in ArduPilot parameters.
  3. Search and edit values, or upload a parameter file.
  4. Apply changes and read values back from the FCU.

Use parameters for the selected robot and firmware. Protected values have restrictions. Configure mass, inertia, collision and propulsion in the Custom Vehicle.

Exported files omit known read-only flight statistics, barometer IDs and automatically calibrated ground pressures. The preview skips these values when an imported file contains them, including the statistics reset command.

Generated BlueROV2 worlds use depth acceleration feedback gains PSC_ACCZ_P=0.5, PSC_ACCZ_I=0.1 and PSC_ACCZ_FF=0. This profile matches the simulated wave-aware hull. It is not a tuning recommendation for a physical vehicle.

At an underwater waypoint, the robot reaches the target before holding position. If it drifts outside the hold limits, the timer resets and the robot returns to the target.

In personal WAM-V missions using the default controller without an explicit heading, a positive hold timer counts only while the navigation estimate remains within 0.75 m of the original target, fresh estimated horizontal speed is at most 0.2 m/s, and absolute body-z angular rate is at most 1°/s. A received motion violation or loss of qualifying measurements restarts the timer. These are estimator conditions; waves and GNSS noise affect physical motion and settling time. A waypoint with zero hold time remains a transit point.

QGroundControl

For an Autopilot vehicle, select Open QGC in the ArduPilot panel. Keep the installed app and signed-in workspace open. The connection dialog prepares the vehicle and hands control to QGroundControl. See Control with QGC for installation, connection and release of control.

Mission depth limits

Underwater mission inputs start at 2 m, with a standard planning range of 0–10 m. Only a built-in BlueROV2 KMOU session with a verified shipwreck planning profile can receive a wider server-computed limit. The built-in BlueROV2 KMOU demo starts underwater. See Demo worlds for its initial position and preparation.

The displayed limit is a simulation planning bound derived from the current authored core and navigation grid. It is not a vehicle pressure rating or proof of control performance. Every route retains 1 m terrain clearance and a 2.5 m planning footprint radius; segments deeper than 10 m must keep that entire footprint inside the authored core. The server rechecks session, model, engine and scene identity. Failed identity checks or missing information restore the standard limit and require a new route check.

Travel shallow before descending at an observation point, then ascend before returning. A deeper limit does not permit a vertical descent at every location. Review the route and readiness checks before starting.

Search documentation