doozy of a question: How would you Select+Serve Components, tabletop size!!

this absolutely mind-bogglingly complex task people able easily.  i don't expect able build anytime soon, i'm curious how done.

first, task @ high level "i want 10k resistor!"  you might have in bins, or binders, or baggies, or strewn across desk, or, doesn't matter.  however it's organized, few seconds later have it.  to return it, have pick out , return it.

the doozy of question is: "how can system this?"

this means 3 parts:
1) catalogue.  the system knows has , doesn't.
2) contain.  the system stores has , doesn't.
3) retrive.  when has requested can retrieve it.
4) serve.  the user can served user has asked for.
5) accept.  it can accept things user.
6) identify.  it can either identify has received user or must ask.
7) catalogue.  it must add catalogue of things has
8 ) store.  it must store has gotten.

er, helluva "3 parts".

let's keep things simple , see if working resistors.  how possibly of above?  what might such system like?

one thing think of this.  suppose had thousands of plastic layers, pages of plastic binder.  if knew layer in, perhaps layers controlled in automated way (p. 340), opens page , component there falls out.


what other parts?  any other way this?

note:  this totally out-there idea not currently building.  maybe in 3 years.  but i'd know feasibility , how possibly done.


edit: don't mean move goalposts,  reason said "thousands of sheets of plastic" there not space around components,  , can small,  tabletop size!  fast,  small-sized retrieval system few hundred tiny parts.  inspiration read storing components in 3-ring binders of baseball card holders (9 page)  - surely clevwr solution not larger that. . how catalogue?  rfid tags? don't work little tiny smd's...  kind of user input may best,  perhaps after weighing component?  dwsoldered components wouldnt weigh same after use... many questions...

you researching inventory management , storage system. database can used track recognized , available parts, nothing new far. physical handling of parts can not unified easily, each kind of package deserves different machinery, , possibly storage compartments of different sizes. recognition of labeled items or bags can standardized, degree.

such automated inventory management systems in use since decades, feasibility out of question. diy approach limited genie, time, space , money required machinery.

Arduino Forum > Community > Bar Sport > doozy of a question: How would you Select+Serve Components, tabletop size!!

arduino