Logging and Troubleshooting
On this page

Troubleshooting

Start with the smallest failing workflow. Preserve the last valid Layout/route and settings; do not reinstall dependencies or reset preferences to mask an unexplained problem.

Common workflow checks

SymptomCheck in order
Generator runs, instrument does not changeGenerate mode, source Enable, Dispatch, compatible mapping, matching instance, destination lifetime; use optional binding lifecycle logging
Instrument changes, no external dataIndividual Enable/interval, explicit global Sending, transport readiness/policy, supported encoder; local simulation does not imply TX
Autopilot checkbox disabledManual movement off, valid selected route, engine/profile/gear readiness and mode. A field named Path may be the imported route's real internal name.
Weather fails while movingRead provider error, valid request coordinates and bounded movement freshness. Normal movement is allowed; large relocation invalidates geographically stale results.
Unexpected extra RX widgetInspect PGN, source address/NAME, instance and identity fields; different sources must stay distinguishable
Saved value changes at loadInspect Template Saved Value/Setup Default policies and eligible generator samples; global Sending stays off
Custom theme absentCorrect external .qss directory/extension; reopen Setup to rediscover; check readability and stylesheet validity
Old log remains after ClearChoose current channel and confirm Yes; explicit Clear/Refresh must work even with Pause selected

Linux Serial Port Permissions

CANable SLCAN and other USB serial adapters commonly appear as /dev/ttyACM* or /dev/ttyUSB*. A permission error can mean insufficient device access or another application holding the port; Qt does not always distinguish these cases. Stop Sending before troubleshooting.

  1. Replace the example path with your actual selected device. Check ownership and permissions with ls -l /dev/ttyACM0. Check your effective session groups with id -nG (or groups).
  2. The owning group is commonly dialout. The actual device-owning group shown by ls -l takes precedence if it differs. Ask your administrator when the correct access policy is unclear.
  3. Only when appropriate to your system and device ownership, an administrator can add your normal desktop account with sudo usermod -aG dialout "$USER". Substitute the actual authorized device group when different. Log out completely and log back in, then check id -nG again; restarting the application alone does not renew session groups.
  4. Check whether another application owns the serial interface, for example with fuser /dev/ttyACM0 or lsof /dev/ttyACM0 when installed. Lack of output is not proof that no other user or process holds it. Close the competing serial monitor or application normally.
  5. Refresh ports, select the actual device, and reconnect explicitly after correcting access. Reconnection does not grant Sending authorization.

RayNmeaSimulator does not change user groups, device ownership, udev rules or permissions. Do not run the application as root or make devices world-writable to bypass access restrictions.

Controlled reproduction

  1. Stop/F12 and disconnect external hardware if it is unnecessary to reproduce.
  2. Use an isolated test profile or an intentionally disposable workspace; back up valuable files before replacement.
  3. Add the smallest relevant instrument and optional generator. Try both creation orders when a binding is involved.
  4. Compare display, Property Editor canonical value and Object Tree. Check unavailable versus genuine zero.
  5. Inspect Application Log; enable connection/disconnection detail temporarily when needed.
  6. Record expected/actual behavior and restore only the settings you intentionally changed.

For a display problem, include the selected theme, desktop scale and window size in your report. Try a built-in theme and resize the window before changing unrelated settings.

Illustrated controls

Viewer entry offers Clear, Keep Existing or Cancel. Sending is revoked before this choice.
Figure 93. Viewer entry offers Clear, Keep Existing or Cancel. Sending is revoked before this choice. Click to enlarge.

Autopilot route selection, speed source and waypoint progress controls.
Figure 94. Autopilot route selection, speed source and waypoint progress controls. Click to enlarge.

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

Help Home · Back to top

Image