> -----Original Message-----
> From: Gene Heskett [mailto:[email protected]]
> Sent: Thursday, April 02, 2020 6:42 AM
> To: Enhanced Machine Controller (EMC)
> Subject: [Emc-users] wild hare continued.
>
> Greetings Andy;
>
> I have some of the data transfers working, but I then recall you said
> G33.1 ran in metric internally.
>
> So if I am capturing data during the execution, but its in inches at the
> nc_file origin, the captured data being passed back needs to be
> *25.4000000 to be usefull, both as a display and as a correction to the
> Z stroke.
>
> The fact that m66 Enn uses #5399 regardless of the nn is being an
> obstacle. It means that I'll have to use some digital outputs to tally
> whether or not #5399 has been read and by whom.
>
> Could this use be expanded to a memory location dependent on ENN? That
> would greatly simplicate the gcode.
>
> Thanks Andy.
>
> Cheers, Gene Heskett
> --
I like the suggestion. I believe that the docs say that M66 Enn is limited
to nn=0 to 3. Tormach's PathPilot appears to allow nn=0 to 7. If so, you
need to allocate more than four cells to hold the most recently read value.
Just a consideration to avoid breaking stuff.




_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to