> 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`. 
* For a different NMEA2000 Gateway, set `product_id` to `gps.`
* **For any other GPS device**, set `product_id` to `gps`. 

If using any other GPS device, your session plan would look like this: 

```
    {
      "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 
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ceruleansonar.com/c/sonarview/deprecated/mission-configurations/surveyor-240-16.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.