Knowledge Base /
Industry Applications
DeltaV Virtual IO Module Integration with Allen-Bradley 1734-AENT
By Geoff Nash on 03.22.12
Product: IOD-4104 - Ethernet/IP Scanner Driver (Generic Devices)

This application note details the integration of the Allen-Bradley 1734-AENT Point IO Adapter with the DeltaV Virtual IO Module using the Generic Ethernet/IP firmware.

Throughout the procedure, there are several references to the manuals of the respective devices used in this application. Links to the manuals have been provided below:

Allen-Bradley 1734-AENT Point IO Adapter - PDF

DeltaV Virtual IO Module IOD-4104 (Generic Ethernet/IP) - Web Help


Initial 1734-AENT Network Setup

1.       Connect the POINT IO to the 1734-AENT.

2.       Set the IP Address of the AENT via the Network Address Dial.  (See user manual, page 19).

3.       Supply power to the AENT.

4.       Secure an Ethernet connection between a computer and the AENT via a hub or crossover cable.  Set the IP address of the computer to a static address under the same subnet as the AENT.

5.       Open an Internet Browser and connect to the device by the IP Address in the Address Bar.

a.      Default Username:  admin

b.      Default Password:  password

6.       Under the Configuration Tree, select Configuration > Network.

7.       Select Static for Ethernet Interface Configuration.

8.       Change the IP Address and Subnet Mask to allow communication on the intended network.

9.       Select Autonegotiate Speed and Duplex for Autonegotiate Status.

10.     Select Apply Changes.

11.     Under the Configuration Tree, select Configuration > Identify.

12.     Select the correct Chassis Size.

a.      Chassis Size = 1 + (number of POINT IO Slots physically connected).

b.      The AENT is included within the Chassis Size, hence the + 1 (See user manual, page 1).

c.      Selecting the correct Chassis Size is absolutely necessary for IO communications.  According to the manual, “When the adapter’s non-volatile chassis size does not match the actual number of modules present on its backplane, the adapter does not make any I/O connections and an error occurs…” (page 2).

13.     Select Apply Changes.

14.     Use the Network Address Dial on the AENT to set the address to 0 or a number greater than 254 but not 999.

a.      This will indicate that the AENT will use the static IP Address that was provided in the configuration. 

b.      When 999 is selected, DHCP will be enabled.  (See user manual, page 20).

15.     Power cycle the 1734-AENT to update the IP address and configured Chassis Size.

16.     When the 1734-AENT is connected properly, the LED status at this point in time (i.e., no connections yet) should be:

a.      Module Status:  Solid Green

b.      Network Activity:  Flashing Green

c.      Network Status:  Flashing Green

d.      Point Bus Status:  Solid Green

         i.      If Point Bus Status is anything other than Solid Green, you will not be able to establish IO communications.

                                                        ii.      For more information on the LED Statuses, please see the user manual, pages 63-65.


1734-AENT Connection Definition Setup

1.       Create a new Connection Definition for a POINT IO Slot type.  The same connection definition can be reused.  Right-click Ethernet IP Connection Library and select “Add Connection Definition”.

2.       Configure the Connection Definition using the following screenshot as a guide.

a.       Currently, VIMNet Explorer only supports 1734-AENT POINT IO. Select this for the device.

b.       Select the Device and Item, this corresponds to the POINT IO at the slot.  When the Item is selected the EtipBuffer section will be updated with the appropriate Input, Output, and Configuration Buffer.

c.       Make sure that Slot Addressing and Default are checked.  When Default is checked, the slot address will be configured when adding the conneciton definition to the device.  Remember, the 1734-AENT itself is considered to be Slot 0.  If you're adding the first slot, the address will be 1.

f.        The 1734-AENT uses the following data structure:  4 byte header + 6 bytes of data.  When you add Input Buffer Definition, you can create a dataset with a length of 10 bytes (or 5 16-bit registers), but because of the buffer, data will only be contained in Registers 3-5.  Registers 1-2 will only contain 0.  You can take this into account by first creating a header buffer of 4 Unmapped Bytes and creating a dataset of 6 bytes (or 3 16-bit registers) with 0 Offset.  This method removes the unnecessary empty registers.

3.       Click the Msg Parameters button and use the following screenshot as a guide for configuration.

a.         All of the settings shown above should be generated automatically when selecting the AENT Device and Item in the Ethernet Buffer Mapping screen.

4.       Click OK to exit the Message Parameters and click OK to exit the Connection Definition Properties.

5.       Make sure that the Controller, VIM, and Serial Devices have been added and are configured correctly.

6.       Right-click the Serial Device that represents the 1734-AENT and select “Add Connection”.

7.       Select the Ethernet Library Definition and make sure that the Slot ID corresponds to the Slot Number that the POINT IO occupies in the chassis.

8.       Click OK to finish adding the Connection Definition.

9.       Add more Connections as necessary.

10.     Commission the VIM and Upload the Configuration.


1734-AENT DeltaV Setup

1.       After commissioning the controller, Auto-Sense the IO to automatically pull in the VIM cards into the DeltaV configuration.

2.       Add the serial device that represents the 1734-AENT.

3.       When the Connection Definitions are added to the Serial Device in VIMNet Explorer, the corresponding dataset parameters for DeltaV are automatically generated.  In VIMNet Explorer, expand down to the dataset and select it.  The right-hand window will display what needs to be configured in DeltaV for the DeltaV Dataset.

4.       Add more DeltaV datasets as necessary.  (Note that as Diagnostics goes, it is easier to configure one connection at a time rather than to try to configure everything at once).

5.       Download the controller, not just a single card, at least once.

6.       At this point, IO Communication should be established.


1734-AENT Communication Diagnostics


1.       Check DeltaV Diagnostics at the Dataset Level for communication status errors.

2.       In DeltaV Diagnostics, right-click the dataset and select “View Dataset Registers”.  Compare the register values to the data expected.  The registers should indicate if there is a configuration error.

3.       Port Statistics are not meaningful for the Generic Ethernet IP firmware so this will not be useful.


1734-AENT Web Config

1.       Check Status under Home.

2.       Check the LED Status and CIP Connection Statistics under Diagnostics Overview.

3.       Check Media Counters for physical network issues under Ethernet Statistics.

4.       Check the number of connections match under I/O Connections.

5.       Check the Physical Chassis Size matches the Chassis Size under Identify.

6.       Check the IP Address under Network.

7.       Use Browse Chassis to view Channel Data and Module information for each slot.