search

Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.5k stars 5.32k forks source link

DS18B20 unable to read crashing Klipper #4393

Closed jvinraviv closed 3 years ago

jvinraviv commented 3 years ago

I've had this happen a a couple of times now where for some reason Klipper can't find the DS18B20 sensor and resets the FW. Problem is when this happens in a print it is ruined.

In the attached file the crash occurred on line 1659 while I was running a PID tune.

Is there a way to prevent a misread of the sensor from resetting the FW?

klippy.log

github-actions[bot] commented 3 years ago

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, ~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

screech24 commented 3 years ago

I having the same issue and I've done everything possible to make sure that it's not a hardware related issue. Would be nice if Kevin didn't just disregard small issues like this and looked into them further:( I've asked in the discord server several times and have had no response to this issue. klippy.log

charredchar commented 2 years ago

I am having the same exact issue. I've had it happen once during a print but multiple times outside of printing. I have moved away from trying to use the DS18B20 for anything more than monitoring temps around my printer and not tie it to any device as it doesn't seem reliable enough within Klipper.

There is another issue open related to it failing for a heater, it seems Klipper is just not happy with this sensor. I think the next best thing would be to have an option within Klipper that, when used as just a temperature_sensor and not tied to a device then set it to not cause a firmware error. If this is not a viable option then the use of this sensor should probably just be removed from Klipper until it can be reliable. The fact it is mentioned in the config reference led me to believe I could use it as I would any other sensor and purchased a handful, now none are usable in Klipper.

klippy.log