extract_bus_logging MF4 format requirements #1152
-
|
I am currently transitioning from using the CSS Electronics loggers, to my own logger application that writes CANbus data in MF4 format. The AsamMDF library has been fantastic and we have built some useful tools around it's ability to process CAN log files. I am currently running into some issues when applying DBCs to the MF4 files created by our in-house logger. It appears that it is caused by the function being unable to determine the bus type, but our MF4 structure appears setup just like the CANEdge-produced files in this regard. I am able to open a CANbus trace with my generated MF4 files in asammdf GUI, but I cannot apply DBCs through the GUI either. Is some piece of information missing in my Source Information or metadata blocks? Error when running extract_bus_logging: Example layout of my MF4 structure: Example CAN trace in asamMDF GUI with my generated MF4: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Of course, when you ask for help you end up shortly figuring it out... My non-Data Frame channel groups did not have source information blocks with bus_type defined. Once all my channel groups had the source information defined, the extract_bus_logging() function ran as expected.
|
Beta Was this translation helpful? Give feedback.
Of course, when you ask for help you end up shortly figuring it out...
My non-Data Frame channel groups did not have source information blocks with bus_type defined. Once all my channel groups had the source information defined, the extract_bus_logging() function ran as expected.