Read/write status codes for direct communication drivers

0

OK

Communicating without error.

None required.

-1

Invalid serial port

• The selected serial port is invalid or unaccessible.

• The port is already in use

• Select another serial port in driver settings.

• Check the serial port settings.

-2

Invalid baud rate

The selected baud rate is invalid.

Select a baud rate in the valid range.

-3

Invalid number of bits

The selected number of bits for the serial port is invalid.

Select a number of bits in the valid range.

-4

Invalid number of stop bits

The selected number of stop bits for the serial port is invalid.

Select a number of stop bits in the valid range.

-5

Invalid parity

The selected parity for the serial port is invalid.

Select a parity in the valid range.

-6

Invalid IRQ

The selected IRQ for the serial port is invalid.

Select an IRQ in the valid range.

-7

Serial port already in use

The selected port is being used by other process.

Choose another serial port for communication.

-8

Invalid buffer size

The buffer size entered is not allowed.

Check the documentation for allowed buffer sizes.

-9

Memory not enough

Out of memory in the system.

Close other processes that may be consuming memory.

-10

Tx buffer empty

The CE device was not able to write the message on the serial port.

Check if the serial port is valid and accessible.

-11

Tx buffer full

The TX buffer has more data than allowed.

Increase the TX buffer size in driver settings.

-12

Rx buffer empty

No data was received.

Check if the serial port is valid and the device is sending data.

-13

Rx buffer full

The RX buffer has more data than allowed.

Increase the RX buffer size in driver settings.

-14

Timeout waiting CTS

The CTS was not received in the expected time.

• Verify if the device should send the CTS, otherwise disable the Verify CTS option.

• Increase the Wait CTS timeout in Advanced Driver Settings

-15

Timeout waiting for message to start

• Disconnected cables.

• PLC is turned off, in stop mode, or in error mode.

• Wrong station number.

• Wrong parity (for serial communication).

• Wrong RTS/CTS configuration (for serial communication).

• Check cable wiring.

• Check the PLC mode — it must be RUN.

• Check the station number.

• Increase the timeout in the driver's advanced settings.

• Check the RTS/CTS configuration (for serial communication).

-16

Timeout waiting for message to finish

The message took too long to be received as completed.

Increase the timeout for End message in driver settings.

-17

Timout between rx character

The time between characters is too long.

Increase the Interval between char in driver settings.

-18

Timout between tx character

• The time to write the buffer has exceeded the limit.

• The driver was not able to write the buffer

Check the serial port settings. Increase the Interval between char in driver settings.

-19

No carrier detected

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-20

No DSR detected

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-21

Could not find a 8250 in address

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-22

Tx line is busy

The TX buffer is full and unable to write to the serial buffer.

• Check the serial port configuration and status.

• Check the device status.

-23

User abort

User has aborted the request.

Retry the request without aborting it.

-24

Function not supported

Serial port received an unsupported function.

Check the serial port configuration and status.

-25

Overrun

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-26

Parity

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-27

Overrun and parity

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-28

Framing

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-29

Framing and overrun

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-30

Framing and parity

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-31

Framing, overrun, and parity

Invalid serial port configuration or hardware fault.

Check the serial port configuration and status.

-32

Timeout waiting for a tx message to finish

The message could not be sent completely or partially.

• Check the serial port configuration and status.

• Check the device configurations.

-33

Invalid driver configuration file

The driver configuration file (drivername.ini) is missing or corrupt.

Reinstall the driver.

-34

Invalid address

The specified address is invalid or out of range.

Check the supported range of addresses described in this document, and then correct the address.

-35

Driver API not initialized

The driver library did not initialize.

Contact technical support.

-36

Invalid data type

The specified data type is invalid or out of range.

Check the supported data types described in this document, and then correct the data type.

-37

Invalid header

The specified header in the driver worksheet is invalid or out of range.

Check the supported range of headers described in this document, and then correct the header.

-38

Invalid station

The specified station in the driver worksheet is invalid or out of range.

Check the supported station formats and parameters described in this document, and then correct the station.

-39

Invalid block size

Worksheet is configured with a range of addresses greater than the maximum block size.

Check the maximum block size number of registers described in this document, and then configure your driver worksheet to stay within that limit. Keep in mind that you can create additional worksheets.

Note: If you receive this error from a Main Driver Sheet or Tag Integration configuration, please contact Technical Support.

-40

Invalid bit write

Writing to a bit using the attempted action is not supported.

• Writing to a bit using Write Trigger is not supported in some drivers. Modify the driver worksheet to use Write On Tag Change.

• The bit is read-only.

-42

Invalid bit number

The bit number specified in the address is invalid. The limit for the bit number depends on the registry type.

Check the addresses to see if there are bit numbers configured outside the valid range for the registry.

-43

Invalid byte number

The byte number specified in the address is invalid. The limit for the byte number depends on the registry type.

Check the addresses to see if there are byte numbers configured outside the valid range for the registry.

-44

Invalid byte write

Writing to a byte using the attempted action is not supported.

The byte is read-only or inaccessible.

-45

Invalid string size

The string is more than 1024 characters.

Modify the addresses that have string data type to be less than 1024 characters.

-50

Invalid modem

The selected modem name is invalid.

Select a valid modem name in driver settings.

-51

Error initializing TCP

The TCP library is not available for serial encapsulation.

Reinstall the driver.

-52

Error listening to port

The port selected in serial encapsulation settings is not available.

• Check for other processes that might be using the same port number.

• Check the selected port number.

-53

Error initializing UDP

The UDP library is not available for serial encapsulation.

Reinstall the driver.

-54

Error sending data packet (TCP or UDP)

The TCP/UDP library was not able to send the packet.

Check the serial encapsulation settings.

-55

Error not connected

Modem is not connected.

• Check the modem settings.

• Check if the modem dial number is available.

-56

Invalid connection handle

The connection is no longer valid.

Please contact Technical Support.

-57

Message could not be sent

The socket was unable to send the TCP or UDP message.

• Check the station IP address and port number.

• Confirm that the device is active and accessible. Try to ping the address.

-58

TCP/IP could not send all bytes

The TCP/IP stack was not able to send all bytes to destination.

• Check the station IP address, port number and/or ID number.

• Confirm that the device is active and accessible.

• Try to ping the address.

-60

Error to establish TCP/IP connection

Error while establishing a TCP/IP connection with the unit device. Possibly incorrect IP address or port number in the specified station.

• Check the station IP address, port number and/or ID number.

• Confirm that the device is active and accessible.

• Try to ping the address.

-61

TCP/IP socket error

The TCP/IP connection has been closed by the device.

Confirm that the device is active and accessible. Try to ping the address.

-62

UDP/IP receive call returned error

The UDP socket is in error.

• Check the station IP address, port number and/or ID number.

• Confirm that the device is active and accessible.

• Try to ping the address.

-63

UDP/IP error initializing

The UDP socket initialization failed.

Confirm that the operating system supports UDP sockets.

-64

UDP/IP receive call returned error

The UDP socket is in error.

• Check the station IP address, port number and/or ID number.

• Confirm that the device is active and accessible.

• Try to ping the address.

-65

UDP/IP bind error, port number may already be in use

The driver was not able to bind the UDP port.

• Check the port number used by the driver.

• Check for other programs that might be bound to the UDP port.

-66

Unlicensed driver

Your runtime license does not allow you to run this driver.

Contact your software distributor.