> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tracenav.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started (Any NTRIP device)

> Connect any NTRIP-capable GNSS receiver to TraceNav corrections

## Overview

TraceNav streams standard RTCM 3.X corrections that let your RTK-capable devices reach centimeter-level accuracy. This guide walks through everything you need to go from a new account to receiving corrections in the field.

<Note>
  **Need manufacturer-specific guidance?** Contact support at [support@tracenav.net](mailto:support@tracenav.net) with your device model. This service emulates RTK base stations so it may not play nice with all receivers.
</Note>

## Step 1: Get Your NTRIP Credentials

<Steps>
  <Step title="Log in to TraceNav">
    Navigate to [tracenav.net/dashboard](https://www.tracenav.net/dashboard) and sign in to your account.
  </Step>

  <Step title="Click on devices, then create or select device credentials" />

  <Step title="Note Your Connection Details">
    Record the following information:

    * **Server/Host**: `ntrip.tracenav.net`
    * **Port**: `2101`
    * **Username**: Your account username
    * **Password**: Your NTRIP password
    * **Mountpoint**: `tracenav`
  </Step>
</Steps>

## Step 2: Configure Your Device

Configuration varies by manufacturer. Below are common methods:

<AccordionGroup>
  <Accordion icon="mobile" title="Mobile App Configuration">
    Many modern RTK devices use companion mobile apps:

    1. Open your device's configuration app
    2. Navigate to **NTRIP** or **Correction Source** settings
    3. Select **NTRIP Client** or **Add NTRIP Connection**
    4. Enter the connection details from Step 1
    5. Enable the NTRIP connection
    6. Verify connection status shows "Connected"
  </Accordion>
</AccordionGroup>

## Step 3: Configure the GGA Interval

TraceNav uses the GGA sentences your receiver sends back to route the best reference station. We require this every 30 seconds or the connection will be dropped.

### How to update the interval

* **Controller app**: Look for `NMEA Output`, `Position Update`, or `Talker Messages`. Set `GGA` to `5s` or `1s`.
* **Web interface**: Under **Advanced → NMEA Messages**, change the `GGA` rate and apply.
* **Serial/CLI**: Commands often resemble `SET,NMEA,GGA,5` or `log gpgga ontime 5`. Refer to the manufacturer manual; the command names vary.

## Step 3: Verify Connection

<Steps>
  <Step title="Check Device Status">
    Look for indicators on your device:

    * **RTK Fix** or **RTK Float** status light
    * NTRIP connection icon in app/display
    * Correction age should be less than 5 seconds
  </Step>

  <Step title="Monitor Position Accuracy">
    Your position accuracy should improve within 30-60 seconds typically (could be up to 5 minutes for RTK Fix):

    * **Standalone**: ±2-5 meters
    * **RTK Float**: ±0.2-1 meter
    * **RTK Fixed**: ±0.01-0.05 meters
  </Step>

  <Step title="Verify in TraceNav Dashboard">
    Return to your TraceNav dashboard to see:

    * Active connection status.
    * Device location on map (this confirms your device is sending NEMA GGA)
  </Step>
</Steps>

## Common Configuration Parameters

| Parameter    | Value                | Notes                     |
| ------------ | -------------------- | ------------------------- |
| Server       | `ntrip.tracenav.net` | Primary NTRIP caster      |
| Port         | `2101`               | Standard NTRIP port       |
| Mountpoint   | `tracenav`           | VRS mountpoint            |
| Format       | RTCM 3.x             | Most devices auto-detect  |
| Version      | NTRIP v1.0           | Typical default           |
| GGA Interval | 1-10 seconds,        | Position report frequency |

## Troubleshooting

<AccordionGroup>
  <Accordion icon="plug" title="Connection Refused or Timeout">
    * Verify internet connectivity on your device
    * Check firewall settings allow port 2101
    * Confirm credentials are correct
    * Ensure your account is active and has available data
  </Accordion>

  <Accordion icon="map-location-dot" title="No RTK Fix">
    * Verify corrections are being received (age \< 10s)
    * Ensure clear sky view (minimal obstructions)
    * Check if mountpoint is within 50km of your location
    * Wait 2-5 minutes for initial fix(strong multipath and(or) ionospheric interference can cause long convergence)
  </Accordion>

  <Accordion icon="key" title="Authentication Failed">
    * Double-check username and password
    * Verify account has active subscription
    * Check for special characters in password
    * Try resetting your NTRIP password on the rover
  </Accordion>
</AccordionGroup>

## Recommended Settings

For optimal performance:

* **GGA Position Updates**: Enable at 5-second intervals for general rovers, or 1-second for high-mobility assets
* **Reconnect on Failure**: Enable automatic reconnection
* **Correction Format**: RTCM or RTCM 3.X
* **Connection Timeout**: 30 seconds
* **Keep-Alive**: Enable if available