AB FlexLogix (Gen1.3)

review the following information for setting up and configuring the ab flexlogix (gen1 3) driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series flexlogix when configuring tags for this driver, you must enter the case sensitive register name exactly as defined in the plc see the free tags section below to learn more 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, follow the steps below to configure your device record the following information and refer to it as needed device ab flexlogix l24er qb1b communication i/f ethernet and usb refer to the following figure connect the device to a pc using a serial port launch rslinx classic and click configure drivers select rs232 df1 device driver and click add new set up the comm and click auto configure make sure the device can be detected successfully the new device appears right click the 02 1788 enbt/a module > module configuration set up ethernet parameters in port configuration page create another ethernet driver select and add the ethernetip driver select the adapter with the same subnet as the device the rockwell device appears including the target launch rslogix5000 v16 create a project with the correct device model and version and then navigate to communication > who active select the target 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 allen bradley driver ab flexlogix (gen1 3) network address the device address you defined in step 1 port 44818 step 3 configure the list of registers when you docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following tag parameters and available value types refer to the following additional resources docid\ mu 6j6zhi0cvchdad0w8n docid\ io7xgyrdvv vmpnfxoaci free tags this driver doesn't have a list of available register names in the devicehub add tag form to add tags, you must enter the case sensitive register name exactly as it is defined in the plc a connected status for the device won't display until a tag with a correct register name is created available value types bool sint int dint real lint tag parameters name enter the case sensitive register name exactly as it is defined in the plc value type select a data type from the drop down list 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 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)