Omron-Hostlink (Gen1.3)

review the following information for setting up and configuring the omron hostlink (gen1 3) driver litmus edge compatible series compatibility parameter compatible items driver type serial validated devices/series c series cj1 cj2 cs 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 as needed device omron cj2m cpu15 communication i/f rs232 refer to the following figure connect pc to the device with serial cable launch cx programmer v9 52 software double click new plc in the navigation panel, and then select the model type and network type for the device communication click plc > work online 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 step 3 configure the list of registers when you add a tag docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following register table and tag parameters 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 parameter value type omron driver omron hostlink (gen1 3) communication port local serial connection file path data bits 7 baud rate 9600 parity even, odd, none stop bits 2 station id 0 name value types address format min address max address description cio bit bit ddddddd 0 3276715 channel i/o bit cio word, string ddddd 0 32767 channel i/o w word, string ddddd 0 32767 work area a word, string ddddd 0 32767 auxiliary relay h word, string ddddd 0 32767 holding area c word, string ddddd 0 32767 counter t word, string ddddd 0 32767 timer d word, string ddddd 0 32767 data memory em0 word, string ddddd 0 32767 extended memory em1 word, string ddddd 0 32767 extended memory em2 word, string ddddd 0 32767 extended memory em3 word, string ddddd 0 32767 extended 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 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)