@andnosobabin
Manually level the print bed with the level wheels... and recalculate the Z offset

Your photos show an extrusion very close to the side of the sensor. I am wondering whether a reflection from that might be interfering with the sensor reading. If that's the case, probing a little further away from that extrusion or putting matt black tape over it might have helped.

That said, a properly working BLTouch is likely to give similar or better results that are not affected by the transparency of the bed surface.

I have beed inspecting and inspecting and not seen anything indicating cracks or movement.

That seems to have got it up an running again. I have probably closed a crack somwhere.

If it stops workkng again I may let a friend of mine re-solder all componets with one of those soldering heat guns.

That may invalidate the warranty, I dont know but may be worth a try.

Inthink we can close this thread.

Thank you for all help!

@jmshep That may have been the case in 3.0 because there were still some default pin associations, but in 3.1.1 all default associations are removed and you no longer need to use nil to undefine them. Rather you now must define the pins being used.

Tried a mesh compensation with a piece of paper, disastrous results, here's a picture:

Heat paper.png

@simplesimson said in IR probe and Duet Maestro:

Hey,

i´m still having the same problem. Do I need to use M558 P2 for the "digital probe"? if I do so, the Probe Z status in DWC shows 0 (5) when not triggered and 0(1000) when triggered. By Triggerd i mean a red LED.

Sorry for the late response. M558 P1 is correct for the IR sensor that we sell. P2 is only for the sensor that RepRapPro included in the Ormerod 2 printer and I think also the Huxley Duo and one of their Mendel printers.

@dc42
Right now it is a little bit blank - it is the magnetic part of one of those aliexpress magnetic print surface - Will try with the print surface on when i get back (the Matt print surface you print on the magnetic sheet)