networks//network theory//determinism

A communication is deterministic when a message always arrives within a bounded time, so its timing is **predictable** and not merely fast. If a response usually takes 1 ms but occasionally takes 300 ms, it can be useless for a control loop even though its average looks excellent.

A communication is deterministic when a message always arrives within a bounded time, so its timing is predictable and not merely fast. If a response usually takes 1 ms but occasionally takes 300 ms, it can be useless for a control loop even though its average looks excellent.

The real-time recipe is low latency plus low jitter plus bounded worst case. Latency is how long a packet takes; jitter is how much that time varies; the bound is what a controller can actually plan around. Office networks and the public Internet optimize throughput and cost and give no bound at all (Latency, Throughput).

It is the first criterion when choosing a bus, ahead of speed, distance and device count (serial bus). Buses reach it by different routes: CAN bounds the wait of its highest-priority frames through arbitration, EtherCAT fixes a cycle in which every device is served, and an SPI link owned by one processor is deterministic by construction.

No single component confers it. An industrial switch, a real-time protocol and a fast PLC still give no bound if a camera floods the same segment or a misconfigured priority puts video ahead of I/O: determinism is a property of the whole network as configured and loaded, verified by measuring the worst case.

Industrial networks are built around this property: the PLC scan cycle is a bounded loop, industrial Ethernet variants add scheduling and synchronization to ordinary Ethernet, and an industrial switch is chosen for recovery time, not for port count.

Radio has none of it: variable latency and losses in bursts are its normal state, which is why fast loops stay on board and only setpoints and telemetry travel over a radio link.

The demand grows with the task: supervision tolerates seconds, a machine interlock needs milliseconds, coordinated motion control needs synchronized microseconds. Determinism is one of the three reasons a REST API is the wrong tool below the control layer (fault semantics).