📖
Cerulean Sonar Docs
Docs DirectoryStore
Tracker 650
Tracker 650
  • Overview
    • CERULEANTRACKER DEPRECATION NOTICE
  • Quick Start for BlueROV / ArduSub Users
  • General Specifications
  • Configuring the Tracker 650
    • Finding the Configuration Web Page
    • Example Configuration Web Page
    • Live Status Page
    • Setting the Static IP Address
    • Setting the Fallback IP Address
    • Setting the Host IP Address
    • Setting the MAVLink REST Server Parameters
    • Setting Pool Mode
    • Setting DVL Mounting Rotation Offsets
      • Scenario: Driving Your Own Kalman Filter
        • Forward-Facing Mount
    • Setting Velocity Adjustment
  • General Usage
    • General Hints and Tips
    • Basic Operating Guidelines and Hints
    • Setting Speed of Sound
    • Scenario: Doing Your Own Dead Reckoning
    • Scenario: Holding Position
  • Using MAVLink and BlueOS for Position Hold on a BlueROV2
    • ArduPilot Parameters
    • Tracker 650 Setup for MAVLink Support
    • Global Origin
  • Mounting the Tracker 650
    • Bottom Mount
    • Thruster Deck Mount
      • Send xxx Message
  • Mounting Drawings (V1 pre-2025)
  • Communicating with the Tracker 650
    • Factory Defaults and Default Messages
    • The Ethernet Interface
    • Tips on How to Find the IP Address Assigned to Your Ethernet Adapter
    • Outgoing Message Formats, Tracker 650 to Host
      • $DVPDL and $DVPDX: DVL Position and Angle Deltas Messages
      • $DVNVM Non-Volatile Memory and Configuration
      • Freeform Error and Informational messages ($DVTXT)
      • $DVKFC Kalman Filter Raw Data Support Message
    • Commands Accepted by the Tracker 650
      • CONFIGURATION
      • SET-VELOCITY-ADJUSTMENT
        • SET-SPEED-OF-SOUND
      • SEND-DVPDL
      • SEND-DVPDX
      • SEND-DVKFC
      • SEND-MAVLINK-DISTANCE
      • MAVLINK-ORIGIN
      • SET-POSITION
      • SET-SENSOR-ORIENTATION
      • IP-ADDRESS
      • HOST-ADDRESS
      • MAVLINK-ADDRESS
      • FALLBACK-ADDRESS
      • UNICAST-TO-ME
      • PAUSE
      • RESUME
      • REBOOT
      • SET-POOL-MODE
    • Blue Robotics Discovery Protocol (Ethernet Only)
    • ARP (Address Resolution Protocol)
    • DHCP (Dynamic Host Configuration Protocol)
    • Ping (Internet Control Message Protocol Ping)
  • Coordinate Systems
  • Mounting Drawings (V2 post-2024)
  • CAD Models
  • Electrical Drawings
    • Power and Ethernet Cabling
  • Expectations
  • Copyright
Powered by GitBook
On this page
  1. Using MAVLink and BlueOS for Position Hold on a BlueROV2

Global Origin

PreviousTracker 650 Setup for MAVLink SupportNextMounting the Tracker 650

Last updated 3 months ago

ArduSub is able to accept inputs from several sensors, and it can use these inputs to do dead reckoning navigation.

The Cerulean Tracker 650 is able to provide ArduSub with delta distance messages via mavlink2rest. ArduSub can then do dead reckoning based in the delta distance from the DVL and ROV orientation from other sensors it is monitoring.

In order for ArduSub to do dead reckoning, it needs to be set up as described earlier. It also needs to receive a global origin, which essentially tells ArduSub where to start from. ArduSub accepts one and only one global origin per session (a session is the time period during which the ROV is powered). You can give ArduSub a global origin in several ways:

  • The DVL can automatically send a global origin of (0,0) each time it connects to the MAVlink REST server. This allows relative positioning not corresponding to the actual latitude and longitude and thereafter ArduSub will attempt to update this position using dead reckoning.. You can . Once the origin is set, it is fixed until you cycle power on the ROV.

  • You can manually send a position through the DVL using the command. You can give ArduSub your actual GPS position and thereafter ArduSub will attempt to update this position using dead reckoning. You can only do this once, as once the origin is set, it is fixed until you cycle power on the ROV. If you have enabled automatic origin as described above, SET-POSITION will be too late and have no effect.

  • You can send ArduSub a global origin using your own MAVlink interface (such as Cerulean's SonarView software or the deprecated capability in CeruleanTracker) and not involve the DVL. Once you have set the global origin, ArduSub will attempt to update this position using dead reckoning with the position delta information supplied by the DVL.

ArduSub is very complicated and does some unintuitive things. If you send NMEA-formatted GPS position information to ArduSub, it will disable the ability thereafter to use position hold and dead reckoning based on DVL inputs. NMEA data could come from a GPS on the same network, or it might come from CeruleanTracker if you fail to turn off NMEA outputs as described .

When the DVL is out of range of a target surface and/or is not accurately calculating velocity and delta distance, ArduSub stops updating the dead reckoning solution.

enable this feature like this
SET-POSITION
here