LioN-X
Note: This driver is available for Belden Horizon Data Operations version 3.5.2 and later.
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 | 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 Connect a Device 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:
|
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 Add Tags to the connected device, refer to the following tag parameters and available value types.
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: 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 only publish NATS messages when the value parameter changes to a new value. 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. Metadata 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).