Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: wpierce47 on October 13, 2013, 08:55:54 PM
-
I have a random problem with my CNC running Mach3 from g-code generated from Cut2D. I can't recall having this problem when running a single part, but when running for multiple identical pieces, the machine goes crazy from time to time. It might cut 3 of 10 pieces perfectly, but when moving to the next might not go to safe z and thus cut a path through a good piece toward the next piece starting point. Other times it may go to the next piece starting point and dive to the mechanical z limit (down). One other random action has been at the end of a run, and returning to zero it tries to go to a point outside of the machine. In this instance I noted that the x and y readouts were completely out of whack so that 0,0 was way outside of the machine boundaries. I can reload the same g-code and it will run past the point where it previously went crazy, so it does appear to be random, and not a problem in the g-code. The PC running Mach3 is dedicated - not connected to the internet, and not running any other programs other than Cut2D (just open - I don't design anything while Mach3 is running), and I don't use the mouse or touch the keyboard. I finally got ticked off today after ruining a couple hundred $ in parts and material, so I really need any help anyone here can offer. The one thing that dawned on me a while ago is that it might be a grounding problem. Without going back to my shop and checking, I'm pretty sure there is no common ground between the gecko controller, router power, controller power supply, and the computer. I'll check that in the morning, but if anyone has other suggestions I'll appreciate any help.
Warren
If I need to add a tag line here it's "When the winds of change blow build a windmill not a windbreak"
-
Reduce your acceleration and velocity settings by half and see if it's better. It sounds like your losing steps on all your axis.
-
Weell it could be as GER21 states. Or it could be you OR Cut2D does not understand offsets. They can be very tricky at times IF the program does NOT account for them. It can leave the machine in a precarious state that creates a crash situation.
Has your machine always had these problem or did they just start. DID you change anything on the machine as far as parameters??
Can you go back and run single programs without problems ??
Just a thought, (;-) TP
-
Thanks for the response. It would seem Cut2D is generating good code, as I can cut several pieces (in a single run) before it goes crazy. I can reload the g-code and run past the last point where it went wild. I also don't see how Cut2qD could cause Mach3 to suddenly loose the x and y positions so that 0,0 is 20-30 inches different