On Thu, Mar 12, 2020 at 7:14 PM justin White <[email protected]> wrote:
> On Thursday, March 12, 2020 at 6:32:52 PM UTC-4, Chris Albertson wrote: > > Isn’t that something the Beagle is strong at with the eQEP and PRUs? >>> >> >> >> Strong only until you hit up against the limited number of I/O pins. A >> PRU based solution is cheap and simple but can't scale. >> >> In general TI's idea to place a small microcontroller on the same chip as >> their ARM Cortex-A was good and we see others doing this too but a big >> machine tool like a 5-axis mill with tool changer and cooling and saftey >> interconnects is going to need something bigger than a PRU. FPGAs work >> well as wold an STM32 tht had on order about 100 pins. >> >> -- >> >> Chris Albertson >> Redondo Beach, California >> > > But that's not what they are going for "Help assemble and provide software > images configured for an open source 3D printer and CNC machine (with > BeagleBoard.org and community guidance and support)"......Pretty much sums > up the mission statement. If they're looking to showcase the Beaglebone > hardware as part of an official beaglebone supported piece, I seriously > doubt they're looking to offload IO to a microcontroller and develop the > firmware for it when: > > >> * Manufacture the design under the BeagleBoard.org name to support the >> BeagleBoard.org Foundation and community >> > > Everytime someone mentions something like this people get all starry eyed > about it.....It's going to be Seeed's version of Cramps. The most helpful > suggestions would probably be along those lines. Jason will have to clarify > but I'm pretty sure this is a maker focused thing, Ethercat and analog > outputs for each axis are not going to happen. > Your statement is mostly accurate. I've gotten a bit distracted and overwhelmed by the input as "Seeed's version of Cramps" was indeed the intended scope. We all need something like CRAMPS and we need it readily available. It isn't that we aren't willing to put in some more effort here, but I want to right-size this based on what will be most broadly used. Sorry I got distracted from this thread for a while. I'm going to re-engage over the next few days to get this kicked-off. Ethercat is somewhat of an option. We could support Ethercat on BeagleBone AI with some software investment. > > Realistically that is the Machinekit audience anyway, otherwise mksocfpga > would have quite a bit more interest than Beaglebone projects, Try running > out of IO on a DE10-Nano, you could probably run a Haas with all that IO. > We can get more I/O out of BeagleBone, but I don't want to quickly get to the situation where we add a bunch of hardware that is useless for 90% of people. -- > 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/d7a07412-c692-4673-9e2e-a87131cadf10%40googlegroups.com > <https://groups.google.com/d/msgid/machinekit/d7a07412-c692-4673-9e2e-a87131cadf10%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- https://beagleboard.org/about - a 501c3 non-profit educating around open hardware computing -- 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/CA%2BT6QP%3DUauT%2BDq6ZA%2BS7UtHp%2BLVOQSw%3DtkjTmf1%2Bb8B3tQj4KQ%40mail.gmail.com.
