Time estimates are just plain weird!

I created a 2D Pocket to flatten my Shapeoko PRO XL by 0.2mm in fusion 360 using my McFly 1" facing bit. Fusion reported it would run for 2h20m. When I loaded the file in Carbide Motion it reported that it would take over 3 hours to complete. When I started the operation, Carbide dropped the estimate to 2h20m like Fusion’s estimate and after about 10 seconds into the actual cutting, Carbide Motion dropped the estimate to 10 minutes which was fairly accurate. What gives with the estimates?
Pierre

Upload your .nc file?

Perhaps we can look into this with you.

Here’s the NC file Will.
Shapeoko PRO Bed Leveling-Removes 0.2mm-2D Pocket2.nc (5.2 KB)
Thx for helping me out.

Why so many different feed rates?

G1 Z5 F2500
Z4.538 F333.33
X198.846 Y210.089 Z4.107 F0.51

Why do you have the machine moving at 0.51 mm/min?

That said, isn’t the solution here to either buy a Subscription or use a different tool?

(When using Fusion for Personal Use, the feedrate of rapid)
(moves is reduced to match the feedrate of cutting moves,)
(which can increase machining time. Unrestricted rapid moves)
(are available with a Fusion Subscription.)


I’m happy about the length of time it took to flatten my bed…10 minutes so I don’t have a need at the moment for a Fusion subscription. I’m a newbie when it comes to machining, so I go with the default values for now. The plunge rate is very slow which is something I’ll look at. The only value I’ve played with is the Cutting Feedrate which has worked out well. Don’t know about the many different feed rates…automatically generated as is the G code.

My question only pertains about why the time estimates vary so much as I go trough the process from Fusion Simulation to loading the NC in Motion, to starting to execute the operation and the final estimate once the operation is underway.

I have been using CC for about 6 years. The time estimates have always been wrong. Usually the estimated time is longer than predicted. I dont think they account for the rapid movements and not for tool changes. Unfortunately that is just the way CC works with CM.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.