Octofarm: Incorrect Print Progress

Created on 14 Mar 2021  ·  10Comments  ·  Source: OctoFarm/OctoFarm

Printers will report incorrect status, for instance 100% when really at 70%. File was uploaded a month ago VIA the API client through CURL. I moved it into a sub folder of my reoccurring prints.

To Reproduce
Steps to reproduce the behavior:

  1. Start a print through Octoprint web interface (not octofarm)

image
The real progress of this print is ~75%

What Octoprint shows:
image

Re-syncing the printer resolves the issue temporarily.

Versions:

  • Docker Monolithic-Latest
  • OctoFarm Version 1.1.12
  • OctoPrint Version: OctoPrint 1.5.3
  • OctoPi: 0.17.0
bug fixed patreon

Most helpful comment

Looks good now! You guys rock.

All 10 comments

Did some testing on this and it seems to get slowly out of sync somewhere.

Is this still an issue @tophattwaffle I've done some more investigating and all I could find was a discrepancy with the estimated print time not aligning with OctoPrints but that isn't what I use to generate the progress.

It seems my progress was more inline with the actual percentage too as OctoPrint rounds to the nearest single digit which i've not replicated on a PR i'm about to make.

Neither of those would cause the massive discrepancy you are seeing though so I'm a little confused at the moment.

At most I'd be a percent out

I have PR'd the request. When this hits development I'd love to get your feed back to see if it actually resolved the issue.

what steps do I need to take to see if this is resolved? I'm running 1.1.12
on docker monolithic, so I'm assuming I'll have to wait for the next build
of that.

On Wed, Mar 24, 2021, 04:35 James Mackay @.*> wrote:

I have PR'd the request. When this hits development I'd love to get your
feed back to see if it actually resolved the issue.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OctoFarm/OctoFarm/issues/364#issuecomment-805647982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTV23MUBIWQLHCZ2BCNQG3TFGW7PANCNFSM4ZEZDFZQ
.

what steps do I need to take to see if this is resolved? I'm running 1.1.12 on docker monolithic, so I'm assuming I'll have to wait for the next build of that.

On Wed, Mar 24, 2021, 04:35 James Mackay @.*> wrote: I have PR'd the request. When this hits development I'd love to get your feed back to see if it actually resolved the issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#364 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTV23MUBIWQLHCZ2BCNQG3TFGW7PANCNFSM4ZEZDFZQ .

Once the pull-request is merged by @NotExpectedYet it will start building on monolithic-dev. This image would then have the latest work. If you have a moment, we can notify you once it is ready

That's now complete @tophattwaffle should be built on the latest development build.

Apologies for the delay. Recently updated, and it looks good so far. I'm gonna monitor it over the next few days to confirm it is resolved.

Fingers Crossed! XD

Looks good now! You guys rock.

I'm just gonna leave this open incase anyone else reports it and can see it's fixed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

cskozlowski picture cskozlowski  ·  5Comments

NotExpectedYet picture NotExpectedYet  ·  27Comments

juangonzalezpr picture juangonzalezpr  ·  10Comments

MTrab picture MTrab  ·  123Comments

fp30 picture fp30  ·  12Comments