Koyo Ethernet

note this driver is deprecated as of litmus edge version 3 11 0 we recommend using the docid\ qb3gged7ne6 f88qgdjef driver instead review the following information for setting up and configuring the koyo ethernet driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series koyo directlogic series https //www automationdirect com/adc/overview/catalog/programmable controllers/directlogic plcs (micro to small, brick a modular)?gclid=cjwkcajwq wgbhbmeiwazksh6cbiykadshgtwxsutgzdlhyfk7y 0u1z0p6v5wzvcfcztv1ol9k03bocjugqavd bwe#bodycontentppc 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 otherwise, use directsoft6 v6 1 software to configure the device for ethernet access step 2 set up the plc device in litmus edge devicehub configure the following parameters when you docid\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device parameter value type koyo driver koyo ethernet network address the device address you defined during step 1 network port 428784 step 3 configure the list of registers when you docid 8se7z3pmrfwl1nmzcwalx to the connected device, refer to the following register table and tag parameters refer to the following additional resources docid 583p fbuozem6whgrdgkq docid\ ifbwcou90qtfodk hrysr register table name value types address format min address max address gx bit oooo 0 2047 x bit oooo 0 1023 sp bit oooo 0 1023 gy bit oooo 0 2047 y bit oooo 0 1023 c bit oooo 0 1023 s bit oooo 0 1023 t bit ooo 0 255 ct bit ooo 0 255 ccm 31 word hhhh 0 17056 ccm 32 word hhh 0 512 ccm 33 word hhh 0 832 v word ooooo 0 17055 tag parameters name select a register name from the drop down list available options depend on the names in the register table value type select a data type from the drop down list 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 in the decimal format within the allowed min/max range omit the leading zeros the device might use the decimal (d), hexadecimal (h), or octal (o) address format see the register table at the bottom of the dialog box 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 publish nats messages only when the value parameter changes to a new one 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 are not 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)