Fuji NB Serial (Gen1)

review the following information for setting up and configuring the fuji nb serial (gen1) driver litmus edge compatible series compatibility parameter compatible items driver type serial validated devices/series fuji nb 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 as needed device fuji nbou14 communication i/f rs485 2w refer to the following figure launch flex pc programmer v2 1 0 35 software click options > communication set up com port and communication parameters click the online icon 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 fuji devices driver fuji nb serial (gen1) communication port local serial connection file path data bits 8 baud rate 19200 parity even, odd, none stop bits 1 step 3 configure the list of registers when you docid 8se7z3pmrfwl1nmzcwalx to the connected device, refer to the following register table and tag parameters refer to the following additional resources docid 583p fbuozem6whgrdgkq docid\ ifbwcou90qtfodk hrysr register table name value type address format min address max address description x bit ddd 1 816 input status (read only) y bit ddd 1 816 output status c bit ddddd 1 2000 control bit t bit ddddd 1 500 timer status ct bit dddd 1 250 counter status sc bit ddd 1 1000 system control bit ds word dddd 1 4500 data registers dd word dddd 1 1000 data registers (double word) dh word ddd 1 500 data registers df word ddd 1 500 data registers (double word) xd word d 0 8 input status registers yd word d 0 8 output status registers td word ddd 1 500 timer current values ctd word ddd 1 250 counter current values sd word dddd 1 1000 system data registers txt word dddd 1 1000 text data registers 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)