Greetings, I've been reading the documentation and browsing the repo for machinekit, and I'm trying to determine if machinekit is what I'm looking for. Here's my use case.
I'm building a "big" SMT pick and place machine. I hope to use Mesa anything i/o for interfacing, big stepper drives, linear encoders, and a number of sensors and other actuators, along with a communications bus for feeders. Instead of using 3d printer firmwares, I'd prefer a linuxcnc-like interface for the machine itself - with visual elements for sensors like pressure/vacuum sensors, etc. Also, I'll have to have G/M codes for "all of the things". For the jobs themselves, I plan to use openpnp. This will require some kind of driver to pipe gcode commands in MDI from openpnp to the linuxcnc stack. (I know there's a few more steps My question is, should I be looking towards machinekit/machinetalk to accomplish this? Or should I just default to linuxcnc and python/nml? (I'm hard-pressed to tell the difference between the two!) What is the difference? I'm seeing things that imply that machinekit can be used for machines that aren't specifically cutting machines, but very few examples. Thanks! -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/a106563b-dd58-44b5-a5ea-d48f7a38d3e6o%40googlegroups.com.
