What is your screen size? Do you have the check on Config/General set to auto enlarge screens?

The wizards have no control over the screen size, thats up to mach to re-size them when they open.

One supplier of kits for model machine tools is PM Research, http://www.pmresearchinc.com/store/home.php?cat=6

They offer many machines, and also several model steam engines. Many of them are aluminum castings, they also offer a couple steam engines in brass. They also have an extensive line of model parts, like pipe fittings, pressure gauges, etc. Nice people to do business, with, always exhibit at the major model engineering shows.

I will fix a 2.79T version as soon as I can. This version will run on Tormach but it will get an error when you try to open the tool table, and if you try to edit the process list.

Version 2.79 is ready for test. The main change in this version is to handle the metric tool units correctly. Old versions were doing a double conversion of metric values to english resulting in bad values for Feed rate.

I have also displayed the units LEDs on every page. You select a unit in the first screen when you select material. From then on all units are assumed to be in the chosen system.

But when you select a tool you may indicate the tool is in the other units. When you calculate chip load and feed rate they will be shown in the selected units, but when you click Continue to move to the next screen the tool values will be converted to the native units. A message Box pops up to tell you it made a conversion. I may eliminate that box if its to annoying.

Consider this a test version for a while.

Download the zip file and unpack it into Mach3/Addons/Newfangled

have fun, let me know if there are errors.

Have you checked to see that INPUT 4 is not always active, or is reversed in active low? Does OUTPUT1 go on?

I dont see anything to cause the code to pause where you have the  'this is where I want to jog' line. Do you expect to use the regular jog keys at that time?

Indeed, it is an important feature of the NFS wizards that you can run several of them in sequence and build a complex program.  If you did not want one of the parts there is a way to list all the parts and to delete anyone of them. There are buttons to list and edit near the bottom of the main menu screen.

Ok, I talked to Brian and I understand why he put the G98 mode on the drill cycles. It is a safer option. If you use G99 the tool only comes up to the retract height between moves.  With G98 it comes up to either retract or the rapid height, whichever is higher. That can take more time, but if you want to get fast, and are sure the retract height is high enough, then simply program the Rapid height to be something like .001 higher that retract. That will operate exactly like the G99 option.

Since wizards are meant to be simple, and for beginners we always try to make them as safe as possible, so this one will stay with G98

Are you sure you are using the 2 Z fields correctly?

Traverse height is a safe height, meant to be OK to  make any XY move, it should be above clamps, etc.

Rapid Height should probably be called something like Retract height. It is the R word in the drill cycle.

Moving the Z down to the Traverse height before moving to the first XY location will be safe if you have used a safe Traverse height.

Yes, the wizard generates a main file called NewProgram.tap that is placed in the Gcode folder, and Index.tap that is placed in the subroutine folder.

You can simply rename the files using Windows Explorer to whatever you like. You will have to also edit the NewProgram.tap file to call whatever name you give to the index file. Then simply use the Load Gcode button and choose the file. When it runs mach will find the subroutine.

The problem is that the wizard generates some A axis moves, in a subroutine and the mach display code does not handle A axis moves. When Brian makes the graphic changes he is working on this may change.

The wizard generates working code, you just dont get the toolpath display