I'm not sure I understand completely but: If I 'stack' 3 moves and the middle one is faulty, I want the last one not to run either. Resetting everything is probably not necessary but stopping (error) is.
We routinely use MDI commands in complicated probing macros and detecting errors is difficult but very important. There is no way to definitively know if a single MDI command was run and failed, other then checking for an error message. It would be so nice if we could 'drip feed' gcode in auto mode for macros instead of MDI commands. The whole manual/MDI/auto process really could use a rethink. There also probably should be a NML message to (at anytime) reset the system to a known state. Chris ________________________________ From: andy pugh <bodge...@gmail.com> Sent: June 5, 2025 2:18 PM 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 15:04, Chris Morley <chrisinnana...@hotmail.com> wrote: > > (I would be easily persuaded that MDI faulty inputs should just do > > nothing at all) > > How would you handle errors with 'stacked' MDI commands? Currently the behaviour of, for example, G1 F1 X100 G81 Z-10 Is to abort the move-in-progress (as the G-code error is detected immediately) This is, I suspect, not what anyone wants, and just ignoring the bad G-code line would seem better. -- 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
