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

Determine a better way to compute the remaining print time #303

Open
kloknibor opened this issue Feb 20, 2017 · 3 comments
Open

Determine a better way to compute the remaining print time #303

kloknibor opened this issue Feb 20, 2017 · 3 comments

Comments

@kloknibor
Copy link
Contributor

Hi,

I think it is an pity the first layers of an print mess up the complete estimated time for the rest of the print. Would it be possible to, in case you are using a static movement/.cws, to don't use the first layers for time estimation? (preferably even calculate the complete expected time for a .cws which should be calculatable by the gcode file)

Kind regards,

Robin

@WesGilster
Copy link
Contributor

You could certainly do that. The problem is that everyone has their own ideas of how to predict the end of the world, but so far I haven't seen anyone do a very good job of it. My theory thus far has been pretty simple. The server side is responsible for supplying the frontend a set of facts about a print job's progress. These facts currently includes things like:
totalSlices
currentSlice
currentSliceTime
averageSliceTime
startTime
elapsedTime
totalCost
currentSliceCost

You are attempting to take a very specific case(cws files) and build a rather complicated theory that may or may not end up being that accurate.

@WesGilster
Copy link
Contributor

Did you ever come up with a way you wanted to do this?

@WesGilster WesGilster changed the title [BUG] first layer mess up time estimation Determine a better way to compute the remaining print time Jun 28, 2017
@kalvisg
Copy link

kalvisg commented Jul 9, 2019

Calculated time will always be easier to calculate but each Raspberry Pi or any other computer will finish at different times which cannot be calculated any more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants