38 Process Image
WAGO-I/O-SYSTEM 750
750-658 CAN Gateway
Manual
Version 1.2.1, valid from FW/HW-Version 01/01
If the "2.0A Standard Frame" is activated, CAN telegrams have the following
structure:
Table 19: Structure of CAN Telegrams with the "2.0A Standard Frame" Setting
Byte Name
Bits
0 Identifier
byte 1
ID.10 ID.9
ID.8
ID.7
ID.6
ID.5
ID.4
ID.3
1 Identifier
byte 2
ID.2
ID.1
ID.0
RTR DLC.3 DLC.2 DLC.1 DLC.0
2 Data
TR/RX Data Byte 1
3 Data
TR/RX Data Byte 2
4 Data
TR/RX Data Byte 3
5 Data
TR/RX Data Byte 4
6 Data
TR/RX Data Byte 5
7 Data
TR/RX Data Byte 6
8 Data
TR/RX Data Byte 7
9 Data
TR/RX Data Byte 8
If the "2.0B Extended Frame" setting is activated, CAN telegrams have the
following structure:
Table 20: Structure of CAN Telegrams with the "2.0B Extended Frame" Setting
Byte Name
Bits
0 Identifier
byte 1
RES RES RES ID.28 ID.27 ID.26 ID.25 ID.24
1 Identifier
byte 2
ID.23 ID.22 ID.21 ID.20 ID.19 ID.18 ID.17 ID.16
2 Identifier
byte 3
ID.15 ID.14 ID.13 ID.12 ID.11 ID.10 ID.9
ID.8
3 Identifier
byte 4
ID.7
ID.6
ID.5
ID.4
ID.3
ID.2
ID.1
ID.0
4 Identifier
byte 5
IDE
RTR RES RES DLC.3 DLC.2 DLC.1 DLC.0
5 Data
TR/RX Data Byte 1
6 Data
TR/RX Data Byte 2
7 Data
TR/RX Data Byte 3
8 Data
TR/RX Data Byte 4
9 Data
TR/RX Data Byte 5
10 Data
TR/RX Data Byte 6
11 Data
TR/RX Data Byte 7
12 Data
TR/RX Data Byte 8
The actual length of the data to be transmitted is based on the length of the user
data. It may vary.
