Duty Cycle Compliance Game
Duty Cycle Compliance Game
Navigate LPWAN Regulatory Requirements
Interactive game
LPWAN compliance
Duty Cycle Compliance Game
Explore LoRa PHY parameters against explicit scenario planning limits. This is not a LoRaWAN configuration validator.
10Scenarios
5Tuning levers
15 minEstimated time
TryTune all five controls, then Check once per scenario. Your submitted settings lock until Next Scenario. Reset is available on the results screen.
ObserveWatch packet airtime, hourly airtime and required rate. Check awards duty 10, packet ceiling 4, rate 4, margin 4 and target fit 8 points (30 total).
ExplainPayload, SF, bandwidth and coding rate determine packet airtime; cadence determines hourly use. TX power affects link budget, not packet duration. Fit points reward the stated scenario target, not a unique technical optimum.
LoRaWAN identity (pale only)Current selectionReference dataSuccessCautionError
Progress
Scenario 1 of 10
0Score
0/30Latest
0Compliant
Loading duty-cycle scenarios...
Technical boundaries. Generic LoRa PHY exploration: arbitrary SF/BW and CR 4/6–4/8 are not necessarily valid LoRaWAN settings (LoRaWAN LoRa uses CR 4/5 and regional data rates). Per-device planning budgets are 1% for EU868/AS923 fixtures, 2% plus a 400 ms packet ceiling for US915/AU915 fixtures; these are not universal regional laws. Airtime includes 13 bytes of LoRaWAN framing, no FOpts, explicit header, CRC and eight preamble symbols. It excludes retries, downlinks and contention. Link budget uses illustrative sensitivity with bandwidth correction; antennas, losses, fade margin and site coverage are unmodeled. Battery lifetime is unmodeled. These exercises do not replace current regulator, network-operator, device-class, channel-plan, listen-before-talk, or certification requirements.
Reference Material
Loading LPWAN compliance notes...