Hi, I have the new 1.4 Turbo board. I also have LJC18A3-B-Z/BX NPN NO DC 6-36V 300mA 1-10mm Capacitive sensor. Worked fine on previous 1.3 board. I know there might be an issue with the board resistor but can’t figure this out. It always shows as z: open. And yes, the sensor lights up when sensing.
I have tmc2209 with the diag pin cut off and jumper set to use uart.
Current code in configuration.h is: (I tried every combination I can think of and same issue, so lets start from here please).
//#define SENSORLESS_PROBING #define AUTO_BED_LEVELING_BILINEAR #define Z_SAFE_HOMING
//#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN #define USE_PROBE_FOR_Z_HOMING #define Z_MIN_PROBE_PIN P2_00 #define FIX_MOUNTED_PROBE
Current pins_BTT_SKR_V1_4.h #define Z_DIAG_PIN P1_27 // Z-STOP #ifdef Z_STALL_SENSITIVITY
I might. I just don’t know what to look for or test. I can’t even confirm what the pin settings should be in pins…h as well as the settings required in config.h
There is tons of conflicting information out there and nothing seems to work.
Yes, it’s always on. The sensor lights up just fine when sensing. I used the exact same configuration for v1.3 and it worked fine. The output is not 12v to the sensor wire. The sensor wire barely gets any voltage. It’s just a signal. I know there is an issue with 1.4 and the resistor setup for the pins but I can’t confirm which resistor to check for. The row of resistors that have relevant numbers are all 103, indicating 10000 which should be fine.
I tried a mechanical limit switch and it reads as triggered when supposed to in the z position. However, it doesn’t stop the z movement down when triggered at the bottom. I’m at a loss because I either get no reading on capacitive sensor or I get triggered on limit switch but it still moves past.
It is always triggered when you use a microswitch? It probably needs a pullup resistor.
But that doesn’t make sense for the sensor.
Voltage or current? It needs to have enough voltage to trigger, but it is a high impedance input, so it shouldn’t allow any current. But still, if you give it 12V, it can very easily break something. But maybe the circuit is helping you, IDK.
Didn’t check current. The point is, it worked fine with this exact same sensor on 1.3
There is very little voltage passing through the signal wire. I tested on multimeter and it showed .7 mv (or something like that).
I don’t know why I can’t get marlin configured now for using the limit switch instead. I just want to test the new build and can get the other sensor working later. Like I said, it now shows triggered on z_min as it should but it keeps going down past. I remember in an older version of marlin that there was a way to bypass the z_min for setup purposes. Is that still there somewhere in marlin 2.0? I might have it allowing lower travel still.
0.7mV is never going to be enough to trigger the endstop. It doesn’t read current. It is looking for a digital signal that is eitger 5V (on) or 0V(off). Somewhere in between is where it decides if it should be on or off. It is an oversimplification, but it may be that anything above 2.5V is going to be considered on and less than 2.5V is going to be off.
One possibility is that the sensor doesn’t toggle between on and off. It toggles between (floating) and (ground). In that case, if you wired a resistor between that pin and 5V, the pin would go to 5V(on) when the sensor was floating and it would go to 0V(off) when it was tied to ground. You don’t actually have to install a resistor though. Because the chip can be configured to use an “internal pullup resistor” on that endstop. You need to enable that in configuration.h. I’m on my phone, but if you search for pullup, it will be there, and you can enable it for one specific pin.