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
DELTA_ANALYZE CALIBRATE=extended using wrong heights. #5455
Comments
Looking at the logs this looks suspicious:
|
It looks like this ticket is a request for help (or similar). Many helpful people will not see your message here and you are unlikely to get a useful response. Instead, see the contact directions at: https://www.klipper3d.org/Contact.html We use github to share the results of work done to improve Klipper. We don't use github for requests. (In particular, we don't use github for feature requests, to answer questions, nor to help diagnose problems with a printer.) Please follow the directions at: https://www.klipper3d.org/Contact.html This ticket will be automatically closed. Best regards, PS: I'm just an automated script, not a human being. |
Please also follow the direction given here https://www.klipper3d.org/Contact.html# and post your topic on https://klipper.discourse.group |
Why do I need to open a discourse discussion when reporting an actual bug (seems like Klipper uses the wrong base values for heights)? This is a reproducible issue and imho followed exactly the guidelines written in the Contact section. //Edit: this sounded way more harsh than it was meant. Sorry for that, still don't understand why I can't report a bug here. |
The vast majority of issues reported here turn out to be configuration or hardware problems, not actual bugs. We use Discourse to triage these reports and help users so the developers aren't inundated with help and feature requests. If a bug is identified and confirmed after discussion on Discourse, then an issue can be opened here. |
Thank you for that explanation. This is what imho should be written in the contact.html then and also the discourse lacks a dedicated "issues" section then as it's absolutely not clear what the correct place would be to report a bug/issue in discourse. Could you please point me to the correct spot on where to report the issue that I discovered? It's neither a General Discussion, nor Frontend, Features, Configs, Macros or Developers related. I'm sorry for derailing this issue but at least I now understand what's the intention here - but it's not very user friendly (yet). If someone points me to the correct place on where to report this I will move my issue there. |
General Discussion is the catch all. I would start by asking if anyone else has experienced this problem. Regarding the contact page, I think the directions are pretty well defined. Point 1 at this link is the most relevant to this discussion. |
SAVE_CONFIG
results in:Position Endstops are off by a magnitude of ~2 as are the arms. Values before were:
Since I'm using 0.9 degree steppers I suspect that the calibration script doesn't account for this and still calculates with the default 200 steps per rotation from a 1.8deg motor?
moonraker.log
klippy.log
The text was updated successfully, but these errors were encountered: