EBB SB2209 RP2040 : Bltouch always open

[cruzer619]

Having issue with Bltouch on newly installed EBB SB2209 RP2040 on manta m8p canbus. I'm able to manually pin up and pin down. but wont sense pin up doing touch mode. everything else works on the ebb, thermistor, heater cart, fans, limit switch and extruder motor. Please help. Thanks.

klipper printer.cfg portion.

[bltouch] sensor_pin: ^EBBCan:gpio21 control_pin: EBBCan:gpio22 x_offset: 0 y_offset: -23 speed: 10 samples: 3 sample_retract_dist: 5.0

[cruzer619]

ok if anyone searches this. This is what I had to do get bltouch working. As it seems that gpio21 has issues as with others in the Tap #76 area are complaining as well. Since bltouch uses gpio22 for control can't just switch to like the tap guys. So I had to move things around. I had to gpio21 wire to gpio24. also move the ground wire as well. So its 2 wires moving to xstop connector. Then for xstop I used gpio6 but you have to jumper on IND and jumper on NPN.

[Ixian]

I don't know if this can be re-opened but it really shouldn't be closed - the problem still exists, and while it is possible to tap another gpio port that is A) a hack and B) takes away use of that port. Right now I have to use two ports for my CR Touch which means I also had to choose between an end stop and a filament sensor. If this worked like it should I wouldn't have this problem.

The board is shipping broken and BTT needs to address it. From the looks of it, gpio21 either doesn't work with a pullup set, or it is too weak, meaning the state will always show 1 (closed) because of the float. I can try playing around with external pullup resistors, though that isn't the long term solution either.

[cruzer619]

@Ixian think your right.. will leave it open as there needs to be a fix.

[Gardosen]

For People like me who uses the Endstop for the X Endstop, it is not even a useable workaround....

this is really fucked up to be honest.....

[cruzer619]

For People like me who uses the Endstop for the X Endstop, it is not even a useable workaround....

this is really fucked up to be honest.....

@Gardosen actually this workaround uses the proximity port/3rd fan port. If you need that port then this workaround doesn't work for you. As we are using that port for X endstop. Still this sucks as we are not using the indented port for what its suppose to be used for. But i'm glad I found a workaround or I would have a useless device.

[kenny000666]

I have put the crtouch into GPIO6 and it works so at least i got a working printer again, but sacrificing the filament sensor.

Has anyone tried putting a 10k resistor between vcc and ground like diagram B here? - https://reprap.org/wiki/File:Reprap_endstops_schem_mech.png

I might try this with a normal endstop, and if it works, at least we can get a working pin

[thatguywhodoesthethings]

I have put the crtouch into GPIO6 and it works so at least i got a working printer again, but sacrificing the filament sensor.

Has anyone tried putting a 10k resistor between vcc and ground like diagram B here? - https://reprap.org/wiki/File:Reprap_endstops_schem_mech.png

I might try this with a normal endstop, and if it works, at least we can get a working pin

Have you gotten a chance to try yet?

[kenny000666]

No, didn’t work. Wired in a 10k resistor and didn’t get the desired results. Swapped it out for the non-rp2040 SB2209 in the endOn 14 Apr 2024, at 14:28, thatguywhodoesthethings @.***> wrote:

I have put the crtouch into GPIO6 and it works so at least i got a working printer again, but sacrificing the filament sensor. Has anyone tried putting a 10k resistor between vcc and ground like diagram B here? - https://reprap.org/wiki/File:Reprap_endstops_schem_mech.png I might try this with a normal endstop, and if it works, at least we can get a working pin

Have you gotten a chance to try yet?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[cruzer619]

@thatguywhodoesthethings @kenny000666 the other you can do is ditch the bltouch/crtouch ( what i'm thinking of doing, want to add ERCF v2 to my printer ) and get klicky or tap type probe. Won't need a sensing pin. And then you have enough ports for filament sensor. So you would use bltouch port for your klicky/tap gpio22 only. then xport for x endstop. Then proximity port with my workaround config for Filament sensor.

[kenny000666]

Yes, I considered that also. Similar to the Tap workaround and use GPIO22 as the z-sensor. I also have Ercfv2 on my printer, and it’s better if you have 2 sensors for the extruder and toolhead. The non-Rp2040 version has enough working pins (and then some) out of the box to solve this problem, so I went that direction. Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[cruzer619]

2 sensors for the extruder and toolhead. The non-Rp2040 version has enough working pins (and then some) out of the box to solve this problem, so I went that direction. Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

hrmmm good point. but can work with only 1 sensor on the toolhead for ercf.. oh and there is no issue with the bltouch port on the non-rp2040 version... it all works right??

[kenny000666]

I figured whilst I had the ports and microswitches, why not use the 2 sensor version of clockwork2.

Yes, the non-rp2040 version works with BLtouch with no issues. Main downside to this version is the connectors are way smaller and a PITA to crimp. Also the temperature sensor port is blocked by the clockwork 2 case so you gotta remove the the sb2209 to plugin the temp sensor. Makes hot swapping or maintenance difficult. Otherwise, functionality wise, it all works

[drowfx]

Looking at the schematic it is clear why this cannot work:

• the rp2040 gpio21 has the internal pullup, which is what is activated when the pin is declared as ^EBBCan:gpio21 in klipper
• between the gpio21 and the external connector (P9, pin 5; or the leftmost pin of the connector labeled "Probe") sits a 74LVC2G17DW buffer (U13) in the schematic. this is a unidirectional schmitt-trigger buffer which is here used to make the input 5V-safe, which the rp2040 is not
• but this means that any internal pullup set via klipper on the rp2040 is totally useless - the input is always actively driven by the buffer chip. To work with an external switch (filament sensor, endstop, ...) that simply closes against GND in one state and is open in the other, a pullup resistor is needed on the input side of the buffer.

One workaround is to solder a ~10 kOhm resistor between pins 2 and 5 of the P9 connector. This adds the necessary pullup and should be moderately easy to solder on the back of the board.

A real fix would have to be done by BTT (add a pullup and a jumper to enable/disable it, at the input side of U13). Or at least this limitation should be clearly documented.

[julien-f-leroy]

@drowfx I tried your workaround to solder a 10kOhm resistor between the pin 2 and 5 of the P9 and it worked perfectly.

[kgadberry]

@drowfx So if I understand correctly, pin 5 (gpio21) is 5v-tolerant?

Wouldn't it possible then to just configure the probe to output 5v to the signal pin instead of operating in open drain mode? (Assuming the probe has that capability, which I believe the BLTouch 3.0 does.)

That said, connecting a 10k resistor between pins 2 and 5 does work, and I appreciate the insight.

[drowfx]

@drowfx So if I understand correctly, pin 5 (gpio21) is 5v-tolerant?

The gpio21 of the rp2040 controller itself is not 5V tolerant. The pin 5 of the external connector is not directly connected to the rp2040, but there is a chip inbetween that translates the external 5V input to 3.3V for the rp2040. That makes the external input (pin 5 of P9) 5V tolerant.

Wouldn't it possible then to just configure the probe to output 5v to the signal pin instead of operating in open drain mode? (Assuming the probe has that capability, which I believe the BLTouch 3.0 does.)

Yes, if your probe supports push-pull mode that would work too, without the external pull up resistor. My suggestion with the resistor was for cases where the probe/sensor only works in open drain mode, or a simple switch is used which shorts the pin against GND when closed (e.g. filament sensor).

That said, connecting a 10k resistor between pins 2 and 5 does work, and I appreciate the insight.

Thanks.

[cruzer619]

going to try the 10k workaround this weekend.. will be nice to have more ports available for when I get ercf v2..

[IggyTheWolf]

I'm running into the same issue. can someone point me in the right direction as which are pin 5 and 9?

[kgadberry]

I'm running into the same issue. can someone point me in the right direction as which are pin 5 and 9?

You're looking for pins 2 and 5 of the connector that's labeled P9 in the schematic, which is the "probe" connector on the board.

See this diagram.

You want to connect a pull-up resistor between +5v and (pin 5 which connects to) GPIO21. This brings the pin to a default state of logic high and the probe completes the path to ground when triggered which brings the pin to logic low. Without the resistor the pin can only be logic low unless the probe itself applies +5v, as the BLTouch/CRTouch can be configured to do.

[IggyTheWolf]

@kgadberry Thanks! I'll add a 10K between the two. I'm surprised this hasn't been fixed on the board or microprobe.

[IggyTheWolf]

I added a 10K resistor between pin 2 and 5 (5v and GPIO21) and either the probe is always triggered when deployed or always open.

I'm going to try and use GPIO6 and see if that will work in place of GPIO21

EDIT: Same result with GPIO6

[cruzer619]

I added a 10K resistor between pin 2 and 5 (5v and GPIO21) and either the probe is always triggered when deployed or always open.

I'm going to try and use GPIO6 and see if that will work in place of GPIO21

EDIT: Same result with GPIO6

if you hookup the bltouch directly to the main board.. do you get the same results... I thought I was having an issue with the sb2209 turned out to be the bltouch.. ( but mine was a clone, got OG and worked as expected directly from mainboard. and then worked from sb2209 with my workaround. still haven't done the 10k resister workaround yet. )

[IggyTheWolf]

@cruzer619 I'm using the MicroProbe, but I can check to see if it works plugged in directly to the board. Right now the Microprobe deploys and stows just fine, it just either registers fully open or closed, even with a 10K resistor on GPIO21 and connected to GPIO6

[looxonline]

@cruzer619 I'm using the MicroProbe, but I can check to see if it works plugged in directly to the board. Right now the Microprobe deploys and stows just fine, it just either registers fully open or closed, even with a 10K resistor on GPIO21 and connected to GPIO6

The microprobe will always be triggered when stowed. It is only not triggered when deployed.

[IggyTheWolf]

@looxonline right, but mine is either always triggered even when deployed, or always open even when stowed.

Here's my config:

gcode:
    SET_PIN PIN=probe_enable VALUE=1

[gcode_macro PROBE_UP]
gcode:
    SET_PIN PIN=probe_enable VALUE=0

[output_pin probe_enable]
pin: EBBCan:gpio22  # Set to the control pin on your board
value: 0

[probe]
pin: ^!EBBCan:gpio21  # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger 
deactivate_on_each_sample: False
x_offset: 0.0
y_offset: 25
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
    PROBE_DOWN
    G4 P500
deactivate_gcode:
    PROBE_UP 

[looxonline]

@looxonline right, but mine is either always triggered even when deployed, or always open even when stowed.

Here's my config:

gcode:
    SET_PIN PIN=probe_enable VALUE=1

[gcode_macro PROBE_UP]
gcode:
    SET_PIN PIN=probe_enable VALUE=0

[output_pin probe_enable]
pin: EBBCan:gpio22  # Set to the control pin on your board
value: 0

[probe]
pin: ^!EBBCan:gpio21  # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger 
deactivate_on_each_sample: False
x_offset: 0.0
y_offset: 25
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
    PROBE_DOWN
    G4 P500
deactivate_gcode:
    PROBE_UP 

So you are saying that the triggered state does not change at all when the probe changes between stowed and deployed?

[IggyTheWolf]

@looxonline right, but mine is either always triggered even when deployed, or always open even when stowed. Here's my config:

gcode:
    SET_PIN PIN=probe_enable VALUE=1

[gcode_macro PROBE_UP]
gcode:
    SET_PIN PIN=probe_enable VALUE=0

[output_pin probe_enable]
pin: EBBCan:gpio22  # Set to the control pin on your board
value: 0

[probe]
pin: ^!EBBCan:gpio21  # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger 
deactivate_on_each_sample: False
x_offset: 0.0
y_offset: 25
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
    PROBE_DOWN
    G4 P500
deactivate_gcode:
    PROBE_UP 

So you are saying that the triggered state does not change at all when the probe changes between stowed and deployed?

Yes. If I remove ! to the probe pin it's always triggered and if I add it, it's always open.

I think my probe is defective since the same thing happens when it's plugged into GPIO6.

[cruzer619]

question.. shouldn't [bltouch] be used. even if its a microprobe. so it knows there is a sensing pin.. which from looking at the support page in biqu.. I just never used [probe] for bltouch type devices. tap or klicky yes.. none sensing probe types. again I could be wrong.. but thats how i've used it with klipper in the past.

[cruzer619]

This is my config :

[bltouch] #control_pin: PB1 #sensor_pin: ^EBBCan:gpio21 sensor_pin: ^EBBCan:gpio24 control_pin: EBBCan:gpio22 x_offset: 0 y_offset: -23 speed: 20 samples: 2 sample_retract_dist: 5.0 #pin_up_reports_not_triggered: True #pin_up_touch_mode_reports_triggered: True #probe_with_touch_mode: True

[IggyTheWolf]

@looxonline right, but mine is either always triggered even when deployed, or always open even when stowed. Here's my config:

gcode:
    SET_PIN PIN=probe_enable VALUE=1

[gcode_macro PROBE_UP]
gcode:
    SET_PIN PIN=probe_enable VALUE=0

[output_pin probe_enable]
pin: EBBCan:gpio22  # Set to the control pin on your board
value: 0

[probe]
pin: ^!EBBCan:gpio21  # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger 
deactivate_on_each_sample: False
x_offset: 0.0
y_offset: 25
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
    PROBE_DOWN
    G4 P500
deactivate_gcode:
    PROBE_UP 

Fixed:

[probe] pin: ^EBBCan:gpio21

Is this the case for V2 probes as well?