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 time with reprap and klipper #379

Closed
robthide37 opened this issue Aug 2, 2020 · 7 comments
Closed

print time with reprap and klipper #379

robthide37 opened this issue Aug 2, 2020 · 7 comments
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem

Comments

@robthide37
Copy link

newest version any file you open if you select klipper or reprap acceleration doesn't change print time and if you set print speed to 200 or 150 or 120 it gives same time for all. I beleive iut is defaulting to a very low accel value for time estimation when not on marlin

@robthide37
Copy link
Author

you can set the accel in print settings but i don't want it to add anything to the gcode and feel like when set to klipper it should est time off the machine limits values entered on the printer settings vs needing to add it to the print settings as well

@supermerill
Copy link
Owner

The slicer simulate marlin firmware. To have a better estimation for other firmware, you have to test & set the "time estimation compensation" in machine limits.

@robthide37
Copy link
Author

i get that what i am saying is that the acceleration doesn't work in the pinter config tab . so set acceleration to 10000 i use 6000 but just go higher for sake of proof. thenslice a file at 150mms then slice at 300mms the time might not change ir if anything will change by a few percent . If you change to marlin then it will behave correctly. the time estimation can't fix this problem becasue if you make it accurate for 200mms it still won't change when dropping to 150 mms. i print at 200 plus alot and when quality i will have 150 and 120 or 100 as my lowest . I set all speeds to the tested values just to make simple.

@supermerill
Copy link
Owner

understood. I'll take a look.

@robthide37
Copy link
Author

robthide37 commented Aug 3, 2020 via email

@supermerill
Copy link
Owner

supermerill commented Aug 3, 2020

Problem is,the current github plateform only allow for month-based subscription.

1- Seems like github sponsor can support annual billing, so if you set up your account for annual billing and select the 2$ reward, you will pay 24$ in one go. Then, you should be able to cancel the support (but you'll be registered as supporter for the whole year).

2- If you prefer, I can create a 25$ tier, so you can select it and cancel, without changing the billing method.

note: I don't want to use paypal (or bitcoin), as it's possible to be scammed. With github, you are sure on who get the donation.

@robthide37
Copy link
Author

lmk if you will get the 24 in one shot ill do that if not make the 25 dollar tier and ill do that and then cancel and switch to the other one

@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Sep 7, 2020
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem
Projects
None yet
Development

No branches or pull requests

2 participants