NB-IoT State-Chain Dry Run
NB-IoT State-Chain Dry Run
animation
nb-iot
cellular-iot
Simulation-First Dry Run
Before a real modem lab, run a small state-machine dry run that names the evidence each state should produce. The dry run is not a substitute for RF testing; it prevents the lab from hiding missing assumptions.
Step 3: Replay the state chain locally before attaching
- In a local Python terminal, advance through the state names in the trace below and mark the expected evidence at each transition.
- This run printed
BOOT,CELL_SEARCH,ATTACH_REQUEST,REGISTERED,UPLINK_REPORT,NETWORK_GRANTED_TIMER_CHECK,PSM_SLEEP_OR_EDRX_PAGING, andWAKE_AND_REPEAT. - Mark
REGISTEREDas conditional on a real modem response, andNETWORK_GRANTED_TIMER_CHECKas conditional on grant readback, not a requested value. - Add placeholders for whole-board current and a cloud receipt with the same payload ID; leave them explicitly unverified until the hardware run.
- The local output is a state-model replay only. It did not perform radio attach, grant negotiation, sleep-current measurement, or cloud delivery.
BOOT
CELL_SEARCH
ATTACH_REQUEST
REGISTERED
ACTIVE_WINDOW_OR_SHORT_ACK
UPLINK_REPORT
NETWORK_GRANTED_TIMER_CHECK
PSM_SLEEP_OR_EDRX_PAGING
WAKE_AND_REPEAT
Check the trace before changing parameters:
First, did the device attach once, repeatedly, or not at all? Then, was the requested PSM or eDRX behavior granted by the network? Next, did weak coverage add repetitions, retries, or longer attach time? After that, did the current trace show the whole board returning to the expected low-power state? Finally, did cloud receipt match the payload ID and modem log timestamp?