Key Log Types for Post-Integration Validation of Automotive DCMs

CAN Logs

• Purpose: Monitor communication between ECUs (e.g., ignition, GPS trigger, vehicle speed)
• Tools: Vector CANoe, CANalyzer, Kvaser, PEAK, PCAN-View
• Format: .blf, .asc, .log

DLT Logs (Diagnostic Log and Trace)

• Purpose: Track internal software activity on Linux-based TCU systems
• Tools: DLT Viewer (GENIVI), OEM-specific viewers
• Format: .dlt (GENIVI-compliant)

Modem & Cellular Logs

• Purpose: Analyze cellular/Wi-Fi connectivity, handovers, signal strength, SIM state
• Tools: Qualcomm QXDM, QCAT, AT command log tools
• Format: .isf, .txt, .log

PCAP Logs (Network Packet Capture)

• Purpose: Inspect data traffic (e.g., OTA updates, cloud communication, V2X messaging)
• Tools: Wireshark, tcpdump
• Format: .pcap, .pcapng

GNSS Logs

• Purpose: Validate positioning accuracy, satellite lock, fallback behavior
• Tools: u-blox u-center, Quectel GNSS Tool, GNSS Logger
• Format: .nmea, JSON, binary

System Logs (Linux / Android)

• Purpose: Monitor OS-level events, crashes, service restarts
• Tools: journalctl, dmesg, adb logcat
• Format: Standard Linux logs, logcat output

OTA Update Logs

• Purpose: Track OTA progress, errors, and rollback status
• Tools: DLT Viewer, cloud platform logs (e.g., AWS IoT, Azure IoT Hub)
• Format: Embedded log + cloud logs

Summary Table