hmm, i think i spoke too soon
i ran one of my more complex programs, and at just one spot in the program, it will stall at the end of a rapid. the program cuts a final pass on a center round pocket, then rapids out and over to start an outside profile, at the end of that rapid, it stalls and misses steps. i stopped it just in time, and it looks like i can save the part, but i ran the program with no spindle, and you can hear it stall at the end of the rapid movement, almost like something put the brakes on. even turning it back down to 75ipm rapids makes the same noise, and seems to be off a couple thou.(at 120ipm, it ends up off .250 or more) funny thing is that the program makes the same series of rapid movements several times as it makes the next pass, and the rest of the rapids no matter what speed i set it at sound nice and smooth, and they are all the same rapid code???
sample of code
finishes center pocket at about X1.45 Y2.17
G0 Z.1
G0 X-.25 Y2.2(stalls at end of this rapid along x axis about .25" shy of destination)
G1 Z-.25
G2 X2.85 R1.65(something like that, too lazy to go out and read it)
G0 Z.1
G0 X-.25 Y2.2(smooth as silk???)
i ran this code on a couple parts last night at 75ipm rapids, and all looked well. upon closer inspection i see that it is off .007" or so left to right matching this stall i see in the x axis. other funny thing is that at first when i went to run this program tonight, it stalled at the end of the rapid and then the x axis would not work. i shut the machine down and fiddled with wiring, and nothing seemed to be off. when i would jog the x axis, the dro would show movement, but the table would not move in the x direction, only y and z. i tried restarting mach3 and still no x axis. i restarted the cd100 and when it came back on, the x axis was back to working. could this be one of those gecko drive problems you speak of? funny thing is it only does this at this one rapid, i ran several parts today at the faster rapids and all came out perfect. this one spot in this code is giving me problems, and it looks like it did on this part yesterday as well. maybe i better start a seperate thread, sorry.