I have a fine line automation CNC Machine That I built I have set it up two times. The first times when I measured with a steel rule and  used the Settings/set steps per unit I got it close and was able to air carve the road runner.

I then made a dust hood with cut2d and that worked. I then tried my hand with the tutorials for cut2d and made a sign. simple one with year 1982 and that was also close.

I saw the tutorials on zeroing with a PC board and clip and got that to work.

I then worked on tweaking the rollers and taking up some slop I worked with the dial indicator and was able to get real accurate, it surprised me how accurate this thing is.

Then I loaded in the same file from cut2d and everything went to the dumper. When I moved the z  axis with the MDI .125. The others where also off. If I restart the mach3 program it was back to where it should be.

Am I saving the g-code with the correct Post Processor?
                                       Mach2/3 Arcs(*.txt) 
I did read something about that but I an using (I think) everything the same as before.

Anyone have a clue?

JR

Could it have something to do with metric and imperial as 0.125 x 25.4 is close to the movement you are seeing.

Hood

Hood,
I don't know just getting started. I looked at the .pp file and it looks like it can be changed. I removed the (Mach2/3postprocessor)  line by putting a + at the start of the line. and I noted N20G00G20G17G20G90G40G49G80 and the next line is N30G70.  so
G00 = Rapid positioning
G20 = inches
G17 = XY plane
G20 = inches again
G90 = Absolute distance mode

G40 = Cancel cutting radius compensation
G49 = Cancel tool length offset
G80 = Cancel motion mode
and then on the next line
G70 = inches again

Don't know why all the inches that's all in the header of the post processor file but until I know more I'm not going to remove anything. I did put that other line back in but I don't think it does anything. I guess cute2d want to make sure it's in inches. The pp files are in cute2d but I just don't know enough yet hopping someone has had this happen and can tell us how to fix it. Not even sure if it's cure2d problem or mach3.
JR

Do the DROs show the 3.3125 or is it just the axis that moves that and the DROs read 0.125?

Hood

Hood,
The dro doesn't sow it it is just the movement. the dro says .125 but movement is around 3 3/8 inch.
JR

mmmmmmm thats going to be a hard one to test in simulation as I will have no idea of the distance the axis would move
If you want attach your xml and code and I will see if I can find an issue.
Hood

Hood,
I am using a gecko controller so the 540b.xml
the other two files are files that worked. The roadrunner still does.

I did load the mach3 program and found that it is always (in regard to movement) correct. oops!
I just went to look at something on the machine and when I loaded mach3 got a blank screen.

I have no idea what to do but uninstall and reload. With all that is going on it may be the best thing.
I will weight a while to see what you think
Jim

Hood

Hood
last two

Do you still see the menu bars in Mach? if so go to View and Load Screen and then in the Mach3 folder choose the screenset you have been using.
Will look through your files in a bit.
Hood