Code Monkey home page Code Monkey logo

Comments (7)

BelgianGuyWithALaser avatar BelgianGuyWithALaser commented on June 27, 2024 1

this is the dump config
estimator 3

as for the gcode, I had to zip it to upload it directly to github :
Body2.zip

and for the klippy log :
klippy.log

from klipper_estimator.

dalegaard avatar dalegaard commented on June 27, 2024

Hi!

Can you send a config(use the dump-config command) along with the gcode file? If you don't want it public you can send it to me at [email protected]. I'll take a look at what's going on! If you can send me a Klippy.log as well that would be very useful!

Thanks!

Best regards,
Lasse

from klipper_estimator.

dalegaard avatar dalegaard commented on June 27, 2024

Hi!

Thanks for the files. Your config doesn't seem to match up with your klipper config. The config has accel and accel_to_decel at 3000, but the Klipper config has them at 5000 and 2500 respectively. If I change those in the config and re-run I get 7h56m12s.

Can you verify what settings the actual print was done with?

Best regards,
Lasse

from klipper_estimator.

BelgianGuyWithALaser avatar BelgianGuyWithALaser commented on June 27, 2024

Hey,

sorry for the late reply. Yeah sorry was doing some experimenting with my acceleration/deacceleration value's. it was printed with the 3k accel , 3k deaccel.

I might have found the culptrit for the extra time, is it possible that the estimator doesn't count in my whole "start_print" macro? (QGL, nozzle heating, nozzle whipe)

Best regards,
Jordy

from klipper_estimator.

dalegaard avatar dalegaard commented on June 27, 2024

Hi!

The estimator counts all macros as 0 seconds, as it can't know how long they will take. Depending on when Klipper/Moonraker starts counting "Print start time" that will affect how off the result is.

Best regards,
Lasse

from klipper_estimator.

dalegaard avatar dalegaard commented on June 27, 2024

@BelgianGuyWithALaser

I've discovered that the time shown in the print history in Fluidd(not sure if you are using Fluidd or Mainsail) is the Total time, not the Actual print time. This means that time will include heatup and everything. From a print I just did:
2022-01-27-134205_182x96_scrot
2022-01-27-134308_263x77_scrot

Maybe this is simply what happened in your case?

Best regards,
Lasse

from klipper_estimator.

dalegaard avatar dalegaard commented on June 27, 2024

I'll close this for now, feel free to post any updates here and we'll re-open if relevant :)

Best regards
Lasse

from klipper_estimator.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.