← Back to the chapter · Previous detail
Technical detail · Edge Acquisition: Control Paths and Bandwidth
Putting Numbers to It: window size and duty cycle
Sending ten seconds of the 18-byte/second stream gives 180 bytes per transmission, six transmissions/minute or 360/hour. Under the example’s assumed 0.6-second SF7 airtime, this is 216 seconds, or 3.6 minutes/hour: a 6% duty cycle, exceeding 1%.
Bundling 60 seconds instead gives 1,080 bytes per transmission. That exceeds the example’s approximate 222-byte single-frame payload allowance. Linear scaling gives about 3.6 seconds × 60 transmissions/hour, still 6%; rechunking the same bytes has not removed them.
Instead, compute the same nine-value, 18-byte summary over a 60-second window. One summary/minute reduces the values sent. Scaling the example’s airtime by payload size gives about 0.06 seconds/minute, or 0.1%. A 120-second window still sends 18 bytes, now 0.5 times/minute; the same estimate is about 0.05%, leaving more headroom for other traffic.
These airtimes are illustrative estimates, not validated radio budgets. Packet overhead prevents exact linear scaling from payload bytes, and SF7 alone does not establish capacity or payload limits. Check the deployed radio settings and regional limits before claiming compliance with a 1% duty-cycle constraint.