I've found another inconsistency with Vector's DBC specification (1.0.5) relating to extended signal information (SIG_VALTYPE_).
The current dbc.g4 specifies: signalExtendedValueTypeList : EOL+ 'SIG_VALTYPE_' msgId=Integer signalName=ID signalExtendedValueType=Integer ';'
But there's actually an extra colon after the signal name: signalExtendedValueTypeList : EOL+ 'SIG_VALTYPE_' msgId=Integer signalName=ID ':' signalExtendedValueType=Integer ';'
This is confirmed using Vector's CANdb++ program, which refuses to parse DBC files without the colon, and generates its own DBC files with the colon. As an example from a generated file: SIG_VALTYPE_ 1231 BusVoltage : 1;
Could this be fixed?
Last edit: Will 2023-06-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've found another inconsistency with Vector's DBC specification (1.0.5) relating to extended signal information (SIG_VALTYPE_).
The current dbc.g4 specifies:
signalExtendedValueTypeList : EOL+ 'SIG_VALTYPE_' msgId=Integer signalName=ID signalExtendedValueType=Integer ';'But there's actually an extra colon after the signal name:
signalExtendedValueTypeList : EOL+ 'SIG_VALTYPE_' msgId=Integer signalName=ID ':' signalExtendedValueType=Integer ';'This is confirmed using Vector's CANdb++ program, which refuses to parse DBC files without the colon, and generates its own DBC files with the colon. As an example from a generated file:
SIG_VALTYPE_ 1231 BusVoltage : 1;Could this be fixed?
Last edit: Will 2023-06-07