Most programmable logic controllers fall into 2 primary hardware categories: fixed units with predetermined I/O and modular systems that accept configurable backplanes and function modules [S2].
The practical choice depends on I/O count, expansion requirements, communication protocol, processing capacity, program complexity, and whether the application requires a safety-rated controller.
Core PLC Architecture and Control Cycle
A PLC contains 6 principal functional blocks: processor, power supply, memory, input/output interface, communication interface, and programming interface [S1]. The processor executes stored instructions, while memory retains the control program, input data, output commands, and temporary working values [S1].
The operating sequence has 3 technical stages: read inputs, execute program logic, and update outputs, followed by internal housekeeping and diagnostic checks before the next cycle [S2]. On many industrial systems, a complete scan takes only a few milliseconds, allowing the controller to react quickly to switch and sensor changes [S5].
Digital, or discrete, I/O represents an on/off state, while analog I/O represents a variable value such as speed, pressure, or temperature [S2]. This distinction affects module selection, wiring, signal conditioning, and the logic required to interpret field equipment.
Fixed and Modular PLC Configurations
Fixed PLCs ship with a predefined number of inputs and outputs, while modular PLCs accept added backplanes, analog I/O, communications modules, and display modules [S2]. Fixed configurations reduce initial design work and suit repeatable machine duties, but changing the installed I/O count is more difficult than expanding a modular rack.
Modular configurations suit systems whose field-device count, communication requirements, or future expansion can change during design, commissioning, or service [S2]. The engineering cost shifts from fixed hardware selection toward backplane planning, module compatibility, I/O addressing, spare capacity, and configuration management.
The programmable logic controller is therefore not selected only by physical size. Fixed-versus-modular construction determines how the I/O and communications architecture can evolve after the initial specification.
Small, Medium, and Large Capacity Classes
Small PLCs generally contain enough memory for local I/O logic and are suited to conveyors and individual motors; medium PLCs add memory, communication ports, processing capacity, and extra I/O for assembly lines; large PLCs support larger machines and process installations with still greater memory and I/O capacity [S3].
Small units commonly expose serial connections such as RS-232 or RS-485 for field devices [S3]. Medium and large systems can add Ethernet, DeviceNet, analog input modules, analog output modules, and network or bus communication [S3]. These are capacity classes, not universal performance boundaries, so local I/O count and network scale must still be checked against the selected model.
Published product data illustrates how sharply those boundaries can differ within one manufacturer range. Four Omron families listed for comparison span 180 to 5,120 local I/O points, 4 to 400K program steps, and 2 to 4 supported axes [S4].
Input, Output, and Programming Classifications
Digital I/O handles switches, buttons, photoelectric cells, and binary equipment states, while analog I/O handles continuously variable measurements and commands [S1][S2]. Typical analog inputs include pressure, temperature, flow, speed, and weight; outputs can operate valves, vary motor speed, switch heaters, or activate warning devices [S2][S3].
Output classification also separates relay, transistor, and triac-style interfaces by the load and switching method they support. The research establishes that relay logic is more difficult to reconfigure and maintain because changes can require physical rewiring [S5]. PLC selection should therefore be checked against the required load type rather than the controller's general size label.
Programming support is another differentiator. Small controllers may primarily support ladder logic, while medium and large systems permit additional logic structures and languages [S3]. Omron's published families support combinations of ladder programming, function block, structured text, and sequential function chart, depending on model [S4].
Communication and Architecture Selection
PLC communication requirements should be converted into an explicit protocol list before selecting hardware. Published examples include Ethernet, EtherNet/IP, Modbus TCP, Modbus RTU, PROFIBUS-DP, PROFINET, CAN, DeviceNet, and CompoNet [S3][S4].
Protocol support alone does not establish compatibility. The selected PLC must match the protocol implemented by each actuator, sensor, drive, remote I/O station, programming terminal, and supervisory system. Product data also shows that communication capability can differ by model even within the same PLC family [S4].
For data-heavy machines, an industrial PC may be considered when visualization, databases, analytics, or operating-system-based applications dominate. It is not interchangeable with a PLC: a compact PLC remains suitable when deterministic discrete control and local I/O are the primary engineering requirement.
Safety PLCs and Application Boundaries
Safety-related control requires more than a general-purpose PLC selected for I/O count. A safety PLC must be assessed for the required safety function, diagnostic behavior, fail-safe I/O, and applicable machine-safety validation. [S3]
Standard PLCs fit conveyors, motor controls, packaging equipment, pumps, temperature loops, and building or utility automation [S3][S5]. They are generally suitable where the controlled process does not require a safety-rated architecture. Public research establishes that PLCs automate electromechanical processes including assembly lines, amusement rides, and lighting systems [S3].
For changing production requirements, a motion controller becomes relevant when coordinated axis control, interpolation, or motion functions dominate the specification. Otherwise, a standard PLC with suitable I/O and communications is usually the simpler control layer.
Engineering Selection Criteria and Sourcing
A defensible PLC classification should record at least 5 measurable items: local digital I/O count, analog I/O count, program memory, data memory, supported communications, programming languages, and motion-axis capacity. The Omron comparison provides 6 of these fields across 4 models, including 180, 320, and 5,120 local I/O points and program memory from 4K to 400K steps [S4].
Power architecture must also be checked. The power supply converts incoming AC to the low-voltage DC required by the processor and I/O interface circuits [S1]. Field requirements then determine whether modules need digital or analog channels, for example 4–20 mA, and what electrical isolation or output switching is required.
Do not classify by case size alone. The most useful category is the one tied to the installation: fixed for a repeatable compact machine, modular for variable I/O and future expansion, capacity class for processing and memory, signal class for I/O, and safety class for the required protective function. Data from a complete I/O schedule, network list, program specification, and expansion plan will produce a more defensible selection than a vendor size label.
The next trackable engineering step is to freeze the critical specification: local and remote I/O counts, required protocol list, memory demand, axis count, environmental limits, and safety function.