← Back to the chapter · Next detail →
Technical detail · IoT Quick Reference: Terms and Hardware
Specifications leave implementation gaps
Under the hood, many appendix facts come from standards or datasheets that deliberately stop at an interface boundary. IEEE 802.11 and IEEE 802.15.4 define radio and MAC behavior, but they do not decide antenna placement, enclosure losses, channel congestion, power policy, or application recovery. IETF RFCs such as RFC 7252 for CoAP, RFC 6550 for RPL, RFC 4944 and RFC 6282 for 6LoWPAN define protocol mechanisms, but a product still chooses timers, buffer sizes, routing policy, security credentials, and observability.
Datasheets draw similar boundaries. A microcontroller technical reference manual can describe ADC resolution, touch channels, UARTs, SPI controllers, I2C controllers, boot pins, and absolute maximum ratings. It cannot prove that a particular dev board exposes the pin safely, that a sensor cable has enough pull-up strength, that a relay module will not drag a boot strap pin, or that Wi-Fi activity will not disturb an analog measurement. A sensor datasheet may quote accuracy under controlled calibration conditions while your enclosure creates heat, dust, condensation, vibration, or airflow constraints.
Formula references also leave gaps. Free-space path loss assumes a simplified propagation model; indoor multipath, body absorption, metal cabinets, antenna orientation, and duty-cycle restrictions change the result. Ohm’s law and voltage dividers are exact circuit relationships, but resistor tolerance, ADC input impedance, noise, leakage, and temperature drift determine whether the measurement is usable. Battery-life math is arithmetic; chemistry, temperature, peak current, regulator efficiency, self-discharge, and aging determine whether the deployed device lasts.
The deep skill is to write down where the reference guarantee stops. A standard may guarantee packet structure but not deployment reliability. A datasheet may guarantee a limit under specified conditions but not your enclosure. A table may compare protocols but not choose one for your threat model or power budget. A formula may be correct while the inputs are fantasy. The appendix becomes dependable when every lookup carries that stop sign and a plan to close the gap with measurement, source revision, or a design review.