# Accuracy solution

**URL:** <https://forums.maslowcnc.com/t/accuracy-solution/24237>\
**Category:** Troubleshooting\
**Tags:** accuracy\
**Created:** [May 28, 2025, 6:41pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237 "2025-05-28T18:41:47Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasB](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/thomasb/32/28287_2.png) [@ThomasB](https://forums.maslowcnc.com/u/ThomasB)\
**Post date:** [May 28, 2025, 6:41pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/1 "2025-05-28T18:41:47Z")

</div>

While setting up my maslow, I noticed there was an accuracy error of about 4mm.

 ![IMG_20250525_201701](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/c/7/c75f0ae7330236ae2e04587b995850ff4e507b74.jpeg)  
 ![IMG_20250525_201710](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/7/2/72cb852ea53f74911500944cbad52b3268f06f3c.jpeg)

It seemed to me that the error was linear in every quadrant of the square.

To compensate for the error I made a program that adjusts all the X-Y coordinates of the NC file into a new NC file.

When I ran the new NC file, the offset error was close to 1mm. (and I think this could get smaller if my measurements were better)

 ![screenshot](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/2/a/2a04b048caf584c44eb922f2bdabecf533f47c0c.png)

I did only 1 cut with this, but for now it seems to work fine.

If anyone is interested, you can find the software here: [https://github.com/tdesign81/Maslow-Post-Processor](https://github.com/tdesign81/Maslow-Post-Processor)

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [May 28, 2025, 8:35pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/2 "2025-05-28T20:35:03Z")

</div>

Nice work!!

There is a version of this built into the machine too

These settings:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/f/0/f0f06681d1671dd2c4b035f680d9cda4d347b4b9.png)

Will let you automatically scale any input gcode linearly automatically.

---

<div class="post-metadata">

**Author:** ![ThomasB](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/thomasb/32/28287_2.png) [@ThomasB](https://forums.maslowcnc.com/u/ThomasB)\
**Post date:** [May 29, 2025, 5:42am UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/3 "2025-05-29T05:42:33Z")

</div>

I know about the scale settings.

But the linear error seems to be different for every quadrant.  
Also there is an error on the X axis when just moving on the Y axis.  
For example:  
If you draw a line on the X axis with y =0  
and you draw a line on the x axis with y=500  
you will see that the lines will drift apart (y).  
So you have to compensate y for x movements too.

I know the adjustments are better done in the maslow but i didnt want to mess around in the firmware.

---

<div class="post-metadata">

**Author:** ![Bhambrew](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bhambrew/32/9966_2.png) [@Bhambrew](https://forums.maslowcnc.com/u/Bhambrew)\
**Post date:** [May 29, 2025, 5:37pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/4 "2025-05-29T17:37:16Z")

</div>

Very cool. What are you using to mark the paper with the M4?

---

<div class="post-metadata">

**Author:** ![ThomasB](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/thomasb/32/28287_2.png) [@ThomasB](https://forums.maslowcnc.com/u/ThomasB)\
**Post date:** [May 29, 2025, 6:14pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/5 "2025-05-29T18:14:35Z")

</div>

A marker diameter 8. It’s not the best, I have to make something better for it.

---

<div class="post-metadata">

**Author:** ![kyleschoen](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/kyleschoen/32/26163_2.png) [@kyleschoen](https://forums.maslowcnc.com/u/kyleschoen)\
**Post date:** [May 29, 2025, 8:17pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/6 "2025-05-29T20:17:01Z")

</div>

I have a few posts on this, but I think this one gets to the heart of the accuracy issue and why it’s not linear: [X & Y Accuracy Analysis: Belt Stretch](https://forums.maslowcnc.com/t/x-y-accuracy-analysis-belt-stretch/23996)

I’ve had to take a break from this research, but next up I want to work with @bar to create a setting in the software that can compensate for belt stretch and keep testing. Hopefully I can get back to it soon!

---

<div class="post-metadata">

**Author:** ![Waldo-cnc](https://avatars.discourse-cdn.com/v4/letter/w/3ab097/32.png) [@Waldo-cnc](https://forums.maslowcnc.com/u/Waldo-cnc)\
**Post date:** [June 3, 2025, 3:53pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/7 "2025-06-03T15:53:37Z")

</div>

Hi all,

Question about the x and y scaling option:  
I ran my first cut yesterday. Cut out a rectangle of 2000mmx38.6mm  
Y isn’t off, but the x measured 1982mm after cutting. What value do I enter into scale x window to compensate?  
Do I enter the scaled value 1982/2000x100=99,1 (0.991) or 2000/1982x100=100,908 (1.009)

My 3D printer (klipper/fluidd) asks for the first value to account for filament shrinkage and automatically compensates so the dimensions are accurate again.

Thanks!!

 ![IMG_2889](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/1/1/11bfcbe551e8bc6b2839900a3c234e93383ebf43.jpeg)

---

<div class="post-metadata">

**Author:** ![Dano](https://avatars.discourse-cdn.com/v4/letter/d/e0b2c6/32.png) [@Dano](https://forums.maslowcnc.com/u/Dano)\
**Post date:** [June 5, 2025, 10:08pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/8 "2025-06-05T22:08:38Z")

</div>

I think you want the 1.009 value a you are trying to increase size. But I’m not 100.009% certain.

Dano

---

<div class="post-metadata">

**Author:** ![Waldo-cnc](https://avatars.discourse-cdn.com/v4/letter/w/3ab097/32.png) [@Waldo-cnc](https://forums.maslowcnc.com/u/Waldo-cnc)\
**Post date:** [June 6, 2025, 6:15am UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/9 "2025-06-06T06:15:30Z")

</div>

🤣 Thanks Dano!  
I’m just going to try that and see what happens!!  
👊🏼

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [June 6, 2025, 5:59pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/10 "2025-06-06T17:59:43Z")

</div>

I’m sorry for the slow reply!

The input gcode will be scaled by that value so since your part is coming out smaller than we want it to I think that 1.009 is in fact correct.

---

<div class="post-metadata">

**Author:** ![Waldo-cnc](https://avatars.discourse-cdn.com/v4/letter/w/3ab097/32.png) [@Waldo-cnc](https://forums.maslowcnc.com/u/Waldo-cnc)\
**Post date:** [June 8, 2025, 3:39pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/11 "2025-06-08T15:39:46Z")

</div>

X axis Scale correction 1.009 worked out fine!  
Designed a quick test stool in Fusion and let Maslow work its magic!  
I set up the slots and pockets with a 0.1mm tolerance. For the seat pockets that turned out a bit tight. Had to do some manual “post processing” to make ik fit. But for a first project I am more than happy with the results!

 ![IMG_2938](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/b/2/b2e70d7919e0560ef3b2c1ccfc4828cab3ce92b0.jpeg)  
 ![IMG_2941](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/b/6/b6b378d0f11344734e57349cc2f1f3666f5c22e4.jpeg)

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [June 9, 2025, 3:54pm UTC](https://forums.maslowcnc.com/t/accuracy-solution/24237/12 "2025-06-09T15:54:08Z")

</div>

Excellent work! I’m loving following along with your exploring of how we can improve the system accuracy, but it’s also good to see that you are able to use the machine as is too 😁
