OPC UA Client Advanced

review the following information for setting up and configuring the opc ua client advanced litmus edge compatible series compatibility parameter compatible items driver type ethernet functionality recommended driver to use to connect to an opc ua server provides subscribe and polling modes support opc ua alarms and events see use the opc ua client advanced driver for opc ua alarms & events docid 4 oqkh6mte4xuqkh rxbk for more details opc ua server needs to be configured accordingly replaces gen 1 driver(s) opc ua client opc ua client poll opc ua client (gen1) opc ua client subscribe (gen1) learn more about gen1 and gen2 driver differences docid 27hyoelb0soehmysjqod5 step 1 set up and configure the driver to find the network parameters of the driver, you have the option of using the asset discovery tool docid\ pvdhiqdfezem4kmkyjk5p otherwise, set up the device for ethernet access and collect the network parameters to use the device discovery tool navigate to devicehub > devices click the connect a device box the connect device dialog box appears click the device type drop down list and select opcua click the driver name drop down list, and select opc ua client advanced click device discovery the device discovery dialog box appears select only one of the following fields to use for discovering the device discovery server url (servers and endpoints discovery) no prior setup/configuration is needed to use this field replace localhost with the appropriate ip address or domain name that will be used to search for the device ensure the correct port number is entered server url (endpoints discovery) you'll need to enable/configure the server to use this field replace localhost with the appropriate ip address or domain name that will be used to search for the device ensure the correct port number is entered delete all text from the field not being used click start discovery when the search is complete, available servers with corresponding security policies will be listed click the appropriate server/security policy, and then click update form with discovery results the connect device dialog box appears with server url , security policy , and security mode pre filled based on the discovery results in the driver mode field, select either polling or subscription move onto step 2 and continue configuring the driver with the remaining parameters step 2 set up the driver in litmus edge devicehub configure the following parameters when you connect a device docid 3eyafppweuvmblcey17sq with this driver update default values to the specific setup of your device parameter value type opc ua driver opc ua client advanced driver mode polling or subscription server url the server endpoint url defined in step 1 security policy the policy you defined in step 1 security mode the mode you defined in step 1 certificate auto generated private key auto generated auth mode anonymous, certificate, or username disable error certificate host name invalid false or true default root start node to browse the server step 3 configure the list of registers browse for tags to add to this freetag device see browse tags docid\ ml 1dnqkd6d zhzbe7qmw to learn more alternatively, when you add tags docid\ xgwokqbtpevii7or82ll0 , for name map the opc server tags to the client using this format ns=1;s=tagname example ns=2;s=demo static scalar boolean the following value types are supported bool sbyte byte int16 uint16 int32 uint32 int64 uint64 float32 float64 string blob bool\[] sbyte\[] byte\[] int16\[] uint16\[] int32\[] uint32\[] int64\[] uint64\[] float32\[] float64\[] string\[] blob\[] refer to the following tag parameters tag parameters name enter a name based on this format ns=1;s=tagname example ns=2;s=demo static scalar boolean value type select a data type from the drop down list polling interval enter a value in seconds this determines how often the tag should poll the register for data tag name enter a name for the tag description (optional) enter a description for the tag tag formula enter a formula for the tag to process the generated data two variables are permitted value (current tag value) and timestamp (current tag unix time in milliseconds) the following math functions are available sin cos sqrt tan power power( x ) performs the operation 10^x log log( x ) is the natural logarithm (the logarithm is in base e ) exp exp( x ) performs the operation e^x only publish on change of value select the checkbox to customize nats messages to be published only when the value parameter changes from a previous value to a new one change of value only applies to boolean, numeric (such as int or float), and simple string data types it does not apply to complex types, such as json or array poll once topics will not be affected by change of value settings these topics will still only see a single message meta data metadata summarizes basic information about data this feature allows you to define key value pair data for the device output payload later on it can then be used to find, use, and reuse particular instances of data note if you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload this can cause two key names to be combined into one for example, configuring the key names a b and a&\&b will cause only one key name to be created (a b) tag parameters name enter a name based on this format ns=1;s=tagname example ns=2;s=demo static scalar boolean value type select a data type from the drop down list polling interval enter a value in seconds this determines how often the tag should poll the register for data tag name enter a name for the tag description (optional) enter a description for the tag tag formula enter a formula for the tag to process the generated data two variables are permitted value (current tag value) and timestamp (current tag unix time in milliseconds) the following math functions are available sin cos sqrt tan power power( x ) performs the operation 10^x log log( x ) is the natural logarithm (the logarithm is in base e ) exp exp( x ) performs the operation e^x only publish on change of value select the checkbox to customize nats messages to be published only when the value parameter changes from a previous value to a new one change of value only applies to boolean, numeric (such as int or float), and simple string data types it does not apply to complex types, such as json or array poll once topics will not be affected by change of value settings these topics will still only see a single message meta data metadata summarizes basic information about data this feature allows you to define key value pair data for the device output payload later on it can then be used to find, use, and reuse particular instances of data note if you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload this can cause two key names to be combined into one for example, configuring the key names a b and a&\&b will cause only one key name to be created (a b)