LinuxCNC with DevFoamWing

Been thinking about this . Have you checked the cad to see if it is set to units = CM as that would cause the problem between CM and MM exactly 10

hi
the G-code is right
alsthru it is not for a XY;UV as it is parallell

PLEASE provide the INI and hal to get a better problem definition
i testet it on my Foam

Probably worse, they are G1s

G1U21.0104V18.9463X20.8698Y61.2523
G1U21.9144V19.1432X21.7883Y61.3637
G1U22.8202V19.3391X22.7084Y61.4738
G1U23.7260V19.5351X23.6286Y61.5840
G1U24.6306V19.7293X24.5474Y61.6926
G1U25.5352V19.9236X25.4663Y61.8013
G1U26.4414V20.1168X26.3866Y61.9088
G1U27.3463V20.3098X27.3056Y62.0161
G1U28.2527V20.5019X28.2260Y62.1224
G1U29.1579V20.6937X29.1451Y62.2286
G1U30.0646V20.8846X30.0658Y62.3336
G1U30.9715V21.0754X30.9866Y62.4386
G1U31.8772V21.2646X31.9060Y62.5421
G1U32.7843V21.4540X32.8269Y62.6457
G1U33.6903V21.6419X33.7465Y62.7478
G1U34.5965V21.8296X34.6663Y62.8498
G1U35.5027V22.0173X35.5860Y62.9517
G1U36.4102V22.2039X36.5071Y63.0525
G1U37.3179V22.3905X37.4283Y63.1532
G1U38.2244V22.5755X38.3482Y63.2524

I thought the CM thing too but can't find anything that looks like that anywhere. I will get the ini file and hal posted soon. I lost my network out to the shop so I need to grab a thumb drive and run out there to get it.

You are correct. I missed that. Other than that and the scaling being a little odd x10 it is running really well. I think we will run it a while and see what shakes out.

Thank you all for helping get to this point.

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.