Troubleshooting RTK scanning
Issue |
Potential cause(s) |
Potential solutions |
---|---|---|
When configuring the GNSS receiver, it is not receiving corrections in the Emlid Flow app |
The GNSS receiver settings are misconfigured. |
Ensure the receiver is configured with the correct settings. Also, check if the NTRIP details (i.e. IP address, user name, password) are spelled/entered correctly. If using a SIM card, turn off the device, remove and re-insert the SIM card, and restart. Restart the device. If issues persist, contact Emesent support. |
When the GNSS receiver is plugged into the Hovermap, Web UI / Commander shows ‘No GPS’ |
The Hovermap was turned on before the GNSS receiver. The GNSS receiver is not turned on. The Emlid cable is not fully inserted. |
Remove the GNSS receiver’s cable and re-insert. Ensure the GNSS receiver is configured with the correct settings. Reboot the GNSS receiver. Reboot Hovermap. |
Web UI / Commander shows ‘RTK Error’ |
The GNSS receiver’s settings are misconfigured. |
Ensure the GNSS receiver is configured with the correct settings. |
I’m not getting RTK Fix I’m seeing No GPS Fix |
Correction is settings are not configured properly. The baseline length is >15km. The current environmental conditions are not ideal for obtaining a good-quality RTK signal. |
Georeferencing accuracy decreases by approximately 1mm for every kilometer of baseline length. Select a closer CORS base station if one exists, or use a base station setup to reduce the baseline length. |
I do not see the RTK status in Emesent Commander |
Incompatible software versions |
Ensure you are using the latest versions of Emesent Cortex (3.3 or later) and Emesent Commander (1.5 or later). Use the Web UI to see the RTK status. However, this has less functionality and you cannot see number of satellites, precision or coordinates. |
VEHICLE |
||
The vacuum mounts are difficult to attach to the vehicle |
The legs are not loose enough. |
Gently loosen the mount legs until they move freely. Then, place the mount on the vehicle and tighten it. |
Troubleshooting RTK data processing
Issue |
Potential cause(s) |
Potential solutions |
---|---|---|
Processing the scan with RTK is causing the scan to “split” |
The Advanced feature matching setting is disabled. The GNSS receiver is returning a high-confidence incorrect GPS data due to an urban canyon or other environmental conditions. |
Go to the Processing Settings (General tab) and enable Advanced feature matching. Review the site to determine if tall reflective buildings may be interfering with the GPS signal. |
RTK data is not in the desired coordinate system |
The scan has not been reprojected. |
Reproject the scan into your desired coordinate system. See Reproject your Point Cloud. |
Colorization is low-quality |
Low point density A mask is applied to the area requiring colorization. |
For Vehicle RTK, increase point density by driving more slowly or doing multiple passes over the scan area. For either Vehicle or Backpack RTK, review the extracted frames to determine if the desired area has been masked. Change the mask if necessary. Change the orientation of the Hovermap during scanning to ensure the GoPro MAX 360 camera has a sufficient view of the area. |
Areas of my point cloud I expect to be colorized are not colorized |
A mask is applied to the area requiring colorization. The area requiring colorization is too far away |
Review the extracted frames to determine if the desired area has been masked. Change the mask if necessary. Change the orientation of the Hovermap during scanning to ensure the GoPro MAX 360 camera has a sufficient view of the area. Go to the Processing Settings (Colorize tab). Under Processing Quality, increase the Colorization Distance value. |
BACKPACK |
||
I’m seeing myself throughout the point cloud |
The bounding box is not large enough to exclude the user from the point cloud. |
Go to the Processing Settings (General tab). Under Exclusion Zone, change the Mode to Bounding Box and adjust the values. |
VEHICLE |
||
I’m seeing my vehicle throughout the point cloud |
The bounding box is not large enough to exclude the vehicle from the point cloud. |
Go to the Processing Settings (General tab). Under Exclusion Zone, change the Mode to Bounding Box and adjust the values based on the size of your vehicle. |
I’m seeing slips or drifts in my scan |
You are driving more than 60kph. |
If appropriate, drive more slowly. |
There is “banding” of the point cloud, where aspects of the cloud have high point density and others have very few points |
When driving too fast, the Hovermap does not have sufficient time to scan the area. |
If appropriate, drive more slowly to allow Hovermap to collect more data Do more passes over the scan area to increase point density. |
Moving object removal is removing too much of the point cloud |
While traveling quickly, stationary points in the Hovermap's point cloud can appear to move, triggering the Moving Object Removal filter. |
It is not recommended to use Moving Object Filtering when conducting a vehicle scan as the detected moving objects have a relative velocity compared to the payload, which can cause inaccuracies. |