Standalone uses satellites alone; differential uses corrections. RTK float is not fixed. RTK fixed does not by itself guarantee accuracy; check the accuracy estimate and conditions too.
1. Is the sky open enough?
Open Technical details on the receiver page. The sky plot shows where the satellites are and the bars show their signals. Buildings, trees and vehicles block or reflect signals: move a few meters into the open and keep the antenna above your head, ideally on a pole. See Reading the sky plot.
Satellite count and green bars alone do not confirm RTK quality. Check signal quality, satellite geometry, corrections and the receiver’s fix status together.
2. Are corrections reaching the receiver?
Under NTRIP on the receiver page, Received from caster and Sent to receiver should keep counting up, and the receiver line should read Using corrections with an age of a few seconds.
- Nothing received: check the account, the mountpoint and the phone's internet connection.
- Received, not used by the receiver: the receiver is not accepting corrections on this connection; enable its RTCM input.
- Corrections are being dropped because the link to the receiver is too slow: bring the phone closer to a Bluetooth receiver.
3. Is the base station close enough?
For single-base RTK, a shorter baseline generally helps. There is no universal distance limit; check the receiver specifications and the correction service’s coverage. Network RTK can work differently.
4. Is it the right kind of mountpoint?
The mountpoint must send satellite observations in RTCM 3. If it doesn't, the app shows This mountpoint sends no satellite observations; pick another.
5. Give it time
Time to RTK fixed varies with the receiver, baseline, satellite visibility, multipath and correction data. Wait for a stable solution and check its accuracy estimate.
Still stuck?
Email us at measure_support@insightspatiallabs.com with screenshots of the receiver page and Technical details, and the receiver model.