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

Print history has inaccurate “print duration” and “used filament” when using T1 #878

Closed
Dycus opened this issue Jun 25, 2024 · 2 comments
Labels
not moonraker reported issue with other software

Comments

@Dycus
Copy link

Dycus commented Jun 25, 2024

What happened

On the Fluidd print history page, all prints have a correct “total duration”.
Prints using T0 also have correct "print duration" and "used filament".
But prints that use T1 almost always have 0m 0s for print duration, and 0.0mm (or sometimes nonsense, even negative numbers) for used filament.
On occasion, a T1 print will show a correct total duration, but the filament used is still wrong. (A recent print shows 2h 27m 6s / 2h 34m 30s / 58.2 mm for print duration / total duration / filament used. I promise more than 58mm of filament were used in this 2.5hr print.)

I have a dual-extrusion printer (Replicator 2X). I pretty much only use only one tool in a print. I haven't tested this behavior with a dual-extrusion print yet.

I initially reported this issue to the Fluidd team, but they say they pull this data directly from Moonraker and so forwarded me here.

Client

Fluidd

Browser

Firefox

How to reproduce

Run a print that uses only T1 (or probably any non-T0 tool) and check the print statistics/history page once finished.

Additional information

image
moonraker.log
klippy.log

@Dycus Dycus added the bug Something isn't working label Jun 25, 2024
@Arksine Arksine added not moonraker reported issue with other software and removed bug Something isn't working labels Jun 25, 2024
@Arksine
Copy link
Owner

Arksine commented Jun 25, 2024

Moonraker pulls the print data stored in job history from Klipper. It appears that you are using a fork of Klipper, so I would recommend attempting to reproduce with pristine Klipper. If you are able to do so you can report the issue on the Klipper Discourse.

@Arksine
Copy link
Owner

Arksine commented Aug 9, 2024

As there has been no further feedback I'm going to close this. If the problem can be reproduced on the official Klipper repo this can be reopened and I will investigate further.

@Arksine Arksine closed this as completed Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not moonraker reported issue with other software
Projects
None yet
Development

No branches or pull requests

2 participants