67 (148)
•
Connection established
The device has established a connection to the portal.
•
Connection closed
The connection to the portal has been closed.
•
Clock synchronised
The device has synchronised its clock with the portal.
•
Logging in
The device is logging in to the portal.
•
Synchronising clock
The device is synchronising its clock with the portal.
•
Initiating close sequence
The device closes the portal connection.
•
Connection closed by Broker
The portal has closed the connection.
•
Connection closed by Broker - Broker is going down
The portal has closed the connection, because the Broker is going down (e.g. for
maintenance).
•
Connection closed by Broker - Protocol error
The portal has closed the connection, because it encountered a protocol error.
•
Connection closed by Broker - Keep-alive timeout
The portal has closed the connection, because the keep-alive mechanism timed out.
•
Connection closed by Broker - Another client logged in with same user name or to same
scope
The portal has closed the connection, because another client logged in with the same user
name or to the same scope. It is not allowed to log in with the same user name from several
clients. And only one producer is allowed to log in to the same scope.
•
Connection closed by Broker - User was still logged in - Retry
The portal has closed the connection, because the same user was still logged in. Both the
existing and the new session have been closed. The device will retry to connect to the portal.
•
Logged in
The device has logged in successfully to the portal.
•
Need to synchronise clock, but user has not set a clock update call-back function.
The device needs to synchronise its clock in order to communicate via the Kolibri protocol.
This warning message means that the device is unable to synchronise the clock with the
portal, because of an internal error. Please contact the manufacturer if you encounter this
error message.
•
Close sequence timed out
A communication timeout occurred while closing the portal connection.
•
Ack with sequence number <
sequence number
> could not be matched
An Ack reply was received from the portal that could not be matched to any request.
Anybus Edge Gateway Reference Guide
SCM-1202-154 1.0 en-US