view the rest of the comments
3DPrinting
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
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
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
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.
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.
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.