I figured that, after a cancelled job, on the next job, print time left is erratic.
How to reproduce:
Start a print (In my example, it is a 16min file, this time is stated by Prusa Mini ETA and PrusaSlicer)
Cancel the print after is is started
Launch the print again:
It starts with an ETA of 16min
Quickly, the time goes down to 15min (but the screen on Prusa still says 16min)
Short after that, the print time raise to 55min
It then keeps going down, but never re-synchronize with the real ETA (when print is finished, it still says there is 3min left)
For this test, I reproduced while using the "DryRun" plugin for the first job, because I didn't want to spoil filament. But the first time I noticed this behaviour, I wasn't using this plugin, it was for real prints.
When launching a print job without cancelling a previous one, the ETA is absolutely fine, this only happens on a print following a cancelled one.
I should mention that I'm using a MK3s with latest 3.9.2 firmware, and the latest Prusa Mini ETA version (0.1.3).
Maybe it is also related to octodash (I'm using it) because when starting prints directly from Octoprint web interface I didn't reproduce this behaviour. But what made me though it could be related to Prusa Mini ETA, is that it doesn't happen when I use the combo PrintTimeGenius (M73 option only) + Prusa ETA override plugin instead of Prusa Mini ETA.
Hi,
I figured that, after a cancelled job, on the next job, print time left is erratic.
How to reproduce:
For this test, I reproduced while using the "DryRun" plugin for the first job, because I didn't want to spoil filament. But the first time I noticed this behaviour, I wasn't using this plugin, it was for real prints.
When launching a print job without cancelling a previous one, the ETA is absolutely fine, this only happens on a print following a cancelled one.
I should mention that I'm using a MK3s with latest 3.9.2 firmware, and the latest Prusa Mini ETA version (0.1.3).
Maybe it is also related to octodash (I'm using it) because when starting prints directly from Octoprint web interface I didn't reproduce this behaviour. But what made me though it could be related to Prusa Mini ETA, is that it doesn't happen when I use the combo PrintTimeGenius (M73 option only) + Prusa ETA override plugin instead of Prusa Mini ETA.
Thank you :)