CSS CANedge2 - Page 41

CANedge2 Docs, Release FW 01.04.02
Message ID mask (hex) properties.id_mask
ID mask of the control message in hex. Example: 1FFFFFFF.
type: string default: 1FFFFFFF
Data mask (hex) properties.data_mask
Data trigger mask (byte 0 to the left). Shall match the length of the control signal message.
type: string maxLength: 16 default: FFFFFFFFFFFFFFFF
Data trigger high (hex) properties.data_high
Data trigger high range (byte 0 to the left)
type: string maxLength: 16 default: 0100000000000000
Data trigger low (hex) properties.data_low
Data trigger low range (byte 0 to the left)
type: string maxLength: 16 default: 0000000000000000
Configuration explained
This section contains additional information and examples.
The control signal has a flexible configuration allowing for integration with many protocols. The control
signal can be set to control the device message reception (effectively the logging) and / or the transmission
(effectively the processing of the transmit list). The control signal can e.g. be used to start / stop logging
based on some application parameters, such as speed, RPM or discrete events.
Control signal overview:
• A control signal can be setup for each CAN-bus channel
• One message ID is used for start and one for stop. These can be different or the same
• The message ID can be masked to trigger on a partial ID match (this allows for e.g. J1939 messages
with unknown source)
• The data trigger can be masked to support CAN-bus frames with multiple signals
• The date trigger uses a high/low range, such that any value in the range will trigger (this allows
for e.g. stop logging when speed is in range 0-10 km/h)
• File splitting is not affected by the control signal (i.e. the control signal does not force additional
log file splits)
Note: The control signal can only be used if accepted by the CAN-bus filter
Note: The control signal data byte fields must match in length vs. the message data
0.4. Configuration 37