Duet 2 wifi homing issue

nicaris

Hi all
Could use some help homing my Ender 5 plus running a Duet 2 wifi .
I completely mashed my config (working on a different printer ) but this had been working fine.
Now I can home X and Y but when I try to home Z the print head moves away form the X endstop .

Links to my Config.g and Homeall :
config.g homeall.g

droftarts

@nicaris After homing X and Y, your homeall.g tries to move to the bed centre:

; home Z
var xCenter = move.compensation.probeGrid.mins[0] + (move.compensation.probeGrid.maxs[0] - move.compensation.probeGrid.mins[0]) / 2 - sensors.probes[0].offsets[0]
var yCenter = move.compensation.probeGrid.mins[1] + (move.compensation.probeGrid.maxs[1] - move.compensation.probeGrid.mins[1]) / 2 - sensors.probes[0].offsets[1]
G1 X{var.xCenter} Y{var.yCenter} F6000 ; go to bed centre
G30 ; probe the bed

Does it move to the centre?

You have a BLTouch configured. What reading do you see in DWC for 'Z-Probe'? It should be '0'. Does the probe pin deploy? If not see https://docs.duet3d.com/User_manual/Troubleshooting/BLTouch_troubleshooting

Test the direction of movement of the Z axis, see https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors
If you command a positive move of the Z axis, the bed should move away from the nozzle. Does it? If not, change the direction of the motor by changing the S parameter of the M569 command of the corresponding motor(s).

Please post the response to M122, so we can see which firmware version you are using.

Ian

nicaris

@droftarts
Hi
sorry for the delay
The probe does deploy. I can home the x and y but the head will move away from the x and Y axis along the x axis (emergency stop triggered !
This is the output from my M122
Thanks in advance

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.2 (2024-11-12 08:12:30) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9X6JA-JUNSW-6JKD0-3S46M-TBLVV
Used output buffers: 2 of 26 (14 max)
=== RTOS ===
Static ram: 23536
Dynamic ram: 66796 of which 16 recycled
Never used RAM 30580, free system stack 184 words
Tasks: NETWORK(1,ready,17.6%,141) HEAT(3,nWait 5,0.0%,328) Move(4,nWait 5,0.0%,361) MAIN(1,running,81.8%,760) IDLE(0,ready,0.5%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:06:04 ago, cause: software
Last software reset at 2024-11-14 10:56, reason: User, Gcodes spinning, available RAM 14232, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 28.1, current 28.8, max 29.6
Supply voltage: min 23.9, current 24.2, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-11-20 12:31:45
Slowest loop: 751.18ms; fastest: 0.19ms
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 251.0ms, write time 157.6ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
no step interrupt scheduled
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 2363.74ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0
MAC address 48:3f:da:a6:e3:4c
Module reset reason: Power up, Vcc 3.41, flash size 2097152, free heap 39280
WiFi IP address 192.168.1.55
Signal strength -60dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
0

Phaedrux

@nicaris said in Duet 2 wifi homing issue:

The probe does deploy. I can home the x and y but the head will move away from the x and Y axis along the x axis (emergency stop triggered !

Can you share a video if what you're seeing during homing?

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.2

It may be a good idea to go back to firmware version 3.5.3 stable release until everything is working well before testing a beta firmware.