This article explains how to start an RTK session with a supported GNSS receiver and a Hovermap. Use this procedure at the start of every scan to make sure the Hovermap records RTK data.
The procedure is the same for Emlid, Trimble, and Leica receivers. Only the method used to connect the receiver to the corrections source is different.
What you will need
A supported GNSS receiver, mounted, connected to the Hovermap, and configured for use with it. Refer to the setup articles in the table below.
The controller or configuration application for that receiver.
Access to a corrections source. This is either an RTN or CORS service, or a local base station.
Emesent Commander 1.5 or later on a smartphone or tablet.
Receiver | Hardware setup | Configuration |
|---|---|---|
Emlid | ||
Trimble | ||
Leica |
Procedure
Step 1: Start the corrections stream
Turn on the GNSS receiver.
Use the controller or the configuration application to connect the receiver to the corrections source.
Confirm that the receiver has a GNSS lock and receives corrections.
For a local base station with an Emlid receiver, refer to Emlid base station corrections.
Step 2: Start the Hovermap
Complete Step 1 before the Hovermap starts. The receiver does not send data until it has a GNSS lock. If the Hovermap starts first, it does not detect the receiver, and no RTK status shows in Emesent Commander.
Turn on the Hovermap.
Wait for the Hovermap to start.
Step 3: Check the RTK status
Connect Emesent Commander to the Hovermap.
Confirm that Commander shows the RTK position and accuracy, and shows no communication warnings.
If Commander shows no RTK status, leave the receiver on and restart the Hovermap. Refer to Troubleshooting RTK.
Outcome
The Hovermap receives RTK corrections from the GNSS receiver and is ready to capture a georeferenced scan.
Additional information
Repeat this procedure for every scan. The start order applies each time the equipment is turned on, not only at first setup.
Supported GNSS receivers: the receivers that work with the Hovermap.
Monitor RTK status: the RTK status indicators in Commander and the expected accuracy.
Processing with RTK data in Aura: process the captured RTK scan.
Best practice for RTK: factors that affect georeferencing accuracy.
