One job, start to finish: wire a single-phase PowerFlex 525 to a Compact GuardLogix 5370, bring it up over EtherNet/IP, and package it as an object built to scale to a second and third drive.
About this course
Most training teaches a platform. This is the other kind of course: one real job, done properly, front to back, on the equipment actually in the lab — a single-phase PowerFlex 525 and the 1769-L33ERMS Compact GuardLogix 5370 already used throughout the GuardLogix program, at the real addresses this lab runs on.
You mount and wire the drive, commission it from the keypad alone, then put it on EtherNet/IP against a network plan that reserves addresses for a second and third drive before either exists. You learn to upload and download parameters without overwriting a commissioned drive, then write control and feedback logic against the real module tags.
The last two modules are the point of the course: that logic becomes an Add-On Instruction, and then a User-Defined Data Type built for the data, the two combined as one reusable object — with an exact, concrete answer for what changes, and what does not, the day a second physical drive actually arrives.
This draws directly on IATCG04 (PowerFlex 525 drives) and IATCG02 (UDTs and Add-On Instructions) and says so by name. Neither is required first — this course re-introduces what it needs as it needs it — but together they are where the two ideas meet on one piece of real equipment.
What you work through
The lab today (controller at 192.168.2.130, drive at 192.168.2.131), why the control logic is built as a reusable object from the start, and what this course covers against what it deliberately defers.
A single-phase PowerFlex 525: why single-phase in still means three-phase out, power and ground wiring, and identifying the Safe Torque Off terminals.
Two-wire against three-wire control, the essential parameters in order, and a motor turning from the keypad alone before the network is involved.
This lab’s real addressing plan, setting the drive’s IP, an Add-On Profile in Studio 5000 v30, the module-defined tags that appear, and going online.
Which direction is which, when to use each, the tools that can do it, and the discipline that stops a saved file overwriting a commissioned drive.
Command and status words against the real PF525_1 tags, a scaled and clamped speed reference, fault handling, and aliasing before anything else builds on it.
What an AOI is, why one drive plus a named plan for a second already justifies building one, choosing parameters, and wrapping module 6’s proven ladder into Drive_Ctrl.
Designing Drive_Data, upgrading the AOI to one InOut parameter, the copy block that joins a fixed address to a generic object, and exactly what changes when drive two arrives.
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 PowerFlex 525 in this course is real: one single-phase, 200-240 V class drive, wired and commissioned in the lab exactly as the modules describe, on the network plan module 4 sets out. The second and third addresses that plan reserves are not yet drives — nothing is plugged in at either one today.
This course deliberately stops before an HMI screen, a conveyor that starts when the drive reaches speed, or a multi-conveyor example. Those are a later project, once more drives are actually on the bench — said here rather than left for a student to discover module 8 already promised it.