Calculate real time needed to execute G-Code (so you know how long your 3D print will actually take)
This code is based on acceleration and junction_deviation calculation smoothieware is doing while executing G-Code. Marlin uses acceleration and jerk so calculation is bit different so it will not be as precise with Marlin based printers as it will be with Smoothieware based ones.
Anyhow even with junction_deviation set to 0 and just using acceleration the Marlin based printer will execute G-code to much closer time then what slicers normally predict, so this code is useful for Marlin too. On TODO list is to add full Marlin's support for jer (if someone else does it and create pull request that would be even better :D )
There are some sample gcode's in the samples directory along with a sample config file for smoothieware (the gcodestat knows how to extract data from config file for smoothieware)
Not everything is taken into account for now. For example if you use firmware retraction/prime feature those are ignored, temperature reaching time is also ignored etc..
clone the git and make
Edit Makefile and modify CURL variable to where you have your CURL libs installed or add "CURL=C:\where\you\have\curl\library\installed" after make command
This will create a static binary that does not require external libs:
make
Or you can do this to build binary that will require gcc runtime dll's
make STATIC=0
Or if you do not want CURL libraries used (required if you want to upload result to octoprint) do
make NOCURL=1
Or you can combine
make NOCURL=1 STATIC=0
have not tried, if you do please lemme know :)
You will want dynamic build on the linux, and you doubtfully want curl on rpi itself so build with:
make STATIC=0 NOCURL=1
Now if you want curl, make sure you have curl libs 7.57 or newer installed (note default armbian on opi comes with 7.38 that's old and won't work so you have to add newer curl lib manually) then this should work
make STATIC=0
On linux:
~$ gcodestat out.nc -Q
681
e:\Dev\eclipse-workspace\gcodestat>gcodestat.exe -c samples\config.txt -g samples\31min17sec.gcode
gcodestat v0.0
Starting with parameters:
acceleration: 1000.000000 mm/sec/sec
junction deviation: 0.020000
x max speed: 30000.000000 mm/min
y max speed: 30000.000000 mm/min
z max speed: 1200.000000 mm/min
retraction time: 0.000000 sec
prime time: 0.000000 sec
speed override: 1.000000
absolute movement: yes
absolute extrusion: yes
metering unit: mm
Total seconds: 1646.337528
Total 27:26
e:\Dev\eclipse-workspace\gcodestat>gcodestat.exe -c samples\config.txt -g samples\2h17min42sec.gcode
gcodestat v0.0
Starting with parameters:
acceleration: 1000.000000 mm/sec/sec
junction deviation: 0.020000
x max speed: 30000.000000 mm/min
y max speed: 30000.000000 mm/min
z max speed: 1200.000000 mm/min
retraction time: 0.000000 sec
prime time: 0.000000 sec
speed override: 1.000000
absolute movement: yes
absolute extrusion: yes
metering unit: mm
Total seconds: 8396.563453
Total 02:19:56
e:\Dev\eclipse-workspace\gcodestat>gcodestat.exe -c samples\config.txt -g samples\2h23min5sec.gcode
gcodestat v0.0
Starting with parameters:
acceleration: 1000.000000 mm/sec/sec
junction deviation: 0.020000
x max speed: 30000.000000 mm/min
y max speed: 30000.000000 mm/min
z max speed: 1200.000000 mm/min
retraction time: 0.000000 sec
prime time: 0.000000 sec
speed override: 1.000000
absolute movement: yes
absolute extrusion: yes
metering unit: mm
Total seconds: 8718.500820
Total 02:25:18
e:\Dev\eclipse-workspace\gcodestat>gcodestat.exe -c samples\config.txt -g samples\53min18sec.gcode
gcodestat v0.0
Starting with parameters:
acceleration: 1000.000000 mm/sec/sec
junction deviation: 0.020000
x max speed: 30000.000000 mm/min
y max speed: 30000.000000 mm/min
z max speed: 1200.000000 mm/min
retraction time: 0.000000 sec
prime time: 0.000000 sec
speed override: 1.000000
absolute movement: yes
absolute extrusion: yes
metering unit: mm
Total seconds: 3026.757087
Total 50:26
The filenames in the samples dir have name indicating "Real time" it took for the code to print (measured by octoprint after the print). The bed preheat time is not there so only extruder heat time is there and that accounts for small discrepancy in time between real print and calculated time. There are also some other places where discrepancies can occur but it's "acceptable" ..
for e.g. you see that 2h17min42sec.gcode file that was printed in reality in 2:17:42 have calculated time of 02:19:56 while Simplify3D predicted 1:39:00 .. so while our estimate was 2min out for over 2 hour print Simplify3D missed the mark by 40 minutes.
To integrate this with Simplify3D you can create a batch file like:
@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%
E:\Dev\eclipse-workspace\gcodestat\gcodestat.exe -d 0.02 -a 1000 --alert --gcode="%if%" --output="%of%" --api_key=YOUROCTOPRINTAPIKEY --api_url="http://192.168.0.1/api/files/local"
--alert will display the windows alert showing time to print --api_key & --api_url if set will upload the file to the octoprint (finally you can send to octoprint from simplify3d)
and then put in the "Scripts" tab, "additional terminal commands for postprocessing" a line that call's it:
e:\path\to\gcodestat\gs.bat "[output_filepath]"
Note that if you don't have --output and you have api_key and api_url the input file will be uploaded to octoprint, but if you have --output then the output file will be the one being uploaded.
One good side effect of this is that finally your API key will not be embedded in the g-code (if you used curl in the additional post processing script to upload to octoprint) so a little bit security there :)
if you don't want the windows popup to show you time left you can add -q or --quiet so you suppress any output
the M117 file you create, even if you don't have a LCD on your printer and you use Octoprint as a host you can use some of the Octoprint plugins to display M117 messages in browser during print, for e.g. https://github.com/AmedeeBulle/StatusLine https://github.com/jneilliii/OctoPrint-M117PopUp
Since v0.8 there is --m117_format option, if option is not set it behaves like you called it with
--m117_format "M117 %p%% Remaining %w weeks %d days ( %h:%m:%s )"
available substitutions are (case sensitive):
- %w - number of weeks
- %d - number of days
- %h - number of hours
- %m - number of minutes
- %s - number of seconds
- %S - number of seconds + minutes * 60 + hours * 60 * 60 + days * 60 * 60 * 24 + weeks * ...
- %p - percentage
- %% - a % sign
- %q - a " sign
Note: gcodestat will not auto add M117 (case sensitive!) so you have to add it to format string yourself
examples:
--m117_format "M117 %p%% Remaining %w weeks %d days ( %h:%m:%s )"
--m117_format "M117 %p%% Remaining"
--m117_format "M117 %S sec remaining"
--m117_format "M117 %w:%d:%h:%m:%s"
Note: % is special char in a BAT file so when adding this to a .bat file you have to use %% instead of % so windows batch interpreter can work properly. Here's an example bat file with M117 format:
@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 -d 0.02 -a 1000 --alert --gcode="%if%" --output="%of%" --api_key=YOUROCTOPRINTAPIKEY --api_url="http://octopi.local/api/files/local" --m117_format "M117 %%p%%%% Remaining %%w weeks %%d days ( %%h:%%m:%%s )"
If you are using OctoPrint I wrote a plugin gcodestatEstimator that will use the M117 codes embedded by the gcodestat to inform OctoPrint about "real" time to finish the print