Confirm the receiver can see satellites and calculate a normal position.
Check the correct high-accuracy unlock and correction source are selected.
Verify mobile internet, credentials, mountpoint and incoming RTCM.
Check sky view, antenna, cabling, correction age and calibration.
Interactive “No RTK” diagnosis
Answer one question at a time. The tool does not send or store your answers.
Goal: identify whether the fault is GPS reception, RTK activation, internet connectivity, NTRIP configuration, correction delivery or the antenna and machine setup.
Does the display have a normal GPS or GNSS position?
If the receiver has no position at all, RTK cannot initialise. Look for satellite count, latitude/longitude or a basic GPS state.
Is RTK or high-accuracy mode unlocked and selected?
A receiver can show GPS while lacking the paid RTK activation. Also check that NTRIP or Internet RTK is the selected correction source.
Does the tractor have working mobile data?
NTRIP requires a live internet connection. A signal icon alone does not prove the SIM, APN or data account is working.
Does the NTRIP client show “Connected”?
The client should be connected to the correct caster with the intended port, username, password and mountpoint.
Recheck every NTRIP field
Usernames and passwords are case-sensitive. A single wrong character, old mountpoint or blocked port can stop the connection.
Are RTCM corrections arriving and updating?
Look for incoming RTCM messages or a correction-age value that remains low and refreshes. A steadily increasing age means the stream has stopped.
What accuracy state is shown?
RTK FIX is the resolved solution. FLOAT means corrections are present but the receiver has not resolved or maintained the full carrier-phase solution.
Is the machine stationary in an open area with clear sky?
Stop for two to three minutes away from trees, buildings and grain stores. Some receivers take longer to resolve after starting or losing corrections.
Have you checked the antenna, connectors and coax?
Inspect for water ingress, loose connectors, damaged cable, crushed coax and a loose roof antenna. Substitute a known-good antenna or cable where possible.
Is the receiver definitely using NTRIP corrections?
Some systems can be set to an OEM satellite correction service instead of Internet RTK. Confirm NTRIP is selected and the RTCM input is assigned to the RTK engine.
No GPS position: check receiver power, roof antenna, coax and connectors first. If the display cannot obtain any GNSS position, the problem is with the receiver installation rather than the RTK correction service.
RTK is not enabled or selected: confirm the receiver has the required RTK activation and that NTRIP or Internet RTK is selected. A standard GPS unlock is not enough.
No working mobile data: check SIM status, APN, roaming, signal strength and account allowance. Test whether the modem can reach the internet, not only whether it shows signal bars.
You need the correct NTRIP details: use the credentials from the welcome email or customer portal. Support can resend them after verifying the account.
NTRIP still will not connect: recheck the caster, port, mountpoint and case-sensitive credentials. Confirm the SIM or firewall does not block the NTRIP port and that the receiver is sending GGA if required.
Connected but no RTCM: the mountpoint may be wrong, the receiver may not be sending GGA, the stream may be blocked or the RTCM input may not be assigned correctly inside the receiver.
The receiver has RTK FIX: if the tractor still steers badly or implements do not line up, investigate steering calibration, antenna offsets, roll compensation, implement measurements and mechanical play rather than the correction stream.
Move into open sky: trees, buildings and reflective structures can keep a receiver in FLOAT. Stop in an open area and allow several minutes for the solution to resolve.
Antenna or cable fault is likely: water ingress and damaged coax are common causes of FLOAT-only or intermittent RTK. Substitute known-good components before replacing the receiver.
RTK FIX is dropping out: watch correction age, mobile signal and receiver power. Intermittent data, loose antenna connections, poor coax, low voltage or electrical interference are common causes.
Select NTRIP or Internet RTK: enter the RTK Solutions caster details and ensure the receiver uses the incoming RTCM data rather than an OEM satellite correction service.
Further diagnosis needs the live status screens: send photos showing the receiver state, satellite count, correction age, NTRIP connection and settings. Support can then identify the next test instead of guessing.
Start the diagnosis above. Nothing is uploaded or stored.
What the symptoms usually point to
No GPS at all
Receiver power, antenna, coax, connectors, water ingress or a failed GNSS receiver.
GPS but no NTRIP connection
SIM, APN, mobile data, caster address, port, credentials, mountpoint or firewall.
NTRIP connected but no RTCM
Wrong stream, missing GGA, blocked data or the correction input not routed to the receiver.
RTK stays FLOAT
Poor sky view, wrong corrections, long baseline, antenna faults, movement during initialisation or receiver configuration.
FIX drops repeatedly
Mobile-data interruptions, rising correction age, unstable power, damaged cabling or local interference.
FIX is good but steering is poor
Machine calibration, antenna offsets, roll compensation, implement geometry or mechanical play.
Useful compatibility and setup guides
Start with the receiver and display model. The tractor badge alone does not always identify the RTK hardware fitted.
Trimble NTRIP help
Check common Trimble receivers, unlocks and whether a system can use Internet RTK.
John Deere RTK
Understand StarFire receiver and display compatibility with NTRIP-based corrections.
Compare RTK options
See when a farm base, base-free licence or another correction route makes financial sense.
Still stuck after the checks?
Send the machine details and photos of the RTK status and settings screens. The aim is to identify the next measured test, not tell you to replace expensive parts blindly.