I don't think you can lost the modes completely as you still need to
know the current machine state. For instance if the machine is running
MDI code and you enter another MDI line before the previous one has
finished, the next line should be queued. However if you enter an MDI
line while running code it should be ignored.
However it would be nice to lose the need to explicitly set the mode. In
effect mode would become a current state flag. Issuing an MDI command
automatically sets the mode to MDI (if the machine isn't running a
program). Once the MDI code has finished it reverts back to jog. The
same with running a program (auto mode). Unfortunately none of this
really helps with being able to jog in auto.
Les
On 05/12/2017 14:29, Rene Hopf wrote:
On 5. Dec 2017, at 10:33, Chris Morley <[email protected]> wrote:
I actually wonder why the controller must have modes at all.
The only thing really important is if it is busy it must finish.
removing modes altogether would solve a lot of problems.
especially jogging while paused, which is a much requested feature, and comes
up very often.
there is a jog while paused branch, which already does most of the stuff, like
going back to the old position when you continue.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
