| #1 | Shared communication path, ACK topology, gateway, or common-power fault | Check first | - BUS_TRAFFIC_LOST: No CAN frame from this channel reached the capture for 1048 ms; adaptive limit=1000 ms. This does not distinguish an idle bus from a capture-path interruption.
- No channel traffic was observed after the fault: CAN2
- Only one attributable ID was present on this channel and all traffic stopped after the fault; observed frames alone cannot distinguish a node stop from a shared-path outage.
| - Several IDs becoming silent together confirms a shared scope, but observed traffic alone cannot distinguish cabling, ACK topology, gateway, common power, or coordinated transmission stop.
| Compare stop and recovery boundaries for other IDs on the channel, then isolate the cause with a known-good ACK node, cable, and power measurements. |
| #2 | Target-node task, operating mode, or transmit period changed | Check next | - UNRESOLVED_AT_END: No CAN2 ID 0x123 frame was observed for at least 11.048 s before the package ended; host-arrival baseline=13.587 ms, forensic threshold=250.000 ms.
- CAN_MESSAGE_TIMEOUT: Auto-learned host period≈14.041 ms, Last seen 323 ms ago, timeout=250 ms, estimated missed periods≈23.
| - A single-ID full-silence case has no continuing channel traffic as counter-evidence, so a target-node task fault cannot be prioritized.
| Compare node mode and transmit-task logs; confirm whether this ID may switch between 10 and 200 ms, then set limits from the manufacturer's timing specification. |
| #3 | Configuration or diagnostic thresholds do not match the network | Additional check | None reported | - No additional counter-evidence is available; perform the next validation action.
| Verify the DBC, manufacturer timing specification, bit timing, and trigger thresholds; first confirm that the message is periodic rather than event-driven or burst traffic. |
