Opto22 MMIO Protocol Ethernet (Gen1.3)

review the following information for setting up and configuring the opto22 mmio protocol ethernet (gen1 3) driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series opto22 snap pac system 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 your 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\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device parameter value type opto devices driver opto22 mmio protocol ethernet (gen1 3) network address the device address you defined during step 1 port 2001 step 3 configure the list of registers when you add a tag docid\ tuy hh0gi8djvot70wroh to the connected device, see the following register table and tag parameters sections you can also browse and add tags from a device docid 8oruw1cmtao49bwbbhwrn for the device see the following additional resources if necessary organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n tag formula variables docid\ io7xgyrdvv vmpnfxoaci register table name value types address format min address max address state bit dd 0 63 onlatch bit dd 0 63 offlatch bit dd 0 63 activecounter bit dd 0 63 onlatch readclear bit dd 0 63 offlatch readclear bit dd 0 63 hdd state bit dddd 0 1531 hdd onlatch bit dddd 0 1531 hdd offlatch bit dddd 0 1531 hdd onlatch clear bit dddd 0 1531 hdd offlatch clear bit dddd 0 1531 alarm hi state bit dd 0 63 alarm hi enable bit dd 0 63 alarm lo state bit dd 0 63 alarm lo enable bit dd 0 63 sp bit bit dd 0 63 eu dword dd 0 63 counts dword dd 0 63 min dword dd 0 63 max dword dd 0 63 min readclear dword dd 0 63 max readclear dword dd 0 63 eu 4096 dword dddd 0 4095 counts 4096 dword dddd 0 4095 min 4096 dword dddd 0 4095 max 4096 dword dddd 0 4095 min readclear 4096 dword dddd 0 4095 max readclear 4096 dword dddd 0 4095 counterdata dword dd 0 63 counterdata readclear dword dd 0 63 hdd counter dword dd 0 15 hdd counter readclear dword dd 0 15 hdd bank state dword dd 0 15 hdd bank onlatch dword dd 0 15 hdd bank offlatch dword dd 0 15 moduletype dword dd 0 63 pointtype dword dd 0 63 feature dword dd 0 63 offset dword dd 0 63 gain dword dd 0 63 hiscale dword dd 0 63 loscale dword dd 0 63 moduletype 4096 dword dddd 0 4096 pointtype 4096 dword dddd 0 4096 feature 4096 dword dddd 0 4096 offset 4096 dword dddd 0 4096 gain 4096 dword dddd 0 4096 moduhiscale 4096 dword dddd 0 4096 loscale 4096 dword dddd 0 4096 alarm hi setpoint dword dd 0 63 alarm hi deadband dword dd 0 63 alarm lo setpoint dword dd 0 63 alarm lo deadband dword dd 0 63 sp integer dword ddddd 0 10239 sp float dword ddddd 0 10239 sp string dword dddd 0 6300 pid cv in dword ddd 0 127 pid cv sp dword ddd 0 127 pid cv out dword ddd 0 127 pid cv ff dword ddd 0 127 pid cv error dword ddd 0 127 pid cv p dword ddd 0 127 pid cv i dword ddd 0 127 pid cv d dword ddd 0 127 pid cv integral dword ddd 0 127 pid lsv in dword ddd 0 127 pid lsv sp dword ddd 0 127 pid status dword ddd 0 127 pid status on dword ddd 0 127 pid status off dword ddd 0 127 pid tune p dword ddd 0 127 pid tune i dword ddd 0 127 pid tune d dword ddd 0 127 pid tune ff dword ddd 0 127 pid cfg max out dword ddd 0 127 pid cfg min out dword ddd 0 127 pid cfg scan time dword ddd 0 127 pid cfg low range dword ddd 0 127 pid cfg hi range dword ddd 0 127 pid cfg alg dword ddd 0 127 pid cfg man mode dword ddd 0 127 pid cfg flags dword ddd 0 127 pid cfg flags on dword ddd 0 127 pid cfg flags off dword ddd 0 127 pid cfg mm in dword ddd 0 127 pid cfg mm sp dword ddd 0 127 pid cfg mm out dword ddd 0 127 pid scale in low dword ddd 0 127 pid scale in hi dword ddd 0 127 pid scale out low dword ddd 0 127 pid scale out hi dword ddd 0 127 pid scan counter dword ddd 0 127 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 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)