33 (148)
•
Portal
–
Opening connection to <
host
–
Connection established
–
Connection closed
–
Clock synchronised
–
Logging in
–
Synchronising clock
–
Initiating close sequence
–
Connection closed by Broker
–
Connection closed by Broker - Broker is going down
–
Connection closed by Broker - Protocol error
–
Connection closed by Broker - Keep-alive timeout
–
Connection closed by Broker - Another client logged in with same user name or to
same scope
–
Connection closed by Broker - User was still logged in - Retry
–
Logged in
–
Need to synchronise clock, but user has not set a clock update call-back function.
–
Close sequence timed out
–
Ack with sequence number <
sequence number
could not be matched
–
Nak with sequence number <
sequence number
could not be matched
–
Point <
path
not assigned to dataset: Point is inactive
–
Point <
path
not assigned to dataset: Data type does not match
–
Commit command could not be matched
–
Transaction ID <
ID
from cancel command could not be matched
–
RPC response does not match a request
–
RPC method <
method
not found
–
Could not enqueue value for point <
path
: Send queue is full
–
HTTP upgrade error (<
error code
)
–
Invalid character in challenge (<
hexadecimal character code
)
–
Empty challenge
–
Mandatory header field missing
–
Could not connect: Socket error (<
error code
)
–
Could not connect: Connect error (<
error code
)
–
Could not connect: TLS error (<
error code
)
–
Could not connect: Could not resolve host name.
–
Could not connect: Could not send HTTP request.
–
Could not connect: Could not receive HTTP response.
–
Could not connect: Protocol error
Anybus Edge Gateway Reference Guide
SCM-1202-154 1.0 en-US