Jun 25, 2020, 01:53 by [email protected]: > Linuxcnc has a hal driver for ethercat master as it doesn't require any > special hardware. > There was support for quite some time now, that's not the problem.
> > Ethercat slaves AFAIK require an ASIC and it's pretty expensive. > Ethercat slave requires a licence - whatever that is ASIC or code is not that important. And the license is relatively cheap, the LAN9252 costs around 8 Euro in 1-piece quantity. > > I hear alot of talk of ethercat but rarely see it actually used in industry. > I don't know the status of the hal ethercat driver in MK but if it's not > there why can't it be added (meaning what does it have to do with Beaglebone > specifically). As for the slave, Not really sure I see why you would use a BB > as a slave but it sounds like it's not practical. > BeagleBone AI uses AM5729, which in contrast to the one used in BBB should have a Ethercat slave support. You can then use the PRU for exchange of Ethercat messages and create distributed, multi-node system (multi Machinekit instances). > > If this was something I were gonna use I'd be glad to have a smart serial > channel or 2 > This seems like an asymmetry to me. You say that nobody use Ethercat based systems, but then want a support for solution that really nobody use and is not that good in first place. Why not use something which is developed and backed by a quite big group instead of one-man-show? But that's probably off-topic to this discussion, as it is going to be a CRAMPS-like board. That's why I am interested in what it will mean for the software side. Cern. > On Wednesday, June 24, 2020 at 6:09:06 PM UTC-4, [email protected] wrote: > >> Hi, >> Jun 23, 2020, 20:45 by >> [email protected] <>>> : >> >> > 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. >> > >> isn't that market already pretty filled with various MCU based boards and >> such? Don't get me wrong, I am all for new hardware, but I am wondering what >> the edge in this case would be. Because though it pains me to say this - >> even Open-Source project (hardware and software) needs marketing. Machinekit >> wasn't really that successful on that front in the past and it can be seen >> on the socFPGA work (in diplomatic speak). >> >> Maybe some kind of combination of Centroid Acorn and CRAMPS, I can see >> people wanting it. (But then people always want all-in-one solution which >> somebody else already thought of.) >> >> Let's talk about what it would mean from software side (as this is the side >> which I am most interested in) - I presume you want to run Machinekit on it, >> right? So how do you envision this? There already is some effort to support >> BB AI from the PocketNC company. >> >> > >> > 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. >> > >> I have always considered distributed multi-node system the holy grail, so I >> would be very much interested in solution, which could function both as >> master and as slave on some kind of industrial bus network. >> >> Cern >> >> > >> > >> >> >> >> 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 >> >> machi...@>> googlegroups.com <>>> >> . >> >> 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 > >> machi...@>> googlegroups.com <>>> > . >> > 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>> <>> https://groups.google.com/d/>> >> > msgid/machinekit/CA%2BT6QP%>> 3DUauT%2BDq6ZA%2BS7UtHp%>> >> > 2BLVOQSw%3DtkjTmf1%>> 2Bb8B3tQj4KQ%40mail.gmail.com?>> >> > utm_medium=email&utm_source=>> footer>> >> . >> > >> >> > > > > -- > 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/69628d2a-bfa1-44c3-9127-a0d479c89572o%40googlegroups.com > > <https://groups.google.com/d/msgid/machinekit/69628d2a-bfa1-44c3-9127-a0d479c89572o%40googlegroups.com?utm_medium=email&utm_source=footer>> > . > -- 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/MAn52Y3--3-2%40tuta.io.
