Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
I was moved to run the “screws_tilt_calculate” command and it seems that I have reconfigured my print head since I set up the printer.cfg because the probe misses the bed.
I have changed the values in the “[screws_tilt_adjust]” section in the printer.cfg and restarted, but it keeps using the old values.
And now we are supposed to use our crystal balls? You know the drill - attach klippy.log and, in this case, printer.cfg.
And honestly, even writing this over and over again is extremely tedious and does not contribute to my willingness to help - especially for someone who is not new.
I told you already: klippy.log is AWOL. Octopi flashes a message at startup to say that it is missing.
Clearly what has happened is that there has been an update that I didn’t hear about and various things have been moved around, meaning that Octopi is looking at a different printer.cfg to what klipper is looking at…
Now, I want to make something clear: I don’t care if it is AWOL or on holiday on the ISS. Please post when you have the relevant information. It is simply brazen to waste our time with questions that force us to practically beg for information to support your issue.
From here, I can only recommend that you tread carefully.
OctoPi is looking at nothing. It’s the OS of OctoPrint on a Raspberry Pi.
And even OctoPrint does not care. The printer config is just a matter of Klipper.
Isn’t “Should” a wonderful word? It’s not there. Always used to be, now it isn’t.
Now it is at ~/printer_data/logs/klippy.log
How it got there, I do not know, because I didn’t move it and I don’t remember doing any updates that would have moved it.
I guess it was at the same time that the virtual serial device got moved from /tmp/printer to ~/printer_data/comms/klippy.serial
That caused me some problems… and I’m not sure they’ve gone away: I still keep having trouble connecting sometimes…
So what relevant information would the log have told you?
None at all.
If I had posted also printer.cfg, the log would have told you that klipper was not loading it, which I told you in the post.
Scroll on friend. It’s not difficult.
Just scroll on.