A collection of programms to parse various files into a .asc format for further use (specifically in Xentry Can Tool)
Find a file
2026-03-19 10:44:11 +01:00
.gitignore first commit 2026-03-18 23:33:06 +01:00
HUD_ECU_Hacker.py Made file names more modular. 2026-03-19 10:44:11 +01:00
README.md Added examples 2026-03-19 10:38:59 +01:00
requirements.txt added Requirements.txt and added a bit of explanations in readme 2026-03-19 10:24:39 +01:00
socketcan_log.py Made file names more modular. 2026-03-19 10:44:11 +01:00

A simple Collection of Programms that can convert to .asc files

The main intrest was to be able to take all kind of Log files and import them into the official MB Xentry CAN-Tool. (It does complain about the series description not matching, but otherwise it works)

It probably could be generated by AI (although its not), since it also largely relies on the python can libary and has quite little own code.

HUD_ECU_HACKER.py

For log files created by the sniffing mode of HUD ECU Hacker.

Input: Command line argument with file name (.htm)

Output: .asc file with the same Can Frames and relative times

If you get a ValueError("Frames not in order."), you can comment anything with time out and and replace rel_time with idx in the can Message creation. This could be a issue with the time parsing.

Tiny unrelated Tip: If you want to capture a non OBD-Port accesible can-bus, with a Tatrix Openport, and get errors about the Voltage, Plug into OBD, open connection, then unplug and do CAN-monitoring

socketcan_log.py

For logs created with the candump utility of Socketcan Tools.

Input: Command line argument with file name (.log)

Output: .asc file with the same Can Frames and relative times

If you have more than one CAN-Bus in the dump, you should uncomment the can checker if.

Example source files

At the top of each file you can find some shotened example files, done by me at the time of creation. These don't necesarily mean this is the only compatible fileformat.