đź“–
Cerulean Sonar Docs
Docs DirectoryStore
CeruleanTracker
CeruleanTracker
  • DEPRECATION NOTICE
  • Overview
    • Sensor Fusion
    • Input Devices
    • Output Messages
      • GPRMC message
      • GPDBT, GPHDT, GPGGA messages
      • Re-Broadcasting (“Re-Tweeting”) Topside GPS Messages
    • Typical Configuration
    • Operating CeruleanTracker
      • Input Device Status Panel
      • Status Detail Examples
      • Output Selection
      • Input Device Configuration Panels
        • Topside GPS Tab
        • ROVL Rx Tab
        • ROVL Command Window
        • ROVL Channels
        • DVL Tab
        • DVL Command Window
  • Installing Firmware
    • Finding Firmware Files
    • ROVL Firmware Files by Device Type
    • Updating Firmware in a Functioning Device
    • Installing Firmware in a Bricked Device
    • Putting ROVL Devices into Hardware Bootloader Mode
    • Putting DVL Devices into Hardware Bootloader Mode
  • Installing DVL Firmware (Deprecated)
  • Installing ROVL Firmware (Deprecated)
  • CeruleanMap
    • Overview
    • Setting Up QGroundControl
    • Copyright
Powered by GitBook
On this page
  1. Overview
  2. Operating CeruleanTracker

Output Selection

PreviousStatus Detail ExamplesNextInput Device Configuration Panels

Last updated 1 year ago

The Output tab the output configuration and status. You can choose to use the DVL dead reckoning position estimate (assuming a DVL is attached). You can choose to use the raw ROV Locator estimate (assuming an ROL Locator is attached. Or, you can choose a combined output, which does sensor fusion of the ROV Locator and DVL estimates, or if no DVL is attached, this option uses a filtered version of the ROV Locator estimate.

The figures below show a examples of the different outputs for a sortie in a challenging acoustic environment.

CeruleanTracker Filter Note

Sortie showing the filtered ROV Locator position estimate, DVL dead reckoning position estimate, and combined output position estimate. The operator was flying close to the surface, which can lead to ROV Locator noise due to multipath. Additionally, the operator was not careful getting the DVL’s GPS fix and the DVL started out with a substantial error. When we surfaced and took another GPS fix, the combined output was close to ground truth – approximately four meters, which is less than the expected GPS errors. This is the same input data as the previous figure.
Note that GPS systems require some time to acquire a fix and it takes more time to refine their estimate of location once a fix is acquired. The figure above shows the start of a sortie where the operator powered up and didn’t wait for the GPS systems to stabilize before taking off. The estimated position should eventually converge with the true position, although maybe not as quickly as happened in this sortie.