Position and Heading Source

To position Omniscan 3D data correctly in space, SonarView requires position and heading data from an external source. Currently supported sources include NMEA 0183, NMEA 2000, and mavlink2rest. After setting up your source, configure it in Session Configurations so SonarView knows where to receive the data.

Before starting this process, make sure you have completed the Quick Start guide and can connect to your Omniscan 3D unit(s)

1. Session Configurations

From the main page of SonarView, go to Session Configurations. It should look something like this:

2. Add Omniscan 3D Device(s)

First, add your Omniscan 3D device by clicking + Add Device. This opens the device editor. If your Omniscan 3D device is powered on and available, click Detect Devices to automatically populate the required information. It should look something like this:

Port # for OS3D is 62312

The mounting offset is configured as Forward (X), Starboard (Y), Down (Z) FROM your position/heading sensor TO the center of the face of the array module shown in the image below.

For example, when mounting an Omniscan3D on a BlueBoat:

• Starboard (right) placement is a positive Y offset

• Forward placement (ahead of the vehicle's center) is a positive X offset

• Below-center placement is a positive Z offset

Depending on if you are running the upgrade kit (RX16 + Omniscan) or the self-contained variant of the Omniscan 3D (most common), the setup is slightly different.

AIO

• Set up an Omniscan 3D device per unit and add them to a session together

• Fill in the mounting information here. The Mounting Angle and Mounting Offset are defined relative to the orientation and position of your heading and position source. In this example, the Omniscan 3D unit is pointed 90° to port relative to the source and is mounted 1 meter to port and 1.5 meters below it.

Upgrade Kit

• Only define ONE Omniscan 3D device regardless of if you're running port and starboard units

• Ignore mounting angles here in Session Configurations. Those will be configured once connected in OS3D Configuration

Once you are satisfied with these settings, click Save.

3. Add Position/Heading Source

Follow the appropriate instructions depending on whether your position/heading source is NMEA or mavlink2rest.

NMEA

Your device must supply at least one heading message and one position message. Below are supported position and heading messages.

NMEA Variant	Heading	Position
0183	HDT, HDG, THS	GGA, RMC
2000	127250	129025

We also support other messages for information such as altitude, heave, course-over-ground, etc. Some other supported messages include 129026, 127252, PASHR, VTG, CHC, and others. Feel free to inquire about additional message support

One commonly used set up we support is the Garmin MSC 10 + NMEA -> serial converter

To add an NMEA position/heading source, click + Add Device. Because device discovery can’t detect arbitrary NMEA sources, you’ll need to configure it manually. For Device Type, select Generic GPS. It should look something like this:

NMEA data can also be provided via TCP/UDP

With your Omniscan 3Ds and NMEA source configured, add them to a session like this:

mavlink2rest

To add a mavlink2rest position/heading source (e.g. a BlueBoat), you will need to select + Add Vehicle from the main page of Session Configurations. It should end up looking something like this

Make sure your System ID matches that of your vehicle

Next, add the vehicle and Omniscan 3Ds to a session together like this:

With your session configured correctly and all devices connected, return to Discovery and connect to your custom session. Once you click Start, data collection should begin, and you should see your position and heading update in the view.