Skip to content

Endpoint Discovery

The OPC-UA Device Service can automatically discover OPC-UA endpoints.

A Local Discovery Server (LDS) must be set up as a device in Edge Xpert to use device discovery.

Note

Endpoint discovery is not supported for HTTPS servers and endpoints.

The device discovery process is as follows:

  1. A discovery request is sent to the OPC-UA Device Service

  2. The OPC-UA Device Service contacts the LDS and requests a list of registered servers

  3. The Device Service requests a list of endpoints from all registered servers

  4. The OPC-UA Device Service adds the endpoints to the Edge Xpert metadata

Driver Configuration

The OPC-UA Device Service must know the name of every LDS used for server discovery.

The environment variables are specified in the environments section of the docker-compose.yml file. The default entry is as follows:

environment:
  <<: *common-variables
  SERVICE_HOST: device-opc-ua
  LDSName:
If you need to update any of the default values, you must create a local copy of docker-compose.yml before starting the OPC-UA Device Service. Once you have created the local file, you can update the environments section and start Edge Xpert from your working directory.

You can configure the environment variables to match your requirements, as shown in the following table:

Environment Variable Description
LDSName The names of LDS devices in Edge Xpert for discovery
Multiple LDS can be specified using a semi-colon as a delimiter

Driver Metadata

The following protocol properties are generated for each discovered endpoint:

  • Address

  • Security

  • SecurityMode

  • ApplicationURI

Note

Security, SecurityMode, and ApplicationURI are optional and are only generated if the endpoint supports OPC-UA security settings.

Back to top