Hello All,
In case others are in the same boat, I just wanted to report back on how I am planning to attack this problem.
Big disclaimers before I start:
1. I do not know what I am doing!
2. The files referenced in this post totally undocumented and there has been no testing as to what problems can arise if someone puts the wrong code in these files.
3. Successful usage I describe requires the gcode to have Z-axis moves isolated on their own lines.
4. This usage requires the above mentioned "Z is 2.5D..." checkbox to be checked.
A member, kcrouch, was kind enough to let me know about two macro/script files that relate to my request: "ZDN_2D.m1s" and "ZUP_2D.m1s". These files are activated when the Mach3 moves the Z-axis, the former when the axis moves down and the latter when the axis moves up. These files need to be put in the [Mach3]\Macros\[profile you use] directory. I am using "Mach3Mill" profile, so that is the directory that I put the script files in.
In each file I placed a line similar to:
MsgBox("Move Z up/down to correct location.")
Make sure to restart Mach3 after everything is set up.
When Mach3 is running and encounters a Z move, the line processing will halt until the OK button in the dialog is pressed, giving you time to adjust the Z height appropriately for the next move. NOTE: If the z move is combined on the same line as another axis move, the other axis will move while the dialog box is being displayed, so you have just plowed through something that you did not intend. Make sure Z moves are on their own lines!
There are lots of problems that could arise using this method, so unless you are sure of what you are doing, I would not suggest following my lead. I could not find any better information about how to do this in the forum, so I thought I would put it out in case someone else finds it helpful.
Thank you for your time.
Jerry