--- title: "Troubleshooting RTK" slug: "troubleshooting-rtk" updated: 2026-08-24T05:26:44Z published: 2026-08-24T05:26:44Z canonical: "knowledge.emesent.com/troubleshooting-rtk" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.emesent.com/articles/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting RTK Use this article to diagnose and resolve common issues with RTK setup and data processing. Find the symptom in the quick reference table and follow the link to the matching resolution. ## Quick reference | Symptom | Likely cause | Go to | | --- | --- | --- | | GNSS receiver is not receiving corrections in the Emlid Flow app | Misconfigured receiver settings or incorrect NTRIP details | [GNSS receiver not receiving corrections](/v1/docs/troubleshooting-rtk#gnss-no-corrections) | | Web UI / Commander shows "No GPS" after plugging in the GNSS receiver | Hovermap was powered on before the GNSS receiver | [No GPS after connecting receiver](/v1/docs/troubleshooting-rtk#no-gps-after-connect) | | Web UI / Commander shows "No GPS" | Receiver not powered on, or Emlid cable not fully inserted | [No GPS](/v1/docs/troubleshooting-rtk#no-gps) | | Web UI / Commander shows "RTK Error" | Misconfigured GNSS receiver settings | [RTK Error](/v1/docs/troubleshooting-rtk#rtk-error) | | No RTK Fix | Incorrect correction settings, baseline length >15 km, or poor environmental conditions | [No RTK Fix](/v1/docs/troubleshooting-rtk#no-rtk-fix) | | RTK status is not visible in Commander | Incompatible software versions | [RTK status not visible in Commander](/v1/docs/troubleshooting-rtk#rtk-status-not-visible) | | Vacuum mounts are difficult to attach to the vehicle | Mount legs are not loose enough | [Vacuum mounts difficult to attach](/v1/docs/troubleshooting-rtk#vacuum-mounts) | | Scan is splitting during processing | Advanced feature matching disabled, or GPS signal interference | [Scan splitting during processing](/v1/docs/troubleshooting-rtk#scan-splitting) | | RTK data is not in the desired coordinate system | Scan has not been reprojected | [RTK data in wrong coordinate system](/v1/docs/troubleshooting-rtk#wrong-coordinate-system) | | Colorization is low quality | Low point density or mask applied to the colorization area | [Low-quality colorization](/v1/docs/troubleshooting-rtk#low-quality-colorization) | | Areas of the point cloud are not colorized | Mask applied, or area is too far from the camera | [Areas not colorized](/v1/docs/troubleshooting-rtk#areas-not-colorized) | | The operator appears throughout the point cloud (backpack) | Exclusion zone bounding box is too small | [Operator visible in point cloud](/v1/docs/troubleshooting-rtk#operator-visible) | | Vehicle appears throughout the point cloud | Exclusion zone bounding box is too small for the vehicle | [Vehicle visible in point cloud](/v1/docs/troubleshooting-rtk#vehicle-visible) | | Slips or drifts in the scan | Driving speed exceeds 60 kph | [Slips or drifts in scan](/v1/docs/troubleshooting-rtk#slips-drifts) | | Banding in the point cloud | Driving too fast for sufficient scan coverage | [Banding in point cloud](/v1/docs/troubleshooting-rtk#banding) | | Moving object removal is removing too much of the point cloud | Moving Object Filtering is not suitable for vehicle scans | [Moving object removal removing too much](/v1/docs/troubleshooting-rtk#moving-object-removal) | ## Before you start - Confirm the GNSS receiver is powered on before Hovermap. - Confirm all cables are fully inserted. - Confirm Emesent Cortex and Emesent Commander are on supported versions (Cortex 3.3 or later, Commander 1.5 or later). ## RTK setup ### Issue 1: GNSS receiver not receiving corrections **Symptom:** The GNSS receiver is not receiving corrections in the Emlid Flow app. **Cause:** The GNSS receiver settings are misconfigured, or the NTRIP details are incorrect. **Resolution:** 1. Confirm the receiver is configured with the correct settings. 2. Check that the NTRIP details (IP address, username, and password) are entered correctly. 3. If using a SIM card, power off the device, remove and re-insert the SIM card, then restart. 4. Restart the device. 5. If the issue persists, contact Emesent support. ### Issue 2: No GPS after connecting receiver **Symptom:** Web UI / Commander shows "No GPS" after the GNSS receiver is plugged into Hovermap. **Cause:** Hovermap was powered on before the GNSS receiver. **Resolution:** 1. Remove the GNSS receiver cable and re-insert it. ### Issue 3: No GPS **Symptom:** Web UI / Commander shows "No GPS". **Cause:** The GNSS receiver is not powered on, or the Emlid cable is not fully inserted. **Resolution:** 1. Confirm the GNSS receiver is powered on and configured with the correct settings. 2. Reboot the GNSS receiver. 3. Reboot Hovermap. ### Issue 4: RTK Error **Symptom:** Web UI / Commander shows "RTK Error". **Cause:** The GNSS receiver settings are misconfigured. **Resolution:** 1. Confirm the GNSS receiver is configured with the correct settings. ### Issue 5: No RTK Fix **Symptom:** The system is not achieving RTK Fix. **Cause:** Correction settings are not configured correctly, the baseline length exceeds 15 km, or environmental conditions are affecting signal quality. **Resolution:** 1. If the baseline length exceeds 15 km, select a closer CORS base station or set up a local base station to reduce the baseline length. Georeferencing accuracy decreases by approximately 1 mm per kilometer of baseline length. ### Issue 6: RTK status not visible in Commander **Symptom:** The RTK status is not visible in Emesent Commander. **Cause:** Incompatible software versions. **Resolution:** 1. Confirm Emesent Cortex is version 3.3 or later and Emesent Commander is version 1.5 or later. 2. If a software update is not possible, use the Web UI to view RTK status. Note that the Web UI does not display the number of satellites, precision, or coordinates. ### Issue 7: Vacuum mounts difficult to attach **Symptom:** The vacuum mounts are difficult to attach to the vehicle. **Cause:** The mount legs are not loose enough. **Resolution:** 1. Gently loosen the mount legs until they move freely. 2. Place the mount on the vehicle. 3. Tighten the mount. ## RTK data processing ### Issue 8: Scan splitting during processing **Symptom:** Processing the scan causes it to split. **Cause:** The **Advanced feature matching with RTK** setting is disabled, or the GNSS receiver is returning high-confidence incorrect GPS data due to an urban canyon or other environmental interference. **Resolution:** 1. Go to **Processing Settings (General tab)** and enable **Advanced feature matching**. 2. Review the site to determine whether tall or reflective buildings may be interfering with the GPS signal. ### Issue 9: RTK data in wrong coordinate system **Symptom:** RTK data is not in the desired coordinate system. **Cause:** The scan has not been reprojected. **Resolution:** 1. Reproject the scan into the desired coordinate system. See Reproject your Point Cloud. ### Issue 10: Low-quality colorization **Symptom:** Colorization is low quality. **Cause:** Low point density, or a mask is applied to the area requiring colorization. **Resolution:** 1. For Vehicle RTK: drive more slowly or do multiple passes over the scan area to increase point density. 2. For Vehicle or Backpack RTK: review the extracted frames to determine whether the desired area has been masked, and update the mask if necessary. 3. Adjust the orientation of Hovermap during scanning to ensure the GoPro MAX 360 camera has a sufficient view of the area. ### Issue 11: Areas not colorized **Symptom:** Areas of the point cloud that are expected to be colorized are not colorized. **Cause:** A mask is applied to the area, or the area is too far from the camera. **Resolution:** 1. Review the extracted frames to determine whether the desired area has been masked, and update the mask if necessary. 2. Adjust the orientation of Hovermap during scanning to ensure the GoPro MAX 360 camera has a sufficient view of the area. 3. Go to **Processing Settings (Colorize tab)**. Under **Processing Quality**, increase the **Colorization Distance** value. ### Issue 12: Operator visible in point cloud **Symptom:** The operator appears throughout the point cloud during a backpack scan. **Cause:** The exclusion zone bounding box is not large enough to exclude the operator. **Resolution:** 1. Go to **Processing Settings (General tab)**. 2. Under **Exclusion Zone**, set **Mode** to **Bounding Box**. 3. Adjust the bounding box values as needed. ### Issue 13: Vehicle visible in point cloud **Symptom:** The vehicle appears throughout the point cloud. **Cause:** The exclusion zone bounding box is not large enough to exclude the vehicle. **Resolution:** 1. Go to **Processing Settings (General tab)**. 2. Under **Exclusion Zone**, set **Mode** to **Bounding Box**. 3. Adjust the bounding box values to match the size of the vehicle. ### Issue 14: Slips or drifts in scan **Symptom:** Slips or drifts are visible in the scan. **Cause:** The vehicle is travelling faster than 60 kph. **Resolution:** 1. Reduce driving speed if operationally appropriate. ### Issue 15: Banding in point cloud **Symptom:** The point cloud shows banding, with some areas having high point density and others having very few points. **Cause:** Driving too fast does not allow Hovermap sufficient time to scan the area. **Resolution:** 1. Reduce driving speed to allow Hovermap to collect more data, if operationally appropriate. 2. Do additional passes over the scan area to increase point density. ### Issue 16: Moving object removal removing too much **Symptom:** Moving object removal is removing too much of the point cloud. **Cause:** When travelling quickly, stationary points in the point cloud can appear to move, triggering the Moving Object Removal filter.

Moving Object Filtering is not recommended for vehicle scans. At higher speeds, detected moving objects have a relative velocity compared to the payload, which can cause inaccuracies.

## Still not resolved? If the issue persists after following the steps above, contact [Client Support](https://emesent.com/customer-support/) with the following information: - Product and version - Steps already tried - Any error messages or logs