36
Process Image
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
Identifier
0
byte 1
Identifier
1
byte 2
2
Data
3
Data
4
Data
5
Data
6
Data
7
Data
8
Data
9
Data
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
Identifier
0
byte 1
Identifier
1
byte 2
Identifier
2
byte 3
Identifier
3
byte 4
Identifier
4
byte 5
5
Data
6
Data
7
Data
8
Data
9
Data
10
Data
11
Data
12
Data
The actual length of the data to be transmitted is based on the length of the user
data. It may vary.
ID.10
ID.9
ID.8
ID.2
ID.1
ID.0
TR/RX Data Byte 1
TR/RX Data Byte 2
TR/RX Data Byte 3
TR/RX Data Byte 4
TR/RX Data Byte 5
TR/RX Data Byte 6
TR/RX Data Byte 7
TR/RX Data Byte 8
RES
RES
RES
ID.23 ID.22 ID.21 ID.20 ID.19 ID.18 ID.17 ID.16
ID.15 ID.14 ID.13 ID.12 ID.11 ID.10
ID.7
ID.6
ID.5
IDE
RTR
RES
TR/RX Data Byte 1
TR/RX Data Byte 2
TR/RX Data Byte 3
TR/RX Data Byte 4
TR/RX Data Byte 5
TR/RX Data Byte 6
TR/RX Data Byte 7
TR/RX Data Byte 8
Version 1.2.0, valid from FW/HW-Version 01/01
WAGO-I/O-SYSTEM 750
750-658 CAN Gateway
Bits
ID.7
ID.6
ID.5
RTR DLC.3 DLC.2 DLC.1 DLC.0
Bits
ID.28 ID.27 ID.26 ID.25 ID.24
ID.4
ID.3
ID.2
RES DLC.3 DLC.2 DLC.1 DLC.0
ID.4
ID.3
ID.9
ID.8
ID.1
ID.0
Manual