Logging and Troubleshooting
On this page

Application Log

The Application Log records timestamped severity/category diagnostics for startup, workspace operations, generators and connections. It is separate from opt-in NMEA Traffic Recording. Open the Log Viewer from Tools; use Setup's logging preferences to control verbosity and retention.

Investigate an operation

  1. Open Log Viewer and select Application.
  2. Repeat the problem using example values where possible.
  3. Read matching timestamps, severity, category and message. Use the readable display or raw structured records as appropriate.
  4. Pause Display while examining a stable view, or click Refresh explicitly.
  5. Copy/export only the useful reviewed excerpt; redact private paths, identifiers and navigation data before sharing.

Choose useful verbosity

Optional Show Widget Signal Connections/Disconnections is off by default. Enable it temporarily when troubleshooting generator bindings: it records source/destination identities, instances and connection changes. It does not log every changing generator value.

Logs use the per-user application-data logs directory, with application.jsonl and separate traffic.jsonl. The viewer exposes the relevant location and health. Defaults are 2 MiB per Application file and 8 MiB per Traffic file, with four archives plus the current file per channel. Configurable per-file limits are bounded; queues are bounded and health/drop reporting matters.

Pause, Refresh and Clear

ControlEffect
Pause DisplaySuspends automatic display refresh; logging/recording continues independently
RefreshExplicitly reloads the selected current file even while paused
Clear → YesClears selected current file and immediately updates its view; Pause remains selected
Clear → NoLeaves file and display unchanged

Clear does not delete archives or the other channel. New records may appear again immediately if recording continues. The viewer reads a bounded tail, not unlimited history into memory. A write/rotation failure is a logging-health problem to resolve, not proof that the attempted operation succeeded.

Illustrated controls

Application verbosity, binding logging, traffic filters and per-file limits are independent preferences.
Figure 87. Application verbosity, binding logging, traffic filters and per-file limits are independent preferences. Click to enlarge.

Choose the Application channel and read entries by time, category and severity.
Figure 88. Choose the Application channel and read entries by time, category and severity. Click to enlarge.

Pause Display suspends automatic refresh. Explicit Refresh and confirmed Clear remain functional.
Figure 89. Pause Display suspends automatic refresh. Explicit Refresh and confirmed Clear remain functional. Click to enlarge.

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

Help Home · Back to top

Image