Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

PixelCNC Has Moved: deftware.org

CAM software developed by artists for artists to create unique and original works on a 3-axis CNC router or mill. · By Deftware

Estimated time vs Gsender vs actual time

A topic by hegartype created May 03, 2025 Views: 373 Replies: 1
Viewing posts 1 to 2
(+1)

Hi all,

I was doing a relief carving of an stl, it mostly worked, but I have an issue with times.  For the roughing pass, 1/4 endmill,  I had an estimated time of 27:44 in Pixel CNC, when loaded in Gsender it gave an estimate of 29:38, in actual time it was about 40 minutes, I didn't record it, it wasn't a crazy difference.  Then for the finishing pass, 1/8th ball nose, estimated time of 1:12:02, Gsender 1:38:00, actual time 3:27:14.  Anyone have an idea why I would get that crazy difference? Or any difference period?  Thanks in advance.

Developer

Hi  hegartype,

Estimating operation runtime is pretty tricky, as you can tell by both PixelCNC and Gsender estimations being way off from the real world runtime. The best we can suggest is to go into your CNC/CAM Settings under the Config menu and adjust the Rapid Speed and Rapid Accel settings to closer match your CNC setup. The rapids between feed commands tend to be what throws off runtime estimation the most because there are many variables at play that affect how fast the machine is actually able to move during each individual rapid, but if you can tune those two settings to more accurately match your machine the time estimation should be more accurate. Generally, the more rapids there are the farther off runtime estimation can be - particularly if those two settings are not tuned to match the machine that G-code will be running on.

Hope that helps! :]

 - Charlie