← Back to the chapter · Previous detail
Technical detail · Hardware Prototyping: Board and Breadboard Bring-Up
Read subsystem names as wiring requirements
Infrared (IR) sensors use light beyond visible red; an active IR sensor may emit light and detect its reflection. A passive infrared (PIR) sensor senses changes in heat radiation and does not emit that light. An H-bridge uses switches to reverse current through a motor, so it needs a suitable driver and power path rather than a direct GPIO load. Check each device’s supply and signal limits.
A user interface (UI) is how a person interacts with a system. A graphical user interface (GUI) uses visual controls such as buttons and menus. Use the same habit for general bench vocabulary. An LED is an indicator load that still needs current limiting, a PCB is the fixed conductive path that a breadboard temporarily imitates, and an IC is the packaged circuit doing the real electrical work. IR and PIR should be recorded as sensing mechanisms, not vague “motion” claims. A software development kit (SDK), UI, and GUI should be recorded as software or user-facing boundaries. H-bridges, amplifiers, motors, and Bluetooth links should be treated as subsystems with their own driver, power, and evidence needs. If a legacy diagram uses master/slave wording, translate it in the record to controller/peripheral, central/peripheral, or controller/responder so ownership is clear without carrying the old label forward.