开云体育

Murky indeed...

Macro's were originally designed so I could reuse code, but they didn't
work out that way. Instead they are used to create usefrull subroutines for
specific purposes. Doc's are a little sketchy. John's idea is a good one, as
functions are needed I will add more. This is a troublesome area however, as
the macro's are run in a separate thread, so unknown interactions may occur.
This is evident in the serial output macro (on my immediate list for
repair) in that while it runs in testing mode, it will not transmit during a
program run. I will be spending some time to strengthen this over the next
little while to allow more complex programs with more stable interaction.
I'm attempting to make the main interpreter loop stop until the macro thread
is finished. This may cure the serial problem and allow for more
functionality. I have many requests for more output, so I am trying to make
the macro facility be able to transmit bytes to port addresses unknown to
Mach2, this would allow a 48pin IO card, for example, to be configured and
used as M-Code I/O no matter what card is desired. It may be the solution
for IO required for toolchangers and such.

I'll get back to you on specifics as I go. In regards to the question, "Can
I execute G-Code in a macro, yes, I believe the command is GCode("G0X0") for
example, but I will have to look this up...

Thanks,
Art
www.artofcnc.ca