Files and device descriptions
A communication recording stores observed data; a device description helps interpret it. Choose a format for your task and keep related files together when sharing.
| File | Purpose | Considerations |
|---|---|---|
.ptrc | Raw CAN-frame recording | Application decoding depends on the module and available descriptions |
.ptrbs | Modbus RTU byte-stream recording | The main file may require adjacent .sNNN.ptrbs segments |
CAN Hacker .trc | Import an existing CAN trace | Other formats with the same extension are not necessarily compatible |
.meta | User trace labels | Share it alongside the main recording |
.log | Text export of source records | Does not replace a binary trace for reopening |
| EDS/DCF | CANopen object and configuration descriptions | Does not replace a recording; share any description used separately |
See trace files for saving, loading, exporting, and hardware ISO-TP limitations. CANopen interpretation is covered on the module page.
For issue reports, distinguish an exported communication log from the application's technical log.