Looks like the bed is so much rotated that it can not untrigger at the back. That is bad - you should manually adjust it to be nearly correct or you get problems during print. You should only correct < 1mm.
Increase Z_PROBE_BED_DISTANCE 10 so it starts higher also reducing the problem.
Thanks for the suggestion, I set the Z_PROBE_BED_DISTANCE to 20, the autoleveling is OK for the first few points and failed due to the probe sending out too fast or the bed is retracting too slow. (After the probe was triggered on the 5th point, the bed keep going for 1mm before it stops. Then as the probe extending, it touch the downward going bed and resulted in error) https://vimeo.com/415853438
Sometimes it fails at point 2, sometimes in point 3. The above video show that it failed in point 5. Any reason for that?
If you look closely you see here at point 5 bed does not go up again. Which means the signal was not received and only after it went into error mode there is a permanent signal which was received making bed go up. So for me it looks like the signal does not always gets triggered. Now question is where the problem lies. First you can try with host/server in console and send M111 S70 this enables end stop reporting. So you see every time the end stop signal gets triggered. Do to bed center 20mm above bed and run G30 P3 several times and see if it sometimes works or always. You also see in log now timing of end stop trigger. Compare working with failing if it fails. As it is always same situation it should result in same timing. If it switches it might be a bad contact on signal wire or something else. Maybe you should enable pullup for zprobe and zmin. In my test printer config I have done that it works reliable.
The cable loom for the extruder has -extruder stepper motor wires -hotend temperature sensor -hotend power -hotend fan power -3Dtouch servo lines -3Dtouch sensor line
Will crosstalk be one of the reasons that the 3Dtouch is failing randomly? Do I just enable the pullup for probe and zmin in the firmware or I wire a 10k resistor between the zmin and 5v?
I used the internal pullup on STM processor. Not sure which resistance it has. In the end it does not matter a slong as pullup is in a good range.
Crosstalk is always a source for signal problems and we speak of 10ms signal. But it also needs high frequency or current so motor and temperature would be the possible sources, but these are off I guess during the tests. But anyhow it is a good idea to always twist the cable pairs so crosstalk gets minimized. Would also improve temperature reading.
I am using standard Arduino mega 2560 with RAMPS 1.4. Other than the LED is blinking, the serial port did not print out any message even I pull or push the probe.
Comments
https://vimeo.com/415442703
May I know what settings did I got wrong?
Increase Z_PROBE_BED_DISTANCE 10 so it starts higher also reducing the problem.
https://vimeo.com/415853438
Sometimes it fails at point 2, sometimes in point 3. The above video show that it failed in point 5. Any reason for that?
First you can try with host/server in console and send
M111 S70
this enables end stop reporting. So you see every time the end stop signal gets triggered. Do to bed center 20mm above bed and run
G30 P3
several times and see if it sometimes works or always. You also see in log now timing of end stop trigger. Compare working with failing if it fails. As it is always same situation it should result in same timing. If it switches it might be a bad contact on signal wire or something else. Maybe you should enable pullup for zprobe and zmin. In my test printer config I have done that it works reliable.
-extruder stepper motor wires
-hotend temperature sensor
-hotend power
-hotend fan power
-3Dtouch servo lines
-3Dtouch sensor line
Will crosstalk be one of the reasons that the 3Dtouch is failing randomly?
Do I just enable the pullup for probe and zmin in the firmware or I wire a 10k resistor between the zmin and 5v?
Thanks.
Crosstalk is always a source for signal problems and we speak of 10ms signal. But it also needs high frequency or current so motor and temperature would be the possible sources, but these are off I guess during the tests. But anyhow it is a good idea to always twist the cable pairs so crosstalk gets minimized. Would also improve temperature reading.
I have also separated the probe signal wires from the cable loom, it still have the same effect.
I am out of idea now, unless it is a faulty 3D touch sensor.
https://github.com/knud/BLTouchTest
failing that, maybe post your full config.h
Other than the LED is blinking, the serial port did not print out any message even I pull or push the probe.
My configuration.h is in page 1 of this thread.