DuetWifi 1.0.1 and BL Touch Smart 3.0 - how to force 3.3V logic?

A Former User

Maybe this illustrates the logic levels well https://learn.sparkfun.com/tutorials/logic-levels/all#33-v-cmos-logic-levels

Nuffe

Back to square one then

Maybe it is faulty BL Touch. I'll test it with another printer tomorrow then.

Phaedrux

Very often problems with the BLTouch come down to the wiring. Either wired incorrectly, or an incomplete connection due to either damaged wire or crimp. A continuity tester comes in handy.

Second to that is a configuration problem.

This may help: https://duet3d.dozuki.com/Wiki/BLTouch_Troubleshooting

Nuffe

I test every cable when I build those, and did that multiple times afterwards too.

Configuration has been checked multiple times. I went through the troubleshooting section in the wiki pages.

But in any case I think those are correct because I am able to send s160 command to bltouch successfully to clear the error situation.

A Former User

if the input pin stays above the threshold for a high signal with the BL touch connected then the signaling should be okay i recon, if it for some reason gets pulled lower you need to add a stronger pull up resistor.

jinx

Any luck with this issue I'm having the same problem went from a v2.2 to 3 and nothing works

dc42

@jinx said in DuetWifi 1.0.1 and BL Touch Smart 3.0 - how to force 3.3V logic?:

Any luck with this issue I'm having the same problem went from a v2.2 to 3 and nothing works

Which Duet are you using, what firmware version, and what M558 command do you have in config,g?

jaurand

I am having this exact same problem. I started another thread a week ago as I tore down my old BLTouch and code and redid it. Now only S160 will clear errors. I am running latest firmware on Duet 2 Wifi. My next stop is to clear out all firmware and start from complete scratch

aidar

@Nuffe said in DuetWifi 1.0.1 and BL Touch Smart 3.0 - how to force 3.3V logic?:

I though BLTouch problem was on version 3.1 and I purchased intentionally V3.0

Hmm, i lately, about 2-3 weeks ago installed two of 3.1-s. One with Wifi, other with Maestro. Both works perfectly so far.

jinx

@dc42 so after some basic test I have come to the same conclusion that you have all made here, bad wiring!! the bl touch I got brand new out of the box white wire had a short. after putting in the older bl touch wring harness if you can call it that everything works fine. should have taken the time and tested every wire.

but thank you for putting up with me

dc42

@jinx, I'm glad you solved it.

Nuffe

Coming back to my old topic. Kinda like a summary.

I never got Smart 3.0 to work with my KosselXL, and eventually purchased smart effector. It is working perfectly and I am happy with it. I have quite old Duet Wifi board on that machine.

At the same time I also purchased 1.04c version of DuetWifi, and I am now installing that to my AM8. I started to be desperate, when the same problems again started. I originally though my board is too old and would require more tinkering with pull-up resistors etc, hence new 1.04 board. I had still possibility for wiring errors, but remembered that I have an another BLTouch. It was version 2.0. It works, at least self test etc is working ok. The same configuration and the same wiring does not work with BLTouch Smart 3.0. Maybe it is in incorrect logic mode or something.

So - eventually this topic is mystery for me. I am currently hoping that Smart 3.0 works better with SKR 1.3 I have in my Tronxy x5s, but lets see.

jnofsinger

Hello Nuffe or anyone else!

Did you ever need to force 3.3v or use a pull resistor to make the BL Touch 3.1 work at all? I understand it didn't ultimately work for you, but I am in the same boat with an older duet 1.0.1 board.

I would like to play around with a BL Touch on a Frankenstein Ender3/Duet Wifi 1.0.1. The configuration and wiring seem pretty straightforward and was just wondering if the BL voltage on the older board was going to be a problem.

Thanks,
Jim

dc42

The current BLTouch models should work OK with Duets (and other users seem to get them working), but if you use them connected to the Duet 2 or Duet Maestro Z probe input and you are using RRF3, then you must enable the pullup resistor in the M558 command.