A better more general idea is to add a nml command that the motion controller 
could sent out to any and all displays to update. I am not sure how difficult 
this would be but I think it's the right fix.
Chris M

----- Reply message -----
From: [email protected]
To: "EMC developers" <[email protected]>
Subject: [Emc-developers] Axis bug in 2.7.3 (was: Question on a change in Axis 
from 2.5 to 2.7.3)
Date: Tue, Jan 5, 2016 7:10 AM



> On Jan 5, 2016, at 8:26 AM, Jeff Epler <[email protected]> wrote:
> \As I tired to indicate in my initial reply in this thread, I am not
> particularly committed to making "axis remote --reload" work while an
> MDI is actively executing; I think this is a mistaken idea.  It was an
> initial design decision in AXIS that a change to the active coordinate
> system that was *NOT* done by AXIS own touch-off would never trigger an
> automatic reload.
>

Well, we don’t want to trigger it WHILE the MDI is executing but we want the 
backplot to be updated after we change the active coordinate system.

> Perhaps *this* is the decision that should be revisted; I would consider
> a patch which would optionally trigger a reload when the active g5x
> offset or g92 offset was changed, at the next moment that AXIS believes
> it is OK to perform a reload (e.g., after the MDI that generated the
> coordinate system change was finished)

Yes, that is fine.  If it doesn’t reload the zero point and your backplot image 
are (usually) off the screen entirely.  I don’t see why that would ever be 
desirable…?

>
> This could be controlled by an inifile option or a menu option.
> Probably the former would be preferable for you, so that an operator
> can't make the wrong setting at runtime.

Yes.  On the gantry machine we are using this on, one positions the touch off 
point of the torch which may be many feet from the initial machine zero and 
then typically clicks the Touch OFF X,Y (or Touch Off X, then Touch Off Y) and 
if the backplot doesn’t update one’s image is off in space somewhere.

-Tom


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

Reply via email to