Hi Fernando,
> This email is meant to be a brainstorming thread for possible improvements
Please share:
* a description of your machine hardware.
* your machine.xml
* a video of your machine running several placement cycles. We might
be able to spot some areas for improvement
> This email is meant to be a brainstorming thread for possible improvements. I understand if this is the limit of openpnp. Still very impressive openpnp can do all of this now with the test branch I am using. Deferring errors saved my machine from being stored labeled "not autonomous" or "not for production". Runs autonomously now but is still slower than loading by hand.
> Huge thanks to whoever contributed to the defer error feature. great work!
I am pleased this is working for you. Thanks for the feedback.
> Situation:
> Currently loading a 612 placement job with the advancedloosepartfeeder and takes about 40 minutes.
That doesnt sound too bad. If I understand right, that is 900 parts
per hour. I dont think I have seen any reports of
advancedloosepartfeeder being used in production and running at that
rate, so I am definitely interested in seeing a video.
> By hand takes about 20 minutes on average.
What does "by hard" mean here?
> I was asked "Can the machine just take a picture of the loose part tray and just know where the parts are?" I can not imagine how openpnp could accomplish this. unless it could scan prior to running the job and store all the imagines it takes. run the feed pipeline, store 1, 2, 3, .. matches and keep the location data for the best matches. then make a pick list of all the stored location data.
... and hope they dont get moved. But they are "loose".
Toby