← Back to the chapter · Next detail →
Technical detail · The Industrial Protocol Landscape
Engineer and test the deterministic path
Frame scheduling sets when a device or switch may send each network frame. Traffic classes group messages for different treatment, such as reserving a timed path for control data. A Time-Sensitive Networking (TSN) profile specifies which timing and traffic rules devices must support for a particular use. Configure the same rules across the path and test them under the expected load.
Industrial determinism is not created by writing “real-time” in a protocol description. It comes from the full path: controller cycle, device role, frame scheduling, switch behavior, clock synchronization, topology, load, diagnostics, and replacement procedure. A protocol family can provide mechanisms, but the plant design has to prove the behavior.
TSN is a good example. It is a set of Ethernet timing, scheduling, and reliability capabilities, not a single drop-in field protocol. It can help selected traffic meet bounded latency when endpoints, switches, clocks, traffic classes, schedules, and profiles are engineered together. Without that engineering record, the label does not prove the machine behavior.
A useful acceptance trace records the behavior before and after load is added. Suppose a controller expects fresh I/O every 10 ms and the release budget reserves 2 ms for network transport. The test should capture normal cyclic traffic, add the planned historian or gateway traffic, force a device replacement or link change, and verify that controller timeouts and diagnostics still put the process into a known state. That evidence is stronger than quoting a protocol family because it ties the network, devices, tooling, and operator response to the actual control consequence.