AB Micro850 (Gen1)

review the following information for setting up and configuring the ab micro850 (gen1) driver manufacturing connect edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series micro800 when configuring tags for this driver, you must enter the case sensitive register name exactly as it is defined in the plc see the free tags section below to learn more to set up and configure this device in manufacturing connect 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 manufacturing connect 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 note down the following information and refer to it when needed device allen bradley communication i/f ethernet refer to the following figure launch rslinx classic, and connect the device to a pc using usb cable the device is added to the browser right click the device and then click module configuration from port configuration , set up the device ethernet parameters create an ab ethp 1 driver select an adapter on the same subnet as the device if you cannot find it in the local subnet, select remote subnet launch ccs, connected component workbench click the discover icon to browse the device double click the device step 2 set up the plc device in manufacturing connect edge devicehub configure the following parameters when you connect a device docid\ rfvijdxz7dbad8mwbisma with this driver update default values to the specific set up of your device parameter value type allen bradley driver ab micro850 (gen1) network address the device address you defined in step 1 port 44818 slot number 0 step 3 configure the list of registers when you add tags docid\ ioanzd2awqnkuppgee3eh to the connected device, refer to the following tag parameters and available value types refer to the following additional resources device and tag metadata use case docid\ f b720nivllber44rfyhn tag formula variables docid\ pwd 7p kzjxkt pyawaow 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 byte word dword lword 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)