Applies to:
WaveView Connect, WaveRadar Rex, Datawell systems, TCP/serial infrastructures.
Explanation:
The debug log is a primary diagnostic tool in WaveView Connect (Ref: Debug Log Notes). In standalone mode, right-clicking the main UI window opens the log, which records startup events, license validation, driver recognition, timestamp parsing, and performance counters. Logs should run for at least 5–10 minutes during troubleshooting to capture message stability and intermittent issues.
Additional notes:
Always gather logs over several minutes to capture intermittent behaviours.
Using the Web UI for Range Settings, Parameters, and Display Modes
Troubleshooting:
- If no debug window appears → confirm that the standalone version is installed alone; the service version block UI access.
- If logs show repeated decoding failures → review driver configuration, baud settings
- If licensing warnings appear → verify licence.xml is valid and system date/time are correct.
- If timestamps appear “out of sequence” → investigate NTP or motion-sensor clock drift.
- If sensor data stops unexpectedly → check for COM-port resets, USB power interruptions, or Windows power-saving policies. For remote support, include debug logs, conf.xml, licence.xml, and recent data samples to enable comprehensive diagnostics.