EtherNet/IP gateway
Wieland Electric GmbH | BA000970 | 11/2016 (Rev. F)
PCCC Object
1127356299
PCCC (pronounced “P C Cube”) is used in several PLCs from Rockwell Automation/Allen Brad-
ley, which still continue to be used. It was developed before CIP and EtherNet/IP were defined.
PCCC telegrams are either:
a) Encapsulated in CIP packages (e.g. via EtherNet/IP)
b) The encapsulation of CIP packages.
The SP-COP2-ENI module supports the encapsulation of PCCC data in CIP packages, as
described above under b). For this, the class ID 0x67 = 103 was specified.
The PCCC commands listed in the following table are supported by the SP-COP2-ENI module.
All PCCC-related data with a size of 16 bits (word) are available in the “Little Endian” format.
This means that the byte with the lowest value is executed first.
Table 43: PCCC commands supported by the SP-COP2-ENI module
Word Range Write [ch. 8.4.7.2, p. 92]
PLC-5 0x0f 0x01
Word Range Read [ch. 8.4.7.3, p. 92]
PLC-3, PLC-5, PLC-5/250
PLC-5 0x0f 0x67
Typed Write [ch. 8.4.7.4, p. 93]
SLC 5/03, SLC 5/04, PLC 5,
PLC-5 0x0f 0x68
Typed Read [ch. 8.4.7.5, p. 93]
SLC 5/03, SLC 5/04, PLC 5,
SLC 0x0f 0xa1
Protected Typed Logical Read with 2 Address
Fields [ch. 8.4.7.6, p. 95]
SLC 0x0f 0xa2
Protected Typed Logical Read with 3 Address
Fields [ch. 8.4.7.8, p. 96]
MicroLogix-1000, SLC 500,
SLC 5/03, SLC 5/04, PLC 5
SLC 0x0f 0xa9
Protected Typed Logical Write with 2 Address
Fields [ch. 8.4.7.7, p. 95]
SLC 0x0f 0xaa
Protected Typed Logical Write with 3 Address
Fields [ch. 8.4.7.9, p. 96]
MicroLogix-1000, SLC 500,
1127357323
PCCC Telegram Structure
Each request telegram comprises 7+5 header bytes.
Table 44: PCCC request header
Length USINT Header size 1 byte 7
Vendor ID of the requester
S/N UDINT Serial number of the requester 4 byte 0 to 2
32
-1
STS USINT State 1 byte 0
Transport sequence number
FNC USINT Function code 1 byte 0x67, 0x68,
Each answer telegram comprises 7+4 header bytes or 7+4+1 header bytes, if the state byte is
0xf0.
To Next Page
Loading...
