Scary is a good way to describe it! I wish the interplay between all the components was easier to understand and work on.
-Rob On Tue, Mar 31, 2020, 3:38 PM Chris Morley <chrisinnana...@hotmail.com> wrote: > Well obviously I didn't check the code - it never occurred to me that > there wouldn't be a motion command to change offset, but as you said motion > doesn't need to know abut it it's baked into the actual command for > movement. > > Thanks for setting me straight on that guys. > It's interesting to get into it a bit (and a little scary). > > Chris > ________________________________ > From: Robert Ellenberg <rwe...@gmail.com> > Sent: March 31, 2020 7:07 PM > To: EMC developers <emc-developers@lists.sourceforge.net> > Subject: Re: [Emc-developers] improve synchronization between backend and > UI > > Chris, unfortunately G10 doesn't send any "motion" commands, it directly > changes the work offsets in interp (where they live), and if the changed > offset is active, sends canon commands to update the current offset values. > Those commands never make it to motion. Canon is basically synchronized > with interp, but task and motion lag behind. > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
