npn 5v fly rrf e3

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

npm1

@gloomyandy have I blown something on the board

npm1

shall i update the firmware

npm1

Electronics
Diagnostics
Board: fly_E3 (STMWiFi)
Firmware: RepRapFirmware for STM32F4 based Boards 3.3RC2+1_1 (2021-05-13)
Duet WiFi Server Version: 1.26-01S-D

Note: You can install updates on the System page.

npm1

will marlin be easier

gloomyandy

@npm1 Can you turn off your board, disconnect the probe and plug in one of the other endstop switches (x or y) into the zstop socket. Then run the two tests again once without pressing the endstop switch, then again with the endstop switch pressed. Run this test with the Z driver still removed.

npm1

@gloomyandy endstop works with zero issues with everything triggered correctly

M119

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

npm1

@gloomyandy the only thing i can think of is to switch the cables on the zstop cables around

gloomyandy

@npm1 @npm1 In which case I would be looking very closely at that probe. Are you sure you have correctly identified the various wires? See: https://forum.duet3d.com/topic/25906/inductive-sensor-npn-no-not-working?_=1645824856161 (thanks to Jay for digging that one out).

npm1

@gloomyandy i knoq that the 5v cable is correctly connected ill switch the cables around and confirm to you shortly

npm1

I'm just gonna call it a day, may use an optical setup it with one of those allen keys

npm1

thanks for your efforts