LoRaWAN classes narrated tour
LoRaWAN classes narrated tour
LoRaWAN classes narrated tour
Narrated audio tour. The full transcript is below.
Play the tour to open the simulator. Pause, replay a beat, or read the full transcript below.
Some beats explain situations this teaching model cannot show; those beats keep the existing frame and provide captions only.
Full transcript — LoRaWAN classes (8 beats)
B1 — Valve listening schedule
You are the operator responsible for a farm valve. It reports every hour, but a stop command may need to reach it within one minute. A command waiting at the network cannot help until the valve listens. How does its listening schedule affect that wait?
Model caption: You operate a farm valve: hourly reports, but a stop command may need to arrive within one minute. A queued command waits until the valve listens.
B2 — Uplink and downlink
LoRaWAN stands for long range wide area network, a low power system for small device messages. A report sent by the device is an uplink. A command returning to the device is a downlink. The device class determines when the receiver listens for that returning message.
Model caption: LoRaWAN is a low power wide area network system. Uplink: device report. Downlink: returning command. Class determines when the device listens.
B3 — Three listening classes
Class A opens two short receive windows after an uplink, then sleeps. Class B adds scheduled listening opportunities called ping slots. Beacons synchronize their timing. Class C keeps listening most of the time except while transmitting. More listening gives commands more chances to reach the device, at an energy cost.
Model caption: A: two post-uplink windows, then sleep. B: additional beacon-synchronized ping slots. C: mostly listening except during transmission, with much higher listening energy.
B4 — Class A wait
For your valve, use a shorter model schedule to compare the classes. Keep uplinks ninety seconds apart and queue the command at thirty seven seconds. In Class A, the next uplink is at ninety seconds; its first receive window is at ninety one. Ninety one minus thirty seven gives fifty four seconds of waiting for a receive opportunity.
Model caption: Model schedule: uplinks at 0 and 90 s; command at 37 s. Next receive window: 91 s. Wait: 91 − 37 = 54 s.
B5 — Class B wait
Keep the same command time and uplink period for Class B. With timing synchronized by beacons and ping slots sixteen seconds apart, the command arrives after the slot at thirty two seconds. The next slot is at forty eight. Forty eight minus thirty seven gives eleven seconds of waiting.
Model caption: Locked beacon timing; ping spacing 16 s. Next opportunity: 48 s. Wait: 48 − 37 = 11 s.
B6 — Class C availability
Now keep those times and choose Class C. The model gives less than one second of waiting because the receiver is already available. That availability carries a much higher listening energy cost. These calculated opportunities describe the schedule; actual delivery can take longer.
Model caption: C is already listening in this model: next opportunity 37 s, display <1 s wait; highest receive duty. These are schedule opportunities, not guaranteed delivery times.
B7 — Scheduled is not continuous
The misconception is that scheduled Class B listening means a command can arrive at any time. It fails because scheduled slots leave gaps. Your command at thirty seven seconds still waits eleven seconds for the slot at forty eight. Scheduled listening is not continuous listening.
Model caption: Scheduled does not mean continuous: a command at 37 s waits for the 48 s slot, a gap of 11 s.
B8 — Choose a schedule
Choose a listening schedule that meets the command's waiting budget with energy the device can afford.
Model caption: Choose a listening schedule that meets the command's waiting budget with energy the device can afford.
Command timing field check
Send one command after an uplink, during a planned slot, and between planned listens. Record request time, receive window, result time, missed case, energy source, and recovery after a restart. Compare the evidence with the product promise.
Valve prediction and stopped-uplink check
Predict whether Class C guarantees that a valve closes immediately. It does not. A receive opportunity is only one part of the path; the downlink can fail, and the actuator must still check and carry out the command. Next, stop the periodic uplinks from the Class A valve. Its next downlink opportunity may now be unbounded, so the operator interface must stop presenting the old timing estimate as assured.