Sick Flexi Serial (Gen1.3)

review the following information for setting up and configuring the sick flexi serial (gen1 3) driver litmus edge compatible series compatibility parameter compatible items driver type serial validated devices/series sick flexi fx3 cpu1 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 record the following information and refer to it when needed device sick flexi fx3 cpu1 communication i/f rs232 refer to the following figure launch the flexi soft designer v2 01 0 software and click com settings edit the connection profile check com auto detection test the connection click connect step 2 set up the plc device in litmus edge devicehub configure the following parameters when you docid\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device parameter value type sick flexi driver sick flexi serial (gen1 3) data bits 8 baud rate 115200 parity even, odd, none stop bits 1 station 1 communication port local serial connection file path step 3 configure the list of registers when you docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following register table and tag parameters see the following additional resources if necessary docid\ mu 6j6zhi0cvchdad0w8n docid\ io7xgyrdvv vmpnfxoaci register table name value type address format min address max address description i bit ddo 0 127 input q bit ddo 0 127 output logic result bit ddo 0 197 logic result rs232 to flexi soft bit bit do 0 37 flexi soft to rs 232 bit bit ddo 0 997 module status bit array bit bit ddo 0 597 operating data block bit word do 0 97 configuration crcs bit bit ddo 0 197 cpu module type key bit bit ddo 0 177 extension modules type bit bit dddo 0 3377 extension modules type word ddd 0 336 cpu module type key word dd 0 16 configuration crcs word dd 0 18 operating data block word d 0 8 module status bit array word dd 0 58 flexi soft to rs 232 word dd 0 98 rs 232 to flexi soft word o 0 2 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)