npn 5v fly rrf e3

npm1

@jay_s_uk im using 5v from the bltouch connector and the original zstop connector...its from china brought through aliexpress M12 4mm DC 5V NPN NO LJ12A3-4-Z/BX-5V Inductive Proximity Sensor.

It is a widely used component in the automatic control industry for non-contact detection, control and switching.
When the proximity switch is close to a target object, it sends out a control signal.
As it is a capacitive type proximity switch, its sensing object target is not limited to conductor, but also liquid and even powdery objects, like plastic, water, glass , oil, etc.
It is widely used in machine, papermaking, light industry for limiting station, orientation considering, acceleration test ect.

Specifications:
3-wire polarity: NPN sensing
Voltage: DC 5V
Sensing distance: 4mm
Output status: normally open
Output current: 300mA
Sensing objects: Conductor
Part number: LJ12A3-4-Z/BX
Screw length: 61mm
Quantity: 1 Pc
Note:
Please allow 1-3mm error due to manual measurement. Please make sure you don't mind before you bid
Due to the difference between different monitors, the picture may not reflect the actual color of the item. Thank you!

Package Content:
1pc x Inductive Switch

jay_s_uk

@npm1 what wires do you have going to where?

npm1

@jay_s_uk I have the + wire going to the 5v connection for the bltouch, the negative going to the left of the zstop connection and the signal going to the right of the zstop connection

npm1

@jay_s_uk the sensor lights up correctly when i put metal prong against it

gloomyandy

@npm1 Please try the following...

Run M98 P"config.g" and post any output.
Run M119 and G31 in the console both with and without the probe being triggered.
3 Comment out the line: M574 Z1 S2 and then repeat the two tests run above.
Power off the board, remove the Z driver module, power the board on again and re-run the tests in step 2.
Post the output from all 6 of the tests.

npm1

@gloomyandy
With M574
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped
G31
Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0

npm1

@gloomyandy Without M574
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Endstops - X: not stopped, Y: at min stop, Z: no endstop, Z probe: not stopped
Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0

gloomyandy

@npm1 Are those results with or without the probe being in a triggered state?

npm1

@gloomyandy the first response is with m574 and the second response is without m574

gloomyandy

@npm1 Yes but I asked you to run M119 and G31 twice for each test once without having the probe in a triggered state and then again with the probe in a triggered state (by placing something metal near it so the LED comes on). Have you run the test with the Z driver removed?

npm1

@gloomyandy
without m574 and with metal touching the probe

g31

Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0
2/25/2022, 8:46:38 PM g31
2/25/2022, 8:46:16 PM M119
Endstops - X: not stopped, Y: at min stop, Z: no endstop, Z probe: not stopped
2/25/2022, 8:45:56 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

npm1

@gloomyandy with 574 and metal touching probe
g31
Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0
2/25/2022, 8:50:23 PM g31
2/25/2022, 8:50:05 PM m119
Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped

gloomyandy

@npm1 and the results with the Z driver removed from the socket?

npm1

@gloomyandy

removed z driver with m574
g31
Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0
2/25/2022, 8:59:47 PM M119
Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped
2/25/2022, 8:59:44 PM M119
2/25/2022, 8:59:33 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

npm1

@gloomyandy removed z driver with m574 metal touching

g31
Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0
2/25/2022, 9:01:46 PM g31
2/25/2022, 9:01:24 PM M119
Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped

npm1

@gloomyandy removed z driver without m574

g31

Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0
2/25/2022, 9:04:04 PM g31
2/25/2022, 9:03:53 PM M119
Endstops - X: not stopped, Y: at min stop, Z: no endstop, Z probe: not stopped

npm1

@gloomyandy removed z driver without m574 metal touching

G31

Z probe 0: current reading 0, threshold 500, trigger height 2.500, offsets X0.0 Y0.0
2/25/2022, 9:05:35 PM m119
Endstops - X: not stopped, Y: at min stop, Z: no endstop, Z probe: not stopped

npm1

hope that helps

gloomyandy

@npm1 Are you still using this line for your probe definition:

M558 P5 C"!^zstop" H5 F120 T6000

If so with the Z driver still removed enter

M558 P5 C"zstop" H5 F120 T6000

in the console (or change the line in your config.g and reboot)
and rerun both sets of tests.

npm1

@gloomyandy still no changes, the only thing that change is the z probe value being 1000 instead of zero