Step-by-Step

G3 Valve Manifold Setup on EtherNet/IP with Allen-Bradley PLC

Field-tested commissioning sequence: EDS file, Studio 5000 config, I/O mapping, DLR topology, fault codes. 45–90 minutes from unboxing to running.

What the G3 Is

The Numatics/Aventics G3 is an electronic valve-and-I/O platform with an integrated graphic display. A single node supports up to 128 valve solenoids and up to 1,200 I/O points, communicates over EtherNet/IP with Device Level Ring (DLR) support, and runs a built-in web server for configuration and diagnostics.

That last feature — the onboard web server — is the reason a G3 can be commissioned faster than almost any competing manifold, because it tells you the exact assembly instances and sizes the PLC needs before you ever go online. Use it.

Before You Start

Assemble the following. Missing any one of these is the usual reason a "quick" commissioning turns into an afternoon:

  • Studio 5000 Logix Designer (any recent version) with the built-in EtherNet/IP driver, or RSLinx Classic
  • Aventics G3 EDS file — v1.04 or v1.08 — downloaded from asco.com or emerson.com
  • A laptop with a static IP on the same subnet as the G3
  • A Cat5e or Cat6 Ethernet cable
  • A 24 VDC power supply connected to the node (node power and valve/output power are separate rails — you will need both)
Pro TipDownload the EDS file and confirm its revision BEFORE you drive to site. If the G3 firmware is revision 2 and you register the wrong EDS, the module definition will not offer the correct assembly instances and you will chase phantom errors. Match the EDS revision to the node firmware shown on the display.
Phase 1 — Set the G3 IP Address (Onboard Display)
  1. Power on the G3 manifold. The graphic display lights up and shows the current protocol and IP address. Confirm you see an EtherNet/IP indication, not another protocol.
  2. Set the addressing mode to Static. Using the arrow buttons, navigate to Network Settings > DHCP/BootP > Disable. This forces static addressing so the node does not lose its address on a power cycle.
  3. Enter the static IP address. Navigate to IP Address and enter your value — for example 192.168.1.10. Use the display buttons to scroll each octet in turn.
  4. Set the subnet mask and gateway. Enter the subnet mask (for example 255.255.255.0) and a gateway only if the node must route off-subnet.
  5. Save and restart the node. Confirm the IP address you entered is displayed after the restart. If it reverts, DHCP was not actually disabled — repeat step 2.
Phase 2 — Install the EDS File in Studio 5000
  1. Open the EDS Hardware Installation Tool. In Studio 5000, go to Tools > EDS Hardware Installation Tool.
  2. Register the EDS file. Select "Register an EDS file(s)" then "Register a single file." Browse to the Aventics G3 EDS file (G3 EtherNet/IP v1.08 or v1.04). Click Next through the screens, then Finish.
  3. Verify registration. In the module catalog, search "Numatics G3" or "Aventics G3" and confirm the device now appears.
Phase 3 — Add the G3 to the I/O Tree
  1. Create a new module. In the Controller Organizer, right-click your Ethernet module and select "New Module."
  2. Select the module type. Search "Numatics G3 EtherNet/IP." If the EDS is not yet registered you can fall back to a Generic Ethernet Module, but the registered EDS is preferred. Select and click Create.
  3. Name and address the module. Enter a Name (for example G3_Manifold_1), the IP address you set on the display, and a Description.
  4. Set the module definition revision. Click "Change" next to Module Definition and select Revision 2 for the G3 240–325 EtherNet/IP DLR module.
  5. Set the assembly instances and sizes. Input Assembly Instance: 106. Output Assembly Instance: 150 (or 100 depending on G3 version). Data Type: SINT or DINT.
Sizing rule: Count the solenoid coils on the manifold, divide by 8, and round up to get the number of bytes. A 24-coil manifold needs 24 ÷ 8 = 3 bytes of output. Verify this against the G3 web server (Phase 6) — it publishes the exact size the node expects.
  1. Set the connection parameters. On the Connection tab, set RPI (Requested Packet Interval) to 20 ms. Set Connection Type to Unicast.
  2. Save. Click OK and confirm the G3 module now appears in the I/O tree.
Phase 4 — I/O Mapping and Tag Creation
  1. Go online and find the module tags. In Controller Tags, locate [ModuleName]:I for input data and [ModuleName]:O for output data.
  2. Understand the bit mapping. Each solenoid coil is one output bit. Bit 0 = Solenoid 1A (first coil on the first valve), Bit 1 = Solenoid 1B (second coil if it is a double solenoid), and so on across the manifold.
  3. Configure diagnostic status. Set the Status Assembly (Status Only) in the module definition to map the G3 diagnostic bytes into a status tag. This surfaces coil-fault, short-circuit, and power-fault data directly in the PLC.
  4. Write and run a test rung. Energize output bit 0 and verify Solenoid 1A fires. The G3 display shows active solenoids graphically — confirm at the node and at the PLC simultaneously.
Pro TipMap the diagnostic status tag on day one, even if the machine spec did not ask for it. When a coil opens six months later, the fault bit tells the operator exactly which solenoid failed — instead of an electrician ringing out 24 coils at 2 a.m.
Phase 5 — DLR (Device Level Ring) Topology

DLR wires the network as a ring so a single cable break does not drop the node. Worth the extra cable run on any line where downtime is expensive.

  1. Wire the ring. Connect the primary port of the G3 into the EtherNet/IP ring and the secondary port to the next device on the ring. Continue until the ring closes back on the supervisor.
  2. Enable DLR in Studio 5000. Check the DLR checkbox under module properties. The ring supervisor is typically the PLC itself.
  3. Verify ring status. The G3 display shows RING OK or RING FAULT. In Studio 5000 the module status turns green when the ring is healthy. Test it by pulling one cable — a healthy ring keeps the node communicating.

Common Fault Codes

IndicationMeaningFirst Action
ERR 01Node not on networkCheck IP address, subnet, and cable
ERR 02I/O size mismatchRecheck assembly-instance sizes against the G3 web page
ERR 03Duplicate IP address on networkFind and change the conflicting device
LED red solidNo power to valve solenoid outputsCheck the 24 VDC supply to the output side (separate from node power)
LED flashing redCommunication timeoutIncrease RPI or check the cable / connector
Active in PLC, valve idlePLC shows solenoid on but the valve does not moveCheck valve power supply separately from node power
Pro TipERR 02 (I/O size mismatch) is the single most common commissioning stall. It almost always means the byte count in the module definition does not match what the node actually has. Open the web server, read the published input/output sizes, and set the module definition to match exactly.

The Built-In Web Server

Type the G3 IP address into a browser on the same subnet. The onboard web server shows real-time I/O status, individual solenoid states, network error counters, firmware version, and — critically — the RSLogix configuration table with the exact assembly-instance numbers and sizes. Use this page to verify your Studio 5000 settings before you go online. Reading the node's own configuration table turns most guesswork into a two-minute confirmation.

Air-Oil Systems stocks G3 nodes & valve manifolds

Same-week delivery across PA, NJ, DE, MD & VA. Commissioning support available by phone.

Request a Quote 📞 (215) 721-9595