# Factory Defaults and Default Messages The DVL has several different type of output messages, not all of which are useful in all applications. The DVL 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 for the DVL at 0.0.0.0 (static IP address disabled) * Host IP address 255.255.255.255:27000 (general broadcast to UDP port 27000) * MAVlink interface IP address 192.168.2.2:6040 (enabled with default BLueOS/Ardusub TCP address) * Fallback IP address for the DVL at 192.168.2.3 * $GPRMC: DVL's own position set to OFF * $DVEXT: DVL extended data message used to drive CeruleanTracker features set to ON * Freeform messages: used to provide DVL boot progress and ongoing information messages set to ON * $DVKFA and $DVKFB: messages to support external Kalman filters set yo OFF * $DVPDL: Delta position of the DVL used to drive position hold functions in non-BlueOS/Ardusib systems set to OFF * Retweet GPS: used to pass raw data from the DVL's integrated GPS to external systems set to OFF * Retweet IMU: used to pass raw data from the DVL's integrated IMU to external systems set to OFF * Magnetic Declination: set to 0.0 * Speed of sound: set to 1484 meters/second * Velocity Adjustment: used to adjust DVL performance to specific environments * DVL mounting orientation adjustment set to \[0,0,0] --- # 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/dvl-75/communicating-with-the-dvl/factory-defaults-and-default-messages.md?ask= ``` 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.