looks like i didn't attach the G code files, let me try again.
Edit - having problems attaching files, none for the time being, sorry.
Hello all,
I’m having some issues with my X & Y axis servo motor drives faulting during rapid moves (G0). The catch here is that the machine works fine when running one program, but faults consistently when running another program. This drill program works well, and drills 370 holes with no loss in position. The engraving program starts faulting out my drives from the get-go, and continues throughout the whole program. Both programs work in the same area of the machine, the engraving is done on and around the holes in the drill program. I’ve attached the g-code if it helps. I’ve run both programs ~4 or 5 times a piece with the same results. I’m 99% confident it’s not a mechanical issue, and the machine also fast jogs just fine.
The programs were made in CamBam. Mach 3 version is 3.042.038. Machine specs are as follows:
Gecko G100 running G320 drives
X axis: Sanyo denki Super L motor, speed - 350in/min; acceleration – 50 in/s/s
Y axis: Sanyo denki Super L motor, speed – 300in/min; acceleration – 50in/s/s
I can set the speeds and accel’s lower, to 200ish in/min and accel of 20, and the engraving program works… sort of. It starts rounding off my text to the point where it just doesn’t look good at all. To put some icing on the cake, I changed the G64 to a G61 in the engraving program to get sharper corners, and the X & Y axis started faulting again. I don’t mind if the machine must go slower for such moves, but I don’t care for the idea of globally making the machine slower when it comes time for engraving work.
I’m confused about a few things, why would G0 fault my drives in one program, and not the other, and why would a change from G64 to G61 in one program cause my drives to fault?
The current issue I’m having is only with the x and y axis, but I’ve also had similar issues on the z-axis. On some programs, and only at certain lines of the code, the G0 will not work (no retracting, broken bit, and ruined work). In these cases, I can offset the machine zeros, and run the program again, and it faults at the same line of code every time.
I’d be happy to provide any more info one might require, and thanks in advance for the help!
-Brian
looks like i didn't attach the G code files, let me try again.
Edit - having problems attaching files, none for the time being, sorry.
Last edited by fbmstar; 11-26-2011 at 07:17 PM. Reason: trying to attach files
Here are the programs. they were of the .nc flavor, if that makes any difference.