With proxy (images don't work):
--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/a9754432-2ba8-4632-a40a-9b2b51091673n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/a9754432-2ba8-4632-a40a-9b2b51091673n%40googlegroups.com.
勇気とユーモア
The only way I currently can think something like a independent xy-system with an shared area could work would be, if you define in the shared area some feeders, and then select for each feeder one of the "heaps" as source.But that would limit the number of parts, that could be used in a single job, also probably a huge pain how to get that running asynchronously to the main process without the risk of collisions of both heads...
Would not say impossible, but I guess not (much) easier to get openpnp to support multiple independent heads at the same time.
--Arthur Wolf schrieb am Montag, 22. März 2021 um 23:31:36 UTC+1:The way this would allow for massive parts catalogs within the work area is extremely cool. Definitely worth the time cost for some types of uses/businesses where setup is a large part of the work.With some optimizations, something like 20x20cm would be 400 part types, try to beat that with spools... and you can pretty easily use a few motors to stack things up in the Z axis tooHave you thought about having a separate controller/xy axis actually just dedicated to a catalog built like this, that would just prepare parts in advance in a shared area? (running in parralel to the actual job, or running before the job as an automated setup process). How hard would that be to support in OpenPNP?I really see a ton of potential in this, at least for how we are planning to use OpenPNP in the future, this is definitely something we are looking forward to setting up.Hi,after some inspiration of the Team14 HeapFeeder (https://www.youtube.com/watch?v=rYFK_RLNU-g) that was never really finished, I put a bit of time in an implementation.It is a high density feeder (about 3cm² for each feeder, around 500 1206 parts or > 3.000 0603 parts on that area) but really slow, since it requires many movements and lot's of vision.
My goal was for my liteplacer based pnp, that I can have most passives always on the table, since I mostly do very small numbers of pcbs, so the set up times are the biggest factor. (Probably with the time needed to develop this feeder, tweezers would have been faster for the rest of my life, but I hate placing parts with tweezers)A pull request is planed in the near future, but till then for the guys with IPv6 (or the knowledge how to use an IPv6-proxy) I have written a short(?) introduction with a short video on my homepage: https://www.formann.de/2021/03/openpnp-heapfeeder/greetingsJohannes--You received this message because you are subscribed to the Google Groups "OpenPnP" group.To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/a9754432-2ba8-4632-a40a-9b2b51091673n%40googlegroups.com.
--勇気とユーモア
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/5b312ad4-f1af-4834-988c-d298e9b2169cn%40googlegroups.com.
勇気とユーモア