Explore native AI execution for industrial systems.

An integration preview: VEIZIK’s runtime talking to an S7-1500-style controller over OPC UA and S7comm, validated so far on virtual and bench setups. It is a basis for a joint evaluation, not a certified or production-ready industrial product.

Start a joint evaluation See the technology →

No PLC certification, functional-safety claim or production industrial deployment is implied by this page.

AI controllerVEIZIK runtime on an industrial PC — reads status, proposes trims

TransportOPC UA or S7comm over TCP/IP — confirmed against an emulator

PLC (virtual S7-1500)Control program and command/status data blocks — bench scope only

Real CPU, drives, plantNot yet validated

Connection targets

What it connects to, and how far each link is validated.

Each target carries its own state. “Confirmed on emulator” means a real protocol stack against a simulated controller; it is not a result on Siemens hardware.

OPC UA

Confirmed on emulator

What is confirmed: A client built on the open62541 stack exchanges a command block and a status block with a virtual S7-1500 over real OPC UA, including node naming, namespace resolution by URI and reconnect after link loss.
Not yet confirmed: The same exchange against a real S7-1500 OPC UA server, its security policies and certificates.

S7comm

Confirmed on emulator

What is confirmed: A client built on the snap7 stack reads and writes the same two data blocks against the virtual S7-1500, with data-block offsets and byte order checked.
Not yet confirmed: Behaviour against a real CPU, including its communication load.

Siemens PLCSIM Advanced

Bench captures, not published

What exists: Bench captures of a virtual S7-1500 running under Siemens’ own simulation, used to compare the emulator’s scan behaviour. They were taken on a Windows host with a virtual clock.
Not claimed: No result from this comparison is published on this page, and it says nothing about real-time behaviour.

Real S7-1500, PROFINET IO, drives

Not yet validated

Status: Not run. No physical CPU, no isochronous PROFINET IO exchange and no drive-level test is part of the current evidence.

Virtual and bench scope

Four validation levels, and where this preview stops.

The honest boundary of the work, stated level by level.

Level 1 — in-process model. Control, fault and repair logic run against a modelled plant in one process. It checks logic and the byte-exact command/status encoding; it involves no network and no Siemens behaviour.
Level 2 — network emulator. Real OPC UA and S7comm stacks against our own virtual S7-1500 in a separate process, with injected link faults (stalled link, connection reset, added latency). Done and measured on a general-purpose host. The emulator and the client were written from the same interface header, so a shared misreading of real S7-1500 behaviour would pass both.
Level 3 — PLCSIM Advanced. A Siemens-compiled program on a virtual S7-1500. Bench captures exist; it is a simulation on a non-real-time host and is not presented as a finished validation.
Level 4 — real S7-1500 and drives. A runbook only. Not yet run.

A Level 1 or Level 2 number is never quoted as a Siemens result, and this page quotes no figure at any level.

I/O and cycle requirements

Define the cycle before choosing the transport.

The transport, not the model, sets the fastest exchange that is realistic.

Exchange contract

The AI side reads a status block and writes a command block in the controller. The controller program stays in charge of the process; the AI side only takes the authority it is handed back and gives it up when its own checks fail.

What OPC UA and S7comm can carry

Both run through the CPU’s communication stack and are not deterministic. We treat them as supervisory or slower exchange. Any watchdog and hand-back timing has to be re-derived from the measured transport jitter of your controller and firmware, not inherited from a fast loop.

What a fast cyclic loop would need

A millisecond-class cyclic exchange needs PROFINET IO. PROFINET IO is not implemented in this preview. Your cycle time, I/O list and the role you want the AI to play are the first things to settle in an evaluation.

Timing figures for your configuration

Not measured for this configuration. Latency against a real S7-1500 over OPC UA, S7comm or PROFINET has not been captured, so none is shown.

Current validation

Confirmed and not-yet-complete, side by side.

This preview should be read as the left column only; the right column is open work.

Validated so far

Command and status data blocks exchanged over real OPC UA and S7comm stacks against a virtual S7-1500
Fault handling under injected link loss, reset and latency, on the emulator
Fallback and hand-back of control between the AI side and the PLC program, on the emulator

Bench scope

Explicitly not yet complete

Any test on a physical S7-1500, SINAMICS drives or a real plant
PROFINET IO exchange
PLC certification of any kind
Functional-safety validation; safety functions remain the controller’s and your safety design’s job
Production industrial deployment
Speed claims for inspection or vision workloads on edge GPUs

Not validated

Related research tooling, such as LimAxiom execution-path prediction, is in development and not released. Nothing on this page depends on it.

Evaluate it against your controller.

Tell us the controller family, firmware, cycle time and the role you want the AI to play. We will say which levels above apply and what has to be validated first. We run technical demonstrations, not production deployments.

Start a joint evaluation