📖
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. General Usage

Basic Operating Guidelines and Hints

PreviousGeneral Hints and TipsNextSetting Speed of Sound

Last updated 2 months ago

The Tracker 650 is optimized for use on an ROV. When using in other scenarios also consider the guidelines below in light of your own scenarios.

The Tracker 650 should be operated so it is as close to level as possible when moving. Most ROVs have a flight controller that holds it level during flight. If you fly your ROV in a tilted orientation, then you should adjust the DVL orientation to be level at the normal flight attitude of the ROV.

The ROV should be ballasted so it floats exactly level when it is disarmed.

The Tracker 650 reports a "roll" and "pitch" estimate in the $DVPDX message. Not to be confused with actual roll and pitch, these are based strictly on the range estimated of each beam, and thus will be noisy. The intent of the roll and pitch estimates are for use when the DVL is mounted in a non-standard way (e.g., pointing forward) to help you line up your vehicle with non-seabed items like ship hulls or seawalls. So 0,0 roll and pitch means the DVL sensor is reasonably parallel to some surface which may be at an arbitrary orientation.

We supply a user interface for the Tracker 650 called CeruleanTracker, now deprecated in favor of our SonarView application or the . It does not need to be running for the Tracker 650 to work. You can use it to set options or to send initial positions to the ROV (see below). Sending positions is a deprecated function and we recommend our SonarView software for this.

The Tracker 650 is to do position hold and dead-reckoning navigation in conjunction with QGroundControl (QGC), ArduSub, and BlueOS using an interface called MAVLink ( is the interface to ArduSub). There are no plug-ins required to make the Tracker 650 work with newer versions of BlueOS. You should be aware of a few quirks:

  1. ArduSub is the part of the system that combines the Tracker 650 odometry with the ArduSub's inertial measurement unit (IMU) to provide position tracking. In order to get good position tracking you must make sure the ROV basic sensors are properly calibrated. The Tracker 650 does not require any calibration.

  2. You don't need a BlueOS extension to use the DVL. You do, however, need to .

  3. When ArduSub is powered up it "thinks" it is located at latitude 0, longitude 0, a point somewhere off the west coast of Africa. If you are using QGC, the map overlay is blank here.

  4. Before ArduSub will do position hold, it must be given a Global Origin. The Global Origin tells ArduSub where it is located in the world.

  5. The Tracker 650 can optionally send a Global Origin message of (0,0) to ArduSub while everyone is waking up. This location is that same spot off the coast of Africa. If you set the Tracker 650 to automatically send the Global Origin, then position hold will always work and you can do relative tracking of the ROV position in QGC. This does make it more difficult for novices to get the real-world ROV position to show correctly in QGC. The Tracker 650 is shipped with this feature turned off. Rule of thumb: if you only care about position hold, turn this option ON. If you want to see the true lat/lon position of the ROV on the QGC map, turn this option OFF and figure out how to get the the starting position of the ROV to ArduSub (CErulean's SonarView software may be able to help you with this). Note also if you have an Omnitrack setup, you should leave the auto origin checkbox OFF.

  6. ArduSub can only be told its Global Origin one time per power cycle. The Tracker 650 option to send a global origin defaults to off, because if you have a different way to set the true latitude/longitude position of the ROV, it won't work if the Tracker 650 gets there first with its (0,0) message.

  7. The Tracker 650 does accept a command called that can pass the Tracker 650 an initial position in DD, DDM, OR DMS format, and the Tracker 650 will pass this along to the ROV using a Global Origin message if the checkbox is OFF. So, if you are able to send commands to the DVL, you can leave the default Global Origin message turned off and send the true GPS position when you are ready. The same command can be used to update the position, although if the updated position is too far from the position the ROV has calculated, the Kalyan filter can go whacky.

  8. , the Tracker 650 user interface, can also help send the true position to the Tracker 650 to pass along to ArduSub. There is a facility on the DVL Command Window to do this. This capability of CeruleanTracker is deprecated in favor of Cerulean's SonarView software.

built-in configuration web page
designed to work with MAVLink and BlueOS
MAVLink
tell ArduSub that a DVL will be sending it messages
SET-POSITION
CeruleanTracker