How-to
Control a PowerFlex 525 drive from two PLC controllers
Short answer
Yes — add the PowerFlex 525 to the Logix controller's Ethernet tree and its command tags appear, but a cyclic drive connection has exactly one owner. Give the Logix controller that ownership, read the MicroLogix machine's request into it, and let one rung select the command the drive follows. Never let two controllers write the speed reference.
On this page
Yes — you can add the drive to the Logix controller's Ethernet tree and get controller tags for it, and you can override the MicroLogix 1400, but not by out-writing it. A PowerFlex 525 cyclic command connection over EtherNet/IP has exactly one owning controller, so the working design is to make one controller the owner, bring the other machine's request into it, and let its logic choose the single command the drive sees. Two controllers writing the same speed reference is last-writer-wins: your new speed appears for one update, then the old controller writes its value back over it.
One connection, one owner #
The drive's embedded EtherNet/IP adapter, documented in 520com-um001, serves its cyclic I/O connection — the one that carries start, stop, direction and speed on every update — to a single owning controller. Reading status and writing individual parameters travel on separate messaging connections, so a second controller can watch the drive or set a parameter, but that is not a second live command channel. Override therefore happens in logic, not on the wire.
The MicroLogix 1400 has no Ethernet module tree and no drive profile. If it commands the drive today, it does so with message instructions, or the drive starts from hardwired terminals and follows an analog or keypad reference. That pushes the design the same direction: one Logix controller owns the connection and arbitrates both machines.
Find who commands the drive today #
Before touching the network:
- Read the drive's start source and speed reference settings and record whether each is network, terminals, or keypad/pot.
- Trace the MicroLogix program for the rungs that write run, direction and speed — message instructions to the drive's address, and any hardwired outputs to its terminals.
- Watch the drive's commanded frequency readout against the MicroLogix request during an authorized speed change; if they track, Ethernet is the active path.
- Check for a local/remote selector or machine-mode logic that swaps command sources.
If the drive starts from terminals and follows a pot today, no module entry changes that. The source parameters decide which input wins, and they must be switched to the network source deliberately.
Give the Logix controller ownership #
- Confirm which controller you are targeting — the proposal names both a ControlLogix and a CompactLogix; the steps are identical, but the project, slot and IP must match the real hardware.
- Give the drive a static IP on the controller's subnet. From the drive's main display, press Enter and scroll up to the parameter group shown as the letter C, where the network settings live.
- Back up both controller programs and the drive configuration, and do the cutover with the conveyor stopped.
- Add the drive to the controller project's Ethernet module tree; with the PowerFlex 525 profile installed this creates the command and status tags, and the quick start iasimp-qs036 walks through it. In the same stop, set the drive's start source and speed reference to the network source.
- Configure a message instruction in the Logix controller to read the MicroLogix machine's request and write back a handshake. The MicroLogix 1400 does not produce tags a Logix controller can consume, so messaging is the path; produced/consumed tags (1756-pm011) link only Logix controllers.
- Write the arbitration logic below before enabling the connection.
- Disable the MicroLogix rungs that wrote the drive command, keeping the backup. One writer remains: the owner.
Keep the MicroLogix 1400 as owner instead #
If the standalone machine must keep running when the new machine's controller is offline or rebooting, invert the design. Leave the existing command path in place and have the Logix controller write its speed request into the MicroLogix data table by message; the MicroLogix program then selects local against remote with a mode bit. You accept editing the older program instead of the new one, and the conveyor keeps its familiar behavior whenever the link is down.
Arbitrate one command and prove it is fresh #
- A local/remote selection bit that also defines whether remote changes speed only or run and stop too; protective stops and permissives stay in the path in both modes.
- A scaling block that converts the requester's units into the drive's frequency command (worked example below).
- A freshness check: the requester increments a counter with every new value, and the owner times it. Set the watchdog at three update periods — at a 250 ms poll that is 750 ms — then drop to local or stop per the machine's requirement. Match the drive adapter's own communication-loss action to that same choice so the drive and the logic never disagree.
Worked example: 40 ft/min becomes 8.73 Hz #
Illustrative numbers — replace them with your nameplate and mechanical data, keeping the units in every step.
- Belt speed request S = 40.0 ft/min
- Drive pulley diameter D = 12.0 in, so circumference = 3.1416 × 12.0 = 37.70 in = 3.142 ft per revolution
- Pulley speed = 40.0 ft/min ÷ 3.142 ft/rev = 12.73 rev/min
- Gearbox ratio 20.0:1, so motor speed = 12.73 × 20.0 = 254.6 rpm
- Motor nameplate 1750 rpm at 60.0 Hz, so frequency command = 254.6 × 60.0 ÷ 1750 = 8.73 Hz
Check the loop back the other way: 8.73 Hz × 1750 ÷ 60.0 = 254.6 rpm; ÷ 20.0 = 12.73 pulley rpm; × 3.142 ft = 40.0 ft/min. Commissioning test: command 8.73 Hz, confirm the drive's output frequency reads 8.7 Hz and a tachometer on the belt reads 40 ft/min. The requester's display and the drive must both come from this same conversion, or the units do not match.
Commissioning test and the decision #
Do the first start with the belt guarded and cleared, and every protective stop stays effective in both modes. Then verify three things:
- Force the remote branch: the drive follows the owner's selection and nothing flips it back an update later.
- Stop the requester: the watchdog expires after three missed updates and the owner takes the configured local or stop action.
- Pull the drive's Ethernet cable: the adapter's communication-loss action fires as configured.
| Symptom | Cause | Fix |
|---|---|---|
| New speed appears, then snaps back | The other controller still writes the reference | Remove its command rungs; one owner |
| Tags update but the motor ignores the speed | Speed reference still points to terminals or pot | Set the source parameters to the network |
| Module connection faults on download | IP or module configuration mismatch | Read the connection diagnostic before touching drive settings |
The decision for each case:
- The new machine supervises the conveyor: the Logix controller owns the connection, the MicroLogix command writes are removed, and its request is read by message into the arbitration logic.
- The standalone machine must survive on its own: the MicroLogix stays in command, the Logix controller writes a remote request into it, and arbitration lives in the MicroLogix program.
- The drive runs from terminals or a pot today: switch the start source and speed reference to the network source first — until then, Ethernet writes change a parameter the motor never follows.
Questions asked
Both of my controllers are Logix — does anything change?
Only the transport. One controller still owns the drive connection; the other produces its request as a produced tag that the owner consumes, which is lighter than messaging. In the producing controller, set Max Consumers to at least the number of consuming controllers you will run, per the produced and consumed tags manual 1756-pm011. Arbitration, scaling and the freshness watchdog stay exactly as they are with a MicroLogix requester.
What does adding the drive to the Logix tree actually create?
With the PowerFlex 525 profile installed, adding the drive to the Ethernet module tree creates controller tags for the command word, the speed reference and drive status such as output frequency and faults. The Logix5000 quick start for connecting a PowerFlex 525, iasimp-qs036, walks through adding the drive and configuring the connection. Without the profile you build a generic module and map the assembly data yourself.
How do I stop the MicroLogix 1400 from writing its speed back over mine?
Disable or delete the rungs in the MicroLogix program that write the start command and speed reference, and keep the program backup. If that machine must keep local control, do not fight over the parameter: leave it as the owner and hand your remote request to it instead, so there is still only one writer.
What should the owner do when the remote machine stops sending requests?
Time a changing heartbeat or sequence counter, not the communication port alone, because a failed read leaves the last value looking valid. Three missed update periods is a workable watchdog: at a 250 ms poll, 750 ms. After that, drop to the permitted local command or stop, and make the drive adapter's communication-loss action agree with the same choice.
Will Ethernet speed writes work if the drive starts from terminals today?
No. The start source and speed reference parameters decide which input wins. Until both point to the network, an Ethernet write changes a stored parameter while the motor keeps following the terminal or keypad command. Change those two settings at a controlled stop and update the machine logic that relied on the old source.