We can close that here.... I have opened a other thread. The behavior is completely different now. 😞

@bearer Thanks.. that did it. I'm a bit confused, it my first reflex was the mode 8 but it did not work. Well, I played a bit with the config in the meantime, that ańd your confirmation did the trick. 🙂
At least one success today.

Cheers, Chriss

Thank you guys! I will start reading a bit more documentation tomorrow. Nice nice 😁

@dc42 Thank you very much for your help on this issue 🙂

Yes this could be done with a macro.

You'd need to home the printer in some way first so that you can safely and accurately position the nozzle where you need it.

You'd need the sensor for touching the nozzle to be working in the firmware to begin with.

Then you'd need to position the nozzle, ensure the probe type for the sensor is selected, touch it, and then switch over to the IR sensor and use G30 S-3 to measure the trigger height and apply it

https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe

And then M500 P31 to save the G31 trigger height to the config-override file.

But if you already have a working touch sensor, do you really also need an IR sensor?

@Phaedrux YES! This is the solution. Thank you very much 😳 👍

@kenblu24

I would recommend you follow These instructions to the letter.

And as has already been asked, how does the probe act when it boots ?

i.e. what does the red L.E.D do ?

And kindly post your M558 & G31 Commands in your config.g

I have a rework station. They'll never know. 🙂

@andymidtf said in Occasional hotend crashes into bed during mesh calibration:

And, about the delta requiering home before probe, how does RRF do that which I would like to do on cartisian?

On a delta the towers will home to the max position and then establish the bed position Z0 with a probe. You probably already do the same for a cartesian since the XY position is already homed before moving to the center of the bed to do a G30. So I'm not exactly sure what you mean.

I'm affraid it may be time to replace the probe.

Is there a way of testing that without modyfing the board itself? A resistor in series with one of the connecor wires perhaps?

@Danal said in Genuine BLTouch 3.1 reading "1000" in Z probe on web control:

One last thing-- I tried the stock config home all and home z files, and they did not properly work. Yours did work for me. Thanks, as I still needed those changes.

New sensor works a charm! Pretty happy with it!

See https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M594_Enter_Leave_Height_Following_mode.

The IR sensor doesn't have a true analog output, although it could do with modified firmware and a smoothing capacitor on the output.

Using stand alone Duet 3, MB6HC 3.01-RC10, Duet Web Control 2.1.5. I think youre right. Went I went line by line, M558 is where it changed back to 0.7.

email sent

@dc42 thank you for the info, I can now proceed.

I have now installed a new sheet of plain black buildtak and sensor now works beautifully. Thanks for the help

@jens55 said in Seeking an advise on what Z sensor to go with:

I found that the BLTouch was very sensitive to probing speed. If you run it too fast then the measurements will fluctuate. I also found that multi probing (measure the same point until two successive readings are within tolerance) is pretty much required to get a good result.

BLTouch is sensitive to magnetic fields. The impression I have is that mostly this isn't a problem, but some bed heaters generate enough magnetic field to affect it. That's why we provide the B1 parameter in the M558 command, to make RRF turn off the bed heater temporarily during the bed probing move. Might that have been the reason for your inconsistent results, or were you already using the B1 option?