Scenario. You're a controls engineer at a mid-size packaging house. The old S7‑300 is being retired. A colleague pushes Omron NX1P2: "Primary cycle as low as 4 ms, integrated EtherCAT motion — the Siemens PLC can't touch that." He's half right on the number, but the datasheet hides the eligibility gate. That gate decides whether the spec actually applies to your machine, or whether you're buying a Ferrari for a gravel road. Let me walk you through what I've learned after two decades of specifying PLCs — the real-world constraint that no quick-look comparison reveals.
The Omron NX1P2-9024DT is listed with a primary task cycle of 2 ms. The Siemens S7-1200 (CPU 1214C) executes a bit instruction in ~85 ns (40 ns on G2) and typical scan cycles land around 1–3 ms for a mid-size program. On paper, both are in the same ballpark. But here's the gate: cycle time measured at the CPU doesn't equal the time it takes to react to a physical input and drive an output. The Omron PLC uses EtherCAT for motion and I/O — deterministic, sub-millisecond jitter. The Siemens uses PROFINET RT, which is also deterministic but with a different topology constraint: you need an IRT switch or a dedicated PROFINET controller to hit jitter under 1 ms. The datasheet hides that the Omron's 2 ms cycle is achievable with its built-in EtherCAT port and standard I/O. The Siemens, without a PROFINET IRT-capable network, will see jitter up to 3–5 ms on mixed traffic. Worked consequence: If your machine has a high-speed cam profile or a pick-and-place with When does this reverse? For machines with simple sequential logic, or where your HMI traffic is on a separate bus, the Siemens runs just fine without any extra gear. The eligibility gate here is motion tolerance ≤ 5 ms → Omron is immediately eligible; Siemens requires an infrastructure audit.
The Omron NX1P2-9024DT offers 1.5 MB program memory + 2 MB variable memory. The Siemens S7-1200 1214C has 100 KB integrated work memory. A naive reading says the Omron has ~30x more memory — but that's not the eligibility gate. The gate is how the memory is partitioned. The Omron's program memory includes FB, FC, data blocks, and the Sysmac Studio project database; the 2 MB variable memory is for retain and CAM tables. The Siemens work memory stores the compiled code and data — but it also uses a load memory (onboard flash) for the project, and you can expand via SD card. The real constraint: the Omron's 1.5 MB program memory is enough for a complex motion program with 8 axes of CAM tables and safety logic. The Siemens 100 KB work memory is enough for a mid-size machine but will hit a wall if you try to store large arrays of recipe data or complex motion profiles on the CPU. Worked consequence: If your machine requires 20+ canned motion profiles with tables, the Siemens forces you to either store data in an external HMI or use a memory expansion card — which adds latency and a failure point. The Omron holds it all in one project, no extra hardware. Reversal: For a simple bottle filler with 10 rungs of ladder and no recipe tables, the Siemens 100 KB is ample, and the Omron's larger memory just sits unused. The eligibility gate: if your program + data exceeds 80 KB, the Siemens needs workaround; if not, both are fine — but the datasheet only shows total bytes, not whether your application fits.
The Omron NX1P2 supports up to 8 PTP axes (4 on the -9024DT variant) with EtherCAT. The Siemens S7-1200 has integrated PTO (pulse-train output) for up to 4 axes on the CPU, and can control servo drives via PROFINET with a technology CPU or an external motion controller. The datasheet hides that the Omron's 8-axis support is a software license limit — you buy the hardware and unlock axes via Sysmac Studio activation. The Siemens PTO is hardware-tied: you get 4 axis channels physically on the CPU, and if you need a 5th axis, you must add a signal board or a separate motion module. Worked consequence: If your machine needs 5 simple stepper axes (e.g., a multi-axis pick-and-place), the Siemens forces a hardware add-on, adding ~$150–300 and a DIN rail slot. The Omron handles it with a software key — cheaper and faster to integrate. Reversal: For 1–4 axes, the Siemens is actually simpler (no license, no activation), and the PTO outputs are directly controllable from the CPU cycle without EtherCAT overhead. Eligibility gate: if axis count ≤ 4 and you don't need CAM tables, Siemens is eligible out of the box; if axis count = 5–8 or you need electronic camming, Omron is eligible without hardware expansion.
The Omron NX1P2 includes a built-in OPC UA server. The Siemens S7-1200 does not have an integrated OPC UA server on the standard 1214C — you need an external OPC gateway or a CP 1542-1. This is an eligibility gate for Industry 4.0 or MES connectivity. If your plant requires OPC UA for data collection (many automotive and pharma specs now mandate it), the Omron is eligible with zero extra hardware. The Siemens requires a ~$400 communication processor and configuration effort. Worked consequence: A machine builder who delivers to a Toyota tier-1 supplier will be rejected if the PLC cannot serve OPC UA directly. The Siemens datasheet doesn't show this gap in the standard I/O table. Reversal: If your plant uses PROFINET and S7 communication exclusively, the Siemens built-in PROFINET port is faster and more integrated than the Omron's EtherNet/IP port — and you'll never use OPC UA. Eligibility gate: if OPC UA is in the spec → Omron is eligible; Siemens requires add-on → cost and complexity increase.
| Dimension | Siemens S7-1200 (1214C) | Omron NX1P2-9024DT | Eligibility gate |
|---|---|---|---|
| Bit execution | ~85 ns | Not published; cycle ~2 ms | Both sufficient for logic speed |
| Program memory | 100 KB work | 1.5 MB program + 2 MB variable | Siemens hits wall at ~80 KB; Omron does not |
| Motion axes (integrated) | 4 PTO | 4 PTP (expandable to 8 via license) | ≤4 axes: Siemens eligible; >4 axes: Omron eligible |
| Network determinism | PROFINET (IRT with managed switch) | EtherCAT (native deterministic) | High-speed motion: Omron plug-and-play; Siemens needs network audit |
| OPC UA server | Built-in? No | Built-in | If OPC UA required: Omron eligible; Siemens needs add-on |
Let's look at a real failure pattern. A customer chose the Omron NX1P2 for a 6-axis labeling machine because of the motion spec. They didn't check the I/O expansion limitation: the NX1P2 supports up to 8 NX units, but the -9024DT has only 24 on-board I/O. The machine needed 48 I/O total — they hit the expansion limit and had to add a remote I/O station on EtherCAT, adding cost and a bus node they hadn't planned. The Siemens S7-1200 with signal modules could have expanded to 200+ I/O on the same backplane, and would have been a simpler fit. The datasheet hides that the Omron's expansion bus is limited to 8 units; the Siemens expansion bus supports more modules. The eligibility gate here: if I/O count > 48, the Siemens becomes more eligible even if the motion spec is weaker. This is the kind of constraint that doesn't show up in a "compare features" table.
Based on the four dimensions above, here's a rule you can apply at the spec review stage — no assumptions needed:
These three thresholds cover the hidden eligibility gates that the datasheet doesn't show. The cycle-time spec, memory size, and axis count are all real — but they only matter if your application crosses the gate. My advice: start with the thresholds, then look at the numbers. That's how you avoid buying a Ferrari for a gravel road.
Topology/standards per the cited standards; all product ratings are manufacturer-stated values from the cited datasheets, current to 2026-06; derived/illustrative figures are labelled as such. This is not an independent head-to-head test. Siemens is a brand affiliated with this site; competitor names are used for identification only.