Inductive probe triggers but doesn't show on software

Basic Information:

Printer Model: Ratrig V-Core Pro 1.3
MCU / Printerboard: BTT Octopus v1.1
Host / SBC
klippy (12).log (2.1 MB)

5V PNP inductive probe triggers (light turns off) when it’s near metal but klipper doesn’t recognise it, I’ve checked the voltage and it does drop by around 1.5V, from 5V → 3.5V on the sensor pin. I’ve had exact same model of sensor before in this setup too, which previously worked. The pin works too, checked using a physical endstop.

First off, thank you for including your klippy.log - it may seem like it’s unnecessary but it did help me check something that you’ll see below.

3.5V is not low enough for the MCU (STM32F446) on the Octopus’s MCU’s pins to recognize that the input voltage has changed. It runs at 3.3V so you’re never falling below the power supply voltage of the chip, let alone the “low” input voltage level (which is roughly 1.1V).

Actually, what you’re seeing is exactly what I’d expect. When the PNP driver is “off”, there is no current flow and the voltage rises to the 5V of the device. When the PNP driver is on, the ESD protection in the chip (literally diodes providing a path to ground and chip power if the applied voltage is outside the chip’s VDD and GND voltage range, which in this case is 3.3V and 0V, respectively) brings the voltage down to the chip voltage plus the diode drop which is the 3.5V you’re seeing.

I suspect that the previous part you had was marginal and not working as it should. According to your klippy.log, you’re connecting to PB6 (which, according to the schematic is SERVO/CONTROL pin of the BL Touch connector) and it goes directly to the MCU with no other components.

Now according to the STM32F446 datasheet, PB6 is 5V tolerant, so there should not be any chance of burning out the chip or the IO pins.

Without having any more information on the inductive probe that you’re using, I can’t really suggest a corrective action.

I use inductive probes all the time but I use NPN drivers, which pull a voltage down to ground - Triangle Labs have 5V ones that work very nicely in typical 3Pin endstop connectors (which have 5V, GND and a pulled up sense line).


Just as another point, when I look through your klippy.log, you have:

endstop_pin = probe:z_virtual_endstop

on each of your Z steppers - you only need it on the first one.

1 Like

Thanks for confirming everything is functional, Heschen M8 Inductive Proximity Sensor Switch, Non-Shield Type, LJ8A3-2-Z/AY-DC5V, Detector 2mm, 5VDC 200mA, PNP Normally Closed(NC), 3 Wire : Amazon.co.uk: Business, Industry & Science is the probe I’ve used both times, and I’ve also removed the extra virtual endstops for the other two steppers.

Not a lot of information for this part - I did find it on the Heschen website:

but it doesn’t have anything more than what Amazon says (actually it has less).

What I would suggest is put a pull down on the signal line (4k7 to 10k) like this:

When the PNP is off, the pull down should pull the sensor (PB6) Voltage to GND (or at least less than 1V) so that the STM32F446’s PB6 pin recognizes it as a low and then when the PNP is on, you have 5V across the resistor and the STM32F446’s PB6 pin recognizes it as a high.

Sorry for the poor quality drawing.

1 Like

The drawing just helped massively, I had actually wired the probe incorrectly by looking at the tag which had 5V on the line to black, I had brown wired to PB6 and black wired to 5V, now that i’ve swapped around the two wires so that the black wire is connected to PB6 and brown to 5V it works perfectly, with 0.6V to PB6 when triggered.

1 Like

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