LioN-X
7 min
review the following information for setting up and configuring the lion x driver belden horizon data operations compatible series compatibility parameter compatible items driver type ethernet validated devices/series https //www belden com/dfsmedia/f1e38517e0cd4caa8b1acb6619890f5e/12628 source/lion x product bulletin 2021 03 when configuring tags for this driver, you must enter the case sensitive register name exactly as it is defined in the plc see the free tags section below to learn more to set up and configure this device in belden horizon data operations, you will need to do the following step 1 set up and configure the plc device step 2 set up the plc device in belden horizon data operations devicehub step 3 configure the list of registers step 1 set up and configure the plc device if the device is configured for ethernet access, find its network parameters otherwise, use plc software on your computer to configure the device for ethernet access step 2 set up the plc device in belden horizon data operations devicehub configure the following parameters when you docid\ t cwpe0 jsfw5 aoj8wpp with this driver update default values to the specific setup of your device parameter value type lumberg automation driver lion x driver mode select polling or subscription server url opc tcp\ //localhost 48010 security policy select one of the following aes128sha256rsaoaep aes256sha256rsapss basic128rsa15 basic256 basic256sha256 none security mode select none, sign, or signandencrypt session certificate auto generated session private key auto generated auth mode select anonymous, certificate, or username disable error certificate host name invalid select true or false flag used to disable the check if the hostname the client connected to matches one of the hostnames or ip addresses in the server certificate disable application uri check select true or false flag used to disable the certificate applicationuri match check default root ns=0;i=84 start node to browse the server step 3 configure the list of registers when you docid\ wpe2hmxelarlbnhwbuchy to the connected device, refer to the following tag parameters and available value types refer to the following additional resources docid\ kr5zcbhkxwk89qti0v1t8 docid 9m6xlaq9iopw5alpru96s free tags this driver doesn't have a list of available register names in the devicehub add tag form to add tags, you must enter the case sensitive register name exactly as it is defined in the plc a connected status for the device won't display until a tag with a correct register name is created available value types the following data 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\[] tag parameters name enter the case sensitive register name exactly as it is defined in the plc 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 log exp 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