PINDA Probe Light is working, but not reporting value
My MK3s has not been able to calibrate and through troubleshooting, I found it has something to do with my PINDA probe.
It does not change from 1 to 0 on the printer sensor status page, but the LED does turn on and off when a metal object is put underneath.
I checked the cable, it is pushed in all the way, and none of the pins/connectors appear to be damaged. Any ideas?
You don't give us much history.
Is this a new MK3S? Pre-built or from a kit?
Has it ever worked?
Without more details - I am guessing it is from a kit, never worked - and you have the connector on the wrong pins.
Sorry for the lack of history. It was originally a preassembled MK3 that I had bought in 2018, then I had upgraded to the MK3s I have used it on and off for that time and the PINDA probe was working all this time. Then this week I went to try to print again and the probe was not working.
I rechecked the wires, reseated the connector, undid any possibly tight zip ties and still no luck.
I am now having the same problem. It worked great on my first print of the day. Onn my second print, I had an issue with thermal runout while it was still in the first few layer and the print stopped. I reset the machine, cleaned the bed and went to reprint. This time when it went into bed calibration at the start of the print the nozzle crashed into the bed on the z-axis move. I checked the sensor and the light goes off when I place metal under it but it does not send the code to the controller. I have checked all the wires and zip ties. Installed new firmware, etc.
Did you ever get it resolved?
There are four wires in the Pinda cable, two carry power to the Pinda, these are good, because the LED is changing when you present metal to the tip of the Pinda. the third is the signal wire from the Pinda, you are not seeing the change of status on the 'Support>Sensor Info' LCD Menu
If you look at the 'Support>Temperatures' LCD Menu, you should be able to see if the fourth wire is providing sensible Pinda Temperatures.
It it almost certain that your Pinda cable has suffered a repetitive Flexing Stress fracture. and this will probably be right behind the X carriage Strain relief.
You can resolve the problem by piecing out the broken wire, however it is likely the other three wires in the cable are reaching failure point too.
above, is how I repaired mine. and this got me working until the next upgrade which for me, was Mk3 to Mk3S upgrade.
My old Pinda, is now doing service with another maker in their home brew printer.
Thanks! I will give this a try. BTW my Pind Temp Sensor is reporting a temp.
Do you don't recall what color wires are associated with which functions?
I believe it is
Black, Pinda Output
White, Thermistor Output
Blue, Ground .
Well. I ended up replacing a good portion of the wire and that seemed to fix it. Wanting to test it thoroughly I probed several places around the print bed with success until there was no success. It stopped working completely again. I figured I didn't replace enough wire to remove the break and the positives I was getting were luck due to me moving the wire around. Ended up replacing about 98% of the black wire and while the red light on the sensor still goes off, the value on the display does not change from 0 to 1.
Not sure what else to do... I ended up replacing all the wires thinking maybe a bad ground or intermittent voltage was the issue. Nope. Still same results - Light goes off/on but no value change... then it did, once. Then back to nothing.
I've already ordered a replacement sensor I was just hoping to limp along until it shows up.
Oh well. I appreciate the help!
Better luck next time.
Diď you order 2. So you will have a spare fot next time?
So I received my replacement probe and it is acting the same... The light on the probe switches off but the value on the display does not switch from 0 to 1. Any thoughts on what to do next?
I would test the Pinda probe, in position, with my Multimeter.
see if I could see the signal change at the Einsy Board connector
Thanks. I've contacted support. We did a hard reset on the machine and that did not fix the issue. It looks like the board has failed.
Waiting to hear back from them.