Thanks for the tip FRIDGE. Yeah, rack and pinion would definitely be the way to go in the long run. Can't afford it so it looks like I'm stuck using belt with The RAT for the moment. Good luck with your build.
Back after a little hiatus. Backlash is getting me down. Need to try and find it. There are so many factors to consider and I feel like I'm getting bogged down with it. I feel like the belts are where most of it it originating. I recently went to GT3 from GT2, seems to have helped a bit. Maybe it's to do with the actual setup in Mach3, maybe I'm trying to go to fast.....? Here are some of the settings currently running.. Accel: 100mm/s/s Velocity: 8000mm/minute Steps/mm: 33.33333333 (x and y) Feed: 970mm/minute Speed: 2-2.5 on a makita 700 series trim router ~14000RPM DOC: 2-3.5mm Single flute 1/4" up spiral cutting plywood. Here is a picture if a little test pattern that I just did. Might help pinpoint some of the problems. Red dot is the start point. Numbers represent start point of each cut. All at 2mm depth, except for 10, being the outside/last cut, done at 3.5mm per pass. Seems to be a lot (maybe 1/2 a millimetre or so either way) of movement occurring on entry and exit of material. Any ideas or questions are welcome.
There does seem to be a bit of a pattern there. They are adjacent to each other. Each area involves two movements, and produces two faults in the same general area. I don't think Backlash would be so local, if you see what I mean. At first glance, I'm inclined to look for a mechanical, rather than electrical fault. Gray
Just a guess but that type of problem could well be produced by a loose grub screw in the drive from the stepper motor (pulley, shaft, coupling etc.). Tweakie.
They look fine. Here is a little one minute video of the machine doing air cuts. I sped the whole thing up to around 2910mm/s and accel up to 150mm/s/s from 100mm/s/s and 970mm/s, to see if I could get it to obviously miss steps. After marking the shafts on the steppers while at zero, running the gcode through and then returning to zero, all motors seem to be in exactly the same spot. So to my as yet untrained eye, it isn't missing steps.
Just noticed something. You can kind if see it in the video. It's almost like the z stops at zero on its way down from the 20mm safe z. In this case it's a 1mm DOC. Is this normal with mach3?
Might explain the bad entry's and exits, that is if either the x or the y start moving before the z has reached the end of its movement......
You know, think I saw that same thing on my my little Musk-OX. Before I got my motors all tuned up in Mach3. I really think you're up to something.
Hi Larry, not sure if I quite follow what you are saying. Are suggesting I go over the motor tuning again? If so what recommendations do you have?
Should be (on) to something. Are you using Nema 17 or a 23? when I moved to a Nema 23 things got a lot better.
Ok, so I did some testing. Changing acceleration, rapid and feed rates for every lot of six squares. The numbers at the top right of each lot of six squares represents the acceleration, rapid and feed rates from top to bottom as you see them. The bottom right one is supposed to be 10000 not 1000.. Looking at the bottom right square (the one with the circle in it) is telling me that there is backlash in the y axis. Same with the bottom right corner of that particular square.... So, next thing to do will be to investigate if there is any way to reduce the backlash in the y axis. All in all I'm quite impressed that there is little or no difference as I wind up all the rates.. Left to right is the y axis, top to bottom is the x axis.
great looking test. I hope you figure out where the problem is. I'll probably be following in your foot steps later this month...
Thanks Nick. It's driving me insane. Well, I decided to rotate it all trough 90 degrees to see what the difference was. Not sure exactly what it's telling me yet. Anyone? left to right is the x axis, top to bottom is the y axis.
Still think the y axis is the one with the most backlash....... Tried tightening the belt, checking for binding. No dice....
This will sound dumb because I don`t know what it will prove exactly but can you do a test using just the extreme left and then extreme right of the x axis only. Avoiding the centre area. I`m looking fog a hic-cup. Maybe a test on Y axis at extreme ends as well. i.e. Working areas you normally wouldn`t. Gray
Just so you know the gantry is the y axis in this case. Currently I have a 1200x600 bit of MDF that I've levelled as my working area for the moment, which is roughly centre. So by doing what you are saying, are you trying to remove the possibility of flex in the gantry? I guess I'll move it to one side over and re-level it?
Don't worry about leveling the bed, that's not the problem. The point is to bring new areas of movement and elements into the equation, and therefore remove other more common repeated elements from the problem. Just a "Process of elimination", so to speak. Gray
Interesting that the two lines that are obviously inaccurate in this design appear in all instances. How accurate is your Gcode for this design and could you perhaps post it so that it can be tested ? Tweakie.
You have a very good point Tweaky. I noticed this after I did the 90 rotation. Just getting the gcode out of the computer now. Will post it in a minute.
here it is. Cleaned it up a little when I rotated it. Took out one of the circles and one of the V's. Hope you find the culprit in there.
Well, your Gcode looks and runs just fine here so it's not that. My opinion... If you follow the toolpath your errors appear to show at the point the tool is lowered to the work indicating, to me, that point is possibly correct and much of the other toolpath is off by a small amount. This can often be caused by tool-flex or flex in the Z axis (or elsewhere perhaps) and that is what I would be looking for. Hope this helps. Tweakie.
Thanks Tweaky! I think we are getting somewhere now.. Guess I'll be pulling it all apart to try and find that **** flex, of which there is a little in the z in the x and y direction. need to change the z limit switch anyway. Learning, learning, learning! Silver linings and all. Thanks agin for time and patience.
Something you could try is editing your Gcode to reduce the Z clearance height from 20 to say 5mm and reduce the Z axis plunge rate from 1000 to 500 (or perhaps 250) and see if this solves the problem (it may reduce flex). Just a thought. Tweakie.