Originally Posted by
peteeng
Hi all & sundry - I have been looking at how to get UCCNC to run faster if anyone has insights or suggestions please comment. Currently Scoot will reach 5000mm/min in a straight line (its current max vel setting) but around corners/curves it slows to 1000-1200mm/min. My aim is to get it to run at 4000-5000mm/min everywhere. My usual workflow is design in rhino, export as dxf, import to uccnc. I'm about to change this to Fusion360 so will be interesting to see if there is any delta. When I parse the curves through dxf I usually set the polyline length to 1-2mm depends on what I'm doing . On some small txt it has to be smaller. So instead of randomly plugging in numbers I drew up a CAD dia of 75mm and poly-lined it to 2mm lengths, then looked at it using the tolerances set in UCCNC. So to start with the look ahead is 200 lines and this means its looking 200x2=400mm ahead,,, not much point in that as the linear addition length is 5mm so its making decisions only 2-3 steps away. The linear max error is set at 0.25mm so any point or interpolated line/point can't be more then 0.25mm from the G code points. So I created a +/-0.25mm road along the Dia75mm points. Being an arc I could also set the arc radius tolerance to 0.25mm to achieve the same thing. Now the linear addition length is set to 5mm so that's the outer radius. So the planner adds the first two segments and checks if its on the roadway, then the 3 segments to see if its on the roadway and in this case this exceeds the 5mm addition length so it stops. So I expect its jumping every other step. Now if I add out to 4 steps the path is still in the roadway so instead of setting my parsing to 2mm I could set it to 9mm and it would still be in the 0.25mm tolerance. So I shall set this up and do a test cut to see what happens. Hopefully by using 8-10mm segments it runs faster. Then I'll have to see what F360 does... Peter