The while IsMoving loop is not needed here, thats only when Gcode is being executed and you need to wait for it to complete. That probably doesnt hurt anything, since there is nothing moving it falls right thru.

Try the if test like this:

IF Cur_Z_Inhibit then
  DoOEMbutton(167)
END IF

TRUE should be 1, but any positive number is OK, so maybe the LED function is returning some other positive number.

Ok, very sorry for the long delay, but here it is.

I called it 2.78T because it is the same as 2.78 except for 2 changes.

1) The main screen has been fixed to test for the path using an old VB command, instead of the newer Mach specific call. It works the same, just more trouble to code. I think I have found all the places that refer to path, but if Ive missed any let me know where and Ill fix them.

2) on the tool select screen the button that displays the tool table cannot show the tool description, it will show as 'unknown'. This is because the Tormach version does not have the new VB call GetToolDesc.

I spoke to John and he expects a new Tormach version will be ready 'later in the summer' He is aware of the need for these VB fixes and they should get added then.

sorry it took so long,

ron ginger

I agree that we need to be able to read basic Gcode. But I do not think one needs to spend days learning what is really trigonometry to be able to write G code. Even the simplest projects are likely to be more accurately done using decent software to generate the  code.

I have made several signs and name plates and obviously they would be impossible without CAM software. For simple tasks, like facing stock or circular pockets or bolt circles then use wizards to generate the code.

Dont waste your time studying G code. You will only write the most trivial of programs by hand. For any interesting work you will need to use some software to generate the code. Pick a good CAM system and lean it.  Any interesting parts will be thousands of line long, no one can write that directly.

For plain mechanical work I use Sheetcam. I recently bought Vetric Vcarve Pro and think its great for the more artistic and sign making work.

First you buy the Flash compiler, for about $700. Then you learn Flash. Then you figure out how Flash is hooked to Mach.

Not as easy as using Screen4.

Because of the way the Screen4 program works it would be very difficult to add all those Z DRO values. This is one example of a job that would fit the new Flash screen capability very well.

Suppose the wizard let you open a CSV file generated by a spreadsheet program. Or for that matter even a text editor if you formatted a file with each line contained the 3 values, separated by commas. That would be quiet easy to implement.

Funny this topic should come alive today. Brian is at the CNC workshop, where among other activities the annual 'emcfest' is in full swing. There were several conversations today with lots of EMC and Mach folks.

EMC has a really nifty 5 axis mill running with full kinematics. Mach has both a mill and lathe running with tool changers.

A good time is being had by all!

Sorry, its been a bit crazy for me, I have not made the new version yet. With luck I will get some time next week while Im at the CNC workshop.

Here is the main part of my tool changer routine. This is a 6 position changer, but you could edit it for more.

tool=getcurrenttool()
'MsgBox ("current tool " & tool)
NewTool= getselectedtool()
'msgbox ("new tool " & NewTool)

if NewTool=tool then
 exit sub
end if

if NewTool>tool then
  steps=Newtool-tool
else
  steps=6 - (tool-NewTool)
End If

If tool Mod 2 Then 'even number
  code "G00 Z 2"
Else
  code "G53 G00 X 0"   'move X to machine home 0
  code "G00 z -2"
End If

'msgbox(" move steps " & steps)

for I=1 to steps
  code "G91 G00 A72"
code "g00 A-12"
code "G90"
While IsMoving()
Wend

next I

The Mod 2 part handles the retract for tool change- the even number slots inmy changer are for boring tools, so I need to retract in Z before a change. The Odd number tools are turning tools, so I want to retract X first.

Changing screens is easy- OEMbutton1-99 call the screen number. Screen 1 is the startup screen, 50 is the TAB screen.

But I dont think there is a DRO to tell the current screen number. Your macro could create a DRO to hold the last number it called. That would get messed up if you used some on-screen button to change the screen, the next time you hit your button it would go to what it thought should be next, not the next from where you are.