Repository navigation
User Manual Diagnostics
Hold → DIAGNOSTICS. Four pages, swipe between them.
| Page | Reports |
|---|---|
| System | Firmware version, uptime, why it last restarted, free memory |
| GNSS | Fix type, satellites, accuracy, rate, queue depth and losses |
| Logging | Card state, free space, write failures, write latency |
| Peripherals | Display, touch, motion sensor, clock chip |
Almost certainly the circuit is provisional. Check the track line on the Ready screen. See Tracks.
The device cannot tell you, and the status line says which of two reasons:
- NO RECEIVER — nothing is arriving. A connection or power problem.
- NO FIX — the receiver is working and has not located itself yet. Give it a clear view of the sky and up to a minute from cold.
They are deliberately different messages because they are different problems.
Correct. The heading comes from your direction of travel, and a stationary car has none. The device has no magnetic sensor, so it cannot tell you which way you are facing — only which way you are going. Drive, and the marker appears.
The receiver stopped reporting part-way through. The number is where the run had got to, not a result, which is why it is red rather than green - a run that lost its fixes stops counting in exactly the way arriving at the target does, and the two must never look alike.
Tap to reset, give the receiver a clear view of the sky, and run again.
The fix is fine. The receiver is simply not confident enough about how fast you are going to measure against - and a time produced then would be a reading of its uncertainty rather than of the car. Common under trees, between buildings, or shortly after a cold start.
Correct. It reads GMT all year and is labelled GMT on screen. British Summer Time is
not applied, and there is no timezone setting yet.
The receiver has gone quiet and the clock is running on its own crystal, with how long it has been doing so. It is still close to right — but it is no longer satellite time, which is why it says so rather than carrying on silently.
Check you are holding, not tapping, to open the menu — a tap on the dashboard does nothing by design. Inside a carousel, if swiping is not registering, the arrows at each edge are buttons you can tap instead.
Check the Logging diagnostics page. Missing card, full card and write failures are each reported separately. The Ready screen also shows logging availability before you go out.
The System page reports why the device last restarted — power-on, software, watchdog, brownout or panic. A brownout points at the power supply rather than the firmware; repeated watchdog or panic restarts are worth reporting with what you were doing at the time.
Issues go to the project tracker.
What helps most:
- Which mode you were in and what was on screen
- What the Diagnostics pages said, particularly System and GNSS
- Whether it is repeatable, and what you did just before
The firmware version is on the System page.