Network, Socket, and Communication Errors

NOTE: Email support_preciseflex@brooksautomation.com for help resolving error codes.

 

Code Text Description

-1700

Cannot get local host name

The Ethernet network is not configured properly. Check the parameter values for DataIDs 420, 421 and 422.

-1701

Cannot get local host address

The Ethernet network is not configured properly. Check the parameter values for DataIDs 420, 421 and 422.

-1702

Connection refused

An attempt to connect to a TCP server was refused. Be sure your IP address and port numbers are correct. Be sure the server is ready to accept connections.

-1703

No connection

An attempt was made to send or receive on socket that was not connected to a TCP or UDP port.

-1704

Invalid network address

The IP address specified cannot be accessed.

-1705

Network timeout

A network operation did not complete within the allowed time period. Depending on the operation, the connection may or may not be closed.

-1706

Already connected

An attempt was made to connect a socket to an IP Address and port when there is already a connection.

-1707

Socket not open

An attempt was made to use a network socket that is not open.

-1708

Connection closed

An attempted was made to use a socket whose connection has been closed either locally or by the remote endpoint.

-1709

Invalid protocol

A message was received that does not follow a known communications protocol.

-1710

Invalid multicast address

The IP address is not a valid multicast address. The recommended range for multicast IP addresses is from 239.192.0.0 through 239.195.255.255.

-1720

Web interface not enabled

An external system attempted to access one of the controller's web pages, but access via the web server has been disabled. To enable the web interface, modify the value of the "Web password security" (DataId 450) database parameter.

-1730

Modbus/RIO exception: n

A MODBUS or RIO board request failed with exception code n. The standard MODBUS exception codes are: 1 = Illegal function, 2 = Illegal data address, 3 = Illegal data value, 4 = Device has failed.

-1731

Modbus/RIO device timeout

A MODBUS device or RIO board is not responding or is not responding within the specified timeout period.

-1732

Modbus/RIO disable requested

A MODBUS device or RIO board connection has closed because of a user request. For example, you have set the parameter "Remote IO module enable" (DataID 554) to zero.

-1740

Servo latency too large

The master controller cannot connect with a slave controller because the measured communications latency is too large or is negative. Typically there should be no more than 80 microseconds of latency between the nodes. Verify that both controllers are on the same LAN and external traffic is low. Verify that your Ethernet switch is operating properly. Verify that the servo network protocols for all nodes are compatible.

-1750

EtherCAT error

 

-1751

EtherCAT slave not responding

 

-1752

EtherCAT synchronous message timeout

 

-1753

EtherCAT slave not ready

 

-1754

EtherCAT disabled