Hi everyone,

I've upgraded my CNC recently with powerfull stepping motors and great drivers, beacause I wanted for my CNC to work 3-5 times faster.

But what big surprise for me today was when I have found out that MACH3 just cannot execute the G-code fast enough.

I have attached the screenshot of my CNC and all the configurations I've made. I'm testing on the relief that has 0.9 inch height and 0/7 inch width (1.8cm*2.4cm) The configurations in MACH3 are astronomic, but still the MACH3 executes the G-code in 1 minute 18 seconds.

I definitely see that my CNC mechanics could still engrave fine, if MACH3 would simply do what is does but +50% faster. But I cannot make MACH3 work faster. So, it would appear that the weakest part, the main constraint of my CNC system would be not spindle, not engraving tools, not mechanics, but software???


I hope I'm missing something and there's the way to multiply MACH3 speed?

If your running the same GCode, with the same feed rates then the machine will go the same speed it did before. Your GCode asks Mach3 how fast to drive the Machine.

I am not running the same G Code, I've changed the speed in the G Code as well, it doesent react. Just to demostrate, I've made changes in the MACH 3 G code right now, I've multiplied the speed 100 times, I had FRO (speed rate) 45 000, and I've put 4 500 000, and the G code execution was faster for 2 seconds! It was 1:18 now it's 1:16 !

Any ideas?

Here's the start of my G Code:

T1M6
G0Z10.000
G0X0.000Y0.000S4000M3
G0X0.001Y0.001Z10.000
G1Z1.000F2000000.0
X0.025Z0.997
X10.001Z-0.174
X0.025Z-1.345
X0.001Z-1.348
X0.025Z-1.351
X10.001Z-2.522
X0.025Z-3.693
X0.001Z-3.696
X0.001Y0.001Z-3.696
G1X0.025F4500000.0
X16.666
Y0.024
Y0.298
X16.642
X0.001
Y0.321
Y0.596

attach your xml and your code. Likely it is just your code has very short moves and that you have reached the physical limits of velocity achievable due to that.
Hood

Thank you for your help,

I've attached the same G Code.
I'm working in mm units (metric system) not inches.

(If I need to attach something more please let me know as I do not understant what the XML could be)


I've generated the G Code on the ArtCam, maybe I should have used other software to get better results in G Code. But one is true - my relief is pretty small and has very small details. This is kind of relief I'm working with.

You need to also attach your xml, it is the file that holds all of your config settings, that way I can look and see if I can find an issue.
I have just simulated your file on the profile of my Chiron FZ12 machine and it takes 39 seconds to run.
Hood

Hi,

My guess is that your motor tuning acceleration values are too low and the axis never gets to the feed rate velocity before it needs to start slowing down.

Cheers,

Peter

I agree with Peter. Your movements are exceedingly small, so Mach is trying to accel/decal for each of these really tiny line segments. You need to tune your machine for maximum acceleration, not maximum velocity. Also take a look at the CV functionality in Mach3 as well as the look ahead setting. CV lets Mach blend all those tiny movements and eliminate all of the accel/decal problems, look ahead tells Mach how many lines of good to look ahead to plan its trajectory.

You need to also attach your xml, it is the file that holds all of your config settings, that way I can look and see if I can find an issue.
I have just simulated your file on the profile of my Chiron FZ12 machine and it takes 39 seconds to run.
Hood

Looks like I have found the XML file, I have attached it here.

39 seconds is wow, great result that I could never achieve by some reason And, your Chiron FZ12 would actually execute this file in 39 seconds?

Hi,

My guess is that your motor tuning acceleration values are too low and the axis never gets to the feed rate velocity before it needs to start slowing down.

Cheers,

Peter

I agree with Peter. Your movements are exceedingly small, so Mach is trying to accel/decal for each of these really tiny line segments. You need to tune your machine for maximum acceleration, not maximum velocity. Also take a look at the CV functionality in Mach3 as well as the look ahead setting. CV lets Mach blend all those tiny movements and eliminate all of the accel/decal problems, look ahead tells Mach how many lines of good to look ahead to plan its trajectory.

Hi, thanks for your reply,

As I understand, it is impossible to be so, because my first experiments were executed on my real physical CNC, but after that, I've been doing a lot of tests virtually without any CNC. I just cannot get a virtual result more than 1 minute 16 seconds for that G Code file. It definitely appears that I miss something out since Hood can get almost 2 times faster result on profile of his Chiron FZ12, while I cannot get that result on any astronomic virtual Mach3Mill profile whatsoever...