How would you handle errors with 'stacked' MDI commands?
Sent from my Galaxy -------- Original message -------- From: andy pugh <bodge...@gmail.com> Date: 2025-06-05 6:00 a.m. (GMT-08:00) To: EMC developers <emc-developers@lists.sourceforge.net> Subject: Re: [Emc-developers] Proposal: Change default behavior on abort to 'M2' On Thu, 5 Jun 2025 at 13:51, Bertho Stultiens <l...@vagrearg.org> wrote: > When performed in interactive mode, then it is an error to alter the > state of the machine when an error occurs interpreting a command. > > The user would expect that the user interface tells the user of the > error in the command entered and simply refuses to execute a faulty > command. The state of the machine should not be altered because, from > the user's perspective, nothing was done or executed. I agree, but you will find that if you are in MDI mode and; M6 S1000 M8 then the spindle starts and coolant turns on Then G81 Z-10 (missing R word) the coolant and spindle turn off. This is just an annoyance that I have been putting up with, but at least the change here is obvious. I think it hints that faulty MDI does result in an abort, so altering the scope of abort requires consideration of the MDI case. (I would be easily persuaded that MDI faulty inputs should just do nothing at all) -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 _______________________________________________ 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
