Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Estimate build time with material needed #1766

Open
RenaeMacLeod opened this issue Feb 12, 2014 · 11 comments
Open

Estimate build time with material needed #1766

RenaeMacLeod opened this issue Feb 12, 2014 · 11 comments
Labels
Fixed with PR available to merge There is an update to address this issue in an open pull request. UI: Misc

Comments

@RenaeMacLeod
Copy link

It would be very helpful to have Slic3r calculate an estimated build time, along with the amount of material needed, and save it to the GCode file above or below the 'filament used' comment. It would be a bonus to see this at the bottom of the program beside the 'GCode exported' message.

@alranel
Copy link
Member

alranel commented Mar 16, 2014

Unfortunately, Slic3r cannot estimate build time without knowing the motion implementation of your firmware, including its settings (speed/acceleration/jerk etc.)...

@RenaeMacLeod
Copy link
Author

Can the time estimate be based on the mm/s settings within Slic3r?

@lordofhyphens
Copy link
Member

@RenaeMacLeod Yes, but frankly it's going to be inaccurate anyway and most gcode host programs (like pronterface) already do this.

@bubnikv
Copy link
Contributor

bubnikv commented Jun 18, 2016

Cura contains a simplified Planner code from the Marlin firmware, albeit with the hard coded acceleration values :-) Still the time estimates given by Cura are quite precise.
One can actually build a trimmed down Marlin firmware into the Slic3r just for the time estimates. In my opinion it makes sense.

@lordofhyphens
Copy link
Member

@bubnikv I would rather not put any code from Marlin into Slic3r myself. ;)

@thiagopeixoto16
Copy link

thiagopeixoto16 commented Mar 4, 2019

Hi @lordofhyphens , I just want to check what I'm doing wrong since my UI is not showing the estimated time after gcode export.
► Slic3r 1.3.1 dev 2019.02.10.2284.05a2f902.64bit
image

@thiagopeixoto16
Copy link

Updating: I tried different things on dev version and noticed that it is only being displayed at Controller tab when printing via USB (queue frame).
Can this be moved to the Print Summary screen for those don't print via USB?

Another suggestion:
Repetier Host has a field that allows calibration of this estimated time, it is a percentage field that allows the user to manually fix the real machine print time deviation, screenshot below:
image

@lordofhyphens
Copy link
Member

@thiagopeixoto16 move it and open a pull request :)

Should be easy to find the code that does the display.

One feature at a time though; I have been known to implement the top line feature request and ignore additional asks (closing the issue).

@thiagopeixoto16
Copy link

Thanks for you reply!

@lordofhyphens You're completely correct, in this way we can have different issues for different requests.

About your "DIY" recommendation, I'll ask someone who know coding near me, as I told you before I'm not that guy and certainly will create more problems than solutions trying to change something :)

@saintofinternet
Copy link

so is there still no way to get an Slic3r give you the print time estimate??

@dwillmore
Copy link

dwillmore commented Mar 30, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed with PR available to merge There is an update to address this issue in an open pull request. UI: Misc
Projects
None yet
Development

No branches or pull requests

7 participants