ProSoft Technology PS69-DPM - Manual (Page 87)

PS69-DPM ♦ CompactLogix or MicroLogix Platform Contents
PROFIBUS DPV1 Master User Manual
ProSoft Technology, Inc. Page 87 of 130
October 1, 2014
3.2.5 Messaging Error Codes
This section includes all errors codes and conditions that can occur when using the CIP
messaging commands outlined in the previous sections.
Your application should be constructed in a manner in which it catches the two possible
error cases listed below:
 CIP Message instruction failed itself
 The requested command returns an error in its request confirmation
Only if both possibilities are without any error has the requested command been successful.
CIP Messaging General
Applicable are the generally known error codes for CIP Messages such as "Service Not
Supported". In this case, the parameters of the CIP Message must be checked (Service
Code, Class, Instance ..). All CIP error codes that are returned by the module and their
cause are described in the following table.
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.
CIP
Status
Extended
Status
Meaning Cause Help
02 hex 00CA hex Resources
unavailable
Out of segments System has no segments left to
execute the command
02 hex 03E8 hex 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.
02 hex 0519 hex Resources
unavailable
Out of command
buffer
System has no command buffer
left to execute the command
Call support
08 hex 0000 hex Service not supported The service code of the
requested object is not
supported
Check parameter of the CIP
Message
14 hex 0000 hex Attribute not
supported
The attribute of the requested
object is not supported
Check parameter of the CIP
Message
13 hex 0000 hex Insufficient data 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.