--- title: LioN-X slug: litmusedge-v1/quickstart-guide/industrial-systems-connection-guide/lumberg-automation/lion-x description: Review the following information for setting up and configuring the LioN-X driver. docTags: createdAt: 2023-03-22T19:31:43.000Z --- :::hint{type="info"} **Note**: This driver is available for Litmus Edge version 3.5.2 and later. ::: Review the following information for setting up and configuring the LioN-X driver. # Litmus Edge Compatible Series | Compatibility parameter | Compatible items | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Driver type** | Ethernet | | **Validated devices/series** | [Lumberg Automation LioN-X](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 *Step 3: Configure the List of Registers* below to learn more. | # Step 1: Set up and Configure the Driver To find the network parameters of the driver, you have the option of using the [Device Discovery Tool](docId\:N9jtAdKuUXNU_YNhq87x4). Otherwise, set up the device for Ethernet access and collect the network parameters. **To use the device discovery tool:** 1. Navigate to **DeviceHub **> **Devices**. 2. Click the **Connect a Device** box. The *Connect Device *dialog box appears. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/kWeqiHESLSAdRZjSpgRN0_connectdevice.png" size="80" width="1046" height="528" caption="Connect a Device box" position="center" showCaption="true"} 3. Click the **Device Type** drop-down list and select **Lumberg Automation**. 4. Click the **Driver Name** drop-down list, and select **LioN-X**. 5. Click **Device Discovery**. The *Device Discovery* dialog box appears. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/Yyb3SRNTlXOjTnIkJc5U3_lionxdevicediscovery.png" size="80" width="1161" height="777" caption="Device Discovery option" position="center" showCaption="true"} 6. 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. 7. Delete all text from the field not being used. 8. Click **Start discovery**. When the search is complete, available servers with corresponding security policies will be listed. 9. 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. 10. In the **Driver Mode** field, select either **Polling **or **Subscription**. 11. 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\:pal6ABPZbrimdU9LvGJ30) 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 Browse for tags to add to this FreeTag device. See [Browse Tags](docId\:oJJP6qm8xNGDuIgG8xZdd) to learn more. Alternatively, when you [Add Tags](docId:8sE7z3PmRfwL1nmzcwaLX), for **Name** map the LioN-X server tags to the client using this format, where the semicolon is significant: `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[]` ## 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. :::hint{type="info"} **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). :::