Thank you very much for your time!
That did the trick.

I needed a normaly open switch so there is no connection between the wires when the filament is loaded.

kind regards,
Leon.

Hi to you all,

I'm using firmware version:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.0(RTOS) ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2018-06-05b3

I have connected a simple switch with two leads going to the E0-stop on the ground and the signal pin.

I have put a piece of filament in de sensor housing gausing the switch to be closed.

In de config.g I have:

; Endstops
M574 X1 Y1 Z0 E1 S0

; Filament runout sensor
M591 D1 P1 C3

With a M119 the E-stop does not show up.

What am I doing wrong?

regards,
Leon.

Found the solution already by using a typical Homez.g file for a probe.

G91 ; relative mode
G1 S2 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
G90 ; back to absolute mode
G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
G30 ; lower head, stop when probe triggered and set Z to trigger height

Thanks for the help!!

Kind regads,
Leon

@dc42
Yes thank you very much that did the job!
Instructions followed and they work now.

But please hang on with me.
I want to set the probing grid but have problems with the Z-homing. The sensor does not respond and the nozzle hits the build plate.

Must be something wrong in the homez.g

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.0(RTOS) (2018-06-05b3)
Web Interface Version: 1.19.3

; Endstops
M574 X1 Y1 Z2 S0 ; Set active low endstops

; Z-Probe
M558 P1 H2 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z0.390 ; Set Z probe trigger value, offset and trigger height
;M557 X60:700 Y60:400 S20 ; Define mesh grid
M557 X0:200 Y0:220 S20

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Thu Oct 04 2018 14:52:24 GMT+0200 (Midden-Europese zomertijd)
G91 ; relative positioning
G1 Z5 F10 S2 ; lift Z relative to current position
G1 S1 Z-100 F500 ; move Z down until the endstop is triggered
G92 Z5 ; set Z position to axis minimum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

I'm back with a brand-new Duet Ethernet board and a new Ir-sensor. Ir sensor is flashing 4 times when starting up.
I followed all the instruction several times over here but for some reason it does not work. Constantly getting the message after send "M558 P1 and G31 P500 Z1.0"

"G30 S-1
Error: Z probe already triggered at start of probing move"
Even when sensor is way up like 15 cm.

Reading is 1000 sensor way up, getting closer and touch the sensor reading 461?!
sensor lids red when touching

M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: at min stop

here a piece of my config.g where probably something is wrong

config.g
; Drives
M569 P5 S1 R1 T1 ;Y-as
M569 P6 S0 R1 T1 ;X-as
M569 P7 S0 R1 T4 ;Z-as

M584 X6 Y5 Z7 E3 ; Apply custom drive mapping
M564 S0 H0

M350 X8 Y8 Z8 E8 I1 ; Configure microstepping with interpolation
M92 X125.98 Y125.98 Z500 E495 ; Set steps per mm
M566 X300 Y300 Z50 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X5000 Y5000 Z500 E500 ; Set maximum speeds (mm/min)
M201 X200 Y200 Z50 E100 ; Set accelerations (mm/s^2)
M906 X7200 Y7200 Z4000 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S50 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X700 Y400 Z100 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z2 S0 ; Set active low endstops

; Z-Probe
M558 P1 I1 H2 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
M557 X60:700 Y60:400 S20 ; Define mesh grid

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool on Thu Oct 04 2018 14:52:24 GMT+0200 (Midden-Europese zomertijd)
M561 ; clear any bed transform
; Probe the bed at 4 points

G30 P0 X60 Y60 H0 Z0
G30 P1 X60 Y400 H0 Z0
G30 P2 X750 Y400 H0 Z0
G30 P3 X750 Y60 H0 Z0

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Thu Oct 04 2018 14:52:24 GMT+0200 (Midden-Europese zomertijd)
G91 ; relative positioning
G1 Z5 F10 S2 ; lift Z relative to current position
G1 S1 Z-100 F500 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

I hope it is a simple fault. I'm almost there to get this printer working, dealing with the frustration the nozzle has crashed several times into the build plate and the heat brake is broken now

I made a terrible mistake. Not looking good I plugged the signal wire from the IR probe into the UTXD0 pin.
When starting up de wire begon to smoke intens. No connection possible with the board anymore using ethernet consol to a PC. Also no cnnection with LCD

Is there some information available what is really damaged or do I have to replace the whole board. Seems like a chip on de little ethernet board is fried? 2 of the steppermotors make a load buzzing noise to. O boy!

Thanks!, that what I think too. I will go to my supplier.

In the control panel there is a distance probe reading like the 465 and 535.
After I zero the nozzle tip to the buildplate with G92 Z0
I entered the G30 S-1 after going 5mm up.
I get a reading of 1.15mm so I asume the sensor is triggering something?

I remembered I did not connect the board first with USB but ride away using
the ethernet cable. Could that be the reason for not flashing the led's?

Hello to you all,

Connected the IR probe version 1.3 to the board (Duet Ethernet) and when powered on there is no flashing of the leds at all.
I have measured the VCC+ en ground on the little board and there is 3.3v. Also measured if the signal lead is connected to the main board with an ohm meter and that is also fine. The probe does respond to the surface but when probing to all the points, there is no flashing and If got the message "Z probe was not triggered during probing move". Looks like the there is something wrong with the IR-probe board. What can I do. Wires to the probe are quite long around 3 meters.

kind regards,
Leon.

To complete this thread for others. I had to use the 5v connection from the breakout board to make the DM556 to work properly. For some reason the 3.3v voltage from the +signals ENA PUL and DIR does not do the job for this driver.