AB Logix Ethernet

review the following information to set up and configure the ab logix ethernet driver overview the driver implements two modes symbolic and logical it also supports backplane routing symbolic mode in symbolic mode, the driver uses the symbolic tag names in its requests to the plc, so performance will be reduced if you add tags with long names or need to traverse complex structs compared to logical mode, it performs better when dealing with changes to the plc program logical mode in logical mode, the driver uses numeric handles instead of symbolic names usually, this allows for reading more tags per request than in symbolic mode, especially if symbolic names are long however, the driver must be restarted every time the plc program changes it performs better overall than symbolic mode as long as the plc program does not change routing this driver also supports routing to route through a connected device, configure the ip address of the device, then 1 to port to backplane and then enter the appropriate routing and slot number of the device litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series flexlogix compactlogix controllogix when configuring tags for this driver, you must enter the register name precisely 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, use plc software on your computer to configure the device for ethernet access 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 parameter value type allen bradley driver ab logix ethernet network address the device address you defined in step 1 network port 44818 access mode select symbolic or logical route 1,0 (route describes the path the message takes to get to the destination) step 3 configure the list of registers when you add a tag docid\ tuy hh0gi8djvot70wroh to the connected device, refer to the following tag parameters and available value types you can also browse and add tags from a device docid 8oruw1cmtao49bwbbhwrn for this device refer to the following additional resources organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n tag formula variables 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 register name exactly as it is defined in the plc available value types bool byte sint int dint real dword lint lreal string 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)