Parametric search: from requirement to component shortlist

The problem: „I need a microcontroller” is not a search

A category only tells you which shelf a product sits on. A technical requirement tells you which products fit at all. You feel the difference when the project demands:

• 3.3 V supply (because the rest of the board already runs at it),
• two I²C interfaces (because two buses with different devices),
• an SMD package, because the PCB is yours.

On a classic listing you apply those three constraints by eye. In a parametric search — three clicks.

A filtering order that works

• Apply hard constraints first — supply voltage, package, operating

temperature. These are conditions you cannot design around.

• Add required interfaces — I²C, SPI, UART, USB.
• Only then optimize — price, availability, manufacturer.

Rule: filter what excludes first, then what sorts. The reverse order ends with browsing hundreds of cards that were never going to fit.

Parameters worth asking for in electronics

Every attribute in the catalogue carries a unit and a filter type — a slider for ranges, checkboxes for value lists. The ones that make the biggest difference:

Parameter	Why it matters
Supply voltage (V)	a mismatch means a damaged module
Current draw (mA)	critical in battery designs
Interfaces	they decide how you connect
Measurement range (sensors)	outside the range, the sensor lies
Dimensions (mm)	fit into enclosure and PCB

What's next

The attribute registry grows with usage — if an attribute is missing on a product you need, write to us. The catalogue is young; parameters get added where they genuinely help the choice.