← Back to the chapter · Previous detail

Technical detail · IoT Quick Reference: Terms and Hardware

Conditions hidden by reference tables

Compact tables hide the conditions that make a value true. Wireless range depends on frequency, transmit power, antenna gain, receiver sensitivity, path loss, walls, interference, installation height, and duty-cycle limits. Sensor accuracy depends on calibration, temperature range, supply voltage, self-heating, drift, sampling interval, and mounting. Current draw depends on active state, sleep state, radio burst length, regulator quiescent current, and firmware timing.

Standards links and datasheets matter because they define exact behavior. MQTT QoS uses packet exchanges such as PUBLISH, PUBACK, PUBREC, PUBREL, and PUBCOMP. CoAP confirmable messages use ACK and retransmission timers over UDP. I2C depends on pull-up resistors, bus capacitance, address conflicts, and clock speed. ESP32 boot pins can affect startup if external circuitry pulls them to the wrong state.

Every compressed value also has a revision problem. Vendor breakout boards may differ from the underlying chip datasheet because of regulator choice, level shifting, pull-up values, address jumpers, or board-layout limits. Library defaults may differ from a protocol specification because a driver chooses a timeout, retry count, payload size, keep-alive interval, or power mode. Regional rules may change what looks like a simple wireless comparison: LoRaWAN channel plans, transmit power, dwell time, and duty-cycle behavior are not the same in every region.

For that reason, a final capstone evidence packet should cite the exact reference revision and the observed project value when a number matters. Good records distinguish IEEE or IETF normative behavior from a vendor application note, a forum example, a library default, and a measurement from the team’s device. They also preserve the packet trace, oscilloscope capture, current profile, field RSSI/SNR reading, or calculator inputs that made the reference fact safe to reuse. That separation lets a future maintainer update one layer without guessing which assumptions were inherited from a table.

StateWhat Must Stay Visible
SpecificationProtocol fields, timing, electrical limits, operating ranges, and conformance language.
ImplementationLibrary defaults, board revision, pin mapping, firmware configuration, and peripheral conflicts.
ValidationThe measured value, observed packet trace, or repeatable calculation that confirms the reference fact in the project context.

← Back to the chapter · Previous detail