SEND_REQ: Communication and Operation Reports

Overview

Communication and operation reports are part of the management parameters.

NOTE: It is recommended that communication function reports always be tested at the end of their execution and before the next activation. On cold start-up, it is imperative that all communication function management parameters be checked and reset to 0.

It may be helpful to use the %S21 to examine the first cycle after a cold or warm start. For more information, refer to Control Expert online help for %S21.

Communication Report

This report is common to all functions. It is significant when the value of the activity bit switches from 1 to 0. The reports with a value between 16#01 and 16#FE concern errors detected by the processor that executed the function.

The different values of this report are indicated in the following table:

Value	Communication report (least significant byte)
16#00	Correct exchange
16#01	Exchange stop on timeout
16#02	Exchange stop on user request (CANCEL)
16#03	Incorrect address format
16#04	Incorrect destination address
16#05	Incorrect management parameter format
16#06	Incorrect specific parameters
16#07	Problem in sending to the destination
16#08	Reserved
16#09	Insufficient receive buffer size
16#0A	Insufficient send buffer size
16#0B	No system resources: the number of simultaneous communication EFs exceeds the maximum that can be managed by the processor
16#0C	Incorrect exchange number
16#0D	No telegram received
16#0E	Incorrect length
16#0F	Telegram service not configured
16#10	Network module missing
16#11	Request missing
16#12	Application server already active
16#13	UNI-TE V2 transaction number incorrect
16#FF	Message refused

NOTE: The function can detect a parameter error before activating the exchange. In this case the activity bit remains at 0, and the report is initialized with values corresponding to the error.

Operation Report

This report byte is specific to each function, and specifies the result of the operation on the remote application.

It is significant only if the communication report has the following values:

16#00 (correct exchange),
16#FF (message refused).

If the value of the communication report is 16#00, the operation report will have the following values:

Value	Operation report (most significant byte)
16#00	Positive result
16#01	Request not processed
16#02	Incorrect response
16#03	Reserved
Other Values:
Request code + 16#30	Upon positive reply for certain requests
16#FE	Upon positive reply for certain requests
16#FB	Upon reply to a minor request

If the value of the communication report is 16#FF, the operation report will have the following values:

Value	Operation report (most significant byte)
16#01	No resources towards the processor
16#02	No line resources
16#03	No device or device without resources (*)
16#04	Line error
16#05	Length error
16#06	Faulty communication channel
16#07	Addressing error
16#08	Application error
16#0B	No system resources: the number of simultaneous communication EFs exceeds the maximum that can be managed by the processor
16#0C	Communication function not active
16#0D	Destination missing. For a CIP request, it is detected on a request timeout.
16#0F	Intra-station routing problem or channel not configured
16#11	Address format not managed
16#12	No destination resources. For a CIP request, this can occur when the device number is not part of the configuration.
16#14	Non-operational connection (example: Ethernet TCP/IP)
16#15	No resource on the local channel. For a CIP request, it may be that there are no resources to handle the message; or it is an internal error: no buffer available, no link available, impossible to send message.
16#16	Access not authorized (example: Ethernet TCP/IP)
16#17	Inconsistent network configuration (example: Ethernet TCP/IP)
16#18	Connection temporarily unavailable: For a CIP request, it may be that another explicit message is in progress for this device, or a TCP connection or encapsulation session is in progress.
16#21	Application server stopped
16#30	Transmission error. For a connected CIP request, it may occur when the connection opening times out.
16#80...16#87: Forward_Open response errors:
16#80	Internal error
16#81	Configuration error: the length of the explicit message, or the RPI rate, needs to be adjusted
16#82	Device error: target device does not support this service
16#83	Device resource issue: no resource is available to open the connection
16#84	System resource issue: unable to reach the device
16#85	Data sheet error: incorrect EDS file
16#86	Invalid connection size
16#90...16#9F: Register session response errors
16#90	Target device does not have sufficient resources
16#98	Target device does not recognize message encapsulation header
16#9F	Unknown error from target

Legend:
(*)	Code only managed by PCMCIA cards: TSX FPP20 and TSX FPP10