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 docid\ pal6abpzbrimdu9lvgj30 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 docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following register table and tag parameters refer to the following additional resources organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n tag formula variables docid\ io7xgyrdvv vmpnfxoaci 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)