Centroid Community CNC Support Forum

todd432 wrote: ↑Mon Apr 01, 2019 6:38 am Jay, from what I gather smoothing dose change the code on the fly. That's why CNC 12 wants a min single thread of 1500 or higher CPU.
So any hiccup in the pipe line to BBG would show up in the motion control too.
The only other thing i can think of...... is maybe not having a dedicated video card on the controller PC might slow it down or chop up the code , but i don't know just a guess on my part.
Or a bad Ethernet port.
That's why maybe trying another PC to rule it out might be worth a shot.

Thanks Todd, I'll try using my laptop that runs Fusion this weekend I guess. What was your sons old gaming computer? No issues once you starting using it?

JAYCNC Wrote:THANKS FOR NOTHING!

Well Jay, I'm certainly not one of the "In Crowd" as you say but I've received help on many questions. I got help because I followed the forum rules.

#1. If you want a response from the people who know, you have to post a current report. This report has all the information they need to help diagnose your issue! It even has some data on the computer itself that you are running Acorn with.

I looked back to the very beginning of this thread and I don't see a report. Did it miss it? (I may have as I am much older than most on this forum and I do miss things)

I've seen all types of issues addressed on this forum all the way from beginners to experts and as long as they follow the rules and post a report, they get help.

Many times the solution is to watch a detailed video, slowly, and then came back if that does not solve the issue. With over 1,000+ Acorn users on this forum, I think Centroid and the other experts do a great job!

I do understand how frustrating it can be when we can't make something work the way we want it to and no one seems to know what the issue is.

From what I can gather from the post in this forum you may have the solution in hand by using a different computer. Maybe not, but I have two machines running with Acorn and I don't have any smoothing issues at all.

Keep us in the loop as we would like to know what you do to make the issue go away. Then you can help someone else when you see they have the same issue.

Dave C.

there are soooo many things that could cause this.. a lot of newbies jump right to "it must be some setting in the CNC control" which 99% of the time is Wrong.
the first two categories that need to be look at very carefully are:
1.) Machine Tool Mechanical condition.
2.) "mismatched axis motor to mechanical system: means Axis motor doesn't not enough power/torque and/or "geared" incorrectly to the machine so the axis motor is not operating in its "happy" zone. Could also simply be incorrectly tuned servos"
3.) the G code itself

By far the #1 culprit and least understood is:
1.) Machine Tool Mechanical condition, this involves a HUGE amount variables any number of which can cause these types of issues. no amount of software g code smoothing is going to make up for mechanical system that has issues.
here are a few highlights
- ballscrew SUPPORT bearings not being matched set, and or installed incorrectly therefore introducing slop into the system.
- ballscrew NUT is low quality and has lash introducing lash into the system
- rack and pinion slop between the pinion and the rack under load which contributes to vibration/bounce in the system
- Frame of the machine is not rigid and bounces and gives under cutter load introduces vibration into the system.
- frame of the machine doesn’t have significant mass for cutter vibration damping under normal loads
- spindle bearing play in either xy or z plane
- wrong feeds and speeds for material and cutter which puts vibration into the machine tool accentuating the machine tool deficiencies in rigidity.



post the g code program you are running,
post results of back lash test following these directions... http://www.centroidcnc.com/dealersuppor ... ads/37.pdf
post photos of the machine tool itself, tool holder and cutter, check run out of spindle.
what is the actual spindle speed and feedrate during the cutting

Dave, thanks for the response. My very first post has the "report" in it as I learned that from my actual very first post. I've watched pretty much every video out there so I don't have to bother people asking questions, so when I do, I just flat out need help or for someone to take a minute and actually explain it to me vs a canned "watch the videos" response. It very well need be a computer change, but I'm not about to go buy another computer without knowing that's the actual problem first. I'm kind of shocked that the one I'm using isn't sufficient with the benchmark rating it has, that's why I bought that one! But, if that's the case, what is proven, where was it purchased, ect… I don't actua;;y know for sure if it's a smoothing issue, it's just odd that by playing with the settings on it that I can get different results, so that leads me to believe that it is, but I could be wrong. I just don't know.

JayCNC,
thanks for posting the report.zip
it shows you are running at 800 steps / rev.. this is below the recommended minimum of 1600.
i see you mention you have clearpaths, we recommend running them at 6400. since you mentioned you tried changing these in the past with no effect, that mean the issue has nothing to do with it and be sure to go over the mechanicals with all the basic machine tool checks.

cnckeith wrote: ↑Wed Apr 03, 2019 10:26 am JayCNC,
thanks for posting the report.zip
it shows you are running at 800 steps / rev.. this is below the recommended minimum of 1600.

cnckeith wrote: ↑Wed Apr 03, 2019 10:23 am there are soooo many things that could cause this.. a lot of newbies jump right to "it must be some setting in the CNC control" which 99% of the time is Wrong.
the first two categories that need to be look at very carefully are:
1.) Machine Tool Mechanical condition.
2.) the G code itself

By far the #1 culprit and least understood is:
1.) Machine Tool Mechanical condition, this involves a HUGE amount variables any number of which can cause these types of issues. no amount of software g code smoothing is going to make up for mechanical system that has issues.
here are a few highlights
- ballscrew SUPPORT bearings not being matched set, and or installed incorrectly therefore introducing slop into the system.
- ballscrew NUT is low quality and has lash introducing lash into the system
- rack and pinion slop between the pinion and the rack under load which contributes to vibration/bounce in the system
- Frame of the machine is not rigid and bounces and gives under cutter load introduces vibration into the system.
- frame of the machine doesn’t have significant mass for cutter vibration damping under normal loads
- spindle bearing play in either xy or z plane
- wrong feeds and speeds for material and cutter which puts vibration into the machine tool accentuating the machine tool deficiencies in rigidity.



post the g code program you are running,
post results of back lash test following these directions... http://www.centroidcnc.com/dealersuppor ... ads/37.pdf
post photos of the machine tool itself, tool holder and cutter, check run out of spindle.
what is the actual spindle speed and feedrate during the cutting

Keith, thank you and I will do that this afternoon. As of right now, I know for a fact that there is no slop, backlash is less than .0015 and is compensated for, and this machine is very robust and braced rigid.

As for 800 steps, I literally just switch to that setting from the 6400 setting to check for any change. No change.

JayCNC wrote: ↑Wed Apr 03, 2019 10:29 am
Keith, thank you and I will do that this afternoon. As of right now, I know for a fact that there is no slop, backlash is less than .0015 and is compensated for, and this machine is very robust and braced rigid.

sure thing.. get out the indicator and start pushing and pulling on it...
if i had a dollar for every time i heard this "this machine is very robust and braced rigid." id be rich

JayCNC wrote: ↑Wed Apr 03, 2019 10:29 am
As for 800 steps, I literally just switch to that setting from the 6400 setting to check for any change. No change.

that hints that its most likely mechanical in nature.

and update to v4.14, i'm not supporting v4.12

Machine