IMDHMIControls LibraryShop main store

Selection guide

How to choose an S7 PLC family for a machine

PLC programming Published 6 min read

Short answer

For a new machine, pick the S7-1200 when the job is standalone control with modest I/O and one or two axes, and the S7-1500 when you need coordinated motion, controller-integrated safety, a fast scan or a large I/O count. Use S7-300 and S7-400 only to extend plants that already run them. Program both current families in TIA Portal.

On this page
  1. What each S7 family is positioned to do
  2. The decision rules
  3. Where the S7-1200 wins
  4. Where the S7-1500 wins
  5. What to do with S7-300, S7-400 and S7-200
  6. Worked example: one machine per family
  7. From family to exact CPU
  8. Questions asked

For a new machine the choice is between two current families: the S7-1200 for compact standalone control with modest I/O and simple motion, and the S7-1500 for coordinated motion, controller-integrated safety, fast scans and large I/O counts. Use the S7-300 and S7-400 only to keep existing plants running; both are legacy lines in phase-out, and their successor is the S7-1500. The S7-200 is out of the running for anything new. Fix the family from what the machine must do, then pick the exact CPU from the per-CPU data in the Siemens comparison list (support entry 109816001). The decision rules, the comparison table and a worked example for two typical machines follow.

What each S7 family is positioned to do #

Family Documented position Take it for Engineering tool
S7-1200 Compact controller for small to mid-sized applications, PROFINET on the CPU, modest I/O and motion Standalone machines and skids with a handful of I/O and one or two independent axes TIA Portal
S7-1500 High-performance line: multi-core processors in the stated feature set, integrated safety functions, high-speed networking, shorter cycle times Coordinated motion, safety in the controller, scan-critical and large-I/O machines TIA Portal
S7-300 Modular family for medium to large systems, with a wide catalogue of I/O, special-function and communication modules Extending or repairing existing S7-300 plants only Classic STEP 7 tooling
S7-400 Rack-based high-end line built for extensive I/O capacity, scalability and hot-standby redundancy Existing S7-400 plants and like-for-like legacy replacement Classic STEP 7 tooling

These rows are portfolio positioning from Siemens' own descriptions, not per-CPU specifications. Work memory, instruction execution times, supported module counts and I/O limits live in the vendor's comparison list for the four families, published as Siemens support entry 109816001; the edition dated October 2023 was the latest when this page was researched. The table tells you which column of that list to work in.

The decision rules #

Apply these in order and stop at the first match:

  1. A new standalone machine: safety outside the controller, I/O within the compact line's scope, motion no more complicated than one or two independent axes. Take the S7-1200.
  2. Coordinated motion, with axes geared or cammed to a master; safety functions in the controller; a cycle time the process can feel; or an I/O count beyond the compact line's scope. Take the S7-1500.
  3. The machine joins a plant already running S7-300 or S7-400. Stay on that family for spares and like-for-like extensions, and put genuinely new machines in that plant on the S7-1500.
  4. The design started life as an S7-200 job. Stop, and rebuild the selection on the S7-1200.

The worked example below puts numbers on "within scope" and "beyond" for two machine shapes; use those as calibration, then repeat the arithmetic with your own counts.

Where the S7-1200 wins #

Siemens positions the S7-1200 as the compact family for small to mid-sized applications: PROFINET on the CPU, a footprint for tight panels, and a scope the vendor's material describes as modest I/O and motion. That matches the standalone machine on a skid or a bench: a drive on the network, safety in the door circuits and emergency-stop relays, no coordination between axes.

Keep it there. One axis of speed or positioning control over PROFINET is S7-1200 work. The moment a second axis has to follow the first, or the safety logic has to live in the program, the stated positioning points at the S7-1500, and that is the decision to make.

Where the S7-1500 wins #

The S7-1500 is the high-performance line of the two: multi-core processors in the family's stated feature set, integrated safety functions, high-speed networking, and CPUs Siemens rates for shorter cycle times than the compact family delivers. Large-scale process automation with bigger I/O counts also lands here. The line serves SCADA over OPC UA straight from the controller, with the connection configured in TIA Portal: Connect an S7-1500 to SCADA over OPC UA from TIA Portal walks that setup end to end.

Where safety lives in the controller, select the fail-safe CPU and I/O variants and validate the implemented functions to the performance level the machine's risk assessment demands under ISO 13849, before sign-off.

What to do with S7-300, S7-400 and S7-200 #

The S7-300 is the modular family with the wide catalogue of I/O, special-function and communication modules; the S7-400 is the rack-based high-end line with extensive I/O capacity, scalability and hot-standby redundancy. Both are in phase-out: they belong to existing installations, and Siemens points new designs at the S7-1500 as the successor. The S7-200, the entry-level family for basic standalone tasks, is older still; its slot in the current portfolio is the S7-1200's.

In a plant that runs the older families, the rule is simple: spares and like-for-like extensions stay on the family already in the panel, and any new machine in that plant is an S7-1500. A hot-standby redundancy requirement in an existing S7-400 system stays S7-400. When you replace a legacy controller and its scan time is the number you are not allowed to degrade, How to size an S7-400 CPU against a PLC-5/40 scan time shows the matching arithmetic.

Worked example: one machine per family #

Both machines are illustrative inputs with the arithmetic shown; the decisions are the point.

Machine A, standalone pallet shuttle. 74 digital inputs, 46 digital outputs, 6 analog inputs, one VFD axis on PROFINET, safety in door circuits and emergency-stop relays.

  • I/O today: 74 + 46 + 6 = 126 channels.
  • Spares at 20%: 126 × 1.20 = 151.2, so plan 152 channels.
  • Motion: one axis, speed and position, nothing following anything.

Decision: S7-1200. Nothing in that list leaves the compact family's stated scope.

Machine B, rotary filler-capper. 210 digital inputs, 140 digital outputs, 24 analog inputs, six servo axes geared to a virtual master, guarded doors and emergency stop integrated in the controller, 250 bottles per minute reported to SCADA over OPC UA.

  • I/O today: 210 + 140 + 24 = 374 channels.
  • Spares at 20%: 374 × 1.20 = 448.8, so plan 449 channels.
  • Cycle: 60 s ÷ 250 bottles/min = 0.24 s = 240 ms per bottle, inside which the six geared axes resynchronize.

Decision: S7-1500. Coordinated motion and controller-integrated safety each independently put this machine on the high-performance line, and the OPC UA feed to SCADA is standard work for it.

From family to exact CPU #

The family is the engineering decision; the CPU inside it is a data lookup. Work memory, execution times, supported modules and I/O limits per CPU come from the vendor's comparison list (support entry 109816001), not from a forum post or a reseller summary. Confirm there that the specific CPU carries every interface and protocol role the machine needs: PROFINET, PROFIBUS, Modbus, serial and industrial Ethernet all appear across the S7 range, but the physical port and the master or slave role belong to the exact CPU and its modules, not to the family name.

All four families program in ladder logic, structured text and function block diagram. The two current families are engineered in TIA Portal, so one engineering tool covers a mixed S7-1200 and S7-1500 plant, and What STEP 7 is in a PLC project, and which one you need covers the classic tooling the legacy families were built in. Plan the station that runs it: an industrial panel PC at the cabinet keeps programming, diagnostics and commissioning on the machine instead of on an office desk.

Questions asked

Is one servo axis enough reason to move from the S7-1200 to the S7-1500?

No. A single axis doing speed or positioning over PROFINET with a modest I/O count is S7-1200 territory, and that is where it stays. The S7-1500 earns its slot when a second axis must follow the first through gearing or camming, when safety functions move into the controller, or when the cycle time itself becomes the constraint.

Can a single plant run both S7-1200 and S7-1500 machines?

Yes, and it is normal practice. Both families are engineered in TIA Portal and both speak PROFINET, so a line with an S7-1200 on each simple station and an S7-1500 on the motion-heavy machine integrates on one network and one engineering tool. Choose the family per machine, from that machine's scope, not per plant.

Is the S7-200 still a valid choice for a basic machine?

Not for new work. The S7-200 is the entry-level family for basic standalone tasks, and that slot in the current portfolio belongs to the S7-1200, which adds built-in PROFINET. Treat any S7-200 you inherit as a retrofit candidate rather than a template: rebuild the control on an S7-1200 the next time the machine is touched.

Which programming software do the current S7 families need?

TIA Portal engineers both the S7-1200 and the S7-1500, so one installation covers a mixed plant. Existing S7-300 and S7-400 programs were built in the classic STEP 7 toolchain, which is one more reason those two families stay confined to the plants already running them.

Keep reading

  • Selection guide

    How to size an S7-400 CPU against a PLC-5/40 scan time

    No S7-400 CPU maps one-to-one to a PLC-5/40 by instruction timing, and none needs to: every CPU from the 414 upward is faster on logic execution. Select on memory, I/O and communications capacity, then accept the choice only when the translated program's measured worst-case cycle lands at or below two-thirds of the measured PLC-5/40 scan.

    PLC programming

  • Comparison

    How ControlLogix and S7-400 PLC architectures differ

    A ControlLogix application maps onto an S7-400 only at the requirements level. ControlLogix runs tasks that contain programs and routines on symbolic tags; the S7-400 runs organization blocks that call FBs and FCs against data blocks, mixing symbolic and absolute addressing. Match execution behavior, data ownership and I/O timing — never translate instruction names.

    PLC programming

  • Selection guide

    Migrating a MicroLogix 1500 machine to a current PLC

    Quote CompactLogix as the baseline for the rebuild: Rockwell's migration reference gives the MicroLogix 1500 two documented destinations, MicroLogix 1400 or CompactLogix 5370 (L1/L2), and a low-volume machine rebuild does not justify the Micro850 route. Take the Micro850 only for high build volume, after the 11 uncovered inputs, serial Modbus, the drive interface and a trial CCW import are verified.

    PLC programming