@droftarts I am not using that comand, it was there from a configuration file example.

Okay that’s what I will do, move to the Z probe pin.

Here is all the info, I did not know about M98, it seems very handy.

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJ3SW-6JKD6-3S86R-1BMZG
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94064 of which 44 recycled
Exception stack ram used: 264
Never used ram: 8720
Tasks: NETWORK(ready,392) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:37 ago, cause: software
Last software reset at 2020-09-24 07:15, reason: User, spinning module GCodes, available RAM 8720 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 34.8, current 36.1, max 36.2
Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-09-24 07:16:33
Cache data hit count 61822017
Slowest loop: 1.31ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.4ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 70.27ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address cc:50:e3:76:3f:ab
WiFi Vcc 3.36, reset reason Unknown
WiFi flash size 4194304, free heap 23888
WiFi IP address 192.168.1.239
WiFi signal strength -52dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 0 0 0 0 0

M98 P"config.g"
Warning: M918: Command is not supported
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin 'zstop' does not support mode analog read
Error: Invalid Z probe index
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 170C

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Sep 15 2020 22:46:11 GMT+0200 (Central European Summer Time)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Ender-3"                                    ; set printer name
M918 P1 E4 F2000000                                ; configure direct-connect display

; Network
M552 S1                                            ; enable network
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

; Drives
M569 P0 S0                                         ; physical drive 0 goes backwards
M569 P1 S0                                         ; physical drive 1 goes backwards
M569 P2 S1                                         ; physical drive 2 goes forwards
M569 P3 S1                                         ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                                   ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E408                   ; set steps per mm, ender original E106
M566 X1200.00 Y1200.00 Z120.00 E300.00              ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z900.00 E6000.00            ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z400.00 E5000.00              ; set accelerations (mm/s^2)
M906 X700 Y700 Z800 E1000 I30                      ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout
M204 P600 T2000

; Axis Limits
M208 X-10 Y0 Z0 S1                                   ; set axis minima
M208 X215 Y225 Z260 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                                ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2

; Z-Probe
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
M558 P1 C"zstop" H5 F120 T3000  ; Z probe connected to Z endstop input
G31 P500 X0 Y0 Z2.5
M557 X15:210 Y15:210 S20                           ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092     ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                              ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00                                   ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S100                                       ; set temperature limit for heater 0 to 100C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 C0 R4700      ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                               ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit

; Fans
M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                               ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500                               ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1:0 T45                                ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0                                   ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C
M572 D0 S0.35

; Custom settings

; Trigger buttons
M950 J0 C"^e0stop"
M950 J1 C"^e1stop"
M581 P0 T2 S1
M581 P1 T3 S1


; Miscellaneous
M501                                               ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Hello, I connected the DC42 IR sensor to my board using the Z0 endstop connector, and I can see that electronically the power (3V3) and connection is good (in standby the status led of the sensor is on, when I put something nearby the sensor the led goes off, also, the led on the motherboard has the inverted state of the led on the probe).

The issue remains with the config file, in which I have the following lines:

; Endstops
M574 X1 S1 P"xstop"                                ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2

; Z-Probe
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
M558 P1 C"zstop" H5 F120 T3000  ; Z probe connected to Z endstop input
G31 P500 X0 Y0 Z2.5

And I can't seem to figure it out. On the first page under sensors I don't even have a "Probe" sensor. Also, if I run G31 in the console it returns:

Error: G31: Invalid Z probe index

Thanks guys, it seems to be what I was looking for!

I am looking for a way to test a few Z probe types for their accuracy but to my surprise I could not find a command or example macro for this. In klipper or marlin there are dedicated functions for this.

I know from the probe calibration page that I can raise Z a few millimeters then lower Z until the probe is triggered and the height will be reported, but could I store this value in a list and repeat the command 10 times? Then (not necessarily but would be nice) do some math calculations with the numbers to determine mean value, standard deviation.

Any of you have an idea of this can be implemented?

@jay_s_uk This seems interesting! I'll give it a look and try to replicate the project.

Hello, I saw that it's possible with the Duet Maestro to keep the originak LCD panel and controls from the Ender 3 printer. I would like to do the same with my Duet 2 WiFi board.
Could I manually adapt the hardware pins with a connector and then activate the LCD support from software? How can I find out what pins do I need.

Thanks for your help!

@Phaedrux Yes it is a clone, that's the name, 3D Touch. Everytime I wonder if the probe is not the issue, and I'm not sure, I plan to replace it with a IR-probe to clarify this unknown variable.

@fcwilt the phisical offset is 2.9mm in reality