My machine is 900mm x 900mm x 1500mm.
Manually from the mdi it moves the correct distances. G0 X30 U30 moves the X and U axes 30mm. I generate Gcode that looks right and shows dimensions of 40mm, 50mm etc but when I see it go to those, it moves 400 and 500.
The way we caught it the first time was my oldest son and I were calibrating the scales on the machine. I'd tell him "Take the X and U axes 100mm." He'd do it through the mdi (G0 X100 U100) and I'd measure, calc the distance it was off on my calculator and tell him to adjust scaling in the ini file, save, reload and retry. All went as you would expect and we had it nailing the distances.
Then we loaded up a very small constant chord wing test with 40mm chord. It would have been a useless wing but I wanted something to prove it was reading my GCode that looked like a wing. It moved way past of the small piece of foam we had and tried to cut it as a 400mm chord.
I thought I had screwed up measuring or my son who was running the machine and entering scaling in the ini had screwed up his saves. Nope. All looked right and we performed our scaling checks and again and then confirmed the GCode size error again.
My wife is also an engineer with so I had her stand and watch. She thought she caught a few things we did wrong but each time the numbers were right until we go to automatically cut code.
I think it has to be something in the GCode but I can't see it.
Like I said though, other than that (and a old shaft coupler we broke yesterday) it is running really well so I will probably just run it a while. Usually I find issues where I did something stupid that way.
