Animated Beacon Cycle
The PAN coordinator sends a beacon that defines the superframe timing and wakes synchronized devices.
Explore beacon interval, active superframe timing, CAP, CFP, GTS, and duty-cycle trade-offs
Explore how a PAN coordinator uses beacons to synchronize sleepy devices, divide time into a 16-slot active superframe, reserve optional GTS slots, and trade latency against power saving.
The coordinator broadcasts a beacon every beacon interval so devices know when the next active period begins.
Beacon Order stretches the time between beacons. Larger BO usually means more sleep time.
Superframe Order sets the active duration. SO must not exceed BO in normal beacon-enabled operation.
CAP is contention-based. CFP/GTS is scheduled. Inactive time is when devices can sleep.
Coordinator announces timing.
Devices align to the slot clock.
Devices contend with slotted CSMA-CA.
Reserved GTS slots transmit.
Inactive period saves energy.
Cycle repeats at the next beacon.
The PAN coordinator sends a beacon that defines the superframe timing and wakes synchronized devices.
Change BO and SO first. Then reserve GTS slots or test a traffic scenario to see how synchronization, power, latency, and CAP capacity move together.
Devices can wake near the next beacon, listen during needed slots, then sleep during the inactive period.
Enough active slots remain for association, commands, and slotted CSMA-CA traffic.
Battery life grows when BO is larger than SO, but latency and missed-beacon recovery can become harder.
Calculating...
BI is the time between coordinator beacons. It is controlled by Beacon Order, BO.
SD is the active superframe duration. It is controlled by Superframe Order, SO.
In normal beacon-enabled operation, 0 <= SO <= BO <= 14. SO larger than BO is invalid.
The active superframe is divided into 16 equal slots. Slot duration grows as SO increases.
If BO is greater than SO, the remaining beacon interval is inactive and devices may sleep.
When SO equals BO, the active period fills the beacon interval and the duty cycle is 100%.
The Contention Access Period uses slotted CSMA-CA, so devices contend at aligned backoff boundaries.
The Contention-Free Period contains reserved Guaranteed Time Slots near the end of the active superframe.
802.15.4 allows up to seven GTS allocations in a superframe, subject to remaining CAP space.
The CAP must remain long enough for management traffic. This page highlights a 440-symbol teaching threshold.
Higher traffic load increases contention in CAP. GTS can help time-critical devices avoid that contention.
This page treats each GTS allocation as one slot for clarity. Real allocations can vary by descriptor and implementation.
Increase BO relative to SO to create a longer inactive period, then verify that latency remains acceptable.
Lower BO shortens the time to the next beacon, but devices wake more often and consume more energy.
Use GTS when a device needs deterministic access inside the superframe and the coordinator can reserve slots.
Long beacon intervals save energy but require good clock tolerance and careful missed-beacon recovery.
Unslotted CSMA-CA can be simpler, but power saving and deterministic access move to higher layers.
Battery estimates depend on radio current, sleep current, wake time, beacon tracking, retries, and application behavior.