Hi Daniel, adding this here as well for tracking purposes.
I did some tests in asammdf v7.3.13.dev9 and in asammdf v7.2.0 with some J1939 PGN conversion. It seems that there is an issue with the matching of the J1939 PGN. Specifically, the sample data zip I sent you has a log file containing 'extended OBD2 data' (which can be handled similarly to J1939 data) and a corresponding DBC file.
The data is correctly matched by the DBC if the DBC is modified to have the exact 29-bit CAN ID as the data has. But it should match based on just the 18-bit PGN - which is not happening. It would be great to get a resolution for this.
Hi Daniel, adding this here as well for tracking purposes.
I did some tests in
asammdf v7.3.13.dev9
and inasammdf v7.2.0
with some J1939 PGN conversion. It seems that there is an issue with the matching of the J1939 PGN. Specifically, the sample data zip I sent you has a log file containing 'extended OBD2 data' (which can be handled similarly to J1939 data) and a corresponding DBC file.The data is correctly matched by the DBC if the DBC is modified to have the exact 29-bit CAN ID as the data has. But it should match based on just the 18-bit PGN - which is not happening. It would be great to get a resolution for this.