> 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/rov-locator/multi-unit-operation-swarms/multi-unit-1-2.md).
# Multi-Unit 1:2
The Multi-Unit 1:2 case has two independent transmitters on ROVs or divers, with each transmitter on a different channel. A single receiver tracks both transmitters.
The position of each transmitter is updated once per second.
If a topside GPS is associated with the receiver, the absolute (latitude/longitude) position of each transmitter can be known.
The Mk II Autosync model is the only ROVL model that can operate on two channels (and thus the only model that supports this version of 1:2). In order to maintain clock synchronization, all three units must surface and re-acquire the GPS signal periodically (every hour or two).
{% hint style="info" %}
The 1:2 case is partially supported by CeruleanTracker and CeruleanMap software (one unit is fully supported and the second unit's position can be simultaneously plotted on CeruleanMap). Additionally, users can write their own software to make use of the positional information created.
{% endhint %}
One receiver tracking two transmitters, each on their own channels
---
# 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/rov-locator/multi-unit-operation-swarms/multi-unit-1-2.md?ask=&goal=
```
`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.