Logging and Troubleshooting
On this page

Error Messages

Read the error in the context of the action, active mode and selected transport. A message about a rejected edit, a missing measurement, an unavailable adapter and a failed route request describes different layers.

Message/stateMeaning and next action
UnavailableProtocol field is not a usable measurement. Keep its canonical unavailable value; do not replace with zero merely to hide it.
Invalid/out-of-range edit restoredThe committed text failed the field's engineering constraints. Re-enter a valid value in the displayed units.
Enable Sending disabledCheck Viewer, active Sending, transport readiness/policy and lifecycle. Do not bypass the guard.
Manual movement activeDisable Manual movement before Autopilot Enable; selecting a file alone is not activation.
Route incomplete / import invalidInspect one ordered route, valid coordinates and bounds. Previous valid selection is preserved.
Permission denied / port busyCheck OS access and competing applications; changing CAN bitrate does not fix file permissions.
Request timed out / acknowledgment errorCheck target identity, supported service and connection. No unbounded retry or invented selectors.
Logging unhealthy / recording stoppedCheck writable storage, limits and disk health; a paused viewer is a separate state.

Make a useful report

  1. Record build/platform, mode, selected interface and exact action.
  2. Record the exact status/error and whether it occurred before/after Save, Connect or explicit authorization.
  3. Reproduce with a separate Layout and example values if possible.
  4. Include a reviewed Application Log excerpt and screenshot; never attach keys or unreviewed private Traffic logs.

For UTC date/time fields, all-ones wire dates and unavailable time sentinels must display unavailable rather than a far-future date. Valid zero remains midnight/epoch where defined. A second widget may represent a different legitimate source; inspect source identity before assuming duplication.

Illustrated controls

Unavailable is a protocol validity state, not a huge negative temperature.
Figure 92. Unavailable is a protocol validity state, not a huge negative temperature. Click to enlarge.

Application Log · NMEA Traffic Recording · Troubleshooting · Known Limitations · Connection Troubleshooting · Enable, Dispatch and Sending · Route Overview · Engineering Units

Help Home · Back to top

Image