When using OctoPrint, then the printer makes a "click click" noise before the start of the print. I think it comes from on of the motors, because it appears when the X-axis goes to the very right position before starting the print (heating up phase).
What did you already try to solve it?
I checked if this appears without OctoPrint, but it does not. I checked the settings and compared it with the link above, but this is correct.
I noticed the same behavior on my printer when I started using sensorless homing.
I guess the firmware needs some "normal" movement before the axis is stopped to distinguish between moving and stopping.
If I start homing while one axis is at min I get a few skipped steps until the firmware notices it's already at the min position. I guess those skipped steps are the clicks you are hearing.
I wasn't able to reproduce the clicks until now so I cannot provide a log yet. As soon as I can do, I will do it.
This could be right, @PrintedWeezl. Thanks to this, I had a look in the YouTube video I originally used for the config of Octoprint. I noticed small differences in the axis settings/values compared to the Prusa website. I needed to re-setup my octopi because of a blackout and used for this the Prusa website this time. It might be the reason for "no problems at the moment"..
Hey, after the lastest update to OctoPrint 1.8.6, Python 3.7.3,OctoPi 0.18.0
I have the same problem.... The latest move to warming up position printer makes this click click... I think about 3 short times....
I have configured octoprint with config from prusa website.
But I think it is a issue with the new relase?! Before the update I never had problems with this...
It's unlikely to be an issue in the latest release of OctoPrint. For two reasons, if you look at the tiny bug fixes that were made (read release notes!), and also that this post is over a year old. The original post in 2021 had OctoPrint 1.6.1.
It sounds like more of a mechanical issue to me - but it is worth checking if you can reproduce the issue both in safe mode & not via OctoPrint, as above. Try and follow the same troubleshooting steps that were in the original post.