8355 datasheet(20/25 Pages) PHOENIX

20 / 25 page

IB IL CAN-MA-XC-PAC

8355_en_01

PHOENIX CONTACT

CAN data packet

Example: 11-bit CAN message and 8 byte data

The first CAN data packet in SUPI A is shown.

A CAN data packet in SUPI B starts in the next

free byte (byte 1).

In the case of a CAN bus with 29-bit CAN

message, 2 further bytes are required for the

CAN ID.

Word

OUT2

Byte

Bit

Assig

nmen

CAN ID bit 7 ... 0

(CAN identifier, lower byte)

LEN

(Length of the CAN mes-

sage)

CMD

(Command code)

Byte 4, bit 7 ... 4: LEN (Length of the CAN message)

Indicates the length of the CAN message in bytes, consisting

of CAN ID (2 bytes) + n data bytes

Byte 4, bit 3 ... 0: CMD (command code)

11-bit CAN message

29-bit CAN message

Word

OUT3

Byte

Bit

Assig

nmen

OUT data byte 0

(Output data)

RTR

CAN ID bit 11 ... 9

(CAN identifier, higher bits)

Byte 8, Bit 7: RTR (Remote Transmission Request)

No RTR message

RTR message

OUT4

Byte 9: OUT data byte 2

Byte 8: OUT data byte 1

OUT5

Byte 11: OUT data byte 4

Byte 10: OUT data byte 3

OUT6

Byte 13: OUT data byte 6

Byte 12: OUT data byte 5

OUT7

Byte 15: LEN/CMD of the next CAN data packet

Byte 14: OUT data byte 7

8355 Datasheet(PDF) 20 Page - PHOENIX CONTACT

8355 Datasheet(HTML) 20 Page - PHOENIX CONTACT

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Datasheet Download

Link URL