> For the complete documentation index, see [llms.txt](https://docs.ceruleansonar.com/c/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ceruleansonar.com/c/sonarview/deprecated/mission-configurations/surveyor-240-16.md).

# Surveyor 240-16

1. In the SonarView [config.json](/c/sonarview/deprecated/mission-configurations.md) file, add a new session plan with two devices as shown below:

```
{
  "session_plans": [
    {
      "name": "Surveyor with Garmin",
      "devices": [
        {
          "product_id": "ydnu-02",
          "url": "serial:COMX?baud=9600"
        },
        {
          "product_id": "mbes24016",
          "url": "tcp://XXX.XXX.XXX.XXX:XXXXX"
        }
      ]
    }
  ]
}
```

Where your surveyor's IP and port number would replace the url field below "mbes24016" (e.g "tcp\://192.168.2.1:62311) and COMX would be replaced with the COM port the USB gateway is using (e.g. "serial:COM7?baud=9600")

* If using the Yacht Devices YDNU-02 gateway, set `product_id` to `ydnu-02`.&#x20;
* For a different NMEA2000 Gateway, set `product_id` to `gps.`
* **For any other GPS device**, set `product_id` to `gps`.&#x20;

If using any other GPS device, your session plan would look like this:&#x20;

```
    {
      "name": "Surveyor with GPS",
      "devices": [
        {
          "product_id": "gps",
          "url": "serial:COMX?baud=9600"
        },
        {
          "product_id": "mbes24016",
          "url": "tcp://XXX.XXX.XXX.XXX:XXXXX"
        }
      ]
    }
```

2. Connect to the session plan on SonarView. The Surveyor should now use the provided gps heading and position data.

{% hint style="warning" %}
If you are using a different NMEA gateway and you have the option between NMEA 0183 and 2000, use 2000 because the conversion to 0183 seems to cause gateways to drastically slow the update rate&#x20;
{% endhint %}
