
Contents ILX69-PBS ♦ CompactLogix or MicroLogix Platform
User Manual PROFIBUS Slave Communication Module
Page 68 of 102 ProSoft Technology, Inc.
March 20, 2015
6.3.4 CIP Messaging Error Codes
This section includes errors codes and conditions that can occur when using the CIP
messaging commands.
Your application should be constructed in a manner in which it catches the two possible
error cases:
CIP Message instruction failed
The requested command returns an error in its request confirmation
Note: Some CIP error codes are public and can be generated also by the
controller. Make sure the error was not generated by the controller.
Resources unavailable
Out of segments
System has no segments left to
execute the command
Resources unavailable
Out of CIP com buffer
System has no CIP
communication buffer left to
execute the command
Check the number of parallel CIP
messages send to the module.
The module can process 5 CIP
messages in parallel. Note that
RSLinx can already consume 2 of
this CIP com buffers if the online
browser is active.
Resources unavailable
Out of command buffer
System has no command buffer
left to execute the command
The service code of the
requested object is not
supported
Check parameter of the CIP
Message
The attribute of the requested
object is not supported
Check parameter of the CIP
Message
Too little data was transferred
with the CIP Message
Check the "Source Length"
parameter in the parameter
dialog of the CIP Message and
check the consistency of all
length parameter within the
requested command.
Configuration data size too
large
Too much data transferred with
the CIP Message
Check if the overall length of the
requested command send with
the CIP message and the
consistency of all length
parameter within the requested
command is correct.
The requested object does not
exist within the module.
Komentarze do niniejszej Instrukcji