ShawnM wrote: ↑Fri Jan 20, 2023 6:03 pm
You simply fail to understand or don’t want to understand that the issue is NOT with Acorn or CNC12. The hardware and software are both proven by the thousands of users all over the globe. All the charts and g code in the world won’t help your case. When your machine runs right on the edge of the envelope at 100% and you try to push it to 150% you get………well you know what you get.
My machine is not running at 100% but 30%. Are the graph and video’s not clear enough, you can see the problem exactly.
And there are more people with the same issue.
There are a few people they think they has a lot of experience, but is there a software developer on this forum, that can take a look in de source code of CNC12? May be a software developer can tell us more about the strange "Spikes", where stepmotors strugling with.
It's a little bit still about this feedrate override problem.
I attached a video milling XPS on 3000mm/min with 100% feedrate override. As you can see, machine has no problems with this cutting speeds. I hope that someone (software expert) serious looking to the strange feedrate spikes from CNC12.
It's a little bit still about this feedrate override problem.
I attached a video milling XPS on 3000mm/min with 100% feedrate override. As you can see, machine has no problems with this cutting speeds. I hope that someone (software expert) serious looking to the strange feedrate spikes from CNC12.
XPS_3000mm_min.zip
video really doesn't tell us anything. need the g code program and a fresh report.zip to see how you have it setup. still not sure what the issue is.
It's a little bit still about this feedrate override problem.
I attached a video milling XPS on 3000mm/min with 100% feedrate override. As you can see, machine has no problems with this cutting speeds. I hope that someone (software expert) serious looking to the strange feedrate spikes from CNC12.
XPS_3000mm_min.zip
video really doesn't tell us anything. need the g code program and a fresh report.zip to see how you have it setup. still not sure what the issue is.
The video is showing that my machine is running on 3000mm/min without any problems. I attached a fresh report file and an test file.
When you need more information, please let me know.
I think there is a big misunderstanding. CNC12 does not process g code like Mach3/4 (for good reason)
a requirement for running G code with CNC12 is that the Feedrate Override is set to 100% or lower.
if you discover that the programmed feedrate is too slow for the job. the solution is to simply increase the F command value in the G code program. NOT crank the feedrate override above 100%.
I will give you background on why this is this way.
In order to achieve high performance motion CNC12 "looks ahead" in the g-code to anticipate and pre-calculate acceleration and deceleration moves so it keep the tool moving smoothly for the most accurate motion possible.
this CNC software technique requires the feedrate override selection to be set to 100% or lower when cutting a g code job.
CNC12's "look ahead" uses the PROGRAMMED feedrate (F1000 in your case) to calculate the accell/decell vectors 2000 lines ahead of the g code line that it is currently executing. so it knows what to do before it gets there.
using the feedrate override above 100% is not intended for cutting, if you need to go faster increase the F command in the g code. that is how it works.
as mentioned before the standard operating procedure to cut faster than the programmed feedrate is change the Feedrate in the G code program!
in your case if you want to run 150% faster, change the F command value of 1000 to 1500 in all cases in the G code program and cut the Job with feedrate override set to 100% or lower. easy peasy.
Hi Keith,
Thanks for your explanation. May be it’s better to build in the cnc12 software a maximum value of 100% feedrate override, and remove the parameter max override. This because other software like Mach4 has the functionality to use federate override to 250%.
It’s now clear for me that cnc12 by design can not higher then 100% when a job is running. I set the max override parameter to 100%, to secure that my milling job will not crash when I press by accident on the + button.