Prevent unsupported signal types from producing valid but incorrect decoded values #33

Closed
opened 2026-10-24 00:46:36 +00:00 by deeaitch · 0 comments
Owner

The parser ignores SIG_VALTYPE_ statements with an UnsupportedStatement warning. The affected signal remains available for integer decoding, which can produce an incorrect value marked as valid.

ParseFileWithDiagnostics() exposes the warning, but ParseFile() discards warnings and returns the database. The demo also uses Pars

BO_ 1 FloatFrame: 4 ECU
 SG_ Value : 0|32@1+ (1,0) [0|100] "" ECU
SIG_VALTYPE_ 1 Value : 1;

Build the runtime decode database.
Decode CAN ID 1 with payload bytes 00 00 80 3F, representing IEEE 754 float32 1.0.

The parser ignores SIG_VALTYPE_ statements with an UnsupportedStatement warning. The affected signal remains available for integer decoding, which can produce an incorrect value marked as valid. ParseFileWithDiagnostics() exposes the warning, but ParseFile() discards warnings and returns the database. The demo also uses Pars ``` BO_ 1 FloatFrame: 4 ECU SG_ Value : 0|32@1+ (1,0) [0|100] "" ECU SIG_VALTYPE_ 1 Value : 1; ``` Build the runtime decode database. Decode CAN ID 1 with payload bytes 00 00 80 3F, representing IEEE 754 float32 1.0.
deeaitch referenced this issue from a commit 2026-10-24 00:55:24 +00:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: automotive/dbc#33