Receiver
Base position (ARP)
Outputs
Raspberry Pi
Connected rovers 0
| Client | Rover status | Baseline | From | Time | Sent |
|---|
Satellites
Signal strength (C/N0, dB-Hz). Faded bars = not used in the solution.
RTCM messages
| Type | Meaning | Every | Last | Count |
|---|
Clients
Each client gets an NTRIP username and password. Disabling, expiring or deleting an account cuts its live connection within seconds.
| Client | Status | Expires | Conn. | Last seen | Usage |
|---|
1 · Survey-in
The receiver averages its own position until both the minimum time and target accuracy are met, then starts sending corrections. Good for getting going fast; absolute accuracy is only as good as the averaged fix (≈0.5–2 m).
2 · Fixed position
Use a known coordinate (benchmark, or a PPP result from the raw log below). Rovers that come back to the same field every season then get the same coordinates. Height is ellipsoidal (WGS84/ITRF), not sea level.
RTCM output
Raw logging (for PPP)
Records RAWX/SFRBX to a .ubx file. Log 4–24 h with the antenna fixed, convert to RINEX (RTKLIB convbin) and upload to a PPP service (e.g. NRCan CSRS-PPP) to get an absolute coordinate for “Fixed position”.
Receiver
Settings sent from this page are saved to the receiver's flash, so they survive power cuts.
Turns the ZED-F9P back into a rover. Corrections stop for all clients.
Events
Connection history
| Client | Start | Duration | Data | End |
|---|