OPC UA

opc ua advanced driver opc ua is the most common protocol customers integrate with litmus edge ships with several opc ua drivers, but opc ua client advanced is the one to use for new integrations driver ids driver name driver id when to use opc ua client advanced 2372e68f ba1b 46e9 bc07 e92ca006b377 default for new integrations supports browse, dynamicbrowse, streambrowse opcua client (legacy) older deployments only opcua client poll (legacy) older deployments only the two legacy drivers exist for backwards compatibility with collections created before advanced was available new work should use advanced what "advanced" gets you browse discover the full address space of the opc server and import nodes as tags (no manual nodeid entry) dynamicbrowse re browse on demand for servers whose address space changes streambrowse large server browsing without loading the whole tree at once security policies none / basic128rsa15 / basic256 / basic256sha256, plus user / certificate auth subscription mode (push from server) and polling mode for servers without subscriptions create a device with the advanced driver graphql createdevice mutation against /devicehub/v2 minimum fields driverid 2372e68f ba1b 46e9 bc07 e92ca006b377 name human label deviceproperties server url ( opc tcp\ //host\ port ), security policy, auth, etc exact fields come from getdriver template use getdriver(id "2372e68f ") to fetch the full property schema before constructing the mutation device discovery tool the device discovery tool endpoint is opc ua advanced only point it at a server url and it returns the server's endpoint descriptions, supported security policies, and certificates useful before creating a device because you know exactly what security parameters the server accepts browse a device's address space once a device exists createbrowsetask configure the browse (root nodeid, depth, etc ) startbrowsetasks run it browsetask getfoldersfortreeview , browsetask getfolderitems read results cart additems > cart createallregisters turn selected nodes into tags see browse bulk tag discovery workflow # embedded opc ua server (export tags out) separate from the opc ua client driver, litmus edge has an embedded opc ua server that re exposes devicehub tags to downstream opc ua clients apis at /opcua/v2 see configure opc ua server workflow #