Bad Elf Flex

Bad Elf Flex - How-To Connect to RTKdata.com

Bad Elf Flex GNSS receiver connected via Bluetooth and NTRIP to RTKdata.com

Get centimeter‑grade positioning on your Bad Elf Flex by streaming RTK corrections from RTKdata.com over NTRIP. This step‑by‑step guide follows the workflow shown in the video (power on → pair → Bad Elf Flex app → NTRIP profile → connect → RTK FIX), adapted to RTKdata.com.

Requirements

  • Bad Elf Flex GNSS receiver

  • Bad Elf Flex app on iOS/Android (built‑in NTRIP client)

  • Mobile internet on the phone/tablet (Wi‑Fi / hotspot / LTE)

  • RTKdata credentials (username/password).

Don’t have an RTKdata.com account yet? 👉 Start 30-day Free Trial or View Pricing

Step‑by‑step setup

1

Power on & pair (Bluetooth)

  • Press and hold the power button until the LEDs turn on.

  • On your phone/tablet, pair the receiver via Bluetooth (Settings → Bluetooth → select your Bad Elf Flex).

  • Launch the Bad Elf Flex app — it should auto‑discover and connect to the receiver.

2

Open the NTRIP client in the app

  • In the Bad Elf Flex app, go to Correction Mode → RTK via NTRIP → Network.

  • Tap “+” to create a new NTRIP profile (you can name it e.g. “RTKdata”).

3

Enter RTKdata.com connection settings (Regional hostnames + IP fallback)

Use the regional RTKdata.com hostname where possible. If your device only accepts numbers or your network DNS blocks hostnames, use the numeric IP fallback. Keep ALL CAPS where noted.

  • Host (domain): rtk.rtkdata.com

  • Host (IP fallback): 13.56.117.10

  • Port: 2101

  • Username / Password: From RTK Credentials in the internal dashboard (not website login)

  • Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in no corrections. Always use ALL CAPS.

4

(Optional) Match the output datum to your mountpoint

  • If your workflow requires a specific frame, align the app’s Output Datum to your chosen mountpoint:

    • AUTO → regional frame (e.g., NAD83(2011) in the US, ETRS89/ETRF2000 in the EU)

    • AUTO_WGS84 → WGS84 (G2139)

    • AUTO_ITRF2020 → ITRF2020 (epoch 2015.0)

    • AUTO_ITRF2014 → ITRF2014 (current epoch)

  • Otherwise, keep AUTO to let RTKdata.com apply the correct local frame automatically.

5

Connect & verify FIX

  • Tap Connect in the NTRIP profile.

  • Confirm RTCM is streaming (Connection/Server status OK).

  • Move outdoors with open sky; watch status go Autonomous/SBAS → RTK Float → RTK FIX.

  • You’re now ready to survey with centimeter‑level positions.

Vertical reference (heights)

RTKdata.com streams positions in the selected geodetic frame; heights are ellipsoidal by design. If you need orthometric (mean sea level) elevations, enable a geoid on your rover (if supported) or apply it in your GIS/photogrammetry workflow during processing/export.

Troubleshooting

  • No connection / no RTCM: Re‑check IP + Port (2101), username/password, and mountpoint = ALL CAPS (AUTO recommended).

  • Float, no FIX: Go outdoors with a clear sky view; verify the regional IP is correct for your location, ensure mountpoint is AUTO, then reconnect.

  • App shows a different path: Use Correction Mode → RTK via NTRIP → Network → + (new profile). UI labels can vary slightly by app version.

Why RTKdata.com?

  • Centimeter‑level accuracy with real‑time corrections

  • Global reach with dense coverage in key regions

  • Simple IP‑only setup that works across popular field apps and receivers

Start Free Trial See Pricing Troubleshooting

PreviousDJI Mavic 3ENextBad Elf Flex Mini

Last updated