dbc file

Issue #27 new
Georg created an issue

Hello,

it seems some settings in the DriveByWire.dbc file are incorrect/outdated:

.) Message Throttle_Report: datasheet BrakeThrottle-By-Wire says signals PI/PC/PO are in percent, the same is true for the dbc-file but the factor is set to 1/65535 (should be 100/65535?). Similar for Brake/Throttle _Command/Report messages.

.) Message GPS 2: YEAR has a length of 7 bits in the Steer-By-Wire datasheet, but the dbc-file specifies a length of 5.

BR

Georg

Comments (5)

  1. Kevin Hallenbeck

    Hi Georg,

    Using the documents in the 20190304 release package, the YEAR field in the GPS_2_Report message appears to be consistently 7 bits across all documentation.

    To resolve the previously reported issue #23, the units for PI/PC/PO in the DBC file have been changed to "%/100" with the range of 0-1 to match the datasheet units of "%" from 0-100.

    Let me know if I missed anything.

    Thanks,

    Kevin Hallenbeck

    Dataspeed Inc.

  2. Georg reporter

    Hi Kevin,

    I had a look on that and there are two dbc-files in the release package: one in the Documentation folder, another in dSPACE\lib folder (I used that one).

    The YEAR field has a length of 7 bits in both, but the units are still % in the dSPACE\lib dbc file.

    It also seems the dbc file in the Documentation folder has a lot of additional signals defined.

    BR,

    Georg

  3. Kevin Hallenbeck

    Hi Georg,

    The dSPACE implementation usually lags behind everything else, so the DBC file in the dSPACE folder is a few versions old. We have updated the dSPACE implementation internally, and it should be part of the next release is a few weeks.

    Thanks,

    Kevin Hallenbeck

    Dataspeed Inc.

  4. Kevin Hallenbeck

    The lagging behind is not documented, but I’ll let you know when the next release comes out with an updated dSPACE blockset.

  5. Log in to comment