Hi there. I’ve been printing without issues the last couple months but over the weekend it started acting funny. Auto calibration with the 25 point worked well but when it started the job it started digging into the mat. I have ruined both sides of the mat because of this and a PEI sheet.
I then reseated all the cables - x, y, z power.
Retightened the proximity sensor (about 1mm above from nozzle end)
Changed the nozzle 3x.
Updated to latest firmware.
It was still not printing properly. The other day I started hearing popping noises from inside the module. I have tried different filaments and it also stopped loading. I tried 3 new nozzles same result. It wasn’t loading at all. Once it made a weird sound when I started calibrating as well.
Now I have started smelling smoke from inside so I turned it off.
What could be the problem? Pls help. I’m trying to finish projects for Halloween and have submitted an email to support.
Your bed is installed upside down to start with.
Nuts should be down.
I had nothing but problems with 1.10.1
Went back to 1.10.0
Not sure about burning smell. Can you tell where it’s coming from?
From toolhead? Or from linear modules?
I’m not sure if it was on here or FB that someone had a short in linear.
I’d pull the motor end and make sure nothing is shorted out in there or looking burnt.
Could be printing too close to mat.
Popping can be filament has gotten moisture.
Filament just came out of filament dryer and I’ve tried several. I think the burning smell is coming out of the tool head but I’m at work right now and will check again later, gonna take it out of the enclosure. Thank you
hi! thank you I flipped it! weird i had it working good before while upside down lol. for the burnt smell, seems like it’s just a faulty hot end. I just have bad luck with the hot ends I have ugh. One has broken wire and another shorted. The first one I had was clogged so I just cleaned it and tried using that. The new firmware is a headache too so I went back to 10.0 for now. It’s just a series of unfortunate events to pinpoint the issue haha. Still testing prints to see if it’s fixed for now. Thank you again!