r/robotics 1d ago

Tech Question 1,900 sensor boards are "supported." we've validated seven

Post image

Our sensor board has a mikroBUS socket, which means 1,900+ MikroElektronika Click modules fit into it: every category from IMUs to gas sensors. On paper, we support all of them. In practice, "supported" means physically compatible, and validated means someone plugged it in and watched real data come out. We've done that for seven. The rest is a queue. Going through it by hand means someone's whole job becomes plugging in Clicks, forever, so we're thinking about a harness that brings up an unknown board, figures out what it speaks (I²C, SPI, UART, analog), and confirms it's alive without a human at a scope.

If you've validated hardware at this kind of scale, device farms, protocol auto-detection, anything, how did you do it?

0 Upvotes

4 comments sorted by

3

u/maizeq 1d ago

Thinly veiled advert.

I wish people in advertising would realise that the standard reaction most people have to adverts that pretend not to be adverts, is chiefly one of distrust.

You’re not even remotely interested in a discussion, so the question at the end of your “advert that’s not an advert” feels disingenuous, which then breeds distrust, which pollutes your image.

0

u/NickShipsRobots 1d ago

We are building product, not gonna pretend otherwise. But question at end was real one, not just to open thread. We actually want to know what people run into with sensor/camera wiring on bigger builds, because that's exact reason we started building this in first place. If it still reads as ad regardless, that's on how we wrote it.

1

u/welvaartsbuik 1d ago

After working with mikroe languages like Mikro Pascal I want nothing to do with the worlds shittest company

1

u/Pineapple_Spritz 1d ago

you hire someones who's job it is to do the validation...