On Mon, Feb 17, 2020, 18:09 John Dammeyer wrote:
>
> You're right of course. I don't think the target is existing BBB users.
> I think the target market is people whos PCs are running MACH and the
> hardware has potentially reached end of life. I found with this latest
> set of PCs I bought
> >Perhaps what's needed is the work to make the MESA boards function
> with the BeagleBone. Then it's a plug and play change with no large amounts
> of physical hardware to move around. Like Sam does hanging it off the back
> of the monitor.
>
> How many Bone users are out there that want
The status messages often do change between versions. A big example of
this was when joints and axes were split up. The status messages changed
quite a bit then. Multi spindle support was another biggie. These were
two big examples but there are plenty of other smaller changes that have
It's a BIG change with lots of potential to break things and the
benefits don't really warrant the work and risk. You really don't want
to accidentally introduce a bug that only shows up when someone runs a
particular configuration but when it does, makes the machine eat itself.
Les
On
ange?
> John
>
>
>
> > -Original Message-
> > From: N [mailto:nicklas.karlsso...@gmail.com]
> > Sent: February-17-20 12:38 PM
> > To: Enhanced Machine Controller (EMC)
> > Subject: Re: [Emc-users] [Emc-developers] Looking to make hex offset list
>
> On 17/02/2020 18:15, Johannes Fassotte wrote:
> > I'm reviewing currently available documentation from the NIST on how a
> > remote user is fed status information. From what I can tell based on
> > my experiments is that the raw data file is sent to the remote for
> > decoding and that the
On 17/02/2020 18:15, Johannes Fassotte wrote:
I'm reviewing currently available documentation from the NIST on how a
remote user is fed status information. From what I can tell based on
my experiments is that the raw data file is sent to the remote for
decoding and that the remote is able to
