10.2 | GNSS & Position Issues
| Issue |
Possible Cause |
Recommended Action |
| No GNSS position detected |
Receiver harness disconnected |
Verify GNSS receiver harness connections |
| No GNSS position detected |
Receiver not powered |
Verify GNSS receiver/display powers on correctly |
| No GNSS data after startup |
Receiver still initialising |
Allow receiver sufficient time to initialise and acquire satellite lock |
| Receiver powers on but no data detected |
Incorrect serial/CANreceiver output connection or configuration |
VerifyFor NMEA 2000 receivers, verify connection to the correct receiverCANBUS port operating at 250 kbps. For NMEA 0183 receivers, verify the correct serial output port isand baud rate are configured and connected |
| Receiver powers on but no data detected |
Incorrect RS232 baud rate configuration |
For NMEA 0183 receivers, verify the configured serial baud rate matches the Level COMMAND receiver configuration |
| Receiver powers on but no data detected |
Incorrect CANBUS connection or baud rate |
For CANBUS/NMEA 2000 receivers, verify the receiver is connected to the correct CANBUS network operating at 250 kbps |
Receiver powers on but no data detected
Incorrect serial/CAN output port selected
Verify the correct receiver output port is enabled and connected
Receiver powers on but no data detected
NMEA output messages not enabled
Verify required NMEA output messages are enabled within the receiver/display configuration
Position updates slowly
Low output rate configured
Configure receiver output rate to minimum 5 Hz; 10 Hz recommended
No RTK corrections
Incorrect base station selected
Verify the implement receiver is connected to the intended base station or correction source
No RTK corrections
Base station not transmitting corrections
Verify base station operation and correction output
No RTK corrections
Incorrect base station configuration
Verify base station radio/modem and correction output configuration
No RTK corrections
Incorrect implement receiver configuration
Verify correction source, radio/modem and RTK settings within the implement receiver
RTK intermittently lost
Poor correction radio signal
Inspect correction antenna placement and cable condition
RTK intermittently lost
Excessive distance from base station
Reduce distance to base station or verify correction coverage
RTK intermittently lost
GNSS quality thresholds configured too aggressively
Verify Level COMMAND GNSS requirement settings are suitable for current operating conditions
Poor accuracy or drifting
Low GNSS correction quality
Verify RTK/DGNSS correction status
Poor accuracy or drifting
Multipath or obstructed sky view
Move machine to open sky area clear of obstructions
GNSS accuracy degraded unexpectedly
Receiver operating in Float/DGNSS mode
Verify RTK Fix status before operation
Position intermittently lost
Damaged harness or loose connector
Inspect GNSS harnessing and connectors
Position quality degraded
Receiver firmware outdated
Verify GNSS receiver firmware is up to date
Position appears offset
Incorrect base station coordinates
Verify configured base station coordinates
Position appears offset
Connected to incorrect base station
Verify the implement receiver is connected to the correct base station
Position appears offset
Incorrect receiver offsets configured
Verify receiver height, fore/aft and lateral offsets within Level COMMAND
Cross-slope or terrain response incorrect
Incorrect IMU or receiver assignment
Verify GNSS and IMU configuration within Level COMMAND
Terrain compensation inaccurate
TCM/IMU calibration not completed
Perform TCM/IMU calibration according to manufacturer instructions
Terrain compensation inaccurate
Incorrect machine orientation during calibration
Perform calibration on level ground away from vibration
Terrain compensation unstable
IMU mounted on flexible surface
Mount IMU to a rigid surface isolated from excessive vibration