EtherNet/IP gateway
Wieland Electric GmbH | BA000970 | 07/2019 [9855]
89
PCCC Telegram Structure
Each request telegram comprises 7+5 header bytes.
Table 48: PCCC request header
Name
Data type Description
Size
Data range
Length USINT
Header size
1 byte
7
Vendor UINT
Vendor ID of the requester
2 byte
S/N
UDINT
Serial number of the requester
4 byte
0 to 2
32
-1
CMD
USINT
Command
1 byte
0x0f
STS
USINT
State
1 byte
0
TNSW
UINT
Transport sequence number
2 byte
1 to 65535
FNC
USINT
Function code
1 byte
0x67, 0x68,
0xa2, 0xaa
Each answer telegram comprises 7+4 header bytes or 7+4+1 header bytes, if the state byte is 0xf0.
Table 49: PCCC reply header
Name
Data type Meaning
Size
Data range
Length USINT
Header size
1 Byte
7
Vendor UINT
Vendor ID of requester
2 Byte
S/N
UDINT
Serial number of requester
4 Byte
0 to 2
32
-1
CMD
USINT
Command of requester plus Bit 6 set
1 Byte
0x4f
STS
USINT
Status
1 Byte
0x00, 0x10,
0xf0
TNSW
UINT
Transport sequence number
2 Byte
1 to 65535
EXT STS USINT
Extended Status, only present if STS = 0xf0
0 to 1
Byte
80163083
Word Range Write
The SP-COP2-ENI module supports “Write PLC-5 word range” according to the following table:
Table 50: Data structure of PLC-5 Word Range Write
Name
Data type
Meaning
Data range
Packet offset
UINT
Offset in number of elements
Total Transaction
UINT
number of elements in transaction
Address
BYTE[m]
PLC-5 system address, m >= 2
Payload
UINT[n]
2 x n = Data byte count
0 to 65535
The answer of the SP-COP2-ENI module does not contain any data, only a state.
80188939
8.4.7.1
8.4.7.2
