JTEKT Toyopuc CMP-Link Ethernet (Gen1)

review the following information for setting up and configuring the jtekt toyopuc cmp link ethernet (gen1) driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series jtekt toyopuc pc10 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 plc software on your computer to configure the device for ethernet access step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device docid 3eyafppweuvmblcey17sq with this driver update default values to the specific setup of your device parameter value type jtekt toyopuc driver jtekt toyopuc cmp link ethernet (gen1) network address the device address you defined in step 1 network port 4096 step 3 configure the list of registers when you add tags docid 8se7z3pmrfwl1nmzcwalx to the connected device, refer to the following register table and tag parameters refer to the following additional resources device and tag metadata use case docid 583p fbuozem6whgrdgkq tag formula variables docid\ ifbwcou90qtfodk hrysr register table name value types address format min address max address 1x bit r/w hhh 0 2047 2x bit r/w hhh 0 2047 3x bit r/w hhh 0 2047 1y bit r/w hhh 0 2047 2y bit r/w hhh 0 2047 3y bit r/w hhh 0 2047 1m bit r/w hhh 0 2047 2m bit r/w hhh 0 2047 3m bit r/w hhh 0 2047 1k bit r/w hhh 0 2047 2k bit r/w hhh 0 2047 3k bit r/w hhh 0 2047 1l bit r/w hhh 0 2047 2l bit r/w hhh 0 2047 3l bit r/w hhh 0 2047 1v bit r/w hh 0 255 2v bit r/w hh 0 255 3v bit r/w hh 0 255 1t bit r/w hhh 0 2047 2t bit r/w hhh 0 2047 3t bit r/w hhh 0 2047 1c bit r/w hhh 0 2047 2c bit r/w hhh 0 2047 3c bit r/w hhh 0 2047 1s bit r/w hhhh 0 16383 2s bit r/w hhhh 0 16383 3s bit r/w hhhh 0 16383 1n bit r/w hhhh 0 8191 2n bit r/w hhhh 0 8191 3n bit r/w hhhh 0 8191 1d bit r/w hhhhh 0 196607 2d bit r/w hhhhh 0 196607 3d bit r/w hhhhh 0 196607 1r bit r/w hhhhh 0 32767 2r bit r/w hhhhh 0 32767 3r bit r/w hhhhh 0 32767 b bit r/w hhhhh 0 131071 h bit r/w hhhh 0 32767 u bit r/w hhhhhh 0 2097151 ex bit r/w hhh 0 2047 ey bit r/w hhh 0 2047 em bit r/w hhhh 0 16383 ek bit r/w hhh 0 2047 el bit r/w hhh 0 2047 ev bit r/w hhhh 0 16383 et bit r/w hhh 0 2047 ec bit r/w hhh 0 2047 es bit r/w hhhh 0 16383 en bit r/w hhhh 0 16383 gx bit r/w hhhh 0 65535 gy bit r/w hhhh 0 65535 gm bit r/w hhhh 0 65535 eb bit r/w hhhhhh 0 4194303 fr bit r/w hhhhhh 0 2097151 1xw bit r/w hh 0 127 2xw bit r/w hh 0 127 3xw bit r/w hh 0 127 1yw bit r/w hh 0 127 2yw bit r/w hh 0 127 3yw bit r/w hh 0 127 1mw bit r/w hh 0 127 2mw bit r/w hh 0 127 3mw bit r/w hh 0 127 1kw bit r/w hh 0 127 2kw bit r/w hh 0 127 3kw bit r/w hh 0 127 1lw bit r/w hh 0 127 2lw bit r/w hh 0 127 3lw bit r/w hh 0 127 1vw bit r/w h 0 15 2vw bit r/w h 0 15 3vw bit r/w h 0 15 1tw bit r/w hh 0 127 2tw bit r/w hh 0 127 3tw bit r/w hh 0 127 1cw bit r/w hh 0 127 2cw bit r/w hh 0 127 3cw bit r/w hh 0 127 1sw bit r/w hhh 0 16383 2sw bit r/w hhh 0 1023 3sw bit r/w hhh 0 1023 1nw bit r/w hhh 0 511 2nw bit r/w hhh 0 511 3nw bit r/w hhh 0 511 1dw bit r/w hhhh 0 12287 2dw bit r/w hhhh 0 12287 3dw bit r/w hhhh 0 12287 1rw bit r/w hhhh 0 2047 2rw bit r/w hhhh 0 2047 3rw bit r/w hhhh 0 2047 bw bit r/w hhhh 0 8191 hw bit r/w hhh 0 2047 uw bit r/w hhhhh 0 131071 exw bit r/w hh 0 127 eyw bit r/w hh 0 127 emw bit r/w hhh 0 1023 ekw bit r/w hh 0 127 elw bit r/w hh 0 127 evw bit r/w hhh 0 1023 etw bit r/w hh 0 127 ecw bit r/w hh 0 127 esw bit r/w hhh 0 1023 enw bit r/w hhh 0 1023 gxw bit r/w hhh 0 4095 gyw bit r/w hhh 0 4095 gmw bit r/w hhh 0 4095 wt bit r/w h 0 6 ebw bit r/w hhhhh 0 262143 frw bit r/w hhhhh 0 131071 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 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 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 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)