Roc800 Ethernet

review the following information for setting up and configuring the roc800 ethernet driver litmus edge compatible series 232,302 false true unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type 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 emerson software v2 55 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 193,338 false true unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type 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 you can also search for pre defined device tags docid\ w1est a3midouizrksgvi for the device refer to the following additional resources device and tag metadata use case docid 583p fbuozem6whgrdgkq tag formula variables docid\ ifbwcou90qtfodk hrysr register table 100,304,137,100,101 false true unhandled content type unhandled content type unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type 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 opcode select the opcode to use 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) supported opcodes 6 system configuration 7 read real time clock 8 set real time clock 10 read configurable opcode point data 17 set operator identification 50 request i/o point position 105 request today’s and yesterday’s min/max values 108 request history tag and periodic index 118 request alarm data 119 request event data 135 request single history point data 136 request multiple history point data 137 request history index for a day 138 request daily and periodic history for a day 139 history information data 166 set single point parameters 167 request single point parameters 180 request parameters 181 write parameters 204 long request event data 206 read transaction history data supported point types 60 68 71 84 hart extended point type 85 hart point type 91 system variables 92 93 94 95 communication ports 96 97 98 soft point parameters 99 configurable opcode table 100 101 discrete inputs 103 analog inputs 109 system analog inputs 110 pid control parameters 111 117 modbus configuration parameters 118 modbus register to tlp mapping 119 modbus event, alarm, and history table 120 modbus master modem configuration 121 modbus master table 122 123 security – group configuration 124 history segment configuration 125 history segment 0 point configuration 126 history segment 1 point configuration 127 history segment 2 point configuration 128 history segment 3 point configuration 129 history segment 4 point configuration 130 history segment 5 point configuration 131 history segment 6 point configuration 132 history segment 7 point configuration 133 history segment 8 point configuration 134 history segment 9 point configuration 135 history segment 10 point configuration 136 roc clock 137 internet configuration parameters 138 139 smart i/o module information 142 history segment 11 point configuration 143 history segment 12 point configuration 144 transactional history configuration point type 145 transactional history point configuration point type 196 208 210 216 218 219 230 234