Closed GoogleCodeExporter closed 8 years ago
sorry, I hadn't read the CuttingTool.h properly. It seems to be purely for the
Drilling operation. Maybe it should be renamed DrillingTool, or DrillingPoints?
Original comment by danhe...@gmail.com
on 14 Jun 2009 at 10:42
or reading the wiki page, I think it should be able to be used for all kinds of
operations, so it should probably not have a list of points, which are just for
drilling.
Original comment by danhe...@gmail.com
on 14 Jun 2009 at 10:50
The CuttingTool object doesn't have a list of points. That's the Drilling
object
that contains that. The CuttingTool object really should represent JUST the
tool
being used. The GCode it produces can prompt me to put another drill bit in the
chuck when the tool's diameter changes.
My intention was that the CuttingTool object would be used for all tool table
entries. I would, one day, like to see a simulation of an Adaptive Roughing
path
combine the volumes produced by the CuttingTool definition with the paths
produced by
the GCode to show (visually) what the material will look like at the end of
machining. This sort of visualisation may be used to adapt 'repetition
distances'
used to generate the tool paths. i.e. how far to step across between adjacent
paths.
I expect the CuttingTool class to expand to describe the tool's physical attributes
(cutting area, tool holder area etc.) eventually.
Original comment by David.Ni...@gmail.com
on 15 Jun 2009 at 3:36
I have done this.
I have added "tools" the same as "operations". When you press the "new cutting
tool"
button, the new tool goes in "tools".
See this picture
http://2.bp.blogspot.com/_lpgMldGi1O4/SjYKwYR8qNI/AAAAAAAAAKY/19VvW21MfDE/s1600/
HeeksCNC+drilling.png
Original comment by danhe...@gmail.com
on 15 Jun 2009 at 8:49
Original issue reported on code.google.com by
danhe...@gmail.com
on 14 Jun 2009 at 9:45