đź“–
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

Last updated 2 years ago

When QGroundControl starts, it grabs up all the COM ports on the computer and hangs onto them. Windows and Linux only allow one application at a time to own a COM port, so once QGroundControl has the ports, CeruleanTracker can’t get at the ROV Locator Receiver or the GPS. Follow these instructions to tell QGroundControl to leave the COM ports alone. This will not have any effect on the way a BlueROV2 operates.

Requirements:

  • QGroundControl >= 3.5.2

  • BlueROV2 with a recent version of Companion

Open the Q menu of QGroundControl, and find the section about 1/3 of the way down that looks like the picture below. Change the settings so they look like the following picture:

Note: Each time you upgrade QGroundControl you may have to repeat this process.

  1. CeruleanMap

Setting Up QGroundControl

PreviousOverviewNextCopyright
Q Part of the Q menu of QGroundControl