Use the search and browse feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Search Solutions Results By: View All Solutions

Kepware Knowledge Base: Solution


Received CIP Error 0x05' (Unknown Destination) Error Message

Last Update: 11/7/2018
Print

Problem:
When reading tags with the Allen-Bradley ControlLogix Ethernet driver, the "CIP Error 0x05" is posted to the Event Log.

Possible Cause:
This error is usually caused when a User-Defined Tag (UDT) structure is missing a sub-element. For example, a UDT structure named "Alarm" contains the sub-elements EN, Ack, UnAck, Acked, and Active. If the tags are controller-scoped, the device may access them through the address nomenclature "Alarm.EN," "Alarm.Ack," and so forth. If the driver is asked for a tag like "Alarm.Simulate," the CIP Error 0x05 will be displayed in the Event Log because the sub-element "Simulate" doesn't occur in an existing structure.

Solution:
Add the missing sub-element to the User-Defined Tag structure.

© 2019 PTC Inc. All Rights Reserved.