Log In
Home
05/17/2023
Offline
as opc client can we automatically know devices registered with LDS without LDS address or Lds hostname?
how can you check if a device is a local discovery server on the network with an address or without an address is LDS SERVER?
05/30/2017
Offline
This link describes the discovery process in detail with a flow chart:
05/17/2023
Offline
thanks for replay, but second question
how can you check if a device is a local discovery server on the network under ip adress?
is only under capability (LDS ), or network protocoall and port number!!
05/30/2017
Offline
If you get a response to a connection on port 4840 there is an LDS.
It is not clear what the issue is.
05/17/2023
Offline
not every opc ua Server with port 4840 is an LDS!!!
i mean, i cann start opc ua server on port 4840 like every normal opc ua server and without lds capabiltity!!!!
05/30/2017
Offline
FindServers is designed so clients do not care if a true LDS or a Server is listening on port 4840. The interactions are exactly the same.
Servers should only listen on port 4840 if they are the only server on the device. If there are multiple servers then the device maker needs to ensure an LDS is also running on the device. But it makes no difference from a client perspective.
05/17/2023
Offline
Please correct me if I misunderstood: every server (opc ua) listing on socket port 4840 is an LDS!
05/30/2017
Offline
Every server listening on 4840 looks like an LDS as far as the client is concerned.
If a server, rather than the LDS, listens on 4840 it blocks other servers on the same machine from registering with the LDS. However, this is generally a configuration error and no client needs to designed to deal with the possibility. More importantly, there are use cases where a device owner will want to a secondary UA server on a device to be hidden from discovery so being blocked from registering with an LDS is not a problem.
1 Guest(s)
Usage Policy