TSN time-aware shaper narrated tour

TSN time-aware shaper narrated tour

animation
iiot
industrial
protocols

TSN time-aware shaper narrated tour

Narrated audio tour. The full transcript is below.

Play the tour to open the workbench. Pause, replay a beat, or read the full transcript below. Some situations cannot be shown by this teaching model; those beats keep the existing frame and provide captions only.

Full transcript — TSN time-aware shaper (8 beats)

B1 — Motion cell
You are the engineer responsible for a group of machines whose movements must stay coordinated. This group is called a motion cell. Its control commands share an industrial network with video and routine data.

Model caption: You manage a motion cell’s timing. Control, video, and routine data share scheduled transmission opportunities; late control messages put timing at risk.

B2 — Gate control list
A time-aware shaper gives each traffic queue scheduled turns to send. A queue holds messages waiting to leave through a network connection called an outgoing port. A gate allows or blocks transmission from a queue. A repeating gate control list sets when each gate opens and how long it stays open.

Model caption: A time-aware shaper schedules queue gates at an outgoing port. Deterministic timing bounds delivery time, including understood arrival variation and timeout behavior.

B3 — Guard band
Participating devices need aligned clocks and a shared schedule start time. Before control traffic gets its turn, a guard band blocks lower-priority transmissions. It prevents a frame, or unit of network data, from starting so late it overlaps the protected control window. The guard band protects time by leaving it unavailable for data.

Model caption: Aligned clocks share a schedule start. Guard time blocks lower-priority transmissions before control, preventing a late-starting frame from overlapping the protected window.

B4 — Control window
Use the model’s Motion Cell example. The cycle lasts one thousand microseconds. Control gets thirty percent, and the guard band gets eight percent. Clock error is one microsecond. Eight percent of one thousand gives eighty microseconds of guard time. Thirty percent gives three hundred microseconds for control frames to transmit.

Model caption: Motion Cell: 1000 us cycle; 1 us clock error. Guard = round(1000 × 8 / 100) = 80 us. Control = round(1000 × 30 / 100) = 300 us.

B5 — Remaining windows
The model assigns video twenty-two percent, or two hundred twenty microseconds. For best effort, start with one hundred percent. Reserve eight percent for guard time and thirty percent for control. Reserve another twenty-two percent for video. Forty percent remains: four hundred microseconds for non-critical data. The model never lets the remaining share fall below zero. The windows and guard time fill the thousand-microsecond cycle.

Model caption: Video = 22% = 220 us. Best effort = max(0, 100 − 8 − 30 − 22) = 40%; round(1000 × 40 / 100) = 400 us. Guard 80 + control 300 + video 220 + best effort 400 = 1000 us.

B6 — Service order
After the guard band, the control gate opens while the other data gates stay closed. Video follows, then best effort uses its turn. The schedule repeats when the cycle ends. Admission means checking whether added traffic fits the reserved time budget; control frames must fit their window at every relevant outgoing port.

Model caption: Control transmits first after guard time, then video, then best effort; the gate list repeats. Admission checks whether added traffic fits reserved time. Control frames must fit at every relevant outgoing port.

B7 — Clock drift risk
A common mistake is to assume unchanged window lengths mean unchanged timing risk, but control timing depends on devices keeping their schedules aligned. Keep the same windows but increase clock error to forty microseconds, as in the Clock Drift example. The model reports high risk: clock disagreement consumes timing margin and can shift gate openings across devices. Local window arithmetic cannot establish timing along the whole path.

Model caption: Same 80/300/220/400 us allocation, but clock error rises from 1 to 40 us. The model reports High risk because clock disagreement consumes margin and can shift openings across devices. A local gate list cannot establish whole-path timing.

B8 — Deadline takeaway
A dependable control deadline rests on shared time, traffic fitting its windows, and measured timing from tests.

Model caption: A dependable control deadline rests on shared time, traffic that fits its windows, and tested timing evidence. Teaching values illustrate the schedule; this asset supplies no measured proof for an actual motion cell.

Back to the chapter