What Is a PLC, and Do You Need One for Your Automation Project?
Not every pump or motor project needs a PLC. A lot of them don't. But once you're coordinating more than one device, or a system needs to make decisions rather than just run, a PLC is usually the piece that's missing. Here's what one actually does, and how to tell which camp your project falls into.
What a PLC actually does
A Programmable Logic Controller is, in plain terms, a small industrial computer built to do one job reliably: read inputs (sensors, switches, feedback signals), run logic against them, and drive outputs (motors, valves, indicators, alarms) accordingly — continuously, in real time, in an industrial environment. Where a VSD's built-in PID control handles the behaviour of a single drive, a PLC coordinates across multiple devices — sequencing several pumps, interlocking one piece of equipment against another, or logging and reporting on a whole system rather than one motor.
Inside the Slanvert SH500 series
UTC Industrial stocks the Slanvert SH500 series — SH511, SH522 and SH523 motion PLCs — three CPU tiers scaled for different project sizes, sharing a common architecture:
- An 8-input, 8-output (transistor/pulse type) base configuration, with dedicated high-speed pulse outputs for coordinating precise, synchronised motion — built to work alongside Slanvert N3RE EtherCAT servo drives and VSDs without system latency
- Modular expansion, added on the left or right of the CPU as the project needs: RS485 communication modules (with or without a real-time clock), analog input/output modules, RTD and thermocouple temperature input modules, and additional digital I/O in blocks of 8 or 16 points
- A single ecosystem, so a project's I/O count can grow by adding expansion modules rather than replacing the CPU
That modularity matters in practice: a small booster station might only need the base CPU and a couple of digital I/O expansions, while a larger multi-pump or process control panel can add analog and communication modules as requirements grow, without a different product line.
When you need a PLC
- Multi-pump or booster stations that need to alternate pumps, stage them against demand, or run lead/lag logic between them
- Interlocked systems, where one piece of equipment's state depends on another's (a pump that shouldn't run unless a valve is open, for instance, or an alarm that should stop a process rather than just flag it)
- Data logging and remote monitoring — the SH500's RS485/Modbus communication supports integration into SCADA and remote monitoring setups, so a site can be checked on without a visit
- Coordinated motion control, where a VSD and a servo drive need to move in sync rather than independently
When you probably don't
A single pump or motor with straightforward speed control usually doesn't need a separate PLC. Most VSDs — including the Slanvert Hope65 range — have built-in PID control that can run directly off a pressure or level sensor, which covers a large share of single-pump borehole, booster and irrigation setups on its own. Adding a PLC to a job that doesn't need one is added cost and complexity without added benefit.
Pairing a PLC with an HMI
A PLC on its own has no display — it's the logic layer, not the interface. Most PLC-based panels pair the controller with an HMI (Human-Machine Interface) so an operator can see live status, adjust setpoints, and clear alarms without opening the panel. We've covered how the two work together, along with the VSD and the panel itself, in our complete pump control system guide.
Quick FAQ
Can a PLC replace a VSD? No — they do different jobs. The VSD controls motor speed; the PLC coordinates logic and sequencing across devices, including one or more VSDs. Most PLC-based systems still need a VSD (or several) alongside it.
Do I need programming experience to use one? Not to buy or spec one — that's something we can quote and build into a panel for you, with the logic programmed to your application's requirements. If you're self-installing, some PLC programming knowledge (or a programmer on your team) is needed to write the control logic.
What's the difference between the SH511, SH522 and SH523? They're scaled CPU tiers within the same SH500 family rather than different feature sets — the right one depends on your project's I/O count and complexity. Send us your application details and we'll confirm which tier fits.
Browse the Slanvert PLCs & I/O Modules range, in stock from our Pretoria East warehouse. Not sure whether your project needs a PLC, or which CPU tier fits? Contact us with your application details and we'll confirm before you order.