# Estimated job time in V carve not even close

**URL:** <https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281>\
**Category:** MillMage Software Questions\
**Created:** [September 4, 2026, 8:39pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281 "2026-09-04T20:39:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![wanderingtruckie](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/wanderingtruckie/32/107530_2.png) [@wanderingtruckie](https://forum.lightburnsoftware.com/u/wanderingtruckie)\
**Post date:** [September 4, 2026, 8:39pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/1 "2026-09-04T20:39:42Z")

</div>

this only seems to happen with V carve total time estimated in preview 2.30.32

 ![time](https://forum.lightburnsoftware.com/uploads/default/original/3X/3/8/385c73eb1ed4bb9924eeaf0764da10591c80ceb2.jpeg)

actual job time 4 hrs 57min

even after going into additional setting and clicking read from controller prior to start of job nothing changes

if I’m say doing profile cuts of cabinetry, finish job time is pretty close to estimated time

is this something that cant be computed more closely , due to complexity of how v carve operates ?

or could it be my controller isn’t communicating with MM and updating simulating settings

ive had the odd v carve that has run about 30 min over, which i expect but double the estimated time doesn’t seem right

makes it hard to work out when to start a job , due to over run time

---

<div class="post-metadata">

**Author:** ![misken](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/misken/32/47593_2.png) [@misken](https://forum.lightburnsoftware.com/u/misken)\
**Post date:** [September 4, 2026, 9:09pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/2 "2026-09-04T21:09:12Z")

</div>

Maybe check out this:

> [@VIDEO: Quick Tip - Accurate Job Simulation Times](https://forum.lightburnsoftware.com/t/video-quick-tip-accurate-job-simulation-times/191918):
>
> [image] For CNC machines running GRBL firmware, MillMage lets you import machine firmware speed settings directly from your controller to ensure operation run times are as accurate as possible. If your machine is running a different firmware, you can enter these values manually. Documentation on Additional Settings: [Device Settings: Additional Settings - MillMage Documentation](https://docs.millmagesoftware.com/0.8/Reference/DeviceSettings/AdditionalSettings/) Download MillMage here: [Home - MillMage Documentation](https://docs.millmagesoftware.com/latest/)

---

<div class="post-metadata">

**Author:** ![parsec](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/parsec/32/118933_2.png) [@parsec](https://forum.lightburnsoftware.com/u/parsec)\
**Post date:** [September 4, 2026, 9:15pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/3 "2026-09-04T21:15:46Z")

</div>

Maybe lowering the Z simulation speed/acceleration .

---

<div class="post-metadata">

**Author:** ![Colin](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/colin/32/41542_2.png) [@Colin](https://forum.lightburnsoftware.com/u/Colin)\
**Post date:** [September 4, 2026, 11:13pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/4 "2026-09-04T23:13:57Z")

</div>

There are more variables that MM’s sim can possibly account for, so scaling as per the above video is probably a good idea. I’ve got a 8hr job on the machine right now and I’m really hoping it’s more like a 4 hour job 😁

---

<div class="post-metadata">

**Author:** ![wanderingtruckie](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/wanderingtruckie/32/107530_2.png) [@wanderingtruckie](https://forum.lightburnsoftware.com/u/wanderingtruckie)\
**Post date:** [September 5, 2026, 12:07am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/5 "2026-09-05T00:07:04Z")

</div>

I have done all of that prior to creating topic , my machine is gbrl

---

<div class="post-metadata">

**Author:** ![wanderingtruckie](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/wanderingtruckie/32/107530_2.png) [@wanderingtruckie](https://forum.lightburnsoftware.com/u/wanderingtruckie)\
**Post date:** [September 5, 2026, 12:19am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/6 "2026-09-05T00:19:41Z")

</div>

though that might be the case as the image is very detailed, i generally allow an hours grace when planning my day , that one just threw a spanner in the works being 2 half hrs longer,

hence asking as just updated to RC7 , checking there’s not an issue with control reader as previously have been around 30 min over of estimated times of v carves

---

<div class="post-metadata">

**Author:** ![misken](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/misken/32/47593_2.png) [@misken](https://forum.lightburnsoftware.com/u/misken)\
**Post date:** [September 5, 2026, 7:24am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/7 "2026-09-05T07:24:52Z")

</div>

Did you check that the firmware values are realistic? It’s very common with grbl lasers that the values given in the specifications are just insane and the machines never reach it. Therefore Simulation times are wrong.  
E.g. if your firmware has 1000mm/min^2 as acceleration, but due to the heavy motor the true value is 500, simulation will always be wrong, no matter if you read the parameters or not.  
CNC are much slower overall, so this might not be the case that often, but still important to be checked.

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 6, 2026, 1:08am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/8 "2026-09-06T01:08:19Z")

</div>

> [@misken](#):
>
> no matter if you read the parameters or not.

It says in the box that these are just for the simulation. That means you can make any of them anything you want. Just don’t “read from controller” if you fine tune them for good estimates. 😁

---

<div class="post-metadata">

**Author:** ![misken](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/misken/32/47593_2.png) [@misken](https://forum.lightburnsoftware.com/u/misken)\
**Post date:** [September 6, 2026, 9:34am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/9 "2026-09-06T09:34:00Z")

</div>

I meant, messing around with the simulation parameters doesn’t make much sense, so I recommend changing the firmware parameters (and updating the simulation parameters each time) until the processing time fits. Then the system is set up correctly.

---

<div class="post-metadata">

**Author:** ![Gazman](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/g/ee7513/32.png) [@Gazman](https://forum.lightburnsoftware.com/u/Gazman)\
**Post date:** [September 6, 2026, 10:06am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/10 "2026-09-06T10:06:09Z")

</div>

Would it be too simplistic for me to suggest running a small job, compare the percentage difference between the MM time prediction and the real world time that the job took then change the ‘Global speed scale’ percentage to compensate?

I’ve just noticed that you have noted the projection time and the actual time the job took, making a 66% difference. I would change the global speed scale by this percentage and then the projection time should match?

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 6, 2026, 12:47pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/11 "2026-09-06T12:47:50Z")

</div>

> [@Gazman](#):
>
> change the global speed scale by this percentage and then the projection time should match

You are looking for a quick answer, and there is none. Every machine is different so you will have to experiment. On mine, vectors were very close, but images were 2x to 3x longer. Yet when I got done, both boxes contained 85% to give me 90% accuracy on time estimates for projects large and small.

I believe @misken has the correct answer if you want the best accuracy but remember, it is still an estimate.  
firmware = GRBL, simulation = MillMage.

> [@misken](#):
>
> changing the firmware parameters (and updating the simulation parameters each time) until the processing time fits

---

<div class="post-metadata">

**Author:** ![Gazman](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/g/ee7513/32.png) [@Gazman](https://forum.lightburnsoftware.com/u/Gazman)\
**Post date:** [September 6, 2026, 1:31pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/12 "2026-09-06T13:31:42Z")

</div>

> [@MikeyH](#):
>
> You are looking for a quick answer, and there is none. Every machine is different so you will have to experiment. On mine, vectors were very close, but images were 2x to 3x longer. Yet when I got done, both boxes contained 85% to give me 90% accuracy on time estimates for projects large and small

I wasn’t looking for a quick answer but rather a logical approach, whist you are correct in saying that all machines are different this is the exact reason I chose my logic as what I suggested should work in every individuals setups/scenarios.

Whilst I do not rely on AI for obvious reasons this is what AI thought of my logic…maybe I’m as useless as AI 🤣

Step 1: Read Firmware Parameters (GRBL Machines)

If your CNC runs on GRBL, MillMage can pull your hardware’s actual max speeds and acceleration rates directly:

1. Go to **CNC Tools** → **Device Settings** (or click the **Device Settings** gear icon in the toolbar).

2. Click the **Additional Settings** tab. 

3. Click **Read From Controller**. This imports your machine’s actual firmware settings (`$110-$112` for max speeds, `$120-$122` for acceleration) directly into the simulation model.

### Step 2: Manually Fine-Tune with Speed Scale

Even with firmware parameters loaded, complex 3D toolpaths (like V-carving or detailed pocketing) often take longer due to constant direction changes and Z-axis ramps. You can use the scale modifiers in the **Additional Settings** tab to force the simulation to match reality:

- **Cut Speed Scale:** Scales cut-speed estimates by a percentage. 

- **Global Speed Scale:** Scales all movement calculations across the entire project by a percentage .

**How to calculate your multiplier:**

- _Example:_ If MillMage estimates a pocketing job will take **30 minutes** , but it actually takes **45 minutes** on the machine:

- Entering **`66%`** or **`67%`** into your **Global Speed Scale** will force the software to project the realistic 45-minute completion time on future jobs.

---

<div class="post-metadata">

**Author:** ![parsec](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/parsec/32/118933_2.png) [@parsec](https://forum.lightburnsoftware.com/u/parsec)\
**Post date:** [September 6, 2026, 1:40pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/13 "2026-09-06T13:40:53Z")

</div>

> [@Gazman](#):
>
> 1. V-carves or high-retract jobs are still drifting, manually lower the **Z Axis Max Speed** or **Z Axis Acceleration** values in **Additional Settings**. (Adjusting these simulation-only

What I said with NI.

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 6, 2026, 1:47pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/14 "2026-09-06T13:47:49Z")

</div>

That writeup seems to be pretty much on target. In fact, it seems to be the exact words I have read in some postings! 🤣

> [@Gazman](#):
>
> what I suggested should work in every individuals setups/scenarios

To be honest, good luck with that. My final setting with 85% challenges the “every” for sure.

Anyhow, I think we all have enough information to improve the estimates for our equipment. I know I need to revisit my settings.

---

<div class="post-metadata">

**Author:** ![Gazman](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/g/ee7513/32.png) [@Gazman](https://forum.lightburnsoftware.com/u/Gazman)\
**Post date:** [September 6, 2026, 5:56pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/15 "2026-09-06T17:56:31Z")

</div>

I have to say though, I have tried all sorts of adjustments in the simulation settings and just cannot get the simulation timing to alter more than 1.5 minutes either way for a 22 minute job for example 🤔

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 6, 2026, 7:24pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/16 "2026-09-06T19:24:12Z")

</div>

> [@Gazman](#):
>
> cannot get the simulation timing to alter more than 1.5 minutes either way

Can you upload your **.mage** file so I can look at it. Also include your **$$** GRBL parameters and brand of machine or controller. Maybe not the same machine, but I may be able to spot something running it on my 3018 machine. I am willing to try. 😁

---

<div class="post-metadata">

**Author:** ![wanderingtruckie](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/wanderingtruckie/32/107530_2.png) [@wanderingtruckie](https://forum.lightburnsoftware.com/u/wanderingtruckie)\
**Post date:** [September 6, 2026, 7:48pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/17 "2026-09-06T19:48:54Z")

</div>

get what your saying and agree,for the most part except when i run pockets , profiles etc they are all pretty dam close to the estimated time

---

<div class="post-metadata">

**Author:** ![wanderingtruckie](https://forum.lightburnsoftware.com/user_avatar/forum.lightburnsoftware.com/wanderingtruckie/32/107530_2.png) [@wanderingtruckie](https://forum.lightburnsoftware.com/u/wanderingtruckie)\
**Post date:** [September 6, 2026, 7:54pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/18 "2026-09-06T19:54:04Z")

</div>

> [@Gazman](#):
>
> projection time and the actual time the job took, making a 66% difference.

where do you get 66% from 457 -230 is 50 %

---

<div class="post-metadata">

**Author:** ![MikeyH](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/m/43a26b/32.png) [@MikeyH](https://forum.lightburnsoftware.com/u/MikeyH)\
**Post date:** [September 6, 2026, 8:27pm UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/19 "2026-09-06T20:27:52Z")

</div>

> [@wanderingtruckie](#):
>
> 457 -230 is 50 %

4:57 / 2:30 = 2, not 0.5 I think.😳

---

<div class="post-metadata">

**Author:** ![Gazman](https://forum.lightburnsoftware.com/letter_avatar_proxy/v4/letter/g/ee7513/32.png) [@Gazman](https://forum.lightburnsoftware.com/u/Gazman)\
**Post date:** [September 7, 2026, 6:52am UTC](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281/20 "2026-09-07T06:52:56Z")

</div>

Well spotted and my mistake as somehow my calculation gave the result as an average.

[Next page](https://forum.lightburnsoftware.com/t/estimated-job-time-in-v-carve-not-even-close/192281.md?page=2)
