Troubleshooting Lite

There is no Emlid Reach button in the connect step — the app is in Ditch Assist mode. Open Settings → Mode and tap Ditch Assist Lite. The Reach is never offered in Ditch Assist mode.

"Stop grading before switching mode." — automatic guidance is running. Tap STOP on the Grade screen, then switch.

"Tablet isn't on a Reach hotspot…" — join the reach:XX:XX network (password emlidreach) in the tablet's Wi-Fi settings. Android may have hopped back to the farm or shop Wi-Fi; check which network you are on before tapping Emlid Reach again.

"Reach found, but no NMEA TCP output is configured." — in Emlid Flow, set Position output to TCP, Server, port 9001, NMEA, with GGA and VTG at 5 Hz. See Setting up the Reach.

"Reach found, but the NMEA port refused the connection." — the Reach reports a TCP Server NMEA output, but that port did not accept the connection: the output is switched off or still starting. Turn it on in Emlid Flow (or wait a few seconds) and try again.

The Reach drops every few minutes — almost always the Samsung Switch to better Wi-Fi networks setting. Turn it off under Settings → Connections → Wi-Fi → Intelligent Wi-Fi. The app warns about this once when it connects; the Open Wi-Fi settings button in that notice takes you to the switch. Also make sure you chose Always stay connected when Android warned the hotspot has no internet.

"Couldn't read the receiver ID…" — the Reach was still booting when the tablet connected. Wait a few seconds and tap Retry. Make sure Location is turned on in the tablet's settings.

START only opens the activation screen — this receiver has not been activated yet. Complete Activating a receiver. Until then the app treats the Reach as a plain GPS.

Pre-Flight Checks shows "Not activated" in amber — same cause. Tap the Activate button beside it.

"That code doesn't match this receiver." — re-check the digits. Codes are issued per receiver: a code for another Reach, or one generated from a different receiver's request code, will not work here.

"Too many attempts — try again in N s" — five wrong codes in a row. The wait starts at 60 seconds, doubles with each further wrong code, tops out at an hour, and survives restarting the app. Let the countdown finish, then enter the correct code once.

No Raise / Lower or Hold / Resume buttons — expected. Lite has no hydraulics to command. Use the machine's controls, with Auto-Nudge or manual nudge to stage the cut.

Guidance drifts as soon as you raise or lower the blade — the Reach is probably on the cab. Move it to a mast on the blade, moldboard, bowl, or attachment (see Mounting the Reach) and calibrate again.

Excavation readings change when you move the stick or bucket — expected in Lite: the app follows the Reach antenna, not the bucket tip. Check grade from the same stick and bucket position every time — the one you calibrated in.

"RTK LOST — GUIDANCE PAUSED" / "GPS STALE — GUIDANCE PAUSED" while grading — the receiver lost its RTK fix, or stopped sending positions. Guidance freezes until it recovers, then the warning clears itself. If it keeps happening, check the Reach's correction link (NTRIP or LoRa) in Emlid Flow.

Chevrons and GPS badge look dimmed — the position feed has gone stale; this is the few-second window before the 10-second watchdog. If it does not recover, the app drops the connection, the badge shows disconnected, and the app retries the Reach every 2 seconds in the background — check that the tablet is still on the Reach hotspot.

Levee opens the activation screen when you try to follow contours — generating and following contours needs an activated Reach. Activate it first.

Moving to another tablet — activate the receiver on the new tablet with the same unlock code. Codes belong to the receiver, not the tablet.