this post was submitted on 14 Sep 2023
20 points (100.0% liked)

3DPrinting

15590 readers
179 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

If you need an easy way to host pictures, https://catbox.moe/ may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] remotelove@lemmy.ca 6 points 1 year ago* (last edited 1 year ago) (1 children)

It could be a loose wire, or a one that is about to snap off. If the cable is bad or on the way out, it could easily be screwing with the resistance measurement. I wouldn't think that just a loose thermistor could cause that mess of a graph, but who knows.

It's the motion bit that you mentioned that gave us just a little more data.

If you can isolate the wire for the thermistor, jiggle it around at different points to see if you can replicate the rapid temperature changes.

[–] atocci@kbin.social 2 points 1 year ago (1 children)

Hmm, I might have to order a new replacement and see if that helps then. I had replaced the hot end assembly with the spare that came with the printer a couple weeks ago. I was very careful with the change, but I suppose it's possible I damaged a wire in the process. It's been running smoothly since then though, until today when the temperature started swinging wildly.

[–] remotelove@lemmy.ca 3 points 1 year ago* (last edited 1 year ago)

Yeah, something got loose or broken. Try your best to isolate the fault while you wait for a replacement though. It's always good to know absolutely sure what happened to hopefully prevent the issue again in the future.