If the depth of each pocket can be cut in one pass then it should work. Just specify each pocket, starting with the top one for the full depth and for a step down of the same size. If each pocket cannot be cut in one pass this wont work.

The problem is I dont think there is a standard for how big the flat is. The way the shapes wizard works requires a piece of gcode for the exact shape, the wizard can scale and rotate it but cannot alter the basic geometry. If you have one standard shape send me the details, Ill see if I can add it to the list.

First, it is a feature of all the Newfangled wizards that they let you build a cumulative program. You can run as many sub-wizards as many times as needed and they will all build in one file. When you finally exit from the wizard you will have one big file that does it all. Just remember, each time you run the wizards they build the same filename, so if you create a big file you want to re-use be sure to save it before you run the wizards again.

The multiple pockets will work, but each deeper pocket will assume the top of work is at z zero, so it will do a lot of 'air cutting' as it works its way down. There have been requests for setting the top of work at something other than zero, but Ive been afraid to do it because there are a lot of ways that could generate code that breaks tools and I hate doing that.

Depending on the depth of each pocket you might be able to fake it with setting the depth for each pocket to be made in one cut For something like the turners cube this could work, since each pocket is not deep.

Glad you like the wizards.

The keyway wizard must be the only one without a climb or conventional button. However, in the code there is a note that it does climb milling for the finish pass. Im not sure this works, but Ill have a look at it. Try setting an amount for finish and see if it climbs the finish.

I dont know what you mean about rounding in the rectangle. If you are cutting outside a rectangle the path always makes an arc around the corner, but the rectangle left will have a sharp corner. For inside cuts the tool must leave a round corner.

The electrical shapes wizard uses a file shapes.tap that should be in Mach3/Gcode. If you look at that file you will see it has each of the shapes defined in a standard format. Each shape starts with a (#). If you got the gcode for whatever shape you want and added it to that file with a unique segment number then the wizard will call it up just fine. You wont have an icon on the menu page for your shape, but if you remember its number simply enter that number in the Segment ID box  and it will generate the code.

Ill see about fixing the wizard to read all the ids in the shapes.tap file and displaying a list, then it could be a general purpose shape file

File I/O is pretty basic in VB, to make a bad pun. Something like:

open "filename.txt" For Output as #1
Write #1 "some junk in the file"
Write #1 Xval, Yval
Close #1

There is a complete Basic manual on this site under the documents section.

OK, I have some updated info. If you check the box in config/general that says auto toolchanger then only the m6start runs. The m6end is only used when you do manual tool change.

Are you entering the full command- " m6 t0303" I dont think T3 alone works.

I am having the same trouble with my macro. It appears to me that when the m6start macro runs the tool number is the old tool, not the one we are changing to. I think when m6end runs the tool number has been changed.

I have a message in to Brian to get help on this, when I get it figured out I will post more here.

Always good to hear when an answer is found. There are many places in Mach for that kind of duplication. I have had several problems with macropumps using the same DROs as my wizards.

I have the following macro in the "set tool offset' button on the Offsetts screen

CurrentFeed = GetOemDRO(818) 'Get the current feedrate.
PlateThickness = 0.062 'plate thickness
ProbeFeed = 1.0 'probing feedrate


If GetOemLed (825)=0 Then
'Code "G4 P5" Time to get to the z-plate
Code "G31Z-1 F" &ProbeFeed
While IsMoving()
Wend
Code "G4 P0.25"
ZProbePos = GetVar(2002)
Code "G0 Z" &ZProbePos
While IsMoving ()
Wend
Call SetDro (2, PlateThickness)
Code "G4 P0.5" 'Pause for Dro to update.
Code "G0 Z 0.1" 'Change the Z retract height here
Code "(Z axis is now zeroed)"
Code "F" &CurrentFeed
Else
Code "(Plate is grounded, check connection and try again)"
Exit Sub
End If 


Note it has the plate thickness coded into it, and a move of .1 after the touch. You could edit those values to anything you want.

To use this select the offsets screen, then select from the Operator menu the item Edit button script. All the VB buttons will blink, select the 'Set tool offset' button. When the VB window opens delete all the code there and replace it with this code.

Note that this one is going to try to move Z to -1. If you were already below -1 it wouldnt move for a probe cycle. I ought to be more clever and do a relative mode of -1. Maybe someday Ill fix that.

How do you know its ignoring the G4?

try this simple test program:

code "G4 P10"
While Ismoving()
Wend

MsgBox "time done"


when I run it in the script editor there is a 10 second delay before the message box appears.

Are you sure output 5 and 6 are setup correctly? Be sure the port number is 2 if they are on the second parport.