Transmit (same for transmit 1 to 20)

This page documents the [transmit1], [transmit2], …, [transmit20] configuration sections.

The device supports scheduled single-shot or periodic transfers of static CAN-bus messages. Up to 20 transmit messages can be defined.

---

Default

Below shows the default configuration of [transmit1]. The remaining transmit sections use a identical structure.

[transmit1]
transmitEnb = false             ; Enable transmit message
destination = 0                 ; 0 = None, 1 = Logger, 2 = Interface, 3 = Both
period = 2000                   ; Period in ms (DEC, 10 ms resolution)
delay = 0                       ; Delay in ms (DEC, 10 ms resolution)
extendedID = false              ; Use extended 29 bit message IDs (2.0B)
msgID = 00000001                ; Transmit message ID (HEX)
msgData = {0102030405060708}    ; Message data (HEX)

---

Fields explained

transmitEnb

Type	Options
Boolean	true, false

• true: Transmit message enabled

• false: Transmit message disabled

---

destination

The destination configures if the transmit message should be logged, forwarded to the USB-interface or both.

Note

Transmit messages are always transmitted on the CAN-bus

Type	Minimum	Maximum	Example
Integer	0	3	0

• 0: None

• 1: Messages are logged

• 2: Messages are forwarded to USB-interface

• 3: Messages are logged and forwarded to USB-interface

---

period

The transmit period in ms (milliseconds) in steps of 10 ms. If set to zero, the message will be transmitted only once (single shot).

Type	Minimum	Maximum	Example
Integer	0	4294967290	1000

---

delay

The transmit delay in ms (milliseconds) in steps of 10 ms. The delay can be used to e.g. offset messages with the same period or to delay single shot messages.

Note

If the message is periodic (not single shot), then the delay must be less than the period.

Type	Minimum	Maximum	Example
Integer	0	4294967290	0

---

extendedID

The message ID type of the transmit message.

Type	Options
Boolean	true, false

• true: Use extended ID format (29-bit)

• false: Use standard ID format (11-bit)

---

msgID

The message ID (in HEX) of the transmit message.

Type	Minimum	Maximum	Example
HEX	0	7FF / 1FFFFFFF[1]	1F4

---

msgData

The message data bytes (in HEX) enclosed by curly brackets. 0-8 data bytes can be set.

Examples of message payloads with different lengths

Length	Data	msgData
0		{}
1	0x01	{01}
2	0x01, 0x02	{0102}
3	0x01, 0x02, 0x03	{010203}
4	0x01, 0x02, 0x03, 0x04	{01020304}
5	0x01, 0x02, 0x03, 0x04, 0x05	{0102030405}
6	0x01, 0x02, 0x03, 0x04, 0x05, 0x06	{010203040506}
7	0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07	{01020304050607}
8	0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08	{0102030405060708}

---

Examples

One single-shot message.

This example demonstrates how to set up a single single-shot (period set to zero) transmit message to be transmitted 6 seconds after the device has been powered on.

Compact overview of transmit configurations

#	transtransmitEnb	period	delay
transmit1	true	0	6000

Multiple periodic messages.

This example demonstrates how to set up five periodic transmit messages each with a period time of 100 ms. The messages are delayed (offset) in time by 20 ms each.

Compact overview of transmit configurations

#	transtransmitEnb	period	delay
transmit1	true	100	0
transmit2	true	100	20
transmit3	true	100	40
transmit4	true	100	60
transmit5	true	100	80

Below timeline shows how the transmit messages are spread out in time (due to the delay).

Timeline showing when each transmit message (indicated by index) triggers

---

[1]

The maximum ID depends on extendedID. With extendedID = false, maximum becomes \(\texttt{11111111111}_{2} = \texttt{7FF}_{16}\), else \(\texttt{11111111111111111111111111111}_{2} = \texttt{1FFFFFFF}_{16}\).