---
title: AB FlexLogix (Gen1.3)
slug: bhdo-v1/ab-flexlogix-gen13
createdAt: 2022-05-26T20:56:06.000Z
---

Review the following information for setting up and configuring the AB FlexLogix (Gen1.3) driver.&#x20;

# Belden Horizon Data Operations Compatible Series

| Compatibility parameter      | Compatible items                                                                                                                                                                             |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Driver type**              | Ethernet                                                                                                                                                                                     |
| **Validated devices/series** | FlexLogix<br />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 Belden Horizon Data Operations, you will need to do the following:

- Step 1: Set up and Configure the PLC Device
- Step 2: Set up the PLC Device in Belden Horizon Data Operations 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.&#x20;

**To configure your device**

1. Note down the following information and refer to it as needed.&#x20;
2. **Device**: AB FlexLogix L24ER-QB1B
3. **Communication I/F**: Ethernet and USB. Refer to the following figure.

   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/GbbzCKrgmVLWpRH5UjYkv_ab-flexlogix.png" size="80" width="613" height="341" caption="AB FlexLogix reference" position="center" darkWidth="613" darkHeight="341" showCaption="true"}
4. Connect the device to a PC using a serial port.

   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/mJdLZWqx7p9MbnipjxQWQ_ab-flexlogix-serial.png" size="80" width="407" height="197" caption="Serial port" position="center" showCaption="true"}
5. Launch RSLinx classic and click **Configure Drivers**.
6. Select **RS232 DF1 Device driver**, and click **Add New**.
7. Set up the *Comm&#x20;*&#x61;nd click **Auto-Configure**. Make sure the device can be detected successfully. The new device appears.&#x20;
8. Right-click the **02 1788-ENBT/A module > Module Configuration**.
9. Set up Ethernet parameters in *Port Configuration* page.
10. Create another Ethernet driver, select **EthernetIP** Driver, and add it.
11. Select the adapter with the same subnet as the device. The Rockwell device appears including the target.&#x20;
12. Launch RSLogix5000 v16, create a project with the correct device model and version, and then click **Communication > Who Active**.
13. Select the target.&#x20;

# Step 2: Set up the PLC Device in Belden Horizon Data Operations DeviceHub

Configure the following parameters when you [Connect a Device](docId\:T-cWPe0_Jsfw5-aoj8WPP) with this driver. Update default values to the specific setup of your device.&#x20;

Because this device belongs to a free tag PLC, the case-sensitive register name must be entered exactly as it is defined in the PLC. The device does not display a **Connected&#xA0;**&#x73;tatus until a tag with a correct register name is created.

| 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 [Add Tags](docId\:Wpe2HMXelARLBnhWbuChY) to the connected device, refer to the following tag parameters and available value types.

Refer to the following additional resources:

- [Organize Device and Tag by Using Metadata](docId\:kR5ZcBhkXWK89Qti0v1t8)
- [Tag Formula Variables](docId:9m6xLAQ9IoPW5alpru96S)

## 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.&#x20;
- **Value Type**: Select a data type from the drop-down list.&#x20;
- **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. &#x20;
- **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
  - log
  - exp
- **Only Publish on Change of Value**: Select the checkbox to customize NATS messages to be published only when the *value&#x20;*&#x70;arameter 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.&#x20;

