From: dave <den...@ch...> - 2005-03-28 15:10:59
|
Hi Paul, However, this only happens if the axes are in motion. If one enters another line after motion has ceased then it executes correctly. So...queuing mdi commands should fix this and pulling them off the queue at the completion of the current motion should fix this nasty little bugger. Dave On Monday 28 March 2005 03:16 am, Paul wrote: > Hi Ray > > MDI mode has always worked in this way. Any MDI command > entered at the GUI is passed to the rs274ngc interpreter for > evaluation. If a value is not given for an axis, it's value is > read from the current (at the time of evaluation) position. > To break this behaviour would require the interpreter to > ignore the world model and remember the last XYZABC > coordinates that were issued. > > Regards, Paul. > > On Monday 28 March 2005 04:17, Ray Henry wrote: > > Both Dave and I tested this on machines. He ran it on > > BDI-2.18 with a compile from the sf repository a couple days > > ago and I ran it with BDI-4.18. Our conclusions are that > > the MDI bugger up is back. I suggest that you issue a bug > > report at SF. In the mean time, We are recommending that > > folk not try to issue one MDI command while another is > > executing. |