Re: EMC Source M-codes pause motion

Thanks for the encouragement,
I set up a (very slow) test machine in my office with 2.2 on it & I
have been hacking away all day.
I figured out that I was not correct in my previous assumptions, the
pause in motion is not caused by the preconditions of the mist
command, but rather the preconditions of the motion command i.e.
motion waits for io. The end result was no edits to the mist
function, but removing the io preconditions for motion. This fix
leaves a lot to be desired because now the system will not halt on
any io. The present structure does not allow differentiation between
io types.
There should be at least 2 types of io defined for the task
sequencing, io that causes a motion halt & io that does not cause a
halt. To get really fancy if each io command type could be set by
inifile variable, everyone could have what they want. This would be
epically useful if a PLC ever gets integrated into EMC, all io
generating m-codes could have the option of forcing a wait-for-io-
done message or be open loop.
I noticed when I set up my test machine that the default inifiles
have been "cleaned up". This is probably going to be a source of
great frustration to any new users because the possible alternatives
are not included in a "remmed out" fashion as they were in previous
releases. Along that line is there any resource available that
itemizes ALL the current inifile variables?

As for me becoming a developer, I think I have a long way to go
before that happens!
Thanks,
Dean


--- In CAD_CAM_EDM_DRO@yahoogroups.com, Matt Shaver <mshaver@e...>
wrote:

> On Wednesday 03 September 2003 18:57, foxprints2003 wrote:
> > You may recall my earlier inquiry into the motion pausing to

execute

> > m-codes issue.

<snip>