What You’ll Need

1. Bad Elf Flex Mini Extreme, Bad Elf Flex Extreme, or Bad Elf Flex Standard with an Active Token
2. Latest version of the Bad Elf Flex App
3. Updated receiver firmware
4. Internet access on your phone or tablet

Step-by-step Instructions

Step 1: Update the Bad Elf Flex App

1. Search for the Bad Elf Flex App on the iOS App Store or Google Play Store.
2. Install updates if available.

Step 2: Connect to your Bad Elf receiver

1. Power on your Flex or Flex Mini.
2. Open the Bad Elf Flex App.
3. Connect to the receiver over Bluetooth.
4. If an orange firmware update message is visible at the top of the main menu, install firmware update. Reconnect via Bluetooth.
1. Flex Mini firmware update page
2. Flex firmware update page

Step 3: Open the RTK Marketplace

1. Tap Corrections.
2. Review the available correction options.
   

The RTK Marketplace includes:

1. built-in partner correction providers
   
2. any previously saved NTRIP profiles
3. public RTK networks
   

Use the RTK Marketplace if you need help finding a correction source or want to avoid manually entering NTRIP server settings you haven't already saved.

Step 4: Choose a correction option

The RTK Marketplace includes three common correction setup paths.

Built-in partner providers

For the simplest setup experience, you can select a partner correction network provider in the RTK Marketplace, enter your email address, and follow the provider checklist from the app.

Built-in provider options include:

1. Point One Navigation Polaris: 2-week free trial
   
2. GEODNET: 30-day free trial
3. SwiftNav Skylark Cx: 6-month free trial
4. SwiftNav Skylark Nx: 6-month free trial

Use these trial periods to confirm that the provider has coverage in your work area, supports your accuracy requirements, and works reliably with your field collection workflow.

For built-in providers, the app handles the connection workflow, eliminating the need to manually select or configure a NTRIP profile during initial setup.

The most commonly used datum is selected by default.

Public RTK networks

The Bad Elf Flex app provides a list of public networks available in the US, categorized by state. The Flex app displays information about how to sign-up, base station locations, and suggested connection settings. Public RTK networks require you to create an account with the network and enter your login credentials.

The app suggests the best port, mount point, and datum for public networks when applicable. If you decide to change the default mount point, prioritize MSM4, MSM5, or RTCM 3.2+ streams/formats, as these are better suited for modern multi-constellation RTK workflows. Incorrect mount point selection may prevent connection or fail to reach an RTK fix. For more information, please see the article Logging into an RTK network.  

Sharing Custom NTRIP profiles

Use a custom NTRIP profile if your organization already has RTK correction credentials or operates its own correction source.

Profiles can be shared with other users to reduce manual setup. To share a profile from the Bad Elf Flex app, copy the link from the profile editor.

To generate a URL to share a profile, try the NTRIP Profile Generator.

Supported sharing methods include:

1. URL: Send a profile link to another user.
2. QR code: Let users scan and import the profile.
3. MDM: Push profiles to managed mobile devices.

This is useful when multiple users need the same correction source, mount point, datum, or organizational RTK account.

Step 5: Connect and confirm corrections are flowing

1. Place the receiver in a location where the antenna has an unobstructed view of the sky.

Please see this article for best practices: Best Practices for GNSS Data Collection with Bad Elf Receivers

2. Confirm all green marks on the provider section of checklist.

3. Connect to the provider or network.

4. Confirm that corrections are flowing.

5. Confirm the receiver reaches RTK fix when field conditions allow.

The Corrections screen should show:

1. connected to the provider
2. corrections flowing
3. corrections in use
4. GNSS fix: RTK (FIXED), when available
   

Auto-reconnect

After the correction connection works successfully, Auto-reconnect is automatically enabled.

Auto-reconnect allows the Bad Elf Flex App to reconnect to the saved provider or correction source when your Bad Elf receiver connects over Bluetooth in the future. Once Auto-reconnect is enabled, your Bad Elf Flex or Bad Elf Flex Mini can reconnect to the last phone or tablet it was paired with, and the Bad Elf Flex App can begin streaming corrections in the background. 

Troubleshooting

I do not see any providers in the RTK Marketplace

1. The Bad Elf Flex App is updated.
2. Your phone or tablet has internet access.
3. Your receiver is connected.
4. Your receiver supports RTK workflows.

I selected a built-in provider, but I cannot start the trial or service

1. Your email address was entered correctly.
2. Your phone or tablet has internet access.
3. The provider supports your region.
4. You completed any required provider sign-up steps.
5. The provider trial or account is active.

I selected a public RTK network, but I cannot connect

1. Your username and password are correct.
2. The network account is active.
3. The selected mount point is correct.
4. Your phone or tablet has internet access.
5. The network has coverage in your work area.
6. If the app does not suggest a mount point, or if the first mount point does not work, try another available mount point. When available, prioritize MSM4, MSM5, or RTCM 3.2+ streams/formats.

Corrections are connected, but I do not have RTK fix

1. The receiver has a clear view of the sky.
2. The correction stream is still connected.
3. The selected provider or network has coverage in your area.
4. The receiver has enough satellites available.
5. The selected mount point is appropriate for your location, if using a public network or custom NTRIP profile.
6. The selected datum matches your project requirements.

My data appears shifted or does not line up as expected

1. The selected output datum matches your project requirements.
2. Your field app is using the expected coordinate system or transformation.
3. Your correction provider is outputting the datum expected by your workflow.
4. Your GIS administrator or project lead has confirmed the correct datum settings.

Corrections do not reconnect automatically

1. Auto-reconnect is turned on.
2. The correction connection was tested successfully first.
3. The receiver is connected over Bluetooth.
4. The phone or tablet has internet access.
5. The provider account or credentials are still valid.

My field app does not show the expected accuracy

1. RTK fix is shown in the Bad Elf Flex App.
2. Corrections are flowing.
3. Your field app is using the Bad Elf receiver as its location source.
4. The receiver is outside with a clear view of the sky.
5. The selected datum and field app settings match your project requirements.

Need More Help?