CPU vs Processor in PLCs: How to Choose and Source the Right PLC CPU Module

Jul 22, 2026

Leave a message

Chen Tuo
Chen Tuo
Chen Tuo, Senior Automation Engineer at Shenzhen Chentuo Technology, has 15+ years of hands-on PLC, HMI, and VFD experience with Siemens, ABB, Allen-Bradley, Mitsubishi, Omron, and Schneider, supporting automation projects in 80+ countries.

A modular PLC system on a DIN rail with a CPU and several IO modules wired to color-coded field cables inside a control cabinet.jpg

 

You are replacing a failed controller; the datasheet says "processor," the label on the old unit says "CPU," and the part number does not match anything on your shelf. That gap is where most wrong orders start. In an industrial control system, the PLC CPU module is the part that runs your logic, and depending on the brand, it may be printed as CPU, processor, or controller. This guide clears up the CPU vs processor confusion in a PLC context, then walks through the specs that actually decide which module you need and how to source the correct one without ordering the wrong revision.

 

Quick Answer

If you only have thirty seconds:

 

  • In a PLC, the "CPU module" is almost always the same physical part people call the "processor." It is the unit that executes your program.
  • The name changes by brand. Siemens prints "CPU"; Allen-Bradley says "processor" or "controller"; Omron says "CPU Unit"; and Mitsubishi says "CPU."
  • To pick the right one, match four things: scan performance, memory, supported I/O count, and communication ports.
  • A brand-to-brand comparison table and links to in-stock modules are further down. Jump to the brand comparison if you already know your specs.

 

Replacing a discontinued module? The sourcing section covers original, refurbished, and obsolete replacements.

 

CPU vs Processor: The General Concept (Kept Short)

What a CPU is

A CPU (Central Processing Unit) is the part that executes instructions. It runs a simple loop: fetch an instruction, decode it, execute it, store the result. Everything else in this article builds on that loop, so we will not spend more time on it.

 

What a processor is

"Processor" is the broader word. Every CPU is a processor, but the term also covers specialized silicon such as GPUs and DSPs that handle one narrow job. So a CPU is one type of processor, not a different thing.

 

Why this matters for you

Here is the part the generic explainers miss. If you searched "CPU vs processor" from an automation job, you are not shopping for a computer chip. You are looking for a replaceable module that sits in a PLC rack. Everything below is written for that module, not for a desktop.

 

What "CPU / Processor" Actually Means Inside a PLC

A PLC in a control panel reading a sensor and driving a conveyor on a production line

The job of the PLC CPU module: the scan cycle

Inside a PLC, the CPU module does not "run programs" the way a laptop does. It runs a tight, repeating loop called the scan cycle:

 

  1. Read the state of every input (sensors, switches, feedback signals).
  2. Execute your control program once, top to bottom, using those input values.
  3. Update every output (valves, motors, actuators, indicators).

 

Then it starts over. On a small machine this loop can repeat every few milliseconds, and it repeats for as long as the machine is powered. Picture an assembly line: on each scan the CPU reads a proximity sensor, checks the logic that says "if part present and guard closed, advance the conveyor," and drives the output that moves the belt. The time it takes to complete one full loop is the scan time, and it is the single number that tells you how responsive the controller is. Hold onto that term, because it comes back when we talk about selection.

 

Why PLCs care about determinism, not raw speed

A desktop CPU is judged on how fast it can finish a heavy task. A PLC CPU is judged on something different: whether it finishes every scan in a predictable, repeatable amount of time. That property is called deterministic control, and it is the real dividing line between an industrial controller and a computer chip.

 

A common mistake in selection is assuming a higher clock speed automatically means a better controller. On a machine, a consistent scan you can count on matters more than a high peak number you cannot. A controller that usually scans in 2 ms but occasionally stalls to 20 ms is worse for motion control than one that scans in 5 ms every single time. When you compare modules, you are comparing consistency under load, not just headline speed.

 

How the CPU module relates to the rest of the rack

The CPU module rarely works alone. In a modular PLC it lives in a rack alongside a power supply that feeds it, input and output modules that connect to the field, and communication modules that link it to the network. The CPU is the coordinator: it depends on the power supply, reads and writes through the I/O modules, and talks upstream through the communication modules.

 

The practical takeaway is that you never select a CPU in isolation. The module you choose has to match the rack, the I/O family, and the firmware generation already installed, or the parts will not work together. That constraint is exactly why the selection steps below exist.

 

Key Specs That Decide a PLC CPU Module

Knowing what each spec means is not the point here. The point is knowing how each one narrows your choice. Every spec below is written as a decision, not a definition. The table at the end of this section is the fast reference; the notes explain how to use it.

 

Close-up of a PLC CPU modules label and communication ports while reading its order number

 

Scan time and processing performance

Use scan time to match the controller to the demand of the machine. Simple sequential logic tolerates a slower scan. High-speed motion, fast interlocks, or a large program with thousands of rungs need a faster processor so the loop stays short. On most datasheets this is listed as an execution time per instruction (for example, so many nanoseconds per bit operation). If your application has hard timing requirements, this spec disqualifies the weaker modules first.

 

Program and data memory

Memory decides how big a program the module can hold. Run out and the program will not download. As a rule of thumb, estimate your program and data block size, then choose a module with clear headroom above it, because projects grow during commissioning and over the machine's life. Retrofits that add logic to an old panel are the usual place teams get caught short here.

 

Supported I/O count

I/O count is the first hard gate in selection. Every CPU module has a ceiling on how many local and expansion points it can address. Add up your digital and analog points, include a margin for future expansion, and drop any module that cannot reach the total. There is no workaround: if the point count exceeds the module's limit, it is the wrong module.

 

Communication protocols and ports

Confirm your network before you confirm the CPU. If the plant runs PROFINET, you need a CPU with a PROFINET port; if it runs EtherNet/IP or Modbus, the module has to speak that protocol natively or through an added communication module. Built-in protocols vary widely between brands and even between series in the same brand, so this spec often decides the exact model, not just the family.

 

Redundancy and safety rating

Only pay for these when the application demands them. Standard machine control does not need a redundant or safety-rated CPU. Process control that cannot tolerate downtime, or a line with a safety function that must meet a specific rating, does. Choosing a redundant module for a job that does not need one is a common way to overspend.

 

Spec

What it decides

Where to confirm it

Scan time

Whether the loop keeps up with the machine

Instruction execution time on the datasheet

Program / data memory

Whether your program fits, with room to grow

Memory size in the technical spec sheet

I/O count

The hard ceiling on points you can control

Max local + expansion I/O in the spec

Comm ports / protocols

Whether it fits your existing network

Onboard ports listed in the order number breakdown

Redundancy / safety

Whether it suits high-availability or safety duty

Product series and rating in the catalog entry

 

Not sure how a spec maps to a specific part number? Send your requirements and our team will match it. Request a quote.

 

Brand by Brand: How Each Vendor Names Its "CPU / Processor"

The same part goes by different names depending on the brand, which is half the reason "CPU vs processor" causes so much confusion in the first place. Here is how the four most common vendors label it, plus a one-line note on picking within each family. Order numbers are shown as format examples so you can learn to read them; always verify the exact suffix against the live catalog.

 

Siemens (SIMATIC S7-1200 / S7-1500 CPU)

Siemens calls it a "CPU." Order numbers begin with 6ES7 (for example, a 6ES7 51x series part for an S7-1500 CPU). The S7-1200 suits compact machine control; the S7-1500 covers larger, faster, or more communication-heavy applications. Browse in-stock Siemens PLC modules.

 

Allen-Bradley / Rockwell (ControlLogix / CompactLogix processor)

Allen-Bradley uses "processor" and "controller," but in this brand's language that is the same part everyone else calls a CPU. ControlLogix (1756 series, for example 1756-L8x) targets large systems; CompactLogix (5069 or 1769 series) targets small to mid-size machines. See available Allen-Bradley PLC modules.

 

Omron (CJ2 / NX CPU Unit)

Omron labels it the "CPU Unit." The CJ2 line (for example CJ2M-CPU3x) is the established modular platform, while the NX line (for example NX102-xxxx) is the newer machine-automation controller. Check Omron CPU Units.

 

Mitsubishi (FX / Q series CPU)

Mitsubishi says "CPU." The FX5U (for example FX5U-32M) is a compact all-in-one controller; the Q and iQ-R series (for example Q03UDVCPU) are modular for larger builds. View Mitsubishi PLC modules.

 

Brand

What they call it

Typical series

Where to look

Siemens

CPU

S7-1200, S7-1500

Siemens PLC modules

Allen-Bradley

Processor / Controller

ControlLogix, CompactLogix

Allen-Bradley PLC modules

Omron

CPU Unit

CJ2, NX

Omron CPU Units

Mitsubishi

CPU

FX5U, Q / iQ-R

Mitsubishi PLC modules

 

How to Choose the Right PLC CPU Module (Decision Checklist)

Once you know what each vendor calls the part, the selection itself is an ordered set of decisions. Work through them in this sequence and you land on a single part number.

 

  • Confirm the platform. In most cases, stay on the brand and series already installed. Matching the existing platform saves rewiring, reprogramming, and commissioning time.
  • Calculate I/O. Total your digital and analog points, add a margin, and set that as your minimum.
  • Estimate memory. Size your program and data, then require clear headroom above it.
  • Confirm communication. List the protocols and ports the machine needs and require them onboard or via a matching comm module.
  • Decide on redundancy or safety. Add these only if the application genuinely requires high availability or a rated safety function.
  • Lock the order number and firmware. Confirm the exact part number and check that the firmware revision matches your project.

 

One piece of practical advice: switching brands mid-life almost always costs more in engineering hours than staying put, even when the new module looks cheaper on paper. Not sure which part fits? Send us your requirements and we will confirm the match.

 

Original, Refurbished, or Obsolete? Sourcing a PLC CPU Safely

Selecting the right part number is only half the job. The other half is buying a unit you can trust, especially when the model is old or discontinued.

 

Original, new, and refurbished, and how to tell them apart

New original stock is factory-fresh and untouched. Refurbished units are tested and restored, and can be a sound choice for legacy lines when new stock has dried up. The risk is buying a relabeled or unverified unit sold as original. Before you commit, check the manufacturer label and logo, the batch or date code, and the packaging and anti-static sealing. The common and costly mistake is buying on price alone while ignoring source and warranty, which is where counterfeit and out-of-spec parts slip in.

 

Finding a compatible replacement for a discontinued model

When your exact CPU is discontinued, you usually have two paths: move up to the successor within the same series, or migrate to a newer platform. Either way, watch two things closely, firmware compatibility and whether your existing program will convert, because a physically compatible module can still refuse to run an old project without a conversion step. If you are staring at an obsolete PLC CPU with no drop-in match, we can help identify a working replacement.

 

What to confirm before you order

Run this quick check before any purchase:

 

  • Stock and lead time: Is the exact part actually available, and when does it ship?
  • Firmware revision: Does it match what your project expects?
  • Condition and origin: New, original, or tested refurbished, with clear provenance?
  • Warranty: What coverage comes with the unit?

 

Ready to confirm a part? Check stock or request a quote.

 

FAQ

 

 

info-470-408

Is a PLC's "CPU" the same as its "processor"?

In almost every case, yes. Inside a PLC the CPU module and the processor are the same physical part that runs your control program. The label just changes by brand: Siemens prints "CPU," Allen-Bradley prints "processor" or "controller." When you compare across vendors, treat the terms as interchangeable.

What is PLC scan time and why does it matter?

Scan time is how long the CPU takes to complete one full loop of reading inputs, executing the program, and updating outputs. It matters because it sets how quickly the controller reacts to a change in the field. Fast motion and tight interlocks need a short, consistent scan; simple sequential logic can tolerate a longer one.

How do I read a Siemens or Allen-Bradley CPU order number?

Siemens CPU order numbers start with 6ES7, and the middle digits identify the series and model (for example an S7-1500 CPU). Allen-Bradley uses a series prefix such as 1756 for ControlLogix or 5069 for CompactLogix, followed by the processor code. The safest approach is to match the full order number, suffix included, against the live catalog before ordering.

Can I replace an obsolete PLC CPU with a newer one?

Often, yes, but not always as a drop-in. You typically move to the successor in the same series or migrate to a newer platform. Confirm firmware compatibility and whether your existing program converts, since a mechanically compatible module can still need a project conversion. If you cannot find a match, send us the old part number and we will look for a replacement.

How many I/O points can one PLC CPU handle?

It depends entirely on the module. Each CPU has a published ceiling for local and expansion I/O, ranging from a few dozen points on a compact controller to thousands on a large modular one. Total your points, add a margin, and confirm the module's maximum covers it before you buy.

Do I need to match firmware versions when replacing a CPU?

Usually, yes. A replacement CPU should run a firmware revision compatible with your project, or the program may fail to download or behave differently. When you order, state the firmware revision you need so the unit you receive is ready to install rather than needing an update in the field.

 

Conclusion

In a PLC, the CPU and the processor are the same module under different brand names, and choosing the right one comes down to matching scan performance, memory, I/O count, and communication to your machine, then confirming the exact part number, firmware, and origin before you buy. If you are ready to move, tell us what you need and we will find the match. Request a quote or browse PLC CPU modules in stock.

 

Free consultation

Send Inquiry