Omron V330-F Series Quick Start Manual page 69

9.7.2. TCP Connection Status Error and Correction
This section describes the situation and corrections if a TCP connection status error
occurs.
● Effect of a TCP Connection Status Error
If, after the occurrence of a TCP connection status error, you execute the project file again
without taking any corrective action or without noticing the error, the following error may
occur: The remote node specified by the input variable DstAdr (Destination Address) or
DstTcpPort (Destination Port) is not waiting for a connect request. (Hereinafter, this error is
referred to as "open processing error".) This is considered as the effect of the TCP
connection status error at the end of the previous communications processing. Refer to
9.7.1 Error Code List for details of errors that occurred.
● Situation When a TCP Connection Status Error Occurs
Both a TCP connection status error after close processing and an open processing error in
the next communications processing due to the effect of the TCP connection status error
can occur because the close processing has not completed in the code reader. In this
situation, despite that the controller has ended all processing steps (up to close
processing) in the project file, it has not received the close completion notification from the
code reader (i.e., the completion of the close processing in the code reader is not
confirmed).
● Correction
Check whether the communications port of the code reader is closed since the close
processing may not be completed in the code reader. As a result, if the communications
port of the code reader is not closed or its state cannot be confirmed, the communications
port must be reset. To reset the communications port of the code reader, you can use
software restart or turn OFF and then ON the power supply. For details, refer to the manual
for the code reader.
Precautions for Correct Use
Reset the communication port of the code reader after confirming that it is not connected to
another device.
● Situation When a TCP Connection Status Error Occurs in the Controller (Built-in
EtherNet/IP Port)
When a TCP connection status error occurs, the project file has ended its processing, but
resending and time monitoring by the built-in EtherNet/IP port (TCP/IP function) may be
active, as described in Resending and Time Monitoring Using the Built-in EtherNet/IP Port
(TCP/IP) in 9.3.2. Time Monitoring Function. However, this resending will stop under the
following situations, so there is no particular need to consciously stop it.
• The project file is executed and an open processing request is issued again.
• A communications problem such as cable disconnection is resolved during resending.
• Resend processing is ended by the TCP/IP time monitoring (timeout) function.
• The controller is restarted or turned OFF.
9. Project File
66