that's pretty accurate considering heating is not something I can guestimateEOW wrote: ↑Sat Jun 09, 2018 11:02 am Thanks arhi for gcodestat, i tried it and compare to real print time, S3D says 29min, gcodestat 39min and real is 40min including heating. I will continue to test it on my future print but is a nice feature. I like the fact it computes only at saving step like this it does not affect the slicing time.
It's not working for me yet. It looks like all you did is delete "--output="%of%" --api_key=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA --api_url="http://octopi.local/api/files/local" from gs.bat. I tried leaving it in and deleting it to no avail.arhi wrote: ↑Sat Mar 31, 2018 6:52 am
...edit gs.bat to be like this (this configuration does not upload file to octoprint, if you want to automatically upload to octoprint leave the api and url thing as original just change api and url values):
save your profile and that's it...Code: Select all
@echo off for %%a in (%1) do ( set filepath=%%~dpa set filename=%%~na set extension=%%~xa ) set if=%filepath%%filename%%extension% set of=%filepath%%filename%_M117%extension% C:\gcodestat\gcodestat.exe --alert -d 0.02 -a 1000 --gcode="%if%" --output="%of%"
set the real acceleration value to the app to get more accurate estimateinventabuild wrote: ↑Sat Oct 27, 2018 4:55 pm Wow, S3D gave me print time est of 2 hrs 46 minutes and your app is saying 4:07:45 so actual print time is 48% longer than the S3D estimate.