Will

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...

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...

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 semicolon after the signal name: signalExtendedValueTypeList : EOL+ 'SIG_VALTYPE_' msgId=Integer signalName=ID ':' signalExtendedValueType=Integer ';' This is confirmed using Vector's CANdb++ program,...