Device Profiles DEMO: Program RTK Corrections in Real Time | Point One Navigation

In this demo, Point One Cloud Lead Mike Kurdziel walks through device profiles, where you can define how your RTK corrections network looks and behaves, down to the device level, in real time via API or Point One's web app.

Program your RTK corrections network behaviour without any firmware updates, reconnections, or reconfiguration on the device.

CHAPTERS
00:00 Introduction — what device profiles are and how the demo is set up
00:37 Demo 1: Correction rate — slow corrections from 1s to 10s to save bandwidth, power, and cost
02:14 Demo 2: Switch back to full corrections — automatic, no reconnection required
02:54 Demo 3: Signal filtering — deliver only the constellations your receiver can use (GPS only)
03:59 Demo 4: Required signals — force association to stations carrying a specific signal (Galileo E6)
05:29 Demo 5: Max baseline — stop corrections when device exceeds distance threshold
07:10 Demo 6: Auto Virtual RTK — automatic fallback from single baseline to Virtual RTK at 20K
08:53 Demo 7: Datums — switch between ITRF 2014 global frame and local datum without post-processing
10:24 Wrap-up

FULL DESCRIPTION
This demo covers all current SDCN device profile capabilities:
Correction rate — Control how frequently your device receives corrections, from 1 to 30 seconds between messages. When a robot is docked, drop to 1/10th the rate to save bandwidth and cellular cost. When it goes active, switch back instantly — no reconnection, no reconfiguration on the device. Your cloud talks to our cloud via API and the network adapts automatically.
Signal filtering — Deliver only the GNSS constellations and frequencies your receiver can actually use. If your device is GPS-only, there's no reason to receive Galileo, BeiDou, or other signals. Configure it once in a device profile and every assigned device gets a clean, optimized stream.

Required signals — The inverse of filtering. If your receiver depends on a specific signal — Galileo E6 is a good example — SDCN will only associate that device with base stations that carry it, even if a closer station doesn't. As your device moves through the world, the network automatically routes it to stations that meet its requirements.

Max baseline — Set a maximum distance threshold for single baseline corrections. When a device exceeds that baseline, corrections stop — keeping your system from using data it can't reliably act on. Adjust the threshold in real time and the network responds immediately.

Auto Virtual RTK — Set a per-device threshold for automatic fallback from single baseline RTK to Point One's Virtual RTK network. When a device crosses that distance from the nearest base station, it switches to a virtual station automatically. When it comes back in range, it switches back. No reconnection. No client logic required. You get the precision of single baseline when you're close and the coverage of Virtual RTK when you need it.

Datums — Switch between the ITRF 2014 global reference frame and a local datum based on where your device is operating — without post-processing or device reconfiguration. Critical for surveyors, map makers, and anyone working in a specific coordinate system.

🔗 Watch the full De livestream: https://www.youtube.com/watch?v=kYLtOtb6fjA

🌐 Learn more: https://pointonenav.com

RTK, GNSS, corrections network, device profiles, SDCN, software defined corrections network, Virtual RTK, signal filtering, datum switching, Point One Navigation, robotics, autonomous vehicles, fleet management, API, programmable GNSS

Видео Device Profiles DEMO: Program RTK Corrections in Real Time | Point One Navigation канала Point One Navigation