Many companies still start by selecting an off-the-shelf sensor. Why is that becoming less effective?
Off-the-shelf sensors are built on a reasonable assumption: that most applications share enough requirements to justify a common solution. In robotics, that assumption rarely holds true for long.
A humanoid balancing on uneven terrain, a surgical robot operating inside the human body, and a warehouse manipulator handling thousands of different products all face fundamentally different mechanical, environmental, and control challenges. As robots become more advanced, those differences become increasingly significant.
Teams that begin with catalogue sensors rarely encounter a single limitation. Instead, they encounter a series of trade-offs. A sensor with the right force range may add too much mass. One with the right mass may introduce unacceptable stiffness. Another, while offering acceptable stiffness, may lack the multi-axis accuracy required by the control system.
Each compromise creates another workaround – a mechanical adaptation, a software filter, a recalibration routine, or a change elsewhere in the system.
The complexity does not disappear. It accumulates, often invisibly, in other parts of the project. By late-stage development, a significant portion of the engineering effort may be spent compensating for a sensing solution that was never designed for the application.
As a result, leading robotics companies are increasingly asking a different question. Instead of asking, “Which sensor should we buy?”, they ask, “What sensing architecture best supports the robot we are building?”
This shift changes where sensing sits in the design process – from a procurement decision made late in development to a foundational architectural decision made at the very beginning.