In CC PRO 815:
1hr 55 min.
CM 644 Preview screen:
2hr 31 min.
CM 644 Run screen at start of job:
1 hr 56 min
Even the two time in CM aren’t close to each other. I’ll update this once I have the actual run time.
1hr 55 min.
1 hr 56 min
Your post reminds me of the proverb,“A man with one watch, always knows what time it is. A man with two watches, never knows what time it is.”
I’m sure they are updating Carbide Create more frequently than Carbide Motion, more tweaking of the time “estimating” in carbide create is happening, than in carbide motion.
1 Like
Time = Distance / Velocity. I’m surprised the result isn’t the same in 2 applications created by the same vendor.
Perhaps CM knows the rapid feedrate, where CC may not. Simple solution, allow us to enter the max/rapid feedrate in CC when we change it on the machine.
discrepancies between calculated and actual cutting times are common. The calculation can’t know what the toolchange time is. It also doesn’t know where the tool is starting before making the first move. There could also be a variance in actual vs programmed feedrates.
Time estimates usually don’t consider acceleration/deceleration either.
So I would never expect estimated times to be precise. But a reasonable accuracy is possible.
2 Likes
The machine also doesn’t go from 0 IPM to 100 IPM instantly. There is time for it to accelerate that neither CC or CM account for.