I guess its not really as important as I used to think, the current
activation signals are really all that are required most of the time.
I was interested in macros to create custom M commands to control
special features particular to a machine like you say.
One case was the arc startup delay for a plasma control before I knew
about using the dwell Gcode. I was going to use the macro to set the
feedrate really low for a time period, then go back to the commanded
speed. Then I found the dwell Gcode which made more sense, and then
tripped on the the related Mach1 'feature:-)' on the first occurance
after a Estop or fresh startup. Art said he killed that rodent in
Mach2.
But I still think the macro docs are murky nananananaa ;-)
-Lee
toggle quoted message
Show quoted text
It would be very helpful if you and others on the Group would like
to post explaining what you would like to do in your macros or,
perhaps easier, what you cannot do at present in Mach2. For example
is it to make MDI easier through less typing, to get round problems
with an existing post-processor, to control special features like a
part catcher etc.
With this sort of background established, I will try to document
sone more interesting examples.
John Prentice
