Re: mdi moves

["Dave Engvall" <dengvall-at-charter.net>]

Hi Paul,
but...but...but.....values should be modal based on the input from the
g-code not on the position of the axes when the commanded is entered....or
did I miss something.

Dave
----- Original Message -----
From: "Paul" <paul-at-bdiemc.fslife.co.uk>
To: "Multiple recipients of list" <emc-at-nist.gov>
Sent: Friday, March 21, 2003 1:11 PM
Subject: Re: mdi moves


>
>
> Hi Dave
>
> I have experienced this problem consistently over the time I have been
> working with EMC. It is not just the X or Y axis that is affected - It
> happens with all of them.
>
> If you monitor the raw data being passed to the trajectory control, you
will
> see any axis that is not given a position on the MDI input will assume the
> *current* position. In your example, if Y5.5 is commanded when X is at
2.775,
> once X reaches 5, the next move on the stack will be Y5.5 X2.775 Z0 F10.
> The short term answer is to enter X5 Y5.5 Z0 to remove any ambiquity. Long
> term perhaps, any unspecified axes should use the last value on the motion
> stack rather than the *current* position.
>
> Regards, Paul.
>
>
> On Friday 21 March 2003 7:26 pm, Dave Engvall wrote:
> > Bring up emc and home:
> > shift to mdi
> > G1 X 12 Y 5 F10
> > X 5
> > before the machine arrives at X = 5 issue:
> > Y 5.5
> > machine completes the X5
> > then does a G1 X(position when the Y 5.5 CR was done) Y 5.5
>
> --
>
> "To err is human...to really f*** things up requires the root password."
> >From a collection of quotes at http://www.indigo.org/quotes.html
>
>