> 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/tracker-650/using-mavlink-and-blueos-for-position-hold-on-a-bluerov2/tracker-650-setup-for-mavlink-support.md). # Tracker 650 Setup for MAVLink Support To support MAVLink integration, the Tracker 650 is shipped with the following required non-volatile memory settings as default. If you have changed them, you may need to change them back to the default: * DVL's MAVLink address: 192.168.2.2 port 6040 (configure this on CeruleanTracker's DVL Command Window user interface or [send it raw DVL commands](/c/tracker-650/technical-details/api/commands-accepted-by-the-tracker-650/mavlink-address.md) via one of the DVL's interfaces). If you have changed your BlueOS address, then you need to change this to the address used by BlueOS. * If you have CeruleanTracker active on the ROV network, go to the **Output tab** of the main window and check "Don't Send on Ethernet", and/or uncheck the GPRMC Output Message Format and/or make sure the Send To address is not the same as the ROV's address (including making sure the Send To address is not a broadcast address) * If you have CeruleanTracker active on the ROV network, go to the **Topside GPS tab** and for the GPS rebroadcast configuration select "Don't Send on Ethernet" or make sure the Send To address is not the same as the ROV's address (including making sure the Send To address is not a broadcast address) Other Tracker 650 parameters not listed here may have any valid value. --- # 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/tracker-650/using-mavlink-and-blueos-for-position-hold-on-a-bluerov2/tracker-650-setup-for-mavlink-support.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.