CODESYS V2 Ethernet Absolute (Gen1.3)
Review the following information for setting up and configuring the CODESYS V2 Ethernet Absolute (Gen1.3) driver.
Litmus Edge Compatible Series
Compatibility parameter | Compatible items |
|---|---|
Driver type | Ethernet |
Validated devices/series | WAGO 750-841 |
Replaces Gen 1 driver(s) | CodeSys Ethernet (Gen1.3) |
To set up and configure this device in Litmus Edge, you will need to do the following:
- Step 1: Set up and Configure the PLC Device
- Step 2: Set up the PLC Device in Litmus Edge 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 including the IP address and port number (default port is typically 2455 for CODESYS V2 devices).
Step 2: Set up the PLC Device in Litmus Edge 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 | CodeSys devices |
Driver | CODESYS V2 Ethernet Absolute (Gen1.3) |
Network Address | The device IP address you recorded in Step 1. |
Port | 2455 |
Step 3: Configure the List of Registers
When you Add a Tag to the connected device, refer to the following register table and tag parameters. Refer to the following additional resources:
Register Table
Name | Value Types | Access Types | Address Format | Min Address | Max Address | Description |
|---|---|---|---|---|---|---|
IX | bit | R/W | DDDDDdd | 0 | 6553515 | Input Bit |
QX | bit | R/W | DDDDDdd | 0 | 6553515 | Output Bit |
MX | bit | R/W | DDDDDdd | 0 | 6553515 | Memory Bit |
IW | word | R/W | DDDDD | 0 | 65535 | Input Word |
QW | word | R/W | DDDDD | 0 | 65535 | Output Word |
MW | word | R/W | DDDDD | 0 | 65535 | Memory Word |
ID | word | R/W | DDDDD | 0 | 65535 | Input Double Word |
QD | word | R/W | DDDDD | 0 | 65535 | Output Double Word |
MD | word | R/W | DDDDD | 0 | 65535 | Memory Double Word |
Tag Parameters
- Name: Select a register name from the drop-down list. The available options depend on the names in the register table.
- Value Type: Select a data type from the drop-down list. The available options depend on the register name selected.
- 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.
- Address: Enter a tag address. The value must be in decimal format, within the allowed min/max range. Omit the leading zeros. For Bit tags, append the bit address without the bit separator. The lowercase letters in the address format indicate how many digits you should enter in the Bit address.
- Count: Enter the number of register values to read. A count higher than 1 will generate an array of values from the address value configured and respective subsequent address values.
- 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 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).