← Back to the chapter · Next detail →

Technical detail · Agile and Risk Management

Locate faults across IoT boundaries

6.3.2 IoT Agile Fails at Boundaries

BLE uses the Generic Attribute Profile (GATT) to organize data and actions between devices. LoRaWAN adaptive data rate (ADR) changes radio settings as link conditions allow. Both depend on conditions across device and network boundaries. The hidden cost in IoT planning is boundary mismatch. Firmware may pass a unit test but miss an MQTT retransmission edge case. A BLE GATT workflow may work in a demo but fail when connection intervals, phone background limits, or pairing recovery are included. A LoRaWAN prototype may pass uplink tests but run into ADR behavior, downlink scarcity, regional duty-cycle limits, or gateway backhaul outages.

A brownout is a drop in supply voltage that can disrupt the device. Heap use is the amount of working memory allocated while code runs. OTA slot health tells us whether the stored update image can boot or roll back. FreeRTOS and Zephyr can schedule tasks, which are separate units of firmware work that share processor time. I2C and SPI are links between chips, while UART is a serial link often used for logs. Capture their errors and timing to locate a fault across the board. A CoAP confirmable message requests an acknowledgement and may be sent again if none arrives. LoRaWAN airtime is the time a radio transmission occupies the channel; long airtime can limit how often a device sends. Repeatedly erasing and rewriting memory gradually reduces how many reliable writes it can handle; this is called flash wear. Agile controls must therefore expose state across layers. Firmware state includes watchdog resets, brownout handling, heap use, flash wear, and OTA slot health. Network state includes join success, retry counts, queue depth, RSSI/SNR, TLS session failures, and broker acknowledgements. Service state includes schema version, alert latency, retention rule, dashboard freshness, permission model, and incident handoff.

At each boundary, name the expected input and output before testing. Give the team a shared clock or another way to link events across logs. If the records disagree, follow the first unexpected change back to its owner and design a focused test. This method helps the review assign a cause instead of treating the last visible symptom as the fault.

← Back to the chapter · Next detail →