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

Next Filament change - incorrect for the next change #378

Open
AlexVercammen opened this issue Mar 18, 2023 · 3 comments
Open

Next Filament change - incorrect for the next change #378

AlexVercammen opened this issue Mar 18, 2023 · 3 comments

Comments

@AlexVercammen
Copy link

First of all, I love your plug-in. But I've noticed the next filament changes ETA seems incorrect and I would imagine for any subsequent changes. I have looked at the python code but I don't know how to look into the locally saved data captured by the code to understand what is happening.
If you tell me how to look for it, I would gladly investigate the issue and be more helpful. I am just an occasional programmer nowadays and I have not invested a lot of time into learning OctoPrint plug-in management.
I have included the file I found the issue with.
OctaTwist_Octagonal-3C_PLA_06mm.zip

@tkunchick
Copy link

I have noticed this is expressed as hours and minutes until next change. If you have "Use 12 hour time for ETA" selected in options, it displays it as a time, rather than a duration.

Would suggest changing so it is always expressed as a duration remaining, or some how do the fancy math to show a time expected for change.

i am not a programmer, no idea how to do either.

@AlexVercammen
Copy link
Author

Cool, I'll try setup to a 12hour ETA since I would prefer a estimated time.
The issue is when you have more than 1 filament change as the 1st change is finished, the next ETA (duration) is wrong.
I can see the program parsing the file for the Filament Change code. But I don't understand how to locate the temporary file to validate the parsed values which should be an array like this [(1, 00:01:00), (2, 00:05:00), (3, 00:14:30).
Then, I need to check the code and make sure it is refreshing the displayed ETA using the correct pair from the array.
I have not worked on this since March, my initial posting.

@j7126
Copy link
Owner

j7126 commented Jul 25, 2023

Hi, this may be related to #347 which should be fixed in the latest 1.19.10 release. Can you please let me know if this issue is still present in this version?

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

No branches or pull requests

3 participants