📖
Cerulean Sonar Docs
Docs DirectoryStore
SonarView
SonarView
  • Overview
  • Installation
    • Linux
    • macOS
    • Windows
    • BlueOS
    • Docker
  • App Bar Controls
  • Device Discovery and IP Addressing
  • Application Settings
  • Replaying Saved Sonar Files
  • Session Configurations
    • Multiple Omniscans
    • Surveyor + NMEA Heading/Position
    • Omniscan + MAVLink2Rest Position
    • Omniscan + NMEA Heading/Position
  • UTC Time
  • Device Specific Controls
    • Omniscan 450
      • Mounting Setup
      • Device Controls
      • Firmware Update
      • Display Controls
      • Replay Controls
    • S500 Sounder
    • Ping
    • Ping360
  • Hotkeys
  • SonarLink
  • Known Issues
  • Troubleshooting
  • Deprecated
    • Mission Configurations
      • Omniscan 450
      • Surveyor 240-16
  • Legal
Powered by GitBook
On this page
  1. Session Configurations

Omniscan + MAVLink2Rest Position

PreviousSurveyor + NMEA Heading/PositionNextOmniscan + NMEA Heading/Position

Last updated 6 months ago

These instructions describe how to use the heading and position estimate from a MAVLink2Rest enabled vehicle in SonarView. A useful example is the Omniscan with a BlueROV to get a better heading and/or position estimate for situational awareness.

To get a position estimate, the ROV will need a sensor to estimate position such as the

  1. Add the Omniscan to the Devices list:

  1. Add the BlueROV2 to the vehicles list:

The vehicle model is just aesthetic. The necessary fields are the nickname, protocol (only mavlink2rest is support atm), hostname and port

Selecting a vehicle as the default makes it used in every other session that doesn't have a vehicle specifically defined

  1. Add session with Omniscan and vehicle

With your Omniscan powered on the network, you should be able to connect to this session plan in Discovery

Tracker 650