0

I'm trying to load this MF4 (MDF) file into asammdf GUI to extract its signals. The MF4 was created with Python using J1939 data extracted from a vehicle. The MF4 loads correctly into asammdf GUI, and in the Bus Logging tab I've loaded a DBC dictionary. When I use 'Extract Bus Signals', I get the message:

CAN bus summary:

  • 0 of 0 IDs in the MDF4 file were matched in the DBC and converted
  • no unknown IDs inf the MDF4 file

It appears asammdf does not recognize the ID column, probably because it is incorrectly formatted. What requirements are missing in this MF4 file for the ID column to be correctly interpreted as IDs?

  • Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. – user11717481 Nov 21 '22 at 19:15
  • the problem seems to be with the DBC file. Does it contain messages? – danielhrisca Nov 22 '22 at 08:09
  • It contains J1939 messages (ID, payload...). I used [your code here](https://stackoverflow.com/a/66681944/17029705) along with data obtained with a CAN sniffer and parsed from a proprietary format. [My code here](https://github.com/Tyronnosaurus/J1939-Decoder). – teddysaurus Nov 22 '22 at 10:55
  • Sorry, read MDF instead of DBC. The DBC dictionary is [this one](https://github.com/nberlette/canbus/blob/main/dbc/j1939.dbc) and also the sample dowloadable [here](https://canlogger.csselectronics.com/canedge-getting-started/log-file-tools/). – teddysaurus Nov 22 '22 at 11:09

0 Answers0