Skip to content

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.

FilePurposeConsiderations
.ptrcRaw CAN-frame recordingApplication decoding depends on the module and available descriptions
.ptrbsModbus RTU byte-stream recordingThe main file may require adjacent .sNNN.ptrbs segments
CAN Hacker .trcImport an existing CAN traceOther formats with the same extension are not necessarily compatible
.metaUser trace labelsShare it alongside the main recording
.logText export of source recordsDoes not replace a binary trace for reopening
EDS/DCFCANopen object and configuration descriptionsDoes 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.

Protohaund is independent software and is not affiliated with, endorsed by, sponsored by, or certified by any third-party organization referenced in the application.Third-party names, trademarks, product names, device names, protocol names, and standards are referenced solely to identify vehicle applicability, supported products, technologies, protocols, formats, or compatibility.All third-party trademarks and other marks are the property of their respective owners. Their use does not imply any affiliation with, endorsement of, certification of, or approval of Protohaund by their respective owners.Compatibility is limited to the features, devices, protocols, standards, and versions explicitly documented by Protohaund.