The Vcarve grbl post-processor does not allow multiple tool files. It seems that automatic tool-changing would need to be implemented in the Control GUI, I use Universal G-code Sender (UGS) which has no support for tool-change so far as I know. Not sure whether the Duet GUI has anything? Geoff

 

@sharmstr is working on a tool change post processor - I'm going to have a look at it one day. I would think tool changing is down to the G code - pause job, move to safe position, change tool, resume job, move to WCS zero, etc.
Alex.

 

You are correct in your assumption (at the moment). Things may change (if I can get my head around @sharmstr's new post processor - she has written it for grbl - need to see if it works with Duet). It may prove to be more hassle than it's worth.
Alex.

 

NB @sharmstr's post processor is for Fusion 360.
Alex.

 

If it's just a change to the Post-Processor then it will be an easy job to make an equivalent Vcarve grbl Post-Processor. However I think there is more to do to interact with the user in the GUI. Geoff

 

Agreed, but the pause and resume macros have already been written.
Alex.

 

Alex, I've changed the Vcarve Grbl Post-Processor to do Tool Changes, but my Control, like my Machine is in bits, I'll test it later, to see if it's of any use. Geoff

 

That will be interesting @GeoffH, I don't use Vectric (sticking to Fusion 360) but I will be very interested to see the result.
Alex.

 

I've had a quick look at the Fusion 360 Post and if this works for Vcarve, it should be an easy job to do Fusion 360 also (JavaScript). At the moment, I have a good looking output from the Post-Processor but my Arduino grbl control isn't playing ball yet, probably need to change the config file I think. Geoff

 

Not good news for my Arduino running grbl, it seems that M6 doesn't do anything and M0 has problems after resume. Having looked at others attempting similar things, the GUI (UGS in my case) has to handle the tool change by intercepting the M6 and pause sending further lines to the Arduino until the Manual Tool Change has completed, reset WSO etc.. This isn't something I'm interested in doing at my age, and I haven't found anything that has a solution.
Regarding the Duet, although Vcarve uses the grbl post, it's not grbl firmware so you may have a better chance of tool-changing with a new Post-Processor with M6 etc..., but since I don't have one, I'll give that a miss also. Hopefully @sharmstr will have done it.

Sticking to individual tool files, Geoff

 

I have created a single file like yours I guess where a manual tool-change could take place. That is, pause the program, jog the tool to enable a manual change the tool, jog the tool to touch the part in Z (or onto a slip or automatically onto a touch probe), reset the work co-ordinates and continue. I was able to create a single file with tool change details T2 M6 etc by modifying the Vcarve Post-Processor but unable to get my Arduino that runs grbl to work correctly after the manual tool-change. Others who have attempted similar think that the tool-change must be implemented in the GUI - I now agree with that. Maybe a Duet user, @Alex Chambers who also uses Fusion 360 could try your post to see if a manual tool-change can be achieved with your post-processor change? If it works then I could make the same modifications to the grbl post used in Vcarve for the Duet - Geoff

 

I'm going to have a look at how the Duet does pause and resume. It should be possible to insert a move to do a manual tool change in between.
Alex.

 

This is a bit ambitious for me, but I am going to try to create a single g code system. Tool changes would still be manual. If I don't succeed I hope the process will force me to learn some g code. Will let you know if/when I make any progress.
Alex.

 

PS initially I am not going to try programming for tool Z offsets - I am a beginner at this after all.

 

Good for you Alex, below is a simple test that fails completely on my system,

(First Tool T1 - End Mill (6.35 mm))
T1
G17
G21G90
G92X0.000Y0.000Z10.000
S12000M3
G0X0.000Y0.000Z3.000
G1Z-1.000F500.0
G1X100.000F1500.0
G1Y100.000
G1X0.000
G1Y0.000
G0Z3.000
M5
G0Z10.000
G0X0.000Y0.000
(Tool Change T2 - End Mill (3.175 mm))
T2M00
S12000M03
G90
G0X25.000Y25.000Z3.000
G1Z-1.000F400.0
G1X75.000F1200.0
G1Y75.000
G1X25.000
G1Y25.000
G0Z3.000
M5
G0Z10.000
G0X0.000Y0.000
M30

It cuts a 100mm square followed by a 50mm square. At the tool-change I have an M00, which stops my machine, but after that no restart is possible. Using M06 which is the ISO standard for tool-change, rather than M00, no pause, it's ignored; arguably M00 is good for a manual tool-change. Ignore the G92 line
Maybe you could try the test on the Duet to see what happens. Probably needs more to set the Z after jogging, but I don't get that far.
Geoff

 

I just knew you wasn't a Newbie

 

I am thinking along the lines of nested macros.
1) run first toolpath
2) call re-written pause macro to include move to tool change position (may be WCS x0y0, z up)
3) z probe/set WCS Z 0
4) resume
5) etc, etc
6) programme stop, move to safe position.
As the toolpaths can be called as macros I may only need an overarching program to call the relevant elements in turn.
I'm busy cutting up bits for model buildings today, but might have a closer look at this tomorrow. The Duet firmware already has most of the macros/G code needed.
Alex.

 

You will also find these bits on Ebay for a fraction of the price.
Alex.

 

If you want a 10 degree V bit in a hurry I could post you one or two.
Alex.

 

The cutter that you propose has non standard tool geometry so you would need to create a Form Tool to get the correct simulation, that said you cannot Vcarve with a form tool because a form tool has no tip angle concept.
So the answer to your question is "maybe or don't know", but in any case you must define it as a V bit. The simulation will not show if you have undercut the larger diameter into the pocket walls, if you are relying on cutting with only the small end diameter. Unfortunately Colin, only you can know the answer to this since you haven't given any size details what-so-ever in your post - Geoff