Prototyping · Study deck

Hardware Components: Selection Evidence

Choose prototype components by proving their measurement, interface, power, and environmental fit on the bench.

Voltage Vera is your guide for this deck.

components
Component Selection Evidence cover: Vera comparing component cards against requirements and test evidence.
iotclass.org

After studying this chapter

Learning objectives

Component acceptance needs evidence from the actual assembled prototype.

  • Sensor acceptance must match the measurement task.Range, environment, interface, power, and calibration evidence determine whether the reading can support the prototype’s intended decision.
  • Loads and radios need startup and failure tests.A pump startup, SD-card write, or radio burst can expose power-path limits that a successful demonstration misses.
  • The build record must identify the complete tested configuration.Part, board, firmware, supply, connector, and enclosure versions keep the assembled prototype reviewable as one unit.
  • Acceptance needs evidence another person can repeat.Raw readings, wiring, supply traces, temperature, fault conditions, and results must support the decision to use the component.

I am reviewing the greenhouse logger’s sensors, radio, storage, and pump. I need evidence from their actual wiring and supply before accepting the component list.

iotclass.org

Major section

Start With the Story

A familiar component still carries electrical and operating assumptions that need testing.

  • A shopping list leaves operating assumptions unproven.Voltage, timing, current, calibration, protection, and failure state need measurements before the component becomes part of the architecture.
  • A short-lead success can fail in the real installation.The sensor may behave differently beside a motor, with a longer harness, or inside the intended enclosure.
  • The component’s limits must fit the prototype decision.Its interface, power path, and operating boundaries need evidence for the specific question the build is meant to answer.
  • A bench record must precede architectural dependence.The team needs a repeatable reason for accepting the part before full-system integration hides its individual assumptions.

I am moving a sensor from its short bench lead into an enclosure beside a motor. I check what changed in the interface and supply before accepting the familiar part.

iotclass.org

Major section

Overview: Components Carry Assumptions

The route connects a need to an accepted component; start at Need, then inspect Interface.

  • The Need field defines the required physical task.The route begins with the measurement, output action, communication path, or power condition the prototype must support.
  • The candidate must pass interface and power checks.Voltage, current, pins, timing, and supply behavior need evidence from the actual assembled build.
  • Bench proof must turn assumptions into measured evidence.Supply, cable, enclosure, and neighboring-load tests show whether the component fits this prototype’s boundary conditions.
  • The final record must justify this particular selection.The decision connects requirement, candidate, operating conditions, and bench result before the part joins the architecture.
Component selection should move from requirement to compatibility, bench proof, and a reusable record before the part becomes part of the architecture.
Component selection should move from requirement to compatibility, bench proof, and a reusable record before the part becomes part of the architecture.
iotclass.org

Major section

Accept Parts With Bench Evidence

Add one neighboring boundary at a time so failures have a traceable cause.

  • A standalone sensor test needs a known supply.A current-limited bench supply or known-good rail isolates initial electrical and communication checks from the rest of the prototype.
  • Communication and raw readings must work before integration.The acceptance sequence confirms the address and a responsive reading before adding cable length, enclosure position, and neighboring devices.
  • The load must be checked before controller connection.Startup or stall current, driver rating, and rail movement need measurement before the actuator path depends on a microcontroller command.
  • Radio acceptance must cover provisioning and reconnect behavior.Join time, antenna placement, transmit current, and recovery after access-point loss provide evidence beyond a successful library example.

I am accepting the greenhouse logger one boundary at a time. I first prove the sensor alone, then add the real harness and the neighboring loads.

iotclass.org

Activity 1 · Predict

✎ Add the real harness

I want you to isolate the change before you blame the sensor.

A digital sensor works on a short bench lead but develops errors with the real harness. List likely interface causes and sketch an acceptance sequence that changes one boundary at a time.

3 minutes · Pen and paper · Answer: Activity 1

Your answer
iotclass.org

Major section

Modules Hide Circuit Choices

The charger photo exposes support circuitry; start at the Micro-USB socket and follow the marked pads.

  • The Micro-USB socket is part of the module’s support circuit.The photo shows a board-level connection that adds behavior beyond the TP4056 charger chip itself.
  • Battery pads and load pads have separate roles.The B+ and B- markings must be distinguished from OUT+ and OUT- when recording the module’s connections.
  • Protection devices and indicators are additional circuit choices.The visible LEDs, resistors, and protection components can affect behavior that the chip’s name alone does not describe.
  • The PCB handoff must preserve the required support behavior.The component record must distinguish charger behavior from the module circuitry before a custom board replaces the breakout.
This TP4056 breakout visibly includes more than the charger IC: the USB connector, protection devices, status LEDs, resistors, and exposed battery/load pads are support-circuit choices that must be understood before a prototype becomes a PCB. Photo: -stk, CC BY-SA 4.0
This TP4056 breakout visibly includes more than the charger IC: the USB connector, protection devices, status LEDs, resistors, and exposed battery/load pads are support-circuit choices that must be understood before a prototype becomes a PCB. Photo: -stk, CC BY-SA 4.0
iotclass.org

Major section

Breakout Circuits Change Interface Behavior

A breakout’s support circuit can change voltage compatibility and bus behavior.

  • Several breakout pull-ups can change the shared bus resistance.Parallel resistors from two or three sensor boards may make the bus too strong for the cable or low-power node.
  • A voltage-compatibility label cannot prove every input is protected.Some boards use level shifters, while others rely on a particular sensor pin tolerating the applied voltage.
  • Regulators and dividers can alter signal and power behavior.A microSD module’s support circuitry may increase current draw or slow signal edges compared with a native 3.3 V part.
  • The record must separate component and support-circuit behavior.The team needs to know which module choices must be preserved when the supplier or PCB changes.

I am adding sensor and microSD modules to the greenhouse logger. I inspect their support circuits because a compatible label does not prove that the combined bus still fits.

iotclass.org

Major section

Power Transitions and Safe Reset Behavior

Power and actuator modules need checks at the moments when their state changes.

  • Power transitions can expose a weak supply path.USB plug-in and battery removal test load sharing, undervoltage protection, dropout, and leakage assumptions in the portable prototype.
  • Short load bursts can exceed available power margin.Radio transmission, SD-card writes, and actuator pulses need measured current and rail evidence from the combined build.
  • Actuator modules must define safe behavior after reset.Relay input polarity, motor-driver current limits, braking modes, thermal shutdown, and fault pins can affect the default state.
  • The custom PCB must retain necessary protection and fault handling.Moving away from modules makes their driver, protection, and support-circuit decisions the design team’s responsibility.

I am watching the logger’s rail during USB connection, radio transmission, and pump startup. I check the module’s hidden protection and reset behavior before blaming firmware for a reset.

iotclass.org

Major section

Parallel Pull-Ups and Antenna Gain

Pull-ups and antenna gain change the margin even when the named component stays the same.

  • Three identical pull-ups produce a smaller combined resistance.The chapter’s three parallel 10.0 kΩ resistors have an equivalent resistance of 3.33 kΩ.
  • The combined pull-ups determine the LOW-level current.The device holding the 3.30 V bus LOW must sink 0.990 mA through the parallel pull-ups.
  • The current uses part of the sink rating.The 0.990 mA load is 33.0% of the stated 3.00 mA sink rating.
  • Antenna gain changes radiated power at the same chip setting.The chapter’s 14.0 dBm setting through a 2.15 dBi antenna gives 16.15 dBm EIRP.

I am checking three sensor boards on the same 3.30 V bus. I calculate their combined pull-up load and keep the radio’s antenna gain in the component record.

iotclass.org

Activity 2 · Work it out

✎ Combine the pull-ups

I want you to check the bus current before accepting another breakout.

Three identical 10.0 kΩ pull-ups share a 3.30 V bus. Calculate their parallel resistance, LOW-level current, and percentage of a 3.00 mA sink rating.

3 minutes · Pen and paper · Answer: Activity 2

Your answer
iotclass.org

Major section

Sensor Selection

The map organizes sensor acceptance; start at Sensor under review and follow the evidence lanes.

  • Measurement and environment evidence must justify the reading.Range, response, mounting, moisture, vibration, and airflow determine whether the sensor represents the physical condition needed by the prototype.
  • Interface evidence must connect pins to operating constraints.Bus address, analog scaling, interrupts, cable length, timing, and pull-ups need to fit the actual controller and harness.
  • Power evidence must include idle and warm-up behavior.The active current alone cannot establish whether duty cycling leaves the sensor’s readings usable.
  • Calibration evidence must connect raw values to engineering units.The reference method, offset, recalibration need, and conversion rule belong in the acceptance record.
Sensor selection evidence map
Sensor selection evidence map
iotclass.org

Major section

Measurement Fit Depends on the Installation

Match measurement evidence to the decision and the place where the sensor will operate.

  • Resolution and response time must serve the intended decision.The sensor’s range, accuracy, drift, and repeatability need evidence for the measurement the prototype will actually use.
  • The environment can change a reading’s usefulness.Moisture, vibration, airflow, mounting, and enclosure heating may matter as much as the sensing element.
  • Sensor families need different installation checks.Environmental sensors need placement review, while motion and position sensors need mounting and noise evidence.
  • Raw evidence can distinguish several possible failure causes.Saved readings help separate sensor behavior from wiring, placement, and firmware problems before the component is accepted.

I am comparing the greenhouse sensor’s bench reading with its enclosed reading. I check placement, airflow, and noise before treating a suspicious value as a software fault.

iotclass.org

Major section

Specification Limits and Calibration

The spec sheet ties each claimed value to a component revision and measurement conditions.

  • The document must match the exact part and revision.The header’s part number, revision, and date establish which silicon and specification rows support the acceptance record.
  • Minimum and maximum limits expose variation around typical values.The stated supply and temperature conditions determine whether the specification remains applicable to the enclosure test.
  • The example sensitivity has a guaranteed range.The tri-axis accelerometer lists 560 mV/g typical, with limits of 543 to 577 mV/g.
  • The zero-g offset also needs calibration evidence.Its typical 1.4 V offset lies between 1.26 and 1.54 V, so a typical-only conversion can misread actual parts.

I am reading the accelerometer specification beside the exact part on the bench. I keep minimum and maximum values visible because a typical sensitivity is not every sensor’s response.

iotclass.org

Major section

Conditions Behind Sensor Acceptance

Bench acceptance must preserve the conditions behind the specification.

  • Specification claims require matching measurement conditions.Supply voltage and enclosure temperature can require renewed bench verification before the table values support acceptance.
  • Calibration must account for sensitivity and offset together.The conversion from raw readings into physical units must account for both sensitivity and zero-g ranges.
  • Electrical sensing needs isolation and range evidence.Voltage, current, resistance, and power measurements require boundaries appropriate to the signal being measured.
  • Human inputs need usable and reliable physical behavior.Buttons, switches, touch pads, and encoders require debounce, accessibility, and enclosure review.

I am checking whether the specification holds at the logger’s rail and enclosure temperature. I keep the calibration and sensor-family checks attached to those conditions.

iotclass.org

Deck summary

Key takeaways

Accept a component through a repeatable argument from requirement to bench result.

  • A part number still needs operating-boundary evidence.The selected component must fit the prototype’s measurement, interface, power, and environmental requirements in the actual build.
  • Module support circuits can change system behavior.Pull-ups, regulators, protection, and driver defaults can affect the power path, signal interface, and safe reset state.
  • Acceptance must cover the assembled configuration.Actual wiring, neighboring loads, enclosure conditions, supply, and firmware must be included in the repeatable bench record.
  • The handoff must state what needs another check.The component record preserves what passed and what must be verified before a PCB change or field deployment.

I am handing the greenhouse logger’s accepted parts to the next integration step. I keep the raw bench evidence and retest conditions with the component list.

iotclass.org

Retrieval practice

Recall check 1 of 2

Voltage Vera says: answer from memory, then check your reasoning.

Q1An I2C sensor works alone but fails with its final cable harness. What should the team investigate?

AA different dashboard without checking bus evidence
BThe sensor brand as the sole explanation
CPull-ups, bus capacitance, routing, and timeout behavior
DThe successful short-cable test as complete acceptance
Show answer

Answer: C The incremental test points to the added interface boundary rather than a vague sensor failure.

iotclass.org

Retrieval practice

Recall check 2 of 2

Voltage Vera says: answer from memory, then check your reasoning.

Q2A prototype works with a breakout board but fails on a custom PCB. What should the design review compare?

AThe prototype result as proof of PCB equivalence
BThe module’s support circuitry and default settings
CThe main chip name without neighboring components
DThe enclosure color as the electrical difference
Show answer

Answer: B Regulators, pull-ups, filters, protection, and defaults can mask integration requirements.

iotclass.org

Print reference

Answers

Answer key.

  1. C · The incremental test points to the added interface boundary rather than a vague sensor failure.
  2. B · Regulators, pull-ups, filters, protection, and defaults can mask integration requirements.
iotclass.org

Print reference

Activity 1 answer

Model answer.

Predict: Check pull-up value, bus capacitance, cable routing, shielding, and firmware timeouts. Model sequence: sensor alone on a known-good rail → confirmed address and responsive raw reading → real cable → enclosure position → neighboring bus device. Keep the result at each step.

iotclass.org

Print reference

Activity 2 answer

Model answer.

Work it out: The parallel resistance is 10.0/3 = 3.33 kΩ. The current is 3.30 V / (10.0 kΩ / 3) = 0.990 mA. The sink-rating share is 0.990/3.00 × 100 = 33.0%.

iotclass.org