69 (148)
•
Could not connect: Could not resolve host name
The host name of the portal could not be resolved to an IP address.
•
Could not connect: Could not send HTTP request
An HTTP request could not be sent while trying to connect to the portal.
•
Could not connect: Could not receive HTTP response
An HTTP response could not be received while trying to connect to the portal.
•
Could not connect: Protocol error
An HTTP protocol error occurred while trying to connect to the portal.
•
Could not connect: Could not log in to proxy server.
The device failed to log in to the proxy server while trying to connect to the portal.
•
Emergency command timeout
A communication timeout occurred while sending an emergency command to the portal.
•
Could not send emergency command: Send error
An error occurred while sending an emergency command to the portal.
•
Keep alive timeout
The keep-alive handshake carried out with the portal timed out.
•
Invalid sequence number <
sequence number
>
A packet with the indicated invalid sequence number was received from the portal.
•
Invalid opcode <
hexadecimal opcode
>
A packet with the indicated invalid opcode was received from the portal.
•
Invalid WebSocket opcode <
hexadecimal opcode
>
A packet with the indicated invalid WebSocket opcode was received from the portal.
•
Closing connection due to communication error (<
error code
>)
The connection to the portal is being closed, because the indicated communication error
occurred.
•
Could not log in: Could not send Login command
The login command could not be sent while logging in to the portal.
•
Could not log in: Timeout
A communication timeout occurred while logging in to the portal.
•
Could not synchronise clock: Send error
The get time command could not be sent while synchronising the device's clock with the
portal.
•
Could not synchronise clock: Timeout
A communication timeout occurred while synchronising the device's clock with the portal.
•
Could not get publish hash: Send error
The get hash command could not be sent while synchronising published nodes with the
portal.
•
Could not get publish hash: Timeout
A communication timeout occurred while synchronising published nodes with the portal.
Anybus Edge Gateway Reference Guide
SCM-1202-154 1.0 en-US