← Back to the chapter · Previous detail · Next detail →

Technical detail · Hardware Components: Selection Evidence

Power paths and actuator defaults

Load sharing is how a power path supplies the device while also charging the battery. Check whether this board supports both at once; measure current into the battery and load with USB connected and removed. Regulator dropout is the smallest input-to-output voltage difference needed to keep its output in regulation. Measure both rails during load bursts and as the battery falls.

A TP4056-style charger board, a boost converter, and a small LiPo cell can make a portable prototype appear straightforward, but the real behavior depends on charge-current setting, load sharing, undervoltage protection, regulator dropout, switch leakage, and how the system behaves during USB plug-in or battery removal. A current monitor such as an INA219 or a bench supply readout can reveal whether the radio transmit burst, SD-card write, or actuator pulse exceeds the power path. Without that evidence, firmware teams may chase resets that are actually rail and layout problems.

An optocoupler transfers a signal using light across an isolation boundary; check the module circuit to see what is actually isolated. An active-low input activates when driven low. Test the required input level and the output state at startup before connecting the load.

Actuator modules also hide design choices. Relay boards may include transistor drivers, optocouplers, indicator LEDs, pull-downs, or active-low inputs. Motor-driver boards include current limits, thermal shutdown behavior, braking modes, and fault pins that should be wired or at least recorded. Moving from a module to a PCB means those decisions become the team’s responsibility. The under-the-hood question is therefore: which behavior did the component provide, which behavior did the support circuit provide, and which behavior must be preserved when the prototype becomes a durable design?

← Back to the chapter · Previous detail · Next detail →