manualshive.com logo in svg

Rockwell Automation Allen-Bradley 1756 ControlLogix, Programming Manual, Page: 56 / 94

Share
Download
Rockwell Automation Allen-Bradley 1756 ControlLogix Programming Manual Download Page 56

Chapter 2 

CIP Services and User-created Tags 

 

56

 

Rockwell Automation Publication 1756-PM020F-EN-P - January 2019 

Message Reply Field 

Bytes 

Description 

Reserved 

00 

 

General Status 

00 

Success 

Extended Status Size 

00 

No Extended Status 

Reply Data 

 
00 00 
C2 00 
00 00 00 00 

Member 1 info, type, offset: 

non-array (0000) 
SINT (00C2) 
Offset (00000000) 

 
00 00 
C1 00 
00 00 00 00 

Member 2 info, type, offset: 

bit 0 (0000) 
BOOL (00C1) 
Offset (00000000) (bit 0 in the previous SINT) 

 
0C 00 
C3 20 
04 00 00 00 

Member 3 info, type, offset: 

12 element array (000c) 
INT (C3 20) 
Offset (00000004) 

 
00 00 
CA 00 
1C 00 00 00 

Member 4 info, type, offset: 

non-array (0000) 
REAL (00CA) 

Offset (0000001C) 

53 54 52 55 43 54 5F 42 
3B 6E 45 42 45 43 45 41 48 41 
00 

Template Name (STRUCT_B) 
The structure name precedes the 0x3B in the stream of bytes. All remaining bytes are 
outside the scope of this document. 

 

5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 
53 54 52 55 43 54 5F 42 30 00 

Member 1 Name: The Logix Designer application selects the name of the member for 

one or more members. The host member for the BOOL (Member 2) follows.

 

Member 1 

is sent on the wire but is not visible to the user in the Logix Designer application Data 
Monitor view. As indicated by the offset value for Member 3, three bytes of pad are 
inserted after the SINT for this host member, for data alignment. When reading or 
writing the structure, the pad bytes are sent on the wire. 

 

70 69 6C 6F 74 5F 6F 6E 00 

Member 2 Name is the first member of the structure that is visible to the user in the 
Logix Designer application Data Monitor view. This is the 

pilot_on

 member. The 

Member 2 information from earlier in the packet indicates this is a BOOL type and the 
data offset is zero. The client identifies that the BOOL is part of the Member_1 at the 

zero data offset, and that this is bit 0 of that member. The other 7 bits of Member_1 
are not used and are not visible. Member 2 is not sent separately on the wire because 
it is part of Member_1. 

68 6F 75 72 6C 79 43 6F 75 6E 
74 00 

Member 3 Name: This is the 

hourlyCount

 

member. 

It is a DINT data type and is at offset 4. 

72 61 74 65 00 

Member 4 Name: This is the 

rate

 member. It is a REAL data type and is at offset 1C. 

The user-defined data type (UDT) Template Name string and structure 

member names, stored as null-terminated strings follow the member 

information. For a UDT structure, the Template Name string contains the 

Template Name followed by the characters 

;n

 plus additional characters. This 

may also apply for some non-UDT structures. For other non-UDT structures, 

the semi-colon may be followed by other characters, or just a NULL instead 

of the semi-colon and characters. Non-UDT structures are beyond the scope 

of this publication and should not be accessed as whole structures. 

Summary of Contents for Allen-Bradley 1756 ControlLogix

Page 1: ...amming Manual Logix 5000 Controllers Data Access 1756 ControlLogix 1756 GuardLogix 1769 CompactLogix 1769 Compact GuardLogix 1789 SoftLogix 5069 CompactLogix 5069 Compact GuardLogix Studio 5000 Logix Emulate ...

Page 2: ...hole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations WARNING Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss ATTENTION Identifies inform...

Page 3: ...rence tables to locate changed information Grammatical and editorial style changes are not included in this summary Global changes None in this release New or enhanced features Subject Reason Tag type serviceparameters for structure on page 38 Added link to the Rockwell Automation Type Encoding ofLogix Structures in CIP Data Table R W document ...

Page 4: ......

Page 5: ...1 Read Tag Service Error Codes 21 Read Tag Fragmented Service 22 Example Using Symbolic Segment Addressing 22 Example Using Symbol Instance Addressing 24 Read Tag Fragmented Service Error Codes 26 Write Tag Service 27 Example Using Symbolic Segment Addressing 27 Example Using Symbol Instance Addressing 27 Write Tag Service Error Codes 28 Write Tag Fragmented Service 28 Example Using Symbolic Segme...

Page 6: ...nformation 55 Example 55 More about BOOLS in UDTs 57 Step 4 Determine the data packing of the members of a structure when accessed as a whole 57 Example of reading an entire structure 58 Step 5 Determine when the tags list and structure information need refreshing 59 How to detect changes 59 Chapter 3 Atomic Members of Predefined Data Types 63 Example 1 Symbolic Segment Addressing Method 63 Exampl...

Page 7: ...nt 84 Unprotected Bit Write CMD 05 45 FNC not present 85 PLC 5 Communication Commands 85 Addressing examples 86 Read Modify Write N CMD 0F 4F FNC 79 87 Typed Read CMD 0F 4F FNC 68 88 Typed Write CMD 0F 4F FNC 67 88 Word Range Read CMD 0F 4F FNC 01 88 Word Range Write CMD 0F 4F FNC 00 89 Bit Write CMD 0F 4F FNC 02 89 SLC Communication Commands 90 SLC Protected Typed Logical Read with 3 Address Fiel...

Page 8: ......

Page 9: ...e and will continue to be the product to program Logix 5000 controllers for discrete process batch motion safety and drive based solutions The Studio 5000 environment is the foundation for the future of Rockwell Automation engineering design tools and capabilities The Studio 5000 environment is the one place for design engineers to develop all elements of their control system These documents conta...

Page 10: ...th the software Corresponding Source code for open source packages included in this product are located at their respective web site s Alternately obtain complete Corresponding Source code by contacting Rockwell Automation via the Contact form on the Rockwell Automation website http www rockwellautomation com global about us contact contact page Please include Open Source as part of the request te...

Page 11: ...he product license The product s performance may be affected by system configuration the application being performed operator control maintenance and other related factors Rockwell Automation is not responsible for these intervening factors The instructions in this document do not cover all the details or variations in the equipment procedure or process described nor do they provide directions for...

Page 12: ...Preface 12 Rockwell Automation Publication 1756 PM020F EN P January 2019 Online Support http www rockwellautomation com support ...

Page 13: ...data Tag Type Service parameter Segment encoding CIP Service Request Response format Data type information is very important in all aspects of CIP communication The type information is used for reading writing and if necessary deciphering structures The Logix 5000 controller supports these data types Atomic A bit byte 16 bit word or 32 bit word each of which stores a single value CIP refers to the...

Page 14: ...izes table for the data type value to use to store a bit To store a Use this data type Bit BOOL Bit array DWORD 32 bit boolean array 8 bit integer SINT 16 bit integer INT 32 bit integer DINT 32 bit float REAL 64 bit integer LINT The Logix 5000 controller stores data in tags in contrast to a PLC 5 or SLC controller which stores data in data files Logix 5000 tags have these properties Name that iden...

Page 15: ...is tag type parameter is A 16 bit value for atomic tags Two 16 bit values for structured tags The value used for structures is a calculated value For details see Tag type service parameters for structures The tag type values used for atomic tags and the resulting data size are shown in the table shown in Tag type service parameter values used with Logix controllers See also Tag type service parame...

Page 16: ...ined by CIP that are supported by the Logix 5000 controller See also CIP services overview on page 13 These tables explain the Logical Segments Not all segment types defined by CIP are supported by Logix 5000 controllers Segment Type Value Byte Order Representation of Element ID Value low byte first 0 1 n n 1 8 bit Element ID 0x28 Value N A N A N A N A 16 bit Element ID 0x29 00 Low High N A N A 32...

Page 17: ... defined in the CIP Networks Library Volume 1 Chapter 2 For complete descriptions see the CIP Networks Library All requests take this form Message Request Field Description Request Service Indicates to the object referenced in the request path to perform a task The CIP or the device manufacturer define these tasks Most of the services covered in this manual are defined by the Rockwell Automation v...

Page 18: ...messages and of the PCCC and DF1 layers All responses take the general form as shown in the table Message Response Field Description Reply Service The request service with the MSB set to 1 00 Reserved General Status An 8 bit value indicating success or error status The CIPNetworks Library Volume 1 Appendix B has a list of the general status codes The objectclass specified in the request path defin...

Page 19: ...to access The client application that accesses the controller must Retrieve the symbol instance information from the controller to associate the name of the tag with its instance ID Use the instance ID to access the tag For best performance in applications that access a large number of tags Also use the Multiple Service Packet Service 0x0a to combine multiple requests in one message frame This imp...

Page 20: ...te Tag Service on page 27 The Read Tag Service reads the data associated with the tag specified in the path Any data that fits into the reply packet is returned even if it does not all fit If all the data does not fit into the packet the error 0x06 is returned along with the data When reading a two or three dimensional array of data all dimensions must be specified When reading a BOOL tag the valu...

Page 21: ...e tag named rate using Symbol Instance Addressing The tag has a data type of DINT and a value of 534 1st Message Request Field Bytes in hex Description Symbol Instance Addressing Request Service 4C Read Tag Service Request Request Path Size 03 Request Path is 3 words 6 bytes long Request Path 20 6B 25 00 8FF6 Logical Segment for Symbol Class ID Logical Segment for Instance ID of the tag rate Reque...

Page 22: ...the number of bytes transferred in the response to the previous request The Byte Offset field is expressed in number of bytes regardless of the data type being read In the example following the data type being read is SINT which happens to be a byte The elements and offset are in the same units which is not the case for other data types See also CIP services on page 13 Services Supported by Logix ...

Page 23: ...ply Field Bytes in hex Description Symbolic Segment Addressing Reply Service D2 Read Tag Fragmented Service Reply Reserved 00 General Status 06 Reply Data Too Large Extended Status Size 00 No extended status Reply Data C2 00 SINT TagType Value nn nn nn nn Data for Elements 490 through 979 3rd Message Request Field Bytes in hex Description Symbolic Segment Addressing Request Service 52 Read Tag Fra...

Page 24: ...ata C2 00 SINT TagType Value nn nn nn nn Data for Elements 1470 through1749 See also Read Tag Fragmented Service Error Codes on page 26 Reading the tag TotalCount that has 1750 SINTs using Symbol Instance Addressing would consist of these four service requests with service data as shown in the tables The value used for Instance ID was determined using methods described in CIP Services and User cre...

Page 25: ...it 2nd Message Reply Field Bytes in hex Description Symbol Instance Addressing Reply Service D2 Read Tag Fragmented Service Reply Reserved 00 General Status 06 Reply Data Too Large Extended Status Size 00 No extended status Reply Data C2 00 SINT TagType Value nn nn nn nn Data for Element 490 through 979 3rd Message Request Field Bytes in hex Description Symbol Instance Addressing Request Service 5...

Page 26: ...for Elements 1490 through 1749 Each response except the last one shows the General Status of 06 Reply Data Too Large to indicate that more data is present than is in this particular frame The last response shows the General Status of 0 indicating that the data read did not exceed the message size limit This means that the entire sequence of bytes has been read See also CIP Services and User create...

Page 27: ...Service Request Request Path Size 06 Request Path is 6 words 12bytes long Request Path 91 0A 4361 7274 6F6E 53 69 7A 65 ANSI Ext Symbolic Segment for CartonSize Request Data C4 00 DINT Tag Type Value 01 00 Number of elements to write 1 0E 00 00 00 Data 0000000E 14 decimal Message Reply Field Bytes in hex Description Symbolic Segment Addressing Reply Service CD Write Tag Service Reply Reserved 00 G...

Page 28: ...n Probably instance number is notpresent 0x10 0x2101 Device state conflict keyswitch position The requestor is changing force information in HARD RUNmode 0x10 0x2802 Device state conflict Safety Status The controller is in a state in which Safety Memory cannot be modified 0x13 N A Insufficient Request Data Data too short forexpected parameters 0x26 N A The Request Path Size received was shorter or...

Page 29: ...Message Request Field Bytes in hex Description Symbolic Segment Addressing Request Service 53 Read Tag Fragmented Service Request Request Path Size 06 Request Path is 6 words 12bytes long Request Path 91 0A 546F 7461 6C43 6F75 6E 74 ANSI Ext Symbolic Segment for TotalCount Request Data C2 00 SINT TagType Value D6 06 Total number of elements to write 1750 00 00 0000 Start at this offset nn nn nn El...

Page 30: ... ANSI Ext Symbolic Segment for TotalCount Request Data C2 00 SINT TagType Value D6 06 Total number of elements to write 1750 B4 03 00 00 Start at this offset nn nn nn Element Data for Elements 948 through 1421 3rd Message Reply Field Bytes in hex Description Symbolic Segment Addressing Reply Service D3 Write Tag Fragmented Service Reply Reserved 00 General Status 00 Success Extended Status Size 00...

Page 31: ...al Segment for Symbol Class ID Logical Segment for Instance ID for the tag TotalCount Request Data C2 00 SINT TagType Value D6 06 Number of elements to write 1750 00 00 0000 Start at this Offset nn nn nn Element Data for Elements 0 through 473 1st Message Reply Field Bytes in hex Description Symbol Instance Addressing Reply Service D3 Write Tag Fragmented Service Reply Reserved 00 General Status 0...

Page 32: ... Request Data C2 00 Tag Data Type D6 06 Number of elements to write 1750 B4 03 00 00 Start at this Offset nn nn nn Element Data 948 through 1421 3rd Message Reply Field Bytes in hex Description Symbol Instance Addressing Reply Service D3 Write Tag Fragmented Service Reply Reserved 00 General Status 00 Success Extended Status Size 00 No extended status 4th Message Request Field Bytes in hex Descrip...

Page 33: ... force information in HARD RUN mode 0x10 0x2802 Device state conflict Safety Status Unable to modify Safety Memoryin the current controller state 0x13 N A Insufficient Request Data Data is too small for expected parameters 0x26 N A The Request Path Size received was shorter or longer than expected 0xFF 0x2104 General Error Offset is beyond end of the requested tag 0xFF 0x2105 General Error Offset ...

Page 34: ...nd reset bit 5 of the DINT named ControlWord Message Request Field Bytes in hex Description Request Service 4E Read Modify WriteTag Service Request Request Path Size 07 Request Path is 7 words 14bytes long Request Path 91 0B 43 6F6E 7H 726F 6C 57 6F 72 64 00 ANSI Ext Symbolic Segment for ControlWord Request Data 04 00 Size of Masks shall be 4 04 00 0000 Array ofOR modify masks DF FF FF FF Array of...

Page 35: ...r faster request processing For details on this service see the CIP Networks Library Volume 1 Appendix A See also Read Modify Write Tag Service on page 33 CIP services on page 13 This is an example for Multiple Service Packets Message Request Field Bytes in hex Description Request Service 0A Multiple Service Packet Service Request Request Path Size 02 Request Path is 2 words 4 bytes long Request P...

Page 36: ... Value 0x000001DC 476 decimal The Multiple Service Packet response follows the same Message Router Response format as all CIP services therefore the General Status Ext Status Size fields are in the same CIP Service Request Response Format as described in previous examples The Reply Data field contains the number of service replies followed by the byte offset to the start of each reply followed by ...

Page 37: ...Defined types and Booleans within these structures see the following topics in this chapter See also Work with Data Structures on page 37 CIP services on page 13 For these guidelines for working with data structures Complete user defined structure tags or individual members are accessed Access to complete structure Tags requires an understanding of the organization and alignment of structure membe...

Page 38: ...ation on data access control and the effect it has on structure access can be found in Logix 5000 Controllers I O and Tag Data Programming Manual publication 1756 PM004 To improve tag access performance and to simplify the task of accessing structured tags through a network create UDTs for the data that needs to be accessed through the network with members of the types listed following only and ac...

Page 39: ...ix controllers arrays report the data type of its members An array of an atomic type reports the corresponding 2 byte Tag Type Service Parameter while an array of structures reports the corresponding 4 byte Tag Type Service Parameter Important Reading a structurebefore writing to it is one way to obtain the value for this parameter but that does not provide any understanding ofthe structuremakeup ...

Page 40: ......

Page 41: ...e Determining the data packing of the members of a structure when accessed as a whole and not member by a member Determining when to refresh the list of tags and structure information See also How tags are organized in the controller on page 41 Symbol object on page 42 Template object on page 42 Creating and maintaining a symbol object list on page 44 A client application interacts with the symbol...

Page 42: ...the name Get_Instance_Attribute_List This service helps find an instance of the class and enables retrieving the name and type attributes for each instance of the class The member names for structures only exist in the template definition It is acceptable for a user defined data type template definition to contain members with the same names as other tags in the controller See also CIP Services an...

Page 43: ...alias tag for the atomic member that needs to be accessed These tags are present in the Symbol object instances and can be accessed like any other atomic tag The previous methods are also used with structured tags of a user defined data type that contain a nested Module Defined Add On Defined or Predefined type member Important The information described in this manual about accessing and understan...

Page 44: ...dentifying the available tags or accessing structures must identify the required tags for access before manipulating tag data This information is used to identify the data type of each tag and enable the application to interpret the data value associated with the tag Update the list of information as required User program changes frequently create or delete tags and add delete and modify user defi...

Page 45: ...t 0x55 service returns instance IDs for each created instance of the Symbol class along with a list of the attribute data associated with the requested attributes See also CIP Services and User created Tags on page 41 Retrieve all symbol object instances on page 45 Example of retrieving the first group of tags on page 46 Analysis on page 47 The maximum size of a packet does not return all instance...

Page 46: ...ex Description Request Service 55 Get_Instance_Attribute_List Service Request Request Path Size 03 Request Path is 3 words 6 bytes long Request Path 20 6B 25 0000 00 Logical Segments Class 0x6B Instance 0 starting instance Request Data 02 00 Number of attributes to retrieve 01 00 Attribute 1 Symbol Name 02 00 Attribute 2 Symbol Type Message Reply Field Bytes in hex Description Reply Service D5 Get...

Page 47: ... the next step The example previously returned number of instances starting with instance 0x0312 and ending with instance 0x5D34 Only instances that are created are returned Gaps in the instance numbers will occur Any symbol instances that represent tags whose External Access is set to None are not included in the reply data See also Continue the retrieval process on page 47 In this example assume...

Page 48: ...Name Length Characters in the symbol name FF 8F Symbol Type 54 72 0000 Second 32 bit Instance ID 0F 00 73 61 6D 706C 65 5469 6D 655F 4465 7374 16 bit Symbol Name Length Characters in the symbol name 83 8F Symbol Type Next E8 08 00 00 Last 32 bit Instance ID in this reply 13 00 50 72 6567 72 61 6D 3A 4D 61 696E 50 72 6F 67 72 61 6D 16 bit Symbol Name Length Characters in the symbol name 68 10 Symbo...

Page 49: ...s Atomic and structured tags are differentiated by the value of bit 15 Do not access Symbols where bit 12 1 is a system tag Tag Type Symbol Type Attribute Description Atomic tag Bit 15 0 Bit 12 0 The value of bits 0 11of the Symbol Type attribute is the Tag Type Service Parameter used in the Read Write Tag services Structured tag Bit 15 1 Bit 12 0 Bits 0 11 of the SymbolType attribute are the inst...

Page 50: ... Bit 15 is set indicating this tag is a structured tag and Bit 12 is reset so it is not a reserved tag The value of bits 0 11 is 0x2E9 is the instance ID of the Template object where the structure makeup of the tag is defined and the value is in the range of values that are accessed Use instance ID 0x2E9 in the Step 3 example to retrieve the structure information for a tag of this type After gaini...

Page 51: ...ls Continue until all nested structures are checked See also Step 3 Determining the structure makeup for a specific structure on page 51 Any remaining tag with the Symbol Type Bit 15 1 is a structured data type The client application must read information from the Template object Instance ID associated with this tag This Instance ID is the value of Symbol Type Bits 0 11 Four attributes of this ins...

Page 52: ...response for each item consisting of the attribute ID 16 bits status of retrieval 16 bits and the attribute data size varies Message Reply Field Bytes in hex Description Reply Service 83 Get_Attributes_List Service Reply Reserved 00 General Status 00 Success Extended Status Size 00 No extended status Reply Data 04 00 Count of Items returned 04 00 00 00 IE 00 0000 Attribute 4 Template Object Defini...

Page 53: ...mplate Read service to retrieve the template member information Attribute 4 Template Object Definitions Size will be used to calculate how much data to read when using the Template Read service 0x4C to get the template definition structure from the Template instance The service data includes the starting byte offset initially 0 and the number of bytes to read The number of bytes to read is calcula...

Page 54: ...nformation on page 54 The first 32 bit value contains The lower 16 bits are the INFO value which is one of these value If the member is an atomic data type the value is zero If the member is an array data type the value is the array size max 65535 If the member is a Boolean data type the value is the bit location 0 31 0 7 if mapped to a SINT The upper 16 bits represent the data type The second 32 ...

Page 55: ...reated and given the name MachineSummary This tag name is used in the following example The instance ID used in this example was determined by examining the Symbol Type attribute of the tag MachineSummary as described in Step 2 Isolating user created tags from system tags identifying structured tags The Template Read service request and response to that instance is shown in the following examples ...

Page 56: ...r this host member for data alignment When reading or writing the structure the pad bytes are sent on the wire 70 69 6C 6F 74 5F 6F 6E 00 Member 2 Nameis the first member of the structure that is visible to the user in the Logix Designer application Data Monitor view This is the pilot_on member The Member 2 information from earlier in the packet indicates this is a BOOL type and the data offset is...

Page 57: ... If BOOLS are defined non contiguously in a UDT they are mapped to more than one host member The Member Offset in the Template identifies where the host SINT is located and the bit order of the BOOL in the SINT is determined by the order of the bit in the structure The host member is sent on the wire when the tag is accessed but the visible BOOL is only present in the structure definition to enume...

Page 58: ...0 Number of elements to read 1 The data returned would be packed like this Message Reply Field Bytes Description Reply Service CC Read Tag Service Reply Reserved 00 General Status 00 Success Extended Status Size 00 No Extended Status Reply Data A0 02 CD 9E Tag Type Service Parameter The Structure Handle Template Instance Attribute 1 See Step 3 01 host SINT for BOOLs 00 Pad byte 00 Pad byte 00 Pad ...

Page 59: ...an change See also How to detect changes on page 59 Controller object attributes indicate changes made to the controller A change in these values indicates changes to symbol instances template instances or both These are not the only changes indicated by these attributes but these provide the most straightforward way to determine when the client application should refresh the list of created tags ...

Page 60: ...nge The client application should refresh this information after re establishing the CIP network connection with the Logix 5000 controller or if a General Status of 0x05 occurs when reading these attributes The service request and reply are shown as Message Request Field Bytes in hex Description Request Service 03 Get_Attribute_List Service Request Request Path Size 03 Request Path is 3 words 6 by...

Page 61: ...ice request to return a General Status 0x10 Device State Conflict when the controller is password locked In this state controller memory can not be altered Rockwell Automation suggests after receipt of the Device State Conflict for the first time the client application should refresh the tag information one time The client application should refresh again if the connection lost The client applicat...

Page 62: ......

Page 63: ...lso Atomic Members of Predefined Data Types on page 63 Accessing User Defined Structures on page 69 The examples access tags that return atomic data types Read a single integer tag named parts The tag has a data type of INT and a value of 42 Message Request Field Bytes in hex Description Symbolic Segment Addressing Request Service 4C Read Tag Service Request Request Path Size 04 Request Path is 4 ...

Page 64: ... Number of elements to read 1 Message Reply Field Bytes in hex Description Symbol Instance Addressing Reply Service CC Read Tag Service Reply Reserved 00 General Status 00 Success Extended Status Size 00 No extended status Reply Data C3 00 INT TagType Value 2A 00 002A 42 decimal See also Atomic Members of Predefined Data Types on page 63 Write the value of 14 5 to the 6th element of an array of RE...

Page 65: ...72 6f 6669 6c 65 00 28 00 28 01 29 00 0101 ANSI Ext Symbolic Segment for profile Member Segment for 0 Member Segment for 1 Member Segment for 257 Request Data 02 00 Number of elements to read 2 Message Reply Field Bytes in hex Description Symbolic Segment Addressing Reply Service CC Read Tag Service Reply Reserved 00 General Status 00 Success Extended Status Size 00 No extended status Reply Data C...

Page 66: ... also Atomic Members of Predefined Data Types on page 63 Read the accumulated value of a timer named dwell3 dwell3 ACC Message Request Field Bytes in hex Description Symbolic Segment Addressing Request Service 4C Read Tag Service Request Request Path Size 07 Request Path is 7 words 14bytes long Request Path 91 06 6477 65 6C 6C 33 91 03 6163 63 00 ANSI Ext Symbolic Segment for dwell3 ANSI Ext Symbo...

Page 67: ...of Predefined Data Types on page 63 Read the tag struct3 today rate which is a structure of type STRUCT_C using both the Symbol Instance and Symbolic Segment Addressing methods Message Request Field Bytes in hex Description Symbol Instance and Symbolic Segment Addressing Request Service 4C Read Tag Service Request Request Path Size 0A Request Path is 9 words 18bytes long Request Path 20 6B 25 00 D...

Page 68: ...ts for Symbol Class ID and Instance ID for myDstruct4 Element ID for element 0 ANSI Ext Symbolic Segment for myarray Element ID for element 1 ANSI Ext Symbolic Segment for today ANSI Ext Symbolic Segment for hourlyCount Element ID for element 3 Request Data 01 00 Number of elements to read 1 Message Reply Field Bytes in hex Description Symbol Instance and Symbolic Segment Addressing Reply Service ...

Page 69: ...al Status 00 Success Extended Status Size 00 No extended status Reply Data C1 00 BOOL Tag Type Value FF BOOL value for 1 See also Atomic Members of Predefined Data Types on page 63 This topic shows examples of accessing simple structures to help illustrate the message formats needed The examples all use the Symbolic Segment Addressing method The four structure examples are defined and various memb...

Page 70: ...uct1 Request Data 01 00 Number of elements to read 1 Message Reply Field Bytes in hex Description Symbolic Segment Addressing Reply Service CC Read Tag Service Reply Reserved 00 General Status 00 Success Extended Status Size 00 No extended status Reply Data A0 02 C1FA Tag Type for STRUCT_A 03 00 0000 55 00 0000 77 00 0000 33 33 2B 41 limit4 and limit7members bits 0 and 1 respectively BOOL 1 travel...

Page 71: ...est Service 4C Read Tag Service Request Request Path Size 0B Request Path is 11 words 22bytes long Request Path 91 09 7374 72 31 41 72 72 61 79 00 28 08 91 06 7472 61 76 65 6c ANSI Ext Symbolic Segment for str1Array Member ID for element 8 ANSI Ext Symbolic Segment for travel Request Data 01 00 Number of elements to read 1 Message Reply Field Bytes in hex Description Symbolic Segment Addressing Re...

Page 72: ... 00 06 00 0x0005 5 decimal 0x0006 6 decimal See also Access User Defined Structures on page 69 Read the tag struct3 today rate which is a structure of type STRUCT_C Message Request Field Bytes in hex Description Symbolic Segment Addressing Request Service 4C Read Tag Service Request Request Path Size 0C Request Path is 12 words 24bytes long Request Path 91 07 7374 72 75 63 74 33 00 91 05 746F 64 6...

Page 73: ...79 00 28 01 91 05 746F 64 61 79 00 91 0B 68 6F75 726C 79 43 6F 75 6E 74 00 28 03 ANSI Ext Symbolic Segment for myDstruct4 Element ID for element 0 ANSI Ext Symbolic Segment for myarray Element ID for element 1 ANSI Ext Symbolic Segment for today ANSI Ext Symbolic Segment for hourlyCount Element ID for element 3 Request Data 01 00 Number of elements to read 1 Message Reply Field Bytes in hex Descri...

Page 74: ......

Page 75: ...l to allow the transmission of larger CIP messages up to 510 bytes For more information see Fragmentation Protocol See also CIP services on page 13 Unconnected Messaging UCMM through PCCC on page 75 Connected Explicit Messages through PCCC on page 76 Fragmentation Protocol on page 78 PCCC Command Code 0B provides CIP unconnected explicit message capability over the controller s serial port Use thi...

Page 76: ...e CIP Services Reserved USINT 00 General Status USINT ss Extended Status Size USINT nn Extended Status Only present if Size 0 Service Response Data Service determines whether present or not and the size data type See also Connected Explicit Messages through PCCC on page 76 CIP Services on page 13 Fragmentation Protocol on page 78 PCCC Command Code 0A provides CIP explicit message connection behavi...

Page 77: ...P services that follow the CIP Service Request Response Format Like all CIP connections an RPI value associated with the connection establishes the rate at which messages must be sent If they are not sent at this rate timeouts occur Rest the RPI timer should be reset when a message is sent When the timer reaches the RPI value the re transmit the connection to the last sent message and keep the sam...

Page 78: ...er to the CIP Specification TransportHeader UINT Transportclass 3 Sequence Count Request Service USINT CIP Service Code See CIPServices Request Path Size USINT Number of 16 bit words in the Request Path Request Path EPATH Logical or Symbolic Segments or both Service Data Service data DLE USINT ASCII escape character See theDF1 Protocol and Command Set Reference Manual publication 1770 6 5 16 ETX U...

Page 79: ...pter 4 Rockwell Automation Publication 1756 PM020F EN P January 2019 79 For more information on the PCCC fragmentation protocol go to http www rockwellautomation com enabled guides html See also CIP Over the Controller Serial Port on page 75 ...

Page 80: ......

Page 81: ... type as the PLC SLC file CIP messaging is the preferred method of interacting with Logix 5000 controllers but PCCC messaging is serviceable for many applications especially where the legacy communications product is not able to be modified and where the Logix 5000 customer is willing to do the extra configuration of data table mappings in the Logix 5000 controller Remote applications that depend ...

Page 82: ...LC Protected Typed Logical Read with 3 Address Fields SLC Protected Typed Logical Write with 3 Address Fields SLC Protected Typed Logical Read with 2 Address Fields SLC Protected Typed Logical Write with 2 Address Fields See also PCCC Commands on page 81 This topic describes the initial fields present in all PCCC commands These fields are followed by command specific fields The name of each comman...

Page 83: ...saction identifier EXT STS 1 byte extended status error code only present if STS 0xF0 See also PCCC Commands on page 81 Use the PLC 2 commands to access one tag in a Logix 5000 controller After sending the command it is acceptable to map the message to an INT 16 bit integer tag in the Logix 5000 controller All the PLC2 commands access the same tag typically an INT array Logix Designer handles prot...

Page 84: ... data Reply Format no data only status See also PLC 2 Communication Commands on page 83 The Protected Bit Write CMD 02 42 FNC not present command provides a protected bit write capability for the PLC 2 commands For each 3 field set the command performs this sequence 1 Copy the specified byte from limited areas of memory 2 Set the bits specified in the SET mask 3 Reset the bits specified in the RES...

Page 85: ...ommand requires a system address in one of these forms Logical binary or logical ASCII which addresses data by file and element The first level of the logical binary must be 0 This is required to access controller scoped tags The second level is the file number This is also the level following the letters in the logical ASCII form The next 1 2 or 3 levels correspond to the array dimension indices ...

Page 86: ...6 bit words Use the PLC 5 file data type that matches the data type of the Logix tag See also CIP data types on page 13 This table lists the addressing examples for PLC 5 PCCC Messages To access This entry is specified 1 Single integer tag namedparts PCCCsymbolic parts The sixth element of the array of REALs named setpoints PCCC Logical ASCII F8 6 PCCC symbolic setpoints 5 Single integer 2 5 257 o...

Page 87: ... AND mask 3 Set the bits specified in the OR mask 4 Write the word back Request Format no of sets PLC 5 system address mask length AND mask OR mask repeats 1 no of sets indicates the number of sets of the following four fields PLC 5 system address specifies the word to be modified mask length specifies 2or 4 byte masks For this command most Logix controllers only support 4 byte mask use RMW comman...

Page 88: ...ion Commands on page 85 The typed write command writes a block of data starting at the PLC 5 system address plus the packet offset Request Format packet offset total transaction PLC 5 system address type ID data packet offset 2 bytes offset in number of elements total transaction 2 bytes number of elements in complete transaction PLC 5 system address type ID 1 byte for integers or by2 bytes for fl...

Page 89: ...ansaction 2 bytes number of 16 bitwords in complete transaction PLC 5 system address data Reply Format no data only status See also PLC 5 Communication Commands on page 85 The Bit Write CMD 0F 4F FNC 02 command sets and resets bits in a single word specified by the PLC 5 logical address It changes a single word in a command For the 3 field sequence the Bit Write CMD 0F 4F FNC 02 command Copies the...

Page 90: ...and Command Set Reference Manual publication 1770 6 5 16 SLC logical addressing has a limited number of logical address levels so there are some special concerns In a The element number is used as the One dimension array Dimension index for addressing data elem Two dimensional array Index of the second dimension and the firstdimension index is 0 data 0 elem Three dimensional array Index of the thi...

Page 91: ... is supported for compatibility with older modules It writes to the logical address Request Format byte size file number file type element number sub element number byte size 1 byte number of data bytes to be written file number 1 byte for 0 254 for 255 3bytes 0xFF followed by 2 byte number lowbyte first file type 1 byte For file types and codes see theDF1 Protocol and Command Set Reference Manual...

Page 92: ... also SLC Communication Commands on page 90 PCCC Commands on page 81 This write command provides a simpler version for writing data Request Format byte size file number file type element number byte size 1 byte number of data bytes to be written file number 1 byte for 0 254 for 255 3bytes 0xFF followed by 2 byte number lowbyte first file type 1 byte For file types and codes see theDF1 Protocol and...

Page 93: ...4 Read tag error codes 21 Read Tag Fragmented Service Error Codes 26 Read Tag Fragmented Service examples 22 24 Read Tag Service 20 21 S Segment encoding 16 17 Services supported by Logix5000 Controllers 18 20 22 27 28 33 SLC Communicatino Commands 90 91 92 Structures user defined 69 70 71 72 73 Symbol object list create 45 49 51 57 59 Symbol object list maintain 45 49 51 57 59 T Tags 41 42 U User...

Page 94: ...xperience a problem within the first 24 hours of installation review the information that is contained in this manual You can contact Customer Support for initial help in getting your product up and running United States or Canada 1 440 646 3434 Outside United States or Canada Use the Worldwide Locator available at http www rockwellautomation com locations or contact your local Rockwell Automation...

Reviews:

No comments