Reports and export

Turn the current project into a document that can leave the bench: an HTML, Markdown or PDF report, a CSV table or a project dump.

Reports

• File → Create report... generates a report for the open project.
• Formats: HTML, Markdown and PDF.
• The dialog can be resized; after creation the report opens by default.
• PDF export renders through Microsoft Edge in headless mode, so no extra PDF library is required.
• The report uses the current project data and values already read; it does not start a diagnostic session on its own.

Reports are useful for a job record, a handover between shifts or a support ticket. Keep the project dump next to the report when the raw values matter.

CSV

Source	Contents
ECU List → Save/Load → Export CSV	Current ECU table. Separator ;, and every row also ends with ;
Measurement Values → Save to CSV	Selected parameters, one per line: "Name","DID","Value Unit", no header row

CSV is for exchange, not for restoring a project. Use .bmprj, .bmecu and .bmdump for full state.

Dumps

• Save Data writes a .bmdump file with the cached ECU values.
• Load Data restores a dump into the project for comparison or offline analysis.
• The dump key is the ECU txid; DID values are stored as the full hex buffer, including the 62 DID_H DID_L header.

Logs

Every session writes a log into <workspace>/logs/. Lines look like [HH:MM:SS.mmm] TAG: message; CAN/UDS traffic uses >> and <<. The Log & Console panel has Clear, a text Filter, Auto-scroll, Save and Save As. A saved log starts with a [build] line containing the application version, configuration and build date, which is the fastest way to tell old builds apart.

Related

• Diagnostics and DTC
• Live measurements
• File formats