Topics

1

VB and the development of wizards / g-code save

« on: June 29, 2010, 10:31:38 AM »

Is there some way to save the g-code that Mach3 has loaded? The situation is that I'm writing a macro that will take some g-code file and adjust certain parameters in it, then feed that to Mach3 (using open/load teachfile). However, sometimes the g-code will originate from another wizard, which would use open/load teachfile itself, so I would need to be able to get to the generated g-code.

2

Machscreen Screen Designer / Tickers

« on: November 29, 2009, 07:34:54 AM »

Not sure if this is a machscreen problem or something else...

If I copy the standard 1024.set and then save it as something else, the tickers no longer work. For instance, on the main screen there is ticker0 next to the reset button which, on startup, displays "Press Reset .... Emergency Mode..." etc. In the saved screenset it just shows 'ticker0' all the time.

However, the 'Error', 'profile' and 'File' labels correctly show messages.

3

General Mach Discussion / Continuation after tool change

« on: September 30, 2007, 09:54:05 PM »

Not sure if I'm doing this the right way, but it used to work for me and now (R2.47) it doesn't:

When a tool change occurs on my mill, I run the spindle up the z-axis to give me a bit of room, then change the tool and re-zero the z-axis by running the spindle down until the tool touches. Most times, I also jog the x- and y-axis to find a nice zero-level part of the job. Once that's done, I click the start cycle button and Mach3 moves to where it was when it stopped for the tool change, then carries on.

At least, it used to. What happens now is that the x- and y-axis are jogged way off to the right/back of where they should be. It seems as if Mach3 assumes we're starting from zero on all axis again. Indeed, if I click the move to zero button before continuing then everything is OK. Even if I then jog the z-axis upwards after the goto zero it still all ends up right.

So it seems to me that something is broken in this bit that wasn't before - Mach3 obviously knows where the axis are, but the start cycle overrides that and thinks wherever we are is zero. Hope that makes sense