Drives and motion
Variable frequency drives and servo systems, and how a PLC commands them.
Latest articles
Comparison
How a PLC controls a VFD: five interfaces compared
A PLC controls a VFD through one of five interfaces: discrete I/O, an analog speed reference such as 0-10 V or 4-20 mA, Modbus RTU or TCP, EtherNet/IP or BACnet/IP, or PROFIBUS or DeviceNet. Discrete and analog wiring carry commands only; the network interfaces also return status and fault data. Pick by how much the PLC must know about the drive, not by brand.
How-to
How to commission five VFD drives on one Modbus gateway
Prove the link in three passes: open the Modbus TCP connection to the gateway, verify one read from one drive against its own display, then run one serial transaction at a time across all five. A TCP-to-RTU gateway must serialize every RS-485 request, so schedule run commands ahead of power reads instead of polling all five at once.
How-to
Interface an EFC5610 drive with a ctrlX CORE over EtherCAT
The EFC5610 runs from a ctrlX CORE over EtherCAT once E8.00 = 1 and H3.40 = EC are set and the drive is rebooted, the ESI is installed, and the xFC01 device is scanned and downloaded. Command it with the Rexroth Mode decimals (128 activate, 129 run forward) and a frequency word scaled at 0.01 Hz per count, so 50.00 Hz is 5000 counts.
Selection guide
Running CiA 402 CANopen drives from an S7-1500 through a gateway
Keep the CANopen drives for axes whose trajectory the drive itself generates — CiA 402 modes 1, 3 and 6 — with the segment's bus load held under about 40% at 250 kbit/s. Replace with PROFINET drives and Technology Objects for any gearing, camming or coordinated axis, because a conformance class B gateway gives cyclic data with no isochronous coupling and no Technology Object can close behind it. This rewinder's axes all generate their profiles drive-side, so the keep path wins.
Troubleshooting
Fix a PowerFlex 40P opto output that will not turn on
The opto outputs on PowerFlex 40P terminals 17 and 18 are always sinking NPN transistor outputs rated 30 VDC at 50 mA, and the drive's sinking/sourcing switch configures only the digital inputs. Fix it with a sourcing PLC input wired between +24 V and the output terminal, an interposing relay, or the drive's form C relay output.
Troubleshooting
Troubleshooting S7-1200 PROFINET servo motion control issues
Fix an S7-1200 PROFINET servo project in order: compile the motion calls in FB1 first, set drive and TIA Portal to the same telegram — Telegram 3 on this pairing — then prove one axis holds enable and velocity through repeated scans. A first-generation CPU 1214C executes independent single-axis motion only; the flying shear's deterministic master-slave cut belongs in the drives or in a motion-class controller, and no telegram adds it.
Troubleshooting
Troubleshooting missing Drive Ready on a V60 axis retrofit
S-rUn on the drive proves the enable reached it; it proves nothing about the return path. Hold the MC_Power enable TRUE for the whole test, then trace the drive-ready contact, its 24 V sense wiring, the PLC input channel and the tag mapping in that order. Local jog proves the motor and power stage, not the PLC interface.
Troubleshooting
Robot PROFINET data reaches the PLC in one direction only
The one-way symptom is a register-direction error, not a PROFINET limit: cyclic I/O carries both directions at once, but input and output are named from the robot's viewpoint. read_input_boolean_register works because it consumes the bank the PLC fills; write_input_boolean_register writes into that same receive bank, so nothing reaches the S7-1200. Write the robot's output registers and bind fresh PLC input tags to them.
How-to
Control an ATV12 drive from a TM200 PLC over Modbus RTU
The ATV12 takes start/stop from register 8601 (CMD) and speed from register 8602 (LFRD, in rpm) once you set Fr1 to Mdb in the CtL- menu and match address, baud, parity and stop bits at both ends. The ladder then writes both words cyclically, one request at a time, gated on completion. Start from the TVDA sample project in Machine Expert Basic.
How-to
Bridging a PLC-5/15 DH+ network to a Kinetix 300 servo drive
Yes, a DH+-to-EtherNet/IP gateway exchanges command and feedback words between a PLC-5/15 and a Kinetix 300, but it only moves data: the drive must execute the motion profile locally. Replace the stepper controller, pulse expander, and encoder-counter functions with an eight-word map that carries a 32-bit position as two 16-bit words behind a data-valid handshake. If the machine needs trajectory points streamed per scan, migrate the controller instead of bridging it.
Troubleshooting
Why a Kinetix 5500 needs a motion-capable Logix controller
A Kinetix 5500 servo drive used as a Logix integrated motion axis requires a motion-capable CompactLogix controller such as the 5069-L306ERM. A non-motion 5069-L306ER cannot add the drive to the module tree and is reported to read only some drive parameters over explicit messaging. Confirm the controller catalog number and the required axis count before troubleshooting anything else.
Troubleshooting
Start and stop a PowerFlex 700 over EtherNet/IP from CompactLogix
Yes — set PowerFlex700:O.DriveLogicRslt_Start and PowerFlex700:O.DriveLogicRslt_Stop in the controller output image; those :O members are the network start and stop commands. Parameter 271 [Drive Logic Rslt] inside the drive is a read-only diagnostic of the combined command, so writing it fails. Keep the hardwired drive enable as the safety path and set the comm-loss action to fault, then prove both by test.