Filter
Top Products
CTI 2572 Installation and Operation Guide
116
HEX DEC Description Possible Corrective Action
2E25 11813 A SEND command was issued on a
Passive connection that has not yet been
established.
Correct the application logic.
2E26 11814 Remote system attempted to open a
connection on a TSAP locally configured
as an Active connection.
Correct the application logic.
2E27 11815 Logic attempted to create an active TCP
connection when the TCP connection is
already established.
Correct the application logic.
2E28 11816 Connection has been lost. Protocol
manager is attempting to re-establish the
connection.
Continue to retry. If the problem persists,
check the network and partner PLC.
2E30 11824 A command is already in process for this
connection number.
Correct the application logic.
2E31 11825 Reserved Not Used in this release
2E32 11826 No data available to Receive command.
Occurs when timeout value of 0 is
specified and no data is currently
available to be read.
Retry the command. If the problem
persists check the partner PLC.
2E33 11827 Error writing to local V memory during
Receive command
Retry the command. If the problem persists
check the PLC I/O configuration and
applicable Command Block entries.
2E34 11828 Error reading from V memory during Send
command
Retry the command. If the problem persists
check the PLC I/O configuration and
applicable Command Block entries.
2E35 11829 The partner controller is not accepting
additional data. TCP window size has
been set to 0 by the partner.
Ensure that the partner controller is running
logic (in Run mode).
Reduce the rate at which messages are
sent to the partner.
2E40 11840 Incoming packet data length is 0. Check partner PLC configuration.
2E41 11841 Incoming packet data length is longer
than the data length specified in the
command block.
This is a warning message that you can
use in your application logic. You may
choose to ignore the error and use the
truncated data.
2E64 -
2E96
11876 -
11926
System Errors. Contact Technical Support.
2E97 11927 Invalid command code. Correct Command Block Entry.
2E98 -
2EFF
11928 -
12031
System errors Contact Technical Support.
DataShare Error Codes
When DataShare detects specified error conditions, it will report them to the PLC application in the
first word of the applicable Command Block. These errors are reported to the PLC only when a
command has been triggered by PLC logic. Errors that occur after successful completion of initiating
command has successfully completed are not reported to the PLC by the protocol.
When automatic triggering is selected (PLC scan, timer, etc.), DataShare will indicate an error
condition only when the DataShare instance is initiated. During the processing of starting a producer
instance, one message will be produced to verify that Ethernet can be accessed. Even when using
one of the automatic triggering options, you can use application logic to detect run time problems.
For example, the logic could periodically trigger a manual production to test the network. A
consumer application could use the embedded sequence number (written to the first V memory