You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems the GUI is unable to handle DBC files with mixed signals (i.e. both J1939 PGNs and e.g. standard 11-bit IDs or 29-bit IDs). Potentially this relates to the GUI/canmatrix relying on the ProtocolType field to determine if a DBC is J1939 or not, rather than basing it off the vFrameFormat attribute marking a specific message ID as a J1939PG type or not.
Seemingly the issue is not replicable in the latest canmatrix code, but it appears to be an issue in the latest asammdf GUI release 7.3.16, making me assume it's related to the asammdf GUI being dependent on an older canmatrix version.
The text was updated successfully, but these errors were encountered:
As per ebroecker/canmatrix#729
It seems the GUI is unable to handle DBC files with mixed signals (i.e. both J1939 PGNs and e.g. standard 11-bit IDs or 29-bit IDs). Potentially this relates to the GUI/canmatrix relying on the ProtocolType field to determine if a DBC is J1939 or not, rather than basing it off the
vFrameFormat
attribute marking a specific message ID as a J1939PG type or not.Seemingly the issue is not replicable in the latest canmatrix code, but it appears to be an issue in the latest asammdf GUI release 7.3.16, making me assume it's related to the asammdf GUI being dependent on an older canmatrix version.
The text was updated successfully, but these errors were encountered: