Oemax Serial (Gen1)

review the following information for setting up and configuring the oemax serial (gen1) driver litmus edge compatible series compatibility parameter compatible items driver type serial validated devices/series rs automation oemax series 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 record the serial communication parameters for the device otherwise, follow the steps below to configure your device note down the following information and refer to it when needed device rs automation oemax nx7 communication i/f rs232 refer to the following figure launch the wingpc software and find the network parameters if needed, refer to the following wiring and switch settings 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 rs automation driver oemax serial (gen1) communication port local serial connection file path baud rate 9600 data bits 8 parity even, odd, none stop bits 1 station id 255 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 description r bit ddddd 0 25515 l bit ddddd 0 2047 m bit dddddd 0 199915 k bit ddddd 0 25515 keep contact f bit ddddd 0 99115 special contact tc bit ddd 0 255 timer/counter w word dddd 0 7999 special auxiliary relay sv word ddd 0 255 timer/counter set value pv word ddd 0 255 timer/counter preset value sr word ddd 0 255 special register wr word ddd 0 255 wl word ddd 0 255 wm word dddd 0 1999 wk word ddd 0 255 wf word ddd 0 991 timer memory 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 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)