Management Parameters: Communication and Operation Reports

At a Glance

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.

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 NOTE: OK value returned when a Modicon M340 CPU sends a `MODBUS BROADCAST` request.
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: OK value returned when a TSX SCP ••• or TSX SCY ••• sends a `MODBUS BROADCAST` request.

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.

NOTE: 16#FF value is returned to indicate a correct exchange using WRITE_VAR function in a Modbus broadcast request. This report value is implemented in TSX SCY 21601 from V2.8 IE46, in TSX SCY 11601 from V1.2 IE11 and in TSX SCP 111/114 from V3.2 IR25.

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 NOTE: For Premium this report signals a bad reception buffer size (the reception buffer is too small to contain the response).
Request code + 16#30	Upon positive reply for certain requests
16#FB	Upon reply to minor request
16#FD	Operational error
16#FE	Upon positive reply for certain request

This list is not exhaustive and depends on the communication function used. Refer to the corresponding communication function for specific values:

Operation report when using SEND_REQ to exchange an UNI-TE request.
Operation report when using SEND_REQ to exchange a Modbus 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
16#0F	Intra-station routing problem or channel not configured
16#11	Address format not managed
16#12	No destination resources
16#14	Non-operational connection (example: Ethernet TCP/IP)
16#15	No resource on the local channel
16#16	Access not authorized (example: Ethernet TCP/IP)
16#17	Inconsistent network configuration (example: Ethernet TCP/IP)
16#18	Connection temporarily unavailable
16#21	Application server stopped
16#30	Transmission error

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