First thing to be aware of is the difference between vectors and pixels. Pixels are the little cubes that are assigned various colours, or shades of grey that when combined side by side, make up any digital image. Pixels are easy to see if you zoom way-way in on a picture on the computer. Resolution defines how many pixels occupy a given space, usually Pixels Per Inch or PPI.
Vectors are precise mathematical lines and curves, that have no loss of quality when an image is scaled up or down.
So let's get down to business!!!!
This whole process only works if you keep your Aspire components separate. There's really no need for us to bake the text into the model. In fact I live by the the motto "I only bake when I have to" This motto applies at home as well ;)
I started my model at 24"X24" in Aspire, with the resolution set to standard (the lowest available option) It's always advisable to have the job size set to the smallest size that will fit the project. A 2" X 2" model will be very, very rough if the job dimension is 4' X8' with a standard resolution setting. This is because the pixels will be very large, compared to a job size of 2" X 2", where the pixels will be a whole lot smaller.
Heres the result of machining the whole 24" X 24" model. This was done with a 1/4" cutter with a 9% stepover. Looks perfectly acceptable on the log model....................
I'm gonna let Aspire, clean this up for me, and on our Techno cnc, it will be 100 times faster than by hand, and WAY more accurate! Re-toolpathing this whole model with an 1/8" cutter is unreasonable as well, as most of the model is perfectly fine
original text vectors that were used to create the 3D text portion of our model.
An important point to remember is that in Aspire, a 3D toolpath is calculated to the CENTRE of the cutter. If I had used the original text vectors as a machining border, the cutter would have stopped at the point it is in the above image, the centre of the cutter right on the vector.
So knowing that the calculations are done to the centre of the cutter, we can plan accordingly!
So in the image above, the dashed line represents the centre of the cutter. This is kind of important to illustrate, because as the cutter will climb up and over the vertical wall to machine the text portion, it's going to leave a radius due to the ballnose cutter having a rounded tip.
We are going to machine of the radius around the text that was left by the .250" ballnose cutter. This will leave us a clean transitition between the woodgrain and the text. I'm going to some extremes in this tutorial, and going to jump right to a .0625" ballnose cutter for the cleanup. That is represented by the smaller circle.
I have dragged my .0625" circle inside the original vector. This looks like a good location to clean off those giant jagged edges as the cutter makes it's way around the text. We now just need to define that location in Aspire. As I said before, 3D toolpaths are calculated to the CENTRE of the cutter.
With those vectors selected, I can now set up for machining.
This is where keeping the text component separate is important. We are going to hide the text component in the component tree. With this component hidden, Aspire doesn't "see" it, and therefore ignores it. If we don't hide it, Aspire will machine all those jagged edges again, making the text still look bad, and that's what were fixing. But as the woodgrain is still visible, it will protect that portion of our model. And as we have already run the .250" cutter, the text now exists physically on our model.
I chose the .0625" ballnose and assigned an OFFSET toolpath strategy. I am using an offset strategy as it will drive the cutter around the vectors smoothly, following each shape precicely, as opposed to rastering back and forth.
TAA DAA! This is text I can live with. It will require NO additional cleanup by hand, and looks fabulous!
This seems like a long process, but it isn't in reality. You just basically offset your original vectors approx half of each cutter your using, hide the component your cleaning up, and assign an offset strategy. DONE!
This process lets you model at lower resolutions (which can speed up operations on slower pc's) And gives you great results.