Scribd
Upload
208 views4 pages

How To Program A CIP Generic Explicit Message With ControlLogix Revision 10 or 11 Firmware

This document provides steps to work around a change in how ControlLogix firmware versions 10 and 11 handle attribute IDs of zero in CIP Explicit messages. The firmware no longer sends the attribute byte if the attribute ID is zero. To resolve this, the steps are: 1) Create an array of SINT (byte) type 2) Copy the data source into the array, leaving the first element zero 3) Modify the MSG instruction to use the new array as the source This ensures an attribute ID of zero is sent by placing it in the first element of the array.

Uploaded by

Saad Bro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
208 views4 pages

How To Program A CIP Generic Explicit Message With ControlLogix Revision 10 or 11 Firmware

This document provides steps to work around a change in how ControlLogix firmware versions 10 and 11 handle attribute IDs of zero in CIP Explicit messages. The firmware no longer sends the attribute byte if the attribute ID is zero. To resolve this, the steps are: 1) Create an array of SINT (byte) type 2) Copy the data source into the array, leaving the first element zero 3) Modify the MSG instruction to use the new array as the source This ensures an attribute ID of zero is sent by placing it in the first element of the array.

Uploaded by

Saad Bro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

How to program a CIP Generic Explicit Message with ControlLogix revision 10 or

11 Firmware that uses an Attribute ID of zero.

Starting with Revision 10 of ControlLogix Processor Firmware, sending a CIP Explicit MSG to a device
will not send the Attribute byte if the Attribute ID value is zero. Using an Attribute ID of zero is valid with
some Class IDs.

This is a change of operation from the way that the same MSG command would operate in previous
versions of Firmware.

To resolve the issue, use the following steps as a work around:

1. Create an array of data type SINT (Byte)


2. Create a Ladder Instruction that copies the current Data Source tag into the array of SINT's.
The destination element of the COPY instruction is element 1, leaving element 0 set to zero (which
will be sent as the Attribute Field by the MSG command.)
3. Modify the Source Field of the MSG command to use the array created in Step 1.

Here is a sample logic file that uses this method:

Rung 1 was added to copy the original data_source for the MSG instruction to element 1 of the array of
SINT's. Remember element 0 must be set to Zero.
In essence, were shifting all data by a byte leaving a byte with a value of zero in the first element of the
Single Integer Array.

Original Source New Data


(Byte) (Byte)

8 (1st Data Byte) 0 (Attribute ID)


0 8 (1st Data Byte)
9 0
0 9
10 0
0 10
0

Here is the MSG instruction:

Heres the original Source Data array:


Here's the new SINT array:

Note: The 1st element is a zero. This value represents the Attribute Field. All data that follows is the data
that will be sent as part of the Explicit MSG. parameter information request.

Here are the values in the Destination Tag specified in the MSG:
(They contain the results back from the Explicit MSG)

You might also like