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 enum value for the message is specified by an integer index into the enum definition.
The current implementation just assumes a string value and copies the index as value into the property.
I couldn't find any solid information how enum values are supposed to be specified, but this is the way CANdb++ writes the dbc file.
I will try to provide a PR to handle this correctly.
The text was updated successfully, but these errors were encountered:
Brainy0207
pushed a commit
to Brainy0207/DbcParser
that referenced
this issue
Sep 25, 2023
* EFeru#47 It seems like dbc files reference the enum value by index. Changed the parser logic to pass the quoted strings to handle both cases correctly and added additional tests.
Brainy0207
pushed a commit
to Brainy0207/DbcParser
that referenced
this issue
Sep 25, 2023
I copied the relevant lines from a sample J1939 file:
It seems the enum value for the message is specified by an integer index into the enum definition.
The current implementation just assumes a string value and copies the index as value into the property.
I couldn't find any solid information how enum values are supposed to be specified, but this is the way CANdb++ writes the dbc file.
I will try to provide a PR to handle this correctly.
The text was updated successfully, but these errors were encountered: