How can be add that the Software check in the 3d Touch is deployed for homing

[Laen]

Basic Information:

Printer Model: Anet A8
MCU / Printerboard: MKS Robin Nano v3
Host / SBC MKS Pi v1.1
klippy.log

Hi

I have since i switched from Marlin to Klipper a Problem with the 3D Touch sensor.

The Problem is that it sometimes not deploy the Pin but the system try to homing and crash in the bed.

How and is there a Way that the system can check 2-5 times if it is deployed before moving to home the Z axis.

Even if it takes several seconds of time.

Under Marlin the System has not that Problem

Its bad for crashing an new calibrating the Z Axis after that.

Its not happens everytime but sometimes and then a while not

…

printer.cfg (6.3 KB)

[EddyMI3D]

Hello @Laen and welcome to the forum.

Please attach the klippy.log to your next post.

As you are using a BL Touch clone, you may have a look here: BL-Touch - Klipper documentation

[Laen]

yeah the log of a full day of using that is to big for here.

Dropbox

I can not let that happens on command. It happens 4 times today and of that 2 times without error message.

Yeah i have a clone but i dont unterstand anything on that page what i need to use.
I got the system to run but i not a programmer

[EddyMI3D]

Please upload the log here. If too large, you can compress it with e.g. zip.

[Laen]

@EddyMI3D

If too large, yo

i extra added it per dropbox but yeah in needed first zip. complicate to net let rar use

klippy(1).zip (1.5 MB)

[Laen]

klippy(1).zip (264.9 KB)

happens again not 1 minute ago before downloading the log

[EddyMI3D]

You get this message in the klippy.log:

BLTouch failed to verify sensor state; retrying.

If this occurs, then manually run the steps to confirm the sensor pin is working as described in the initial tests section.
In result:

If the QUERY_PROBE commands in that test always produce the expected results and “BLTouch failed to verify sensor state” errors still occur, then it may be necessary to set pin_up_touch_mode_reports_triggered to False in the Klipper config file.

[Laen]

the problem is that “BLTouch failed to verify sensor state; retrying.” not everytime comes.

With the Error message its abort homing.

But when the error not appears it trys to homing but the pin is not out.

Happens before the last print in this Log

klippy(2).zip (649.7 KB)

Its a 50/50 chance that the Error Message comes an abort the Homing.
Or it doesnt appears and move in the Bed

[cardoc]

@Laen

switched from Marlin to Klipper a Problem with the 3D Touch sensor.

The Problem is that it sometimes not deploy the Pin but the system try to homing and crash in the bed.

Try inverting your sensor pin.

[bltouch]
sensor_pin: ^PC8
control_pin: PA8
x_offset: -23
y_offset: -30
z_offset: 1.000
probe_with_touch_mode: True
stow_on_each_sample: False
pin_up_touch_mode_reports_triggered: False

[Laen]

can you explain simple what each of these

probe_with_touch_mode: True
stow_on_each_sample: False
pin_up_touch_mode_reports_triggered: False

options does?

i want to understand it

[Laen]

#probe_with_touch_mode: True

that can not be used because the System doesnt regocnize any input of the Touch sensor.

It put down the pin and ignores the input ab crashh full strength in the bed until power cut the system

[EddyMI3D]

Have you checked the wiring?

[Laen]

the wirting is ok an how it shoulld after MKS.
Why should the Wiring be not ok?

Under Marlin it was working everytime and since that nothing changed

[cardoc]

@cardoc

sensor_pin: ^PC8

The key is to put the ‘^’ in front of the pin name. Comment out the logic lines for now.

[mykepredko]

The MKS Robin Nano V3.x has a long list of people who have had problems with connecting a BL Touch or functional clone to the board.

@cardoc

@cardoc

sensor_pin: ^PC8

The key is to put the ‘^’ in front of the pin name. Comment out the logic lines for now.

That may not work with the pin that @Laen has selected.

There is a pull up of unknown value along with a current limiting resistor on the Z- pin (which is PC8):

The actual connection @Laen is wiring to is the z-0 net in the diagram above.

You haven’t said what kind of “3D Touch” hardware you are trying to use.

Personally, when I first used the Robin Nano V3.0 (my first main controller board that I installed Klipper on), I was using a clone BL Touch and had similar problems as @Laen. I changed to a genuine BL Touch which worked with the board.

Sorry.

[cardoc]

@mykepredko

The MKS Robin Nano V3.x has a long list of people who have had problems with connecting a BL Touch or functional clone to the board.

Very true. The OP however states the hardware worked flawlessly under Marlin.

It works intermittently under Klipper so I have to assume PC8 is the correct pin address.

I thought flipping the pin might work.

[mykepredko]

@cardoc

Very true. The OP however states the hardware worked flawlessly under Marlin.

It works intermittently under Klipper so I have to assume PC8 is the correct pin address.

That was my experience with the clone BL Touch that I was using.

I had a genuine BL Touch on another printer so I tried it on the problem printer which had the Robin Nano V3.1 and it worked so I just got another BL Touch and ran it on both printers.

@cardoc

I thought flipping the pin might work.

The “^” parameter enables the internal pull up on the MCU, “!” inverts its function.

Suggesting adding “^” is kind of a go-to suggestion when there are problems with a BL Touch or clone but is controller board hardware dependent and may not work, as in this case, where there is a resistor network on the IO pin.

Unfortunately, neither Antclabs nor any of the BL Touch clone vendors (including Creality) publish the schematics for their sensors so understanding what’s happening here really isn’t possible without a lot of work and it could be very hardware (controller board and “BL Touch” circuitry) dependent so it would not result in any general case rules.

As a quick suggestion (I’ve never done this), @Laen could try using another pin which does not have any hardware attached to it like PB10/TXD3:

I haven’t tried it but it gives a clean connection on the “3D Touch” sensor pin for @Laen to try out - I would recommend using the “^” option on the pin if you do this.

Sorry, I wish I had a better answer.

[Laen]

i will try ^

but other pins are not free on the robin nano v3. Uaert3 is my connetion to the mks pi. ^^

I have a 3d touch from aliexpress (3d touch printed on) an its years in use. Like i said in marlin not that problem . Only since i switched to klipper 2 years ago. And some times not every time

[Laen]

have add ^to the config. now i look if that error happens the next days.

I think the BL touch was from MKS too like the pi and the robin nano v3.

And like i said no extra pins free. everything is populated.

bl touch has its own pins

[mykepredko]

@Laen

but other pins are not free on the robin nano v3. Uaert3 is my connetion to the mks pi. ^^

If TXD3 isn’t available, how about TXD1 which is connected to PA9 - I just checked the printer.cfg you posted and that isn’t used.

It’s on J24:

I’m only suggesting these pins because the two wire connector that has the Sensor pin also requires a ground line and these pins are next to the TXD# pins I’m suggesting.

I don’t think MKS makes or resells a BL Touch clone.

@Laen

Like i said in marlin not that problem .

I hear you and I experienced the same thing you did.

The problem is there isn’t any documentation for these devices that would help pinpoint exactly what’s happening and what the differences between them without a lot of work and having a good range of them to test.

The only real recommendation I can make that I’m sure will work is to only use the genuine Antclabs BL Touch. It costs more than twice as much as the clones but I’ve never had a situation where it doesn’t work.