November 9, 2018, 8:12pm
If I set my bit to 30mm/s and create a tool path that is 30mm shouldn’t it take about a second to cut that tool path?
if not then can someone explain fed rate.
if yes then where should I start trouble shooting my Estlcam G Code?
MPCNC Dewalt 660 Estlcam v11
November 9, 2018, 8:14pm
Yes and no, there is acceleration on both ends of the line.
We can pretty easily figure this out if you upload some gcode or tell us how long it does take. Maybe some build specs as well.
November 9, 2018, 8:15pm
That is right, but your machine can’t go from zero to 30 instantly. It can try, but it would be likely to skip steps and generally not be terribly reliable. The firmware limits the max speed and acceleration. So, 30mm/s would be closer to traveling 300mm in 10 seconds than 30mm in one second.
November 9, 2018, 8:16pm
Dang, how do you say everything so well. I am going to use this line more often and say I thought of it…
November 10, 2018, 6:11am
I’ve uploaded a png of the SVG file that the tool paths were built off of.
Spec’s: 3.5in x 6in sample on .25in MDF using 60 degree v-bit
The g-code is almost a 417mb which seem to me a little odd for 36 path engraving to a total depth of 2mm.
The Capital “T” in “TMB” took 48 minutes to complete
November 10, 2018, 6:16am
Additional info… tool setup.
Highlighted tool is the tool I was using.
November 10, 2018, 6:53am
The diameter should be the maximum diameter of the v bit. You’ve got it set to 0.1mm, so it’s probably driving over the same area over and over, moving 0.1mm per pass.
November 10, 2018, 7:02am
Good to know. I’ll give it a try.
November 12, 2018, 5:36am
Update: re-worked my tools and spent a significant amount of time understanding the various setting in Estlcam which seemed to resolve my issues… Thanks again Jeffeb3 for the clue.