# Factory Defaults and Default Messages

The Tracker 650 has several different types of output messages, not all of which are useful in all applications.

The Tracker 650 is set to the following configuration when shipped from the factory. Commands are provided to set each message type on and off, and when you make changes, the new settings are persisted in non-volatile memory.

* Static IP address at 192.168.2.8 (static IP address enabled)
* Host IP address 192.168.2.1:27000 (unicast to UDP port 27000)
* MAVLink interface IP address 192.168.2.2:6040 (messages enabled, using default mavlink2rest address:port)
* MAVLink auto global position setting disabled
* MAVLink depth-below-transducer sending enabled
* Fallback IP address for the DVL at 192.168.2.8 (this may collide with other device's static or fallback IPs so take care to avoid collisions by using different addresses if necessary))
* $DVKFC: message to support external Kalman filters set to ON
* $DVPDL: Delta position of the DVL used to drive position hold functions in non-BlueOS/Ardusub systems set to OFF
* $DVPDX: Delta position of the DVL (plus a few other useful values) used to drive position hold functions in non-BlueOS/Ardusub systems set to ON
* Speed of sound: set to 1484 meters/second
* Velocity Adjustment: used to adjust DVL performance to specific environments set to 1.0
* DVL mounting orientation adjustment set to (0, 0, 0), or pointed down with arrow forward.


---

# Agent Instructions: 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:

```
GET https://docs.ceruleansonar.com/c/tracker-650/communicating-with-the-tracker-650/factory-defaults-and-default-messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
