Future Request: estimated printing time variable for GCode

[einencool]

Hello :-)

Version

Version 1.42 Alpha 5

Operating system type + version

Windows 10

3D printer brand / version + firmware version (if known)

Ender 3 with MKS Gen L and Marlin 1.1.9

Behavior

Hello,
is it possible to get the Variable Slic3r PE uses to fill the estimated printing time at the end of the GCode?

I would like to take this variable and put a M117 Command with the estimated printing time to show it on the LCD.
Since my Printer doesn't support the M73 Command with the Counter, I would like to add these information automatically to my GCode.

For now I look into the GCode File, take the estimated printing time and put it with an
M117 Printtime - xx h - xx m
into the Custom Start GCode from my file.

Is this a new feature request?
I think so :-)

It would be great if this would be possible, because the calculation of the printing time works like a charm, and there are only 1 or 2 minutes difference, also when the printing time is about several hours.
And I think there must be a chance to get this information easily because Slic3r already put this information into the GCode File...

Thank you in advance.
Greets Chris

[dartrax]

Hello Chris,

welcome in the slic3r PE Community!

I'm missing that feature also, see #1739.
However, thanks for adding your vote on that ;-)

[bubnikv]

Are you aware, that you can enter the following macros into the output file template?

print_time, normal_print_time, silent_print_time, used_filament,
extruded_volume, total_cost, total_weight, total_wipe_tower_cost, total_wipe_tower_filament

That may solve your request at least partially.

[dartrax]

Hi,
yes I am, but thanks for the tip anyway. While that is nice to have, it does not help when you want the printer to show the estimated print time on its LCD. We need that macro inside the Gcode at the Layer Change Script so it can be combined with M117. And of course it should calculate the remaining print time, not the whole print time ;-)

[einencool]

I'll give it a try today.
For me it's OK, because I can see in the bottom of the display the whole printing time, and in the status bar in the mittle the already printed time.

I tried different variables but all of them didn't work.

Do I have to set it in [ ] or do I need other signs?

[einencool]

Well, I tried it, but the variables are not usable :-(
These are the failure messages, when I tried the variables...
Did I something wrong?

!!!!! Failed to process the custom G-code template start_gcode
Parsing error at line 2: Variable does not exist
M117 [print_time]
^
!!!!! End of an error report for the custom G-code template start_gcode

!!!!! Failed to process the custom G-code template start_gcode
Parsing error at line 2: Variable does not exist
M117 [normal_print_time]
^
!!!!! End of an error report for the custom G-code template start_gcode

[bubnikv]

Well, I tried it, but the variables are not usable :-( > Are you aware, that you can enter the following macros into the output

file template? They are usable in the output file template, not custom G-code.

…

On Wed, Feb 27, 2019 at 8:37 PM einencool ***@***.***> wrote: Well, I tried it, but the variables are not usable :-( These are the failure messages, when I tried the variables... Did I something wrong? !!!!! Failed to process the custom G-code template start_gcode Parsing error at line 2: Variable does not exist M117 [print_time] ^ !!!!! End of an error report for the custom G-code template start_gcode !!!!! Failed to process the custom G-code template start_gcode Parsing error at line 2: Variable does not exist M117 [normal_print_time] ^ !!!!! End of an error report for the custom G-code template start_gcode — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1867 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5I0pCTCWrHoiaTpN4A5rYMjhaL_-dks5vRt6NgaJpZM4bQLYL> .

[einencool]

Ah ok, i understand, yes that works, and for the first time it will be ok, but the other M117 command in the Start GCode would be way better to display.

But thank you, I'll give it a try :-)