Omniscan 450

Configuring Omniscan mounting setup with config.json file

If you have more than one Omniscan on the vehicle, the mounting configuration must be specified in the config.json file located in the directory with your SonarView log files. Here is an example config.json file having configurations for 2 or 3 Omniscan devices. We refer to these as "User Defined Sessions." The format of the file must conform to JSON standards. If it does not, you will get error messages.

{
  "session_plans": [
    {
      "name": "Blueboat with Dual Side Scan",
      "devices": [
        {
          "note": "port",
          "product_id": "os450",
          "url": "tcp://192.168.2.104:51200",
          "transducer_deg": -90
        },
        {
          "note": "starboard",
          "product_id": "os450",
          "url": "tcp://192.168.2.115:51200",
          "transducer_deg": 90
        }
      ]
    },
    {
      "name": "ROV with FS + SS",
      "devices": [
        {
          "note": "forward",
          "product_id": "os450",
          "url": "tcp://10.0.1.117:51200",
          "transducer_deg": 0,
          "imu_deg" : 90
        },
        {
          "note": "starboard",
          "product_id": "os450",
          "url": "tcp://10.0.1.107:51200",
          "transducer_deg": 90
        }
      ]
    },
    {
      "name": "Triple Omniscans",
      "devices": [
        {
          "note": "starboard",
          "product_id": "os450",
          "url": "tcp://192.168.2.12:51200",
          "transducer_deg": 90,
          "doppler_enable": false
        },
        {
          "note": "forward",
          "product_id": "os450",
          "url": "tcp://192.168.2.100:51200",
          "transducer_deg": 0,
          "doppler_enable": true
        },
        {
          "note": "port",
          "product_id": "os450",
          "url": "tcp://192.168.2.104:51200",
          "transducer_deg": -90,
          "doppler_enable": false
        }
      ]
    }
  ]
}

During SonarView device discovery you will see the individual Omniscan devices as well as User Defined Sessions with "name" as given in the config.json file representing a SonarView session with multiple Omniscan Devices.

• "name" may be anything you would like to call the configuration

• "note" is also is just an arbitrary name you can set for each device

• "product_id" must be "os450" for Omniscan 450 FS or Omniscan 450 SS

• "url" should be formatted as shown. Omniscan 450 communicates with tcp, ip address must match the actual device settings, and 51200 is the required port number for Omniscan 450.

• "transducer_deg" is the angle in degrees at which the transducer is mounted on the vehicle. 0 degrees is forward, +90 is starboard side and -90 is port side. Angles are typically in the cardinal 0, +/-90, 180 directions, but they don't have to be.

• "imu_deg" is the angle of the IMU Direction in degrees at which the IMU is mounted on the vehicle. 0 is forward and positive angles are CW from there. This value is only required if you are not using vehicle heading. If you are using Omniscan's IMU for heading, you need to specify the IMU direction only for the first device, and that is the device whose heading will be used.

• "doppler_enable" is optional, defaulting to true if not included. The "Triple Omniscans" example above shows a forward looking Omniscan with doppler enabled, and a pair of side scan devices (at +/- 90 deg) with doppler disabled. The advantage is here is that you may use doppler on certain axes without reducing the imaging ping rate on the non-doppler channels.

If doppler is enabled on some devices but not others, the first device in the list should have "doppler_enable": false. This is because the first device is the "master" and if there are non-doppler devices, one of them should be the master. Inter-device sync may have anomalies if the master is a doppler enabled device.

When setting up multiple Omniscan devices, either 0, 1, or 2 devices (and no more) may be enabled for doppler. If 2 devices are doppler enabled, this pair of devices must be oriented 90 degrees apart. Typically this would be one looking forward and one to either port or starboard although this arrangement is not requirement. These restrictions may be relaxed in a future SonarView release.

If the multiple device session name does not appear in discovery, check that the ip addresses of the device match the addresses indicated in the url lines in the config.json file. If illegal json syntax is encountered, you should get an error message. To change IP address, or update firmware, select the individual device in discovery rather than the multiple device session.