Test the Sensor-to-Service Path
Test the Sensor-to-Service Path
A board is useful when it exposes the risk the team needs to test. Choose its role before its name.
Choose the Board That Answers the Next Question
Picture a bench prototype whose loose wiring resets whenever its radio sends. Buying a more powerful board may hide the fault without proving power, wiring, or deployment behavior.
Firmware means the software stored on the device. A gateway means the boundary system that connects local devices to another network or service. Choose a platform for the risk you need to test.
Build one sensor-to-service path, disturb power and one connection, restart it, and replace one module. Keep board version, wiring, software version, fault, recovery, and measurement records.
This runway does not prove that the prototype is ready to manufacture. The deeper sections compare starter boards, controller boards, module carriers, gateway boards, custom boards, and transition evidence.
A hardware platform is the temporary form that lets a prototype answer its next question. Use a starter board to learn pins and firmware, a connected controller board to test embedded device behavior, a module carrier to stabilize wiring, a gateway board to test local application services, and a custom board when layout, enclosure, power, and repeatability become the real risks.