Hello does anyone else have this issue?
Using altmill, when using any other workspace other than 1 and I use the resume from line, irregardless of the workspace selected it used workspace 1 zeroes.
Ie I have 4 workspaces, had to stop to rehome the w2 after a bit change. On the resume at line the machine moved over to workspace 1 and ran. It is repeatable. 1.48
Any ideas?
If anything sent code M2(program end) that would set your workspace to 1.
M2 does all of the following:
- Change from Auto mode to MDI mode.
- Origin offsets are set to the default (like G54).
- Selected plane is set to XY plane (like G17).
- Distance mode is set to absolute mode (like G90).
- Feed rate mode is set to units per minute (like G94).
- Feed and speed overrides are set to ON (like M48).
- Cutter compensation is turned off (like G40).
- The spindle is stopped (like M5).
- The current motion mode is set to feed (like G1).
- Coolant is turned off (like M9).
Was there a reason that you had to home after a bit change? Unless something abnormal happened you should only have to probe Z after a bit change, assuming that the origin point of the tool path didn’t change.
It could be a bug, but I thought I would mention the non-bug possibility that I could think of.
Thanks for the response michael.
I guess I did not use the correct terminology, I did not home after my too change. I rezero my z.
Ie
I stop prog, raise the z, change the bit, confirm workspace 2, zero the z, confirm workspace is set to 2. Then start from line.
At this point the machine begins work from wspace 1
If I restart my job (just hit start instead) the proper workspace ie w space 2 is used, but I have to recarve everything
The bad thing here is that the first move is dropping the z to workspace 1 work height then screaming over to the workspace 1 in rapid. If you’re spindle is over the workspace 2 part, you can guess what happens from there
Reapeatably
2 Likes
EDIT: I was thinking of another thread, my bad. Maybe I should have had my coffee before posting 
If you use separate tool paths you will definitely need be careful of the workspace because M2 is sent at the end of program.
Any chance you could post the Gcode?
Yeah, no problem. they are simple clear toolpaths, for cleaning the plug from an inlay. 1/4" upcut
i’d post the vcarves file but i din’t save 'em
clear_1-Pocket 1.gcode (3.2 KB)
clear2_1-Pocket 1.gcode (8.4 KB)
gerry
In your post, you talked about 4 workspaces and a tool change? Cant see that in the gcode.
No I have just been using the workspaces to hold my zeroes so I don’t have to get my probe out between every job
I put my 4 boards in, zero each board in a workspace and just run the job in the workspace it was zeroed in. No need to adjust in my gcode as they are separate files.
I have just adjusted my order of operations to always use workspace 1 for work and use the other workspaces to only hold zeros as a placeholder for the coordinates