Closed CODeRUS closed 7 months ago
Can you explain the rationale? The log output would never reflect all changes and also does not align to any layer information or similar. Additionally, I do not see any diagnostic benefit, but I might be missing something.
@Sineos exactly for diagnostic purposes. Most common cases are ADC out of range errors after turning on part cooling fan. Can see if temperature goes down (probably) cause of turning on cooling.
Thank you for your contribution to Klipper. Unfortunately, a reviewer has not assigned themselves to this GitHub Pull Request. All Pull Requests are reviewed before merging, and a reviewer will need to volunteer. Further information is available at: https://www.klipper3d.org/CONTRIBUTING.html
There are some steps that you can take now:
Unfortunately, if a reviewer does not assign themselves to this GitHub Pull Request then it will be automatically closed. If this happens, then it is a good idea to move further discussion to the Klipper Discourse server. Reviewers can reach out on that forum to let you know if they are interested and when they are available.
Best regards, ~ Your friendly GitIssueBot
PS: I'm just an automated script, not a human being.
Thanks. As feedback, the code change here doesn't seem correct to me. The main diagnostic case (that I'm aware of) is reporting the "layer cooling fan" speed, but this change doesn't add a stats()
callback to the PrinterFan()
class. Maybe I'm missing something. If we do want to add more diagnostic info, I think we should restrict it to just the layer fan, as most other fans (eg, heater_fan) are unlikely to be needed for diagnostics.
-Kevin
It looks like this GitHub Pull Request has become inactive. If there are any further updates, you can add a comment here or open a new ticket.
Best regards, ~ Your friendly GitIssueBot
PS: I'm just an automated script, not a human being.
Signed-off-by: Andrei Kozhevnikov coderusinbox@gmail.com