Having issues getting BLTouch to work (constantly triggered status)

General Discussion
1

Basic Information:

Printer Model: Custom CoreXY
MCU / Printerboard: Duet 2 Wifi
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…

I’m currently in the process of setting up Klipper on my Duet 2 WiFi board, however my Z endstop status is stuck on TRIGGERED always. I can communicate with the probe and send, up, down etc query commands so it would seem that control_pin is fine but sensor_pin is not working?

I have it hooked up to the probe pin PC1 as per duet documentation.

Config section is below.

[bltouch]
sensor_pin: PC1
control_pin: PA15
stow_on_each_sample: False

This determines if Klipper should command the pin to move up

between each probe attempt when performing a multiple probe

sequence. Read the directions in docs/BLTouch.md before setting

this to False. The default is True.

probe_with_touch_mode: true
z_offset: 3
x_offset: 20
y_offset: -5
pin_move_time: 0.3
speed: 16
lift_speed: 16
samples: 1
samples_result: median
sample_retract_dist: 5.0
samples_tolerance: 0.01
samples_tolerance_retries: 3

I also don’t know if I need to edit anything on Z stepper

[stepper_z]
step_pin: PD8
dir_pin: PD13
enable_pin: !PC6
microsteps: 64
rotation_distance: 10
endstop_pin: ^PD29
#endstop_pin: PD10 # E0 endstop
#endstop_pin: PC16 # E1 endstop
position_endstop: 0.5
position_max: 235
homing_speed: 50

console log:

10:17 PM
probe: open
10:17 PM
QUERY_PROBE
10:17 PM
x:open y:open z:TRIGGERED
10:17 PM
QUERY_ENDSTOPS
10:15 PM
x:open y:open z:TRIGGERED
10:15 PM
QUERY_ENDSTOPS
7:58 PM
x:open y:open z:TRIGGERED
7:58 PM
QUERY_ENDSTOPS

2

I guess when you filled out this post, you somehow missed this:

image
image947×109 5.32 KB

Which is strange because you put in all the requested information above the need for you to attach the klippy.log.

3

sorry… I did miss that.

Attached
klippy.log (3.1 MB)

4

I couldn’t find accurate schematics for the Duet 2 Wifi so you might have to play with the values a bit. Do you know the version of the board that you have?

First off, in your [stepper_z] statement why do you have endstop pin = ^PD29 defined? Isn’t your Z axis endstop the BL Touch (which is a “probe”)? I’m not sure how (or if) they will work together.

To get ONLY the BL Touch working, you need to change the endstop pin = ~PD29 parameter to endstop_pin: probe:z_virtual_endstop to pick up the BL Touch.

Along with specifying the endstop_pin probe, change your sensor_pin = PC1 parameter in the BL Touch statement to sensor_pin = ^PC1 to enable the internal pull up in the MCU as the BL Touch pin is open collector/open drain.

1 Like
5

Is it a genuine BLtouch or some clone?

Also: For what do you use the BLtouch?

Not for homing:

[stepper_z]
step_pin = PD8
dir_pin = PD13
enable_pin = !PC6
microsteps = 16
rotation_distance = 8
endstop_pin = ^PD29    # <---
position_endstop = 0.5
position_max = 200

And not for the bed mesh:

There is no [bed_mesh] macro.

6

Yeah this is a genuine BLtouch 3.1. My duet is a Wifi 1.02 genuine board as well.

Thank you for the pointers, I knew it had to be something with stepper_z config but I wasn’t sure what to put there, so now it’s no longer showing triggered after adjusting probe:z_virtual_endstop

Also, yeah there was no bed mesh macro as I hadn’t even got that far yet, was trying to get the probe to work first.

But now, i’m getting a new error when homing
“BLTouch failed to verify sensor state; retrying.”

I can still send pin up / pin down and that all works fine though.

edit, ok i added
pin_up_touch_mode_reports_triggered: False
And now it starts to home.

edit2, ok so it still does not actually trigger once the pin is pressed.
I did change my sensor pin pullup
[bltouch]
sensor_pin: ^PC1
control_pin: PA15

edit3, ok so all I did was flip the black and white wires on the PC1 / probe pins and NOW it triggers? strange. moving onto setting up bed mesh.

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.