Selection guide
Selecting an ABB AC500 PLC family for your application
Short answer
Shortlist AC500-eCo for compact machines and modular AC500 where the exact I/O, network or timing limits require it. Check the applicable XC variants for harsh conditions. Select and validate safety hardware against the machine risk assessment.
On this page
- Match the family to the application class
- The classification order: safety, environment, scale
- Safety functions: when the answer is AC500-S
- Environment: when the answer is AC500-XC
- eCo or modular AC500: compare exact limits
- Sizing the family for a 66-point machine in a standard cabinet
- What the family choice does not change
- Verify the model against the current lineup
- Questions asked
Start with AC500-eCo for a compact machine, then compare modular AC500 if the required I/O, communication, memory or timing exceeds what an eCo configuration can support. ABB offers XC environmental variants in the standard and safety ranges. Make the safety and enclosure decisions from the machine's requirements, then verify the exact CPU and modules against ABB's documentation. The Mitsubishi MELSEC family selection guide applies the same requirements-first approach to a different catalog.
Match the family to the application class #
Use this comparison to build a shortlist. The safety and environmental rows may apply to the same machine.
| Family | Application class | Choose it when | Rule it out when |
|---|---|---|---|
| AC500-eCo | Compact machines | A specific CPU and supported modules meet I/O, network, timing and spare-capacity requirements | A required feature, usable spare capacity or measured performance exceeds the proposed configuration |
| AC500 | Modular systems | The design needs supported communication modules, a larger application, motion features or other capacity that the compact candidate lacks | A validated compact configuration already meets the design and growth requirements |
| AC500-XC | Extended environmental conditions | The exact XC CPU and companion modules cover the measured installation conditions and required mounting | The documented limits of the specified equipment and enclosure already cover the site |
| AC500-S | Programmable safety functions | The risk assessment and architecture call for a supported safety controller, safety I/O and communication | The complete alternative safety architecture meets the required functions and has been validated |
For example, a safety PLC in an exposed installation needs both the safety and the environmental checks. ABB documents AC500-S-XC hardware for that combined requirement.
The classification order: safety, environment, scale #
Run three questions in a fixed order, because each one is harder to correct after the fact than the one below it.
- Safety first. Identify the required functions, performance and response time. Select the safety architecture and allocate each function to the safety hardware before choosing the standard controller.
- Environment second. Compare temperature inside the enclosure, condensation, vibration and contaminants with the limits on the exact installed part numbers. Include environmental derating and mounting limits.
- Scale last. List point types, network roles, motion interfaces, scan and update targets, and the planned reserve. Calculate these against candidate configurations.
ABB documents AC500-S-XC variants. Check the environmental limits on each CPU, I/O and communication module. The cabinet and any exposed connections have their own protection requirements.
Safety functions: when the answer is AC500-S #
A safety PLC is a candidate when the design requires programmable safety, distributed safety I/O or coordinated functions. Choose between a safety PLC and hardwired safety relays from the risk assessment, required diagnostics, response time and validation plan. Counting safety functions alone gives no design threshold.
One boundary to hold: the machine's required performance is stated as a Performance Level under ISO 13849-1 or a Safety Integrity Level under IEC 62061, and those are separate ratings, not two spellings of one number. Specifying AC500-S buys a platform rated for safety execution; it validates nothing. The complete chain — sensing, logic, actuation, response time — is engineered and validated against the required PL or SIL for that machine, and the controller's rating is a ceiling the function must be shown to reach. If the safety I/O sits in field stations rather than the main cabinet, selecting remote I/O architecture for a safety upgrade is the next layer of the same decision.
Environment: when the answer is AC500-XC #
Measure or estimate the conditions at the controller inside the enclosure before selecting XC. Include cabinet heat rise, cold starts, condensation, vibration, dust and corrosive exposure. ABB lists separate conditions and restrictions by component. Select enclosure ingress protection and cable entries for the installation as part of the same design.
Check the exact order-code datasheets and ABB system data for operating limits, derating and installation conditions. Confirm that the enclosure and every installed component satisfy their respective requirements.
eCo or modular AC500: compare exact limits #
- I/O. ABB lists analog option boards for voltage, current and selected temperature inputs. AC500-eCo V3 CPUs with a side I/O bus can connect up to 10 local modules. The PM5012-x-ETH lacks that local bus. Verify board slots, signal ranges, module compatibility and the power budget before allocating spare capacity.
- Networks. PM5032-T-ETH has one Ethernet interface, and PM5072-T-2ETH has two. A single interface can support multiple devices on its network. Check the protocol, PLC role, firmware, license and concurrent connections per role. A second physical network can require another interface even when the connection count is low.
- Motion and execution. ABB documents pulse-and-direction output on certain transistor models. Verify the exact CPU revision, drive interface, available axis resources and required cycle time. For synchronized axes or a fieldbus motion design, confirm that the proposed controller, drive and engineering software support the required mode.
Sizing the family for a 66-point machine in a standard cabinet #
An illustrative mid-size machine, of the kind this decision usually lands on.
Inputs. 42 discrete inputs at 24 V DC (sensors, limit switches), 18 discrete outputs at 24 V DC (solenoid valves), 4 analog inputs at 4-20 mA, and 2 analog outputs at 4-20 mA feeding proportional valves. Two variable-frequency drives are polled over Modbus TCP on the machine's Ethernet network, and one SCADA station writes setpoints over the same network. Safety is hardwired — gate interlock and emergency stop on relays — and the cabinet is indoors and conditioned. The project carries a 20% growth allowance for future I/O. The point counts are this machine's own schedule; the family classes come from ABB's portfolio positioning.
Rule. Compare the verified I/O schedule and growth by signal type with the exact CPU and modules. Evaluate the documented protocol roles and reserve for peak traffic and commissioning.
Arithmetic.
- Discrete points: 42 + 18 = 60
- Analog channels: 4 + 2 = 6
- Total I/O: 60 + 6 = 66
- Growth allowance by signal type, rounding each up: 9 discrete inputs, 4 discrete outputs, 1 analog input and 1 analog output
- Capacity to order for: 51 discrete inputs, 22 discrete outputs, 5 analog inputs and 3 analog outputs, or 81 points in all
- Assuming a separate Modbus TCP session per device: 2 PLC client sessions for the drives and 1 PLC server session for the SCADA station over 1 Ethernet segment
Decision. Keep AC500-eCo and modular AC500 on the shortlist. As a first-pass candidate, ABB lists 12 dedicated inputs and 8 dedicated outputs for PM5032-T-ETH. Budgeting only those dedicated points leaves 39 discrete inputs and 14 discrete outputs to allocate to supported expansion modules, alongside the 5 analog inputs and 3 analog outputs. ABB documents both Modbus TCP roles on this CPU. Check the exact module list and signal ranges, maximum concurrent connections, output loading, expected scan time and update timing. When the eCo configuration meets all of those with reserve, it remains a viable choice. Choose modular AC500 when a specific requirement exceeds its capacity.
What the family choice does not change #
The four families are engineered in one environment, ABB's Automation Builder, and programmed in the IEC 61131-3 languages the task calls for: ladder diagram, structured text, function block diagram. The portfolio carries industrial Ethernet, Modbus, PROFIBUS and serial communication, plus motion functions for positioning, speed and synchronization, with diagnostics and fault handling built in. Which of those a specific CPU and module set provides, and at what performance, is a model-level check in ABB's documentation — the family name guarantees the class of capability, not the version.
When SCADA writes setpoints, specify which values the PLC accepts, how it checks valid ranges and equipment state, and what happens when data goes stale. Keep machine safety in the validated safety architecture.
Verify the model against the current lineup #
For a new machine, the family decision closes one column of the schedule; the rows are order codes. Fix the exact CPU, count the I/O modules from the point schedule with the growth allowance included, list the communication processors, and confirm every item is in ABB's current lineup before procurement. The model-level numbers — I/O per module, temperature range, safety capability — come from the data sheets of those order codes, never from the family name.
For an installed machine, the committed rule is like-for-like: replace a failed unit with the same order code, and only re-select when ABB has discontinued it. Then the successor comes from ABB's discontinuation bulletins, not from a fresh family pass. A repair is not the moment to change families.
Questions asked
Which AC500 family suits a small machine with two or three fixed safety functions?
Use the machine risk assessment to select the safety architecture. Relays can be appropriate for fixed functions when the complete design meets the required performance and response time. A safety PLC is another option when zoning, diagnostics, coordinated drives or distributed safety I/O matter.
Does choosing AC500-XC change how the control program is written?
ABB offers XC hardware variants in both the standard and safety ranges. Confirm the environment, supported firmware, available libraries and modules for the exact replacement order code before reusing an existing project.
Can I start on AC500-eCo and move to the modular AC500 when the machine grows?
Check the exact eCo CPU, supported I/O and remaining capacity before planning a migration. AC500-eCo V3 CPUs with a side I/O bus support local expansion, and some CPUs provide two Ethernet interfaces. Confirm I/O types, protocol roles, firmware, licenses and timing against the actual schedule.
Is specifying AC500-S enough to satisfy a machine safety requirement?
No. The required performance is set by the machine's risk assessment, stated as a PL under ISO 13849-1 or a SIL under IEC 62061, which are separate ratings, not interchangeable. The S CPU is one element with a rating ceiling; the complete function, from sensor through logic to actuator with its response time, must be engineered and validated to that target.
What should I check before ordering a replacement part for an existing AC500 system?
Order the same order code as the failed unit, and confirm that code is still in ABB's current lineup. If it has been discontinued, take the successor from ABB's discontinuation bulletins, and check that the replacement's supported firmware and tool versions match the existing project before it goes on order.
Corrections
- : Clarified AC500-eCo I/O expansion, network and motion limits by CPU, and corrected the worked example and environmental and safety selection checks.