[tsomer]

My version, 5.06 produces tool paths that seem to wander around the substrate like a drunken sailer, doing the descender of one letter, then a loop for another, and then rapid transfering diagonaly across the panel for an element of yet another, and so on.

I'm still not in production, and am learning the limitations of my router. In the meantime I'm having some disapointing trials. I'm evidently losing steps on Z, or else accumulating backlash error which is screwing up my work. I expect to have that fixed soon. But this error is magnified by what seems to be arbitrary, random tool path generation. Maybe there is some logic to this, but it's beyond my comprehending.

So, while I'm isolating a fixing this problem, does anyone have any advice for workarounds-- strategies for optimizing tool paths? I've considered setting limit switches close to use them as references, and periodically directing the machine to register to home. This will admittedly generate some error, but it won't be cumulative.

Now,I've tried the obvious solution of clicking regions and generating paths in the sequence I want the machine to run. This method takes forever on my machine, (1800 pentium, 500 Megs Ram) . I may as well cut by hand. I have not tried using the layers feature, and this is a possibility.

Final thought: Could an Alphabet of toolpaths be created in VM, exported to Rhino, configured and reimported to VM to circumvent processor time? Ideas about this and the other thoughts?

Thanks.

Thanks.