Signal

Several configuration sections use a similar structure for configuring a signal interpretation (decoding). Different conventions defining signal interpretation exists. The CANedge configuration adopts the convention used by .DBC files.

Below example demonstrates how the interpretation of signal Epoch from message GnssTime (ID 102) defined in a .DBC file is entered in the configuration file.

The .DBC file section describing the GnssTime message (ID 102) is:

Section of a DBC file
BO_ 102 GnssTime: 6 Vector__XXX
 SG_ TimeValid : 0|1@1+ (1,0) [0|1] "" Vector__XXX
 SG_ TimeConfirmed : 1|1@1+ (1,0) [0|1] "" Vector__XXX
 SG_ Epoch : 8|40@1+ (0.001,1577840400) [0|0] "sec" Vector__XXX

The signal interpretation of Epoch signal is defined by the final line. The line is explained below:

../_images/aafig-1cd53848c9bf7148781bafe377d0691c0beede8f.svg

Bit position, length, factor and offset can be copied directly into the configuration file. Byteorder and Data type are defined by the following mappings:

Byteorder

DBC value

Byteorder

0

Motorola

1

Intel
Data type

DBC value

Byteorder

+

Unsigned

-

Signed

Warning

GUI tools supporting the DBC file format may use a different convention for displaying e.g. bit-position. It is recommended to use the information directly from the .DBC file when configuring the CANedge.