AB Micro800 Ethernet

review the following information for setting up and configuring the ab micro800 ethernet driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series allen bradley micro800 replaces gen 1 driver(s) ab micro850 (gen1 3) docid 7vhatas8rlihwfbjsqwvt learn more about gen1 and gen2 driver differences docid\ haixs2l oqxfj1yvywnc1 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 connected components workbench application select file > open , then select your plc project select device > configure the device configuration tab opens go to controller > ethernet , and copy 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\ pal6abpzbrimdu9lvgj30 with this driver update default values to the specific setup of your device parameter value type allen bradley driver ab micro800 ethernet network address the device address you defined in step 1 port 44818 global variables csv optional if you want to browse for udt instances, upload the global variables csv file exported from connected components workbench to /ftp data/devicehub/ and paste the file name here step 3 configure the list of registers browse for tags to add to this freetag device see browse and add tags from a device docid 8oruw1cmtao49bwbbhwrn to learn more alternatively, when you add a tag docid\ tuy hh0gi8djvot70wroh , 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 project organizer > \[your controller] > global variables in connected components workbench the following data types are supported bool byte sint int uint dint udint real lint ulint lreal string addressing tips 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 connected components workbench 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 only global variables are supported by the driver the driver cannot access local (program) variables only user defined tag structures are supported by the driver predefined structures, such as counters or timers are not supported 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 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)