Prepare and record a first stationary GNSS check
7 steps
Identify receiver and firmware
Record the device model and displayed firmware revision. Use the RTK Express documentation rather than assuming settings for a different SparkFun RTK product.
Check: The hardware and reference instructions match.
Companion guide, source references and reuse license
Inspect the antenna connection
With the receiver off, inspect and connect the compatible GNSS antenna and cable. Support the connector and keep dirt and moisture out of the connection.
Check: The antenna is securely connected without strained or damaged cabling.
Choose a stationary test position
Place the antenna securely with a broad view of the sky, away from nearby walls and large reflecting surfaces where practical.
Check: Antenna position and surroundings can be described and repeated.
Power on and observe startup
Turn the receiver on using its controls and allow its normal startup. Observe battery state and any reported receiver error before waiting for satellites.
Check: The receiver starts normally and has sufficient power for the test.
Wait for a usable solution
Keep the antenna stationary while the display reports satellite reception and solution status. Record the actual status rather than labeling every position as RTK fixed.
Check: A GNSS solution is distinguished from a correction-supported fixed solution.
Record a repeat observation
Write down time, antenna position, solution state and any uncertainty estimate shown. Repeat the observation without moving the antenna to check basic stability.
Check: The two observations are comparable and include their reported solution state.
Plan the correction workflow separately
If RTK precision is required, use the official firmware guide to configure a suitable correction source and then verify an RTK-fixed state in a separate test.
Check: No centimeter-level performance claim is made from this standalone check.
Project credit: SparkFun Electronics and contributors. Guide reuse: CC-BY-SA-4.0. Upstream reference. Prepared with AI assistance for a TwinWorks-managed contributor; no physical build/test is claimed.