Guest
Show Posts
1
General Mach Discussion / gcode executions stop matching DRO
« on: January 25, 2014, 11:36:59 AM »
I have a mach3 setup with KL steppers and drivers.
I keep encountering and interesting issue.
When running a G-code program the machine will seem to go wild some times. It seems like an offset changes in the calculating portion of the code, but the DRO still reads exactly correct. Say I am cutting some 2D letters and the first few will cut fine, and then the next few will cut a few inches off in the x&y. I run the same gcode again with a new piece of material and it works fine. When it does go crazy and I cancel the gcode and go to manual input and do something like g0x0, the machine will move sometimes in that direction, sometimes past zero, then back past it. It is like the buffer becomes corrupt.
It does not do it at the same time in the program every time. Sometimes it executes the whole program sometimes ine 50, sometimes line 200.
I would think that DRO in mach3 would check itself with the interpreter program. when it goes okay I am moving to x0y0... I never arrived there, lets not execute the next line or something.
When the machine does go wild and I restart mach3, remembering the offsets and send it to a known position on my work piece to verify, the DRO are ready 100% correct. So I do not think this is a stepper missing steps issue.
Thanks in advance for any insight you may have on this.
I keep encountering and interesting issue.
When running a G-code program the machine will seem to go wild some times. It seems like an offset changes in the calculating portion of the code, but the DRO still reads exactly correct. Say I am cutting some 2D letters and the first few will cut fine, and then the next few will cut a few inches off in the x&y. I run the same gcode again with a new piece of material and it works fine. When it does go crazy and I cancel the gcode and go to manual input and do something like g0x0, the machine will move sometimes in that direction, sometimes past zero, then back past it. It is like the buffer becomes corrupt.
It does not do it at the same time in the program every time. Sometimes it executes the whole program sometimes ine 50, sometimes line 200.
I would think that DRO in mach3 would check itself with the interpreter program. when it goes okay I am moving to x0y0... I never arrived there, lets not execute the next line or something.
When the machine does go wild and I restart mach3, remembering the offsets and send it to a known position on my work piece to verify, the DRO are ready 100% correct. So I do not think this is a stepper missing steps issue.
Thanks in advance for any insight you may have on this.