Expand a Compact GuardLogix 5370 with a 1734 Point I/O node: mount the bus, configure the 1734-AENTR adapter, add digital and analog points, and verify every one from your program.
About this course
A second real job on the same controller as IATPJ01, and just as concrete: one 1734 Point I/O node, one 1734-AENTR EtherNet/IP adapter, taken from the box to verified field I/O on the 1769-L33ERMS already in the lab.
You mount the Point Bus and learn why its power budget is a separate question from the field-side 24 V supply, then configure the AENTR — which, unlike the PowerFlex 525 in IATPJ01, ships listening for an address rather than waiting for one — and set it to a planned, static address on its own reserved block.
Adding it to the I/O tree uses module discovery rather than typing the bus in from memory, and the course covers both halves of Point I/O: digital points (sinking against sourcing again, on a different terminal block) and analog points (4-20 mA wiring, range and filter, scaling in both directions).
The last two modules are what make this a complete project rather than a wiring exercise: the AENTR’s own built-in diagnostic web page, and a verification pass that proves every point against real field devices and states exactly what a second Point I/O node would cost.
What you work through
What 1734 Point I/O and the AENTR adapter are, the network plan for this node (192.168.2.140), and what this course covers against what it defers.
DIN rail assembly, the Point Bus that carries logic power between modules, module keying, and the separate field-side 24 V power distribution.
Factory BOOTP against a static address, the node address switches, disabling BOOTP for good, and labelling the adapter the way the drive was labelled.
The AENTR’s Add-On Profile, discovering the modules already on the bus, RPI and connection type, and going online.
Wiring 1734 digital modules, sinking against sourcing again on a different platform, and the tags that appear per point.
Wiring a 4-20 mA analog input module, range and filter configuration, scaling to engineering units, and an analog output driven from logic.
The AENTR’s built-in diagnostic web server: network settings, per-module status, live I/O data, and when to reach for it instead of Studio 5000.
Proving every point against real field devices, a wiring-to-tag checklist, and exactly what adding a second Point I/O node costs against this one.
Lab times are approximate: they are a guide to how long the hands-on part usually takes, not a limit. You can ask for more lab time whenever you need it.
The 1734 Point I/O node in this course is real: one 1734-AENTR adapter with digital and analog modules, mounted and configured in the lab exactly as the modules describe, at 192.168.2.140 on the addressing plan module 1 sets out.
This is an I/O project, not a control-logic one — it stops at proving every point is wired and reading correctly, the same boundary IATPJ01 draws around its own scope.