It would be nice if in the tool menu you could type the name of the tool with the tool number so when the display says install tool 2 it would say ie Install tool 2 - 1/8 downcut
A partial solution is to change the header in the post-processor to put the info in the gcode which you can review after loading the file. For example, in Vectric post processor I have:
POST_NAME = “RealtimeCNC Mod Toolchange(inch) (*.ngc)”
FILE_EXTENSION = “ngc”
SUBSTITUTE = “({)}”
UNITS = “INCHES”…
begin REVISION_COMMENT
“%”
“(VECTRIC POST REVISION)”
“([REVISION])”
“([POST_NAME])”±--------------------------------------------------
- Commands output at the start of the file
±--------------------------------------------------begin HEADER
“(Tool Information:)”
“(Tool: [T])”
“(Tool Name: [TOOLNAME])”
“(Tool Diameter: [TDIA])”
“(Spindle: [S])”
“(Feed: [F])”
“(Stock Information:)”
“(X: [XLENGTH])”
“(Y: [YLENGTH])”
“(Z: [ZLENGTH])”
“(Safe Height: [SAFEZ])”…
After loading a file I can readily see which tool is going to be used. Trying to remember all the tool numbers is a RPITA, especially at my age.
I seldom combine tool paths for this very reason and opt instead to save each toolpath separately so I can verify. I put in a request to look for this data and display it in addition to the tool number but it will most likely never float to top of feature list”.
Hope that helps.
P.S. The SUBSTITUTE is needed because some databases use embedded parenthesis which the controller will choke on because the gcode parser is not robust enough to handle comments correctly. E.G. “End Mill (1/4) Downcut” is translated to “End Mill {1/4} Downcut” so that in the gcode it reads (Tool Name: End Mill {1/4} Downcut)
I love this idea. I have added it to our feature request list for a future software version.
Thats great cant wait to see it come around!!!