Capstone & Resources · Study deck
IoT Quick Reference: Conversions and Standards
A design note now has the right component and protocol names, but its numbers still need consistent units and formulas.
Test Tessa is your guide for this deck.

After studying this chapter
Learning objectives
You will be able to:
- Explain: The board view reminds you that the selected address depends on how the breakout exposes and wires SDO; it cannot be inferred from the sensor name alone.
- Explain: Scenario: Your capstone project has a BME280 temperature, humidity, and pressure sensor plus a BH1750 light sensor, both using I2C.
- Explain: These tables do not make design decisions for you; they help you ask the right questions before consulting detailed chapters.
- Explain: The appendix does not teach when to apply these formulas; it assumes you have already learned the underlying principles.
Major section
Worked Example: Using the Appendix to Resolve a Missing I2C Device
Scenario: Your capstone project has a BME280 temperature, humidity, and pressure sensor plus a BH1750 light sensor, both using I2C.
- The board view reminds you that the selected address depends on how the breakout exposes and wires SDO; it cannot be inferred from the sensor name alone.

Major section
Worked Example: Using the Appendix to Resolve a Missing I2C Device (continued)
That observation sends the investigation back to wiring, power, bus scan, and board documentation before firmware is rewritten.
- Problem identified: The possible addresses are different, so an address conflict is unlikely.
- The next check is wiring and bus assignment.
- Quick lookups save time during prototyping when they are used with a clear diagnostic sequence.
Major section
Common Mistake: Using Appendix as Primary Learning Resource
The result is memorized definitions without enough context for design decisions.
- Key insight: The appendix is a map, not a guidebook.
- It helps you navigate once you know the terrain; it does not teach the underlying engineering by itself.
Major section
Concept Relationships
The appendix does not introduce new concepts; it consolidates them for quick reference.
- Understanding this mapping helps you find authoritative documentation.
- These tables do not make design decisions for you; they help you ask the right questions before consulting detailed chapters.
- The appendix does not teach when to apply these formulas; it assumes you have already learned the underlying principles.
Deck summary
Key takeaways
Scenario: Your capstone project has a BME280 temperature, humidity, and pressure sensor plus a BH1750 light sensor, both using I2C.
- That observation sends the investigation back to wiring, power, bus scan, and board documentation before firmware is rewritten.
- The result is memorized definitions without enough context for design decisions.
- The appendix does not introduce new concepts; it consolidates them for quick reference.
Retrieval practice
Recall check 1 of 4

Test Tessa says: answer from memory, then check your reasoning.
Q1Place each capstone activity where it lives so you can trace a project decision from scope to field evidence.
Show answer
Answer: A Place the four activities across intent, engineered proof, and field evidence so you can defend how a capstone decision reached its conclusion.
Q2Complete the IoT project configuration scaffold:
Show answer
Answer: A json.dumps() with indent=2 produces human-readable JSON. Nested dicts represent the hierarchical IoT project structure.
Retrieval practice
Recall check 2 of 4

Test Tessa says: answer from memory, then check your reasoning.
Q31. Which standards body is most directly associated with IEEE 802.11 (Wi-Fi) and IEEE 802.15.4?
Show answer
Answer: B IEEE publishes the 802 family of networking standards, including 802.11 (Wi-Fi) and 802.15.4 (LR-WPAN used by Zigbee/Thread).
Q42. RFC 7252 specifies which IoT application protocol?
Show answer
Answer: A RFC 7252 defines CoAP, a lightweight REST-like application protocol designed for constrained devices and networks.
Retrieval practice
Recall check 3 of 4

Test Tessa says: answer from memory, then check your reasoning.
Q53. If you need a quick comparison of wireless and application protocols while making design decisions, this appendix is best used as:
Show answer
Answer: D The appendix is meant to accelerate recall with tables, glossaries, and formulas; the main chapters provide deeper explanations and context.
Retrieval practice
Recall check 4 of 4

Test Tessa says: answer from memory, then check your reasoning.
Q64. RFCs for protocols like CoAP, RPL, and 6LoWPAN are published by:
Show answer
Answer: C The IETF publishes RFCs (Request for Comments) for many internet protocols, including key IoT-related specifications like CoAP and RPL.
Print reference
Answers 1 of 2
Answer key.
- A · Place the four activities across intent, engineered proof, and field evidence so you can defend how a capstone decision reached its conclusion.
- A · json.dumps() with indent=2 produces human-readable JSON. Nested dicts represent the hierarchical IoT project structure.
- B · IEEE publishes the 802 family of networking standards, including 802.11 (Wi-Fi) and 802.15.4 (LR-WPAN used by Zigbee/Thread).
- A · RFC 7252 defines CoAP, a lightweight REST-like application protocol designed for constrained devices and networks.
Print reference
Answers 2 of 2
Answer key.
- D · The appendix is meant to accelerate recall with tables, glossaries, and formulas; the main chapters provide deeper explanations and context.
- C · The IETF publishes RFCs (Request for Comments) for many internet protocols, including key IoT-related specifications like CoAP and RPL.