Scribd
Upload
333 views

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

This document provides steps to program a CIP Generic Explicit Message with a ControlLogix revision 10 or 11 firmware that uses an Attribute ID of zero. It explains that starting in revision 10, an Attribute byte is not sent if the ID is zero. The workaround is to: 1) Create an array of SINT type, 2) Copy the data source into the array starting at element 1 to leave element 0 as zero, and 3) Modify the MSG source to use this new array so element 0 contains the Attribute ID of zero.

Uploaded by

Anonymous OYLvnCx
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
333 views

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

This document provides steps to program a CIP Generic Explicit Message with a ControlLogix revision 10 or 11 firmware that uses an Attribute ID of zero. It explains that starting in revision 10, an Attribute byte is not sent if the ID is zero. The workaround is to: 1) Create an array of SINT type, 2) Copy the data source into the array starting at element 1 to leave element 0 as zero, and 3) Modify the MSG source to use this new array so element 0 contains the Attribute ID of zero.

Uploaded by

Anonymous OYLvnCx
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, 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 ID’s.

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, we’re 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 0 (Attribute ID)


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

Here is the MSG instruction:

Here’s 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