📖
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. Configuring the Tracker 650

Setting the MAVLink REST Server Parameters

PreviousSetting the Host IP AddressNextSetting Pool Mode

Last updated 2 months ago

In the default configuration, the Tracker 650 sends odometry information to the autopilot on a BlueROV via an interface on the BlueROV called the MAVLink Rest Server. There are several configuration parameters, all of which are set to reasonable parameters at the factory. Most users can leave these at the default settings. See also .

The MAVLink Server Address and Port parameters set the IP address of the MAVLink server, which on a BlueROV is the IP address of the BlueROV itself. By default it is 192.168.2.2:6040. If you have changed the BlueROV address you need to re-enter it here. The port number is virtually always 6040.

The MAVLink System ID identifies the Tracker 650 itself and is used by the MAVLink server to sort out who is talking to it. You only need to change this if you have a complicated network with other similar systems talking to the MAVLink server, and there is a collision with the system ID used by another device.

The MAVLink Vehicle ID identifies the autopilot associated with the BlueROV you are trying to control. You should know if you changed the ID on the BlueROV and what you set it to. One situation where you might have to change your BlueROV vehicle ID is if you have other BlueBoats and/or BlueROVs on the same subnet.

The checkbox to send the global origin is tricky. If you have a small basic system with just a BlueROV and Tracker 650, checking this box will cause a global origin of (0,0) to be send when everyone powers up. This will enable the BlueROV to use the Tracker 650 for position hold and dead reckoning. The downside is, the BlueROV thinks it is located off the west coast of Africa and the map on QGroundControl won't be correct. But, this does get position hold working for a basic user.

If you know how to set a global origin by other means (e.g., CeruleanTracker, SonarView, an Omnitrack system), you definitely do NOT want this box checked. For arcane reasons, the autopilot accepts only one global origin per power cycle, so once set to (0,0) you are stuck with it until you reboot the ROV.

this discussion