Vendor field notes
The Year 2038 Problem and Specific Industrial/Embedded Vendors.
Y2038 risk does not distribute evenly across brands. It concentrates by architecture: how long a controller family has been in production, whether the vendor has published a validated path past 2038, and what the engineering environment lets you see. These are our working notes on the platforms we audit most.
- Tier 1 · full-stack providers
- Tier 2 · regional & vertical specialists
- Edge · gateways & embedded controllers
- Software · SCADA & runtime layers
How we audit a vendor platform
Same method on every logo. The deliverable is a per-family register of what runs, what has a validated path past the overflow, and what needs an engineering decision before the deadline makes it for you.
We start at family level, an approach more discrete than embedded controller brand level. Each controller line gets mapped against its production status, current, legacy, discontinued, and the vendor's published Y2038 position. A current-generation platform with vendor documentation is a firmware-revision problem; a discontinued line is a capital-planning and field-technician replacement labor scheduling problem, and the two answers arrive in different budget formats.
We read the clock off the device. Our audit process does not rely on possibly obsolete vendor documentation. The vendor bulletin describes the latest release; your floor runs the revision installed during commissioning, possibly three firmware generations back. For each family we record the actual firmware version, the engineering-tool version that manages it, and the time data types compiled into the running application.
We trace the protocol layer. Modbus, DNP3 and IEC 60870-5 carry time fields in older implementations, and each vendor's fieldbus: PROFINET, EtherNet/IP, CC-Link, EtherCAT, POWERLINK, Sercos III, all distribute clocks in their own way. That is where a "time fault" first surfaces on the plant network.
We audit the supply chain inside the box. Vendors assemble timekeeping from third-party libraries; if a library is unpatched, every downstream product inherits the flaw, and some discontinued models ship no official patch at all. When the OEM answer is silence, the audit output is a replacement decision, not a ticket.
We validate with the clock, not around it. Every platform exits the engagement with time-warp evidence: a replica of the real configuration rolled past 03:14:07 UTC on 19 January 2038, with the results documented in the form the IEC 62443 and ISO 26262 auditors will eventually ask for.
The shape of the market
Industrial control is dominated by four full-solution houses: Siemens, Rockwell, Schneider Electric, and ABB, the vendors that will sell you the complete chain from sensor to historian. That convenience is exactly the Y2038 concern: when one logo spans the PLC, the SCADA, and the database write, a single family's decision to standardize on 32-bit time propagates through your whole audit scope at once.
The tier-2 field: Omron, Mitsubishi, Beckhoff, B&R, Phoenix Contact, Bosch Rexroth, Panasonic, Keyence, WAGO, Hitachi all compete by being better in a vertical: packaging, semiconductors, machine control, water, infrastructure. Their clocks concentrate where the machines are fastest: motion services, vision triggering, and the new Linux-based runtimes that bolt open ecosystems onto closed controllers.
And most real fleets are multi-vendor. Which makes the integration points as OPC servers, protocol gateways, historian writers, the first place where 32-bit and 64-bit time meet. Those handoffs are where we start looking, and where the IT/OT convergence of the last five years quietly installed a thousand new timestamp paths that never existed in the firmware a decade ago.
| Vendor | HQ | Primary strengths | Key PLC family | SCADA platform | Key protocol |
|---|---|---|---|---|---|
| Siemens | Germany | Full-stack, DCS, process | SIMATIC S7-1500 | WinCC / PCS 7 | PROFINET |
| Rockwell | USA | Motion, discrete, North American market | ControlLogix / CompactLogix | FactoryTalk View | EtherNet/IP |
| Schneider | France | Process, energy, software | Modicon M580 | Aveva System Platform | Modbus TCP |
| ABB | Switzerland | Process, power, robotics | AC500 / AC 800M | System 800xA | PROFIBUS, Modbus |
| Omron | Japan | Packaging, motion, vision | Sysmac NX/NJ | Sysmac Studio | EtherCAT |
| Mitsubishi | Japan | Asian market, CNC, small machines | MELSEC iQ-R / FX5 | GOT / Gen64 | CC-Link, SSCNET |
| Beckhoff | Germany | PC-based control, open, motion | TwinCAT (SW) / CX (HW) | TwinCAT HMI | EtherCAT |
| B&R (ABB) | Austria | Premium machine control | X20 System | mapp View | POWERLINK |
| Phoenix Contact | Germany | Openness, connectivity | PLCnext (AXC F 2152) | Visu+ | OPC UA, PROFINET |
| WAGO | Germany | Modular I/O, building | PFC200 | e!COCKPIT | OPC UA, Modbus |
| Inductive Automation | USA | SCADA only | — | Ignition | OPC UA, MQTT |
Choose your stack
No single vendor is "best", the right choice depends on industry, region, legacy integration, and performance needs. For our purposes the question is narrower: what does the stack do with time, and can you prove it? Each field note below ends with exactly that.
-
T1
Siemens
The default supplier across Europe, Asia, and the Middle East. The S7-1500 has a published Y2038 firmware bulletin; the S7-300/400 estate still in service does not have a bulletin at all.
-
T1
Rockwell Automation
North America's standard. ControlLogix is a revision problem; the PLC-5 and SLC 500 fleets — still in thousands of installations — are a capital problem.
-
T1
Schneider Electric
Process, energy, and buildings — plus the Modbus protocol itself, and the Aveva/Wonderware SCADA layer that sits over half the multi-vendor estates we audit.
-
T1
ABB
Power and process, from 800xA to Symphony Plus — the two industries where time synchronization is most critical. Includes B&R, now part of ABB.
-
T2
Tier 2 & specialists
Omron, Mitsubishi, Beckhoff, B&R, Phoenix Contact, Bosch Rexroth, Panasonic, Keyence, WAGO, Hitachi — where the ceiling lives in motion control and open runtimes.
Edge & software layer
The gateway rack
Compact, often headless devices: Advantech and Moxa's UNO and UC series, Eurotech's ReliaGATE line, National Instruments' CompactRIO (now inside Emerson), and the industrialized Raspberry Pi and Arduino builds from Industrial Shields and KUNBUS's Revolution Pi. They run current Linux or Windows IoT, which supports time64 so the 2038 exposure in this layer usually hides in 32-bit userland tooling, the protocol stacks they bridge, and the cloud ingestion behind them. A gateway that stamps "now" with a 32-bit helper function is a rollover you built yourself.
The SCADA layer above the PLC
Most multi-vendor fleets are supervised by software not made by the hardware vendors: Aveva's Wonderware lineage (InTouch, System Platform) and Citect, GE Digital's Proficy, and Inductive Automation's Ignition, whose web-based, per-server licensing made it the disruptor of the last decade. PTC's Kepware KEPServerEX and Iconics/ASEM's Genesis64 sit underneath as the connectivity and integration rails. Each has its own time path — and each inherits every controller's.
Shifts that change the audit
-
IT/OT convergence
Controllers now carry native MQTT, OPC UA, and REST interfaces. Every new interface is a timestamp path, and new paths are rarely validated against the overflow before deployment.
-
Software-defined control
Beckhoff's TwinCAT and Schneider's EcoStruxure Automation Expert move "the PLC" onto industrial PCs and cloud images. The clock becomes the operating system's problem, which makes it fixable by patching, and breakable by neglect, at software speed.
-
Openness & certificates
Linux-based controllers (PLCnext, ctrlX) and mandatory secure boot and certificate management mean time now decides trust: a certificate-validation fault at rollover is a security fault. These are the same integer.
-
Cloud at the edge
Controllers acting as edge gateways stream to AWS, Azure, and Google Cloud. The backend ingestion may timestamp in its own arithmetic, and older 32-bit components are still being found in cloud paths.
-
IEC 61499
"Plug-and-produce" interoperability between vendors means one platform's time semantics will drive another's. Interoperability tests that never cross 2038 are incomplete tests.
Your fleet is a list of vendors we haven't audited yet.
Big-4 stack, tier-2 mix, or a decade of acquisitions in one control room, same method, and you get the register in writing.