Troubleshooting
| Symptom | Check |
|---|---|
| Device missing but ports exist | Refresh, interface recognition, other applications owning ports |
| All ports and disk disappear | Whole-device reset/disconnection or boot failure; USB/power and FBL startup logs |
| COM opening reports a device not functioning | Enumeration/reconnection state; not proof of a CAN frame error |
| Started (1/2) | The other interface's opening error |
| BEL rejection | Command parameters, mode, resource conflicts, protocol support; retain surrounding logs |
| CAN Error in Trace | Error reason and TEC/REC; peer ACK, bitrate, wiring, termination and controller state |
LIN !3 | Timeout: responder, expected length, rate and transmission completion |
| RX shows host clock time | Absolute display mode or absent MCU metadata; verify the exact build |
| Trace stops updating after scrolling | Resume display; acquisition/logging continue |
| Event row count does not grow | Existing IDs update in place; use scroll mode for ordering |
| No log file | Logger enabled/source, folder/rule and Information errors |
| Missing database on another computer | Reselect external DBC/LDF/replay paths |
Errors describe symptoms, not necessarily root causes. CAN timeout alone does not establish a firmware scheduler defect.
CAN errors appear in Trace without automatically stopping measurement. Firmware timestamps the error interrupt and captures controller registers; on a TX timeout or Bus-off the host pauses CAN transmission, shows "TX paused" on the CAN status chip and stops periodic sender rows; single bus errors are only shown in Trace. On TX timeout, firmware cancels the pending request and preserves reception. LIN, UART and logging continue. Correct the peer measurement state, bitrate or wiring, then manually stop and restart measurement to resume sending. A Bus-off controller itself cannot communicate until reinitialized. This behavior requires the matching CAN Error firmware; an actual USB/device disconnection still stops measurement.
Classic CAN mode rejects FD transmission; listen-only mode rejects transmission. Node simulation checks the complete cyclic batch before startup, and the shared send path guards manual frames, schedules and online replay. FD requires a peer with matching format and bitrates; classic-only traffic does not require an FD-capable peer.
Isolate transmission failures
Keep the complete Start-to-Stop Information log and record ID, period, frame format, and bytes. Disable simulation, replay, and unrelated cycles. Test one manual frame, verify the peer and bus settings, then add one slow cyclic task and increase load gradually.
Use MCU timestamps or a bus analyzer for timing, not host log arrival times. If traffic persists after an abnormal exit, first identify its source; host tasks and MCU tasks run in different places. Reconnect and stop/clear tasks with simulation and replay off.
Disk failures and problem reports
Out-of-memory copy dialogs, 0x80070022, 0x800701B1, and zero-byte files do not by themselves prove low host RAM. Check whether the whole USB device disconnected. Formatting is not a routine post-update step and cannot repair missing USB enumeration or an application that fails to boot.
Provide host version, App version/compile time, bridge versions, hardware and wiring, project configuration, and full Information logs. Include ASC/BLF for timing issues and package name/SHA256 plus FBL boot logs for update issues. Do not include passwords or update keys.