AB CompactLogix Ethernet FreeTag

review the following information for setting up and configuring the ab compactlogix ethernet freetag driver note we recommend this driver for compactlogix and controllogix plcs, as it provides the best stability over other compatible drivers if you prefer speed over stability, you can use the ab compactlogix ethernet advanced docid 7mirggubyntgdefqvsug6 litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series compactlogix controllogix replaces gen 1 driver(s) ab compactlogix (gen1) docid\ fwms60rd9svb0is50zybo ab controllogix (gen1) docid\ gpbnqomss7gopifbygvlb learn more about gen1 and gen2 driver differences docid 27hyoelb0soehmysjqod5 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 start the studio 5000 logix designer application select file > open , then select your plc project in controller organizer , right click the device and select properties from the popup menu the module properties dialog box appears select the port configuration tab copy aside the ip address from the ip address field 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 allen bradley driver ab compactlogix ethernet freetag network address the device address you defined in step 1 port 44818 slot 0 step 3 configure the list of registers browse for tags to add to this freetag device see browse tags docid\ ml 1dnqkd6d zhzbe7qmw to learn more alternatively, when you add tags docid\ xgwokqbtpevii7or82ll0 , type the tag name in the name field exactly as it is defined in the device (case sensitive) you can find a list of tags by navigating to controller organizer > controller > controller tags in studio 5000 logix designer the following data types are supported bool byte sint int dint real dword lint lreal string addressing tips to access the bits of a dint tag, use the data type bool and append the bit address ( 0 to 31 ) to the name of the dint tag to access the elements of a two or three dimensional array, use multiple square brackets instead of commas to separate the indices for example, if the array in rslogix 5000 has the name myarray with the data type dint\[2,2,2] , you can access the 0th index by entering myarray\[0]\[0]\[0] in litmus edge refer to the following tag parameters in litmus edge 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 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)