@oliof I really thought about that... but makes no sense does it? I tell you why. Yesterday my desktop computer died and believe it or not, I took my new laptop and connected via wifi to my router at home and no disconnect issues anymore.

This leads me to the following. The network card must have had a glitch or the port on the switch which my desktop was connected. Strange thing about is that no other connection was showing problems, only those to the printer. I also connected via a desktop switch... no difference.

Anyways thanks for the engagement. I was so suprised that for such a long time it must have had to sit and wait and all of a sudden a major problem solved, without DUET2 interaction.

All the best

@sonderzug, hello I might say, but I did install it today as substitute to my "plasticbottle" and I just unplugged it and replugged it and it works... no changes in config, no wire issues. Swapout and continue working.

Just wanted to note that if somebody swaps a BL-Touch for Creality CR-Touch.

All the best.

@SetraX Well done !!! I screwed up with relative and absolute positioning.
M82 ... I figured out from some partfiles sets to absolute positioning
M83 ... sets the relative position as I need it ...SOLVED

@Phaedrux Well after "unbelieving" that stepper motors if they work do not have a problem I learned it the hard way. Two motors had a play (about 0.5° and almost 0.75°). This is unbelievable. I'm so reality checked now.

This issue must have occured as I crashed the bed quiet a few times that the inner structure of my motors did loosen and created a play and I could never get same results. Also the noise of the moving machine changed into a humming. Before it had some tingeling (like a screw loose somewhere-could not chase it down to the source).

Also I changed every component:
RODS - Rod joints
BLTOUCH - CRTOUCH
Electronics, Drivers, even I shorted all cables to the minimum
I changed the buildplate to get a more even one
I changed the hotend
I chanaged the extruder ( I do not regret this one - now LDO Orbiter V2)
Yes also I upgraded to linear Rails with carriages...
Changed the belts to steel enforced belts...
The number of nozzles I changed I stopped counting (crash or hard touch and change)

Anyway not much more to change left besides the motors
Now the printer spits out results .... I'm so happy

Still a few issues with automation - and multiprobe, but I will get to that later

All the best and thank you

@Phaedrux Well after "unbelieving" that stepper motors if they work do not have a problem I learned it the hard way. Two motors had a play (about 0.5° and almost 0.75°). This is unbelievable. I'm so reality checked now.

This issue must have occured as I crashed the bed quiet a few times that the inner structure of my motors did loosen and created a play and I could never get same results. Also the noise of the moving machine changed into a humming. Before it had some tingeling (like a screw loose somewhere-could not chase it down to the source).

Also I changed every component:
RODS - Rod joints
BLTOUCH - CRTOUCH
Electronics, Drivers, even I shorted all cables to the minimum
I changed the buildplate to get a more even one
I changed the hotend
I chanaged the extruder ( I do not regret this one - now LDO Orbiter V2)
Yes also I upgraded to linear Rails with carriages...
Changed the belts to steel enforced belts...
The number of nozzles I changed I stopped counting (crash or hard touch and change)

Anyway not much more to change left besides the motors
Now the printer spits out results .... I'm so happy

Still a few issues with automation - and multiprobe, but I will get to that later

All the best and thank you

@sonderzug, hello I might say, but I did install it today as substitute to my "plasticbottle" and I just unplugged it and replugged it and it works... no changes in config, no wire issues. Swapout and continue working.

Just wanted to note that if somebody swaps a BL-Touch for Creality CR-Touch.

All the best.

Hello,
even I have all motors with the same current, I noticed that one (Z) Axis is weak and elastic like rubber. Also the motor is kind of cooler than X and Y.
I only use E0, so my first guess was to unplug Z on board of Duet2 and plug in at E1. I also tried to tell in config.g that now Z is on drive 3... did not work.
Since I have a delta configuration, can I do that?
I had to take the sdcard from the controller and set the config.g back to original since I could not get into DWC anymore to set it back... self destruction ...

; Drives
M569 P0 S1                      ; Drive 0 (X) goes forwards
M569 P1 S1                      ; Drive 1 (Y) goes forwards
M569 P2 S1                      ; Drive 2 (Z) goes forwards
M569 P3 S0                     ; Drive 3 (E0) goes backwards
M584 X0 Y1 Z2 E3							; X on motor0, Y on motor1, Z on motor2, E0 on motor4
M350 E128 I1								; Configure microstepping without interpolation
M350 X128 Y128 Z128 I1 						; Configure microstepping with interpolation
M92 X640 Y640 Z640 E1100 					; Set steps per mm
M566 X500 Y500 Z500 E50 				    ; Set maximum instantaneous speed changes (mm/min)
M203 X10000 Y10000 Z10000 E5000 			; Set maximum speeds (mm/min)
M201 X2500 Y2500 Z2500 E1000			    ; Set accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 E1500 I35 			; Set motor currents (mA) and motor idle factor in per cent

this is my config.g

All the best and maybe we can figure something out... Thx

Hi,
I ran into a strange problem, since after executing G32, the webinterface does not show that any compensation is in use??

What do I have to do that it shows BED, since if I load my mesh is says Mesh.

This is after G32 - NONE
I use 2 Probes finally, since i got such a messed up bed heightmap after BLTOUCH. Now I use basically a switch for probing the bed to get real measurements.
Measurements with K1 -BLTOUCH

Measurements with simple touch switch

I don't know what the problem is anymore since if I use K0 or K1 as probe ... BLTOUCH always deploys and retracts if it was used even if it supposed to be sitting still. I have no Idea if that needs to be like that either?

I tried to remember it did it sometimes before I upgraded to 3.4.
Please enlight me.
Well I still try to get a solid first print (first layer) out of the machine... not happening

all the best

bed.g - my G32 exec

M190 S65
;G4 S180	; Pause 3min to thouroughly heat bed

M561 ; clear any bed transform, otherwise homing may be at the wrong height

G28

G1 X0Y0Z15 F15000

M291 R"NOZZLE SENSOR REQUIRED" P"CONNECT NOZZLE SENSOR NOW AND PRESS OK" S3

;G1 X0 Y0 Z50 F15000 ; get the head out of the way of the bed

;M401
G30 P0 X0.00 Y130.00 Z-99999 H0 K0
G30 P1 X112.58 Y65.00 Z-99999 H0 K0
G30 P2 X112.58 Y-65.00 Z-99999 H0 K0
G30 P3 X0.00 Y-130.00 Z-99999 H0 K0
G30 P4 X-112.58 Y-65.00 Z-99999 H0 K0
G30 P5 X-112.58 Y65.00 Z-99999 H0 K0
G30 P6 X0.00 Y65.00 Z-99999 H0 K0
G30 P7 X56.29 Y32.50 Z-99999 H0 K0
G30 P8 X56.29 Y-32.50 Z-99999 H0 K0
G30 P9 X0.00 Y-65.00 Z-99999 H0 K0
G30 P10 X-56.29 Y-32.50 Z-99999 H0 K0
G30 P11 X-56.29 Y32.50 Z-99999 H0 K0
G30 P12 X0 Y0 Z-99999 K0 S9
;M402

;M402 ; retract the Z probe

G1 X0 Y0 Z150 F15000 ; get the head out of the way of the bed

config.g

; Configuration file for testing Duet Ethernet and Wifi
M575 P1 S1 B57600    						; enable support for PanelDue
M550 P"Monstaprint"					        ; Machine name and Netbios name (can be anything you like)
; Network
M552 P0.0.0.0 S1                                ; enable network and acquire dynamic address via DHCP
M586 P0 S1 R80                                  ; enable HTTP on Port80
M586 P2 S1 										; enable Telnet 

; General preferences
M665 R170 L397.19 B155 H525     ; set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0                   ; put your endstop adjustments here

; Drives
M569 P0 S1                      ; Drive 0 (X) goes forwards
M569 P1 S1                      ; Drive 1 (Y) goes forwards
M569 P2 S1                      ; Drive 2 (Z) goes forwards
M569 P3 S0                     ; Drive 3 (E0) goes backwards
M584 X0 Y1 Z2 E3							; X on motor0, Y on motor1, Z on motor2, E0 on motor4
M350 E128 I0								; Configure microstepping without interpolation
M350 X128 Y128 Z128 I0 						; Configure microstepping with interpolation
M92 X640 Y640 Z640 E1100 					; Set steps per mm
M566 X1500 Y1500 Z1500 E1500 				; Set maximum instantaneous speed changes (mm/min)
M203 X12500 Y12500 Z12500 E7500 			; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 				; Set accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 E1250 I35 			; Set motor currents (mA) and motor idle factor in per cent

; Endstops
M574 X2 S1 P"xstop"   ; X min active high endstop switch
M574 Y2 S1 P"ystop"   ; Y min active high endstop switch
M574 Z2 S1 P"zstop"   ; Z min active high endstop switch

; Z-Probe - BLTouch
M950 K1 S0 C"exp.heater7" 							; create servo pin 0 for BLTouch
M558 K1 P9 C"^zprobe.in" H5 F1500:150 T5000 A2		; set Z probe type to bltouch and the dive height + speeds
G31 K1 X0 Y20 Z1.435 P50							; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment 1.44 Worked well

; Z-Probe - Nozzle
M574 K0 E0 P"nil" 									; (RRF 3.0 on Duet 2 ONLY) no Z endstop switch, free up Z endstop input
M558 K0 P5 C"!^e1stop" H5 F1000:250 T10000 A2
G31 K0 X0 Y0 Z0.25 P30 								; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment

M557 R150 S15 K0									; Define mesh grid Nozzle Sensor ;
M557 R150 S15 K1									; Define mesh grid BLTOUCH;

; Bedheater
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138       				; sensor 0 ### R4700
M950 H0 C"bedheat" T0  												; create bed heater and map sensor 0
M140 H0 															; the bed heater is heater 0
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 							; Use PID on bed heater (may require further tuning) - old allowed to stay
M140 S65 R0															; set bed temperature to 65C and bed standby temperature to 20C
M144 S0																; activate standby temperature

;Hotend
M308 S1 P"e0temp" Y"thermistor" T100000 B4607 C8.950070e-8 R4700	; sensor 1
M950 H1 C"e0heat" T1 												; create heater and map sensor 1; Tools
M307 H1 B0 S1.00   													; disable bang-bang mode for heater  and set PWM limit
M143 H1 P0 S280 A2 													; switch off heater 1 temporarily if it exceeds 280°C
M143 H1 P1 S290 A0 													; raise a heater fault if it exceeds 290°C

; Fan Modes
M950 F1 C"fan0" 													; Fan 0 definition
M950 F0 C"fan1" 													; Fan 1 definition
M106 P1 T40 H1														; Turn on Fan0 if Heater Temperature is above 40°C
M106 P0 S0 H-1 														; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0 S"Extruder" 			                           	; define tool 0
G10 P0 X0 Y0 Z0                                       				; set tool 0 axis offsets
G10 P0 R120 S0                                          			; set initial tool 0 active and standby temperatures to 120C

M280 P0 S160 I1            											; Clear any Alarms of BLTOUCH 
M579 X1Y1Z1                                                         ; Axis scaling factor
M501

My M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5beta2 (2023-02-08 17:41:22) running on Duet Ethernet 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F4-3SN6M-92ZVY
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 22216
Dynamic ram: 70800 of which 0 recycled
Never used RAM 19808, free system stack 188 words
Tasks: NETWORK(ready,30.0%,233) HEAT(notifyWait,0.0%,315) Move(notifyWait,0.0%,361) MAIN(running,69.3%,496) IDLE(ready,0.6%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:19 ago, cause: software
Last software reset at 2023-03-06 08:35, reason: User, Gcodes spinning, available RAM 19320, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 23.4, current 24.7, max 25.2
Supply voltage: min 24.1, current 24.3, max 24.4, 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
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: 
Date/time: 2023-03-06 08:37:59
Cache data hit count 4294967295
Slowest loop: 10.08ms; 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 0.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== 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: 10.47ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex

@SetraX Well done !!! I screwed up with relative and absolute positioning.
M82 ... I figured out from some partfiles sets to absolute positioning
M83 ... sets the relative position as I need it ...SOLVED

Hello,

this is my load MACRO....
and it changes direction just because of ???

; Load filament
T0
M109 S200 ; set heater/nozzle target temperatuer and wait until reached
M116 ; Wait for the temperatures to be reached

G1 E10 F600 ; Feed 10mm of filament at 600mm/min
G1 E100 F3000 ; Feed 120mm of filament at 3000mm/min
G4 P2000 ; Wait one second

!!! Crazyness starts here... changes direction here and does other crazy stuff so that my filament just lands where it started 1mm after extruder E0 motor

And the best part of it... it started when I tried to adjust the command to 20mm....

G1 E20 F300 ; Feed 20mm of filament at 300mm/min
G1 E5 F150 ; Feed 20mm of filament at 300mm/min
M400 ; Wait for moves to complete
G1 E-2 F300 ; Retract 2mm of filament at 1800mm/min

;M292 ; Hide the message
;M106 S0 ; turn off cooling fan
M104 S0 ; set extruder temperature to 0C
;M140 S0 ; set bed temperature to 0C

Anybody any ideas what I do wrong?

All the best

@Phaedrux

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F4-3SN6M-92ZVY
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 70408 of which 0 recycled
Never used RAM 20132, free system stack 122 words
Tasks: NETWORK(ready,28.0%,237) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,311) MAIN(running,71.7%,445) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:09:47 ago, cause: power up
Last software reset at 2023-02-13 14:38, reason: User, GCodes spinning, available RAM 20132, 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
Step timer max interval 0
MCU temperature: min 17.4, current 27.9, max 28.3
Supply voltage: min 24.0, current 24.3, max 24.4, 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
Driver 0: position 132587, standstill, SG min/max 0/289
Driver 1: position 132587, standstill, SG min/max 0/291
Driver 2: position 132587, standstill, SG min/max 0/282
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2023-02-13 18:05:45
Cache data hit count 4294967295
Slowest loop: 6.22ms; fastest: 0.17ms
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 2.8ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 410ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 11, completed moves 11, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 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
LCD 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: 8.25ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

OK, I answered to oliof just before that the network problem dissolved.... wrong. After issuing the response for M122 the network disconnect popped up on the right lower screen, it seems to be faster reconnected on a newer computer though...

DWC files... i did not intentionally, so how do I do it. yesterday I downgraded to 3.3.

Paneldue ... no since it says it only has about 29kb memory and as far as I read it, it is impossible to run
a newer firmware as 1.22 on it anyways...Am I wrong?

Config.g comes here....

; Configuration file for testing Duet Ethernet and Wifi
M575 P1 S1 B57600 ; enable support for PanelDue
M550 P"Monstaprint" ; Machine name and Netbios name (can be anything you like)
; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 R80 ; enable HTTP on Port80

; General preferences
;M665 L397.190:397.190:397.190 R175.000 H537.500
M665 R170 L397.19 B155 H525 ; set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here

; Drives
M569 P0 S1 ; Drive 0 (X) goes forwards
M569 P1 S1 ; Drive 1 (Y) goes forwards
M569 P2 S1 ; Drive 2 (Z) goes forwards
M569 P3 S1 ; Drive 3 (E0) goes forwards
M584 X0 Y1 Z2 E3 ; X on motor0, Y on motor1, Z on motor2, E0 on motor4
M350 E128 I0 ; Configure microstepping without interpolation
M350 X64 Y64 Z64 I1 ; Configure microstepping with interpolation
M92 X320 Y320 Z320 E1100 ; Set steps per mm
M566 X1200 Y1200 Z1200 E2500 ; Set maximum instantaneous speed changes (mm/min)
M203 X10000 Y10000 Z10000 E3000 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 E1250 I50 ; Set motor currents (mA) and motor idle factor in per cent

; Endstops
M574 X1 S1 P"xstop" ; X min active high endstop switch
M574 Y1 S1 P"ystop" ; Y min active high endstop switch
M574 Z1 S1 P"zstop" ; Z min active high endstop switch

; Z-Probe - BLTouch
M950 H7 C"nil" ; Disable heaters h7 to free up pins
M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch

M558 P9 C"^zprobe.in" H5 K0 F1500:150 T5000 ; set Z probe type to bltouch and the dive height + speeds
G31 X0 Y20 Z2.70 P50 K0; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment

; Z-Probe - Nozzle
M558 P5 C"!e1stop" H10 K1 F1000:100 T2500 ; set Z probe type to bltouch and the dive height + speeds
G31 X0 Y0 Z0.1 P50 K1 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment

M557 R150 S15 ; Define mesh grid ;

; Bedheater
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning) - old allowed to stay
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; sensor 0 ### R4700
M950 H0 C"bedheat" T0 ; create bed heater and map sensor 0
M140 H0 ; the bed heater is heater 0
M140 S65 R0 ; set bed temperature to 65C and bed standby temperature to 20C
M144 S0 ; activate standby temperature

;Hotend
M308 S1 P"e0temp" Y"thermistor" T100000 B4607 C8.950070e-8 R4700 ; sensor 1
M950 H1 C"e0heat" T1 ; create heater and map sensor 1; Tools
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 P0 S280 A2 ; switch off heater 1 temporarily if it exceeds 280°C
M143 H1 P1 S290 A0 ; raise a heater fault if it exceeds 290°C

; Fan Modes
M950 F0 C"fan0" ; Fan 0 definition
M950 F1 C"fan1" ; Fan 1 definition
M106 P0 T40 H1 ; Turn on Fan0 if Heater Temperature is above 40°C
M106 P1 S0 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0 S"Extruder" ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R120 S0 ; set initial tool 0 active and standby temperatures to 120C

M501

M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
G28

My M501 seems to work now... why don't know.

I tried to setup a second probe since the offset was to high and I can not make it work with BLTouch, since it is 20mm from the nozzle so I tried to go with some supermicro aliexpress tactile switch which I have to stick on the tip of the nozzle...

Bad thing about it ... can't get it configured as Probe ONE, always reads zero. I connected it to E1Stop and GND on DUET2... G31 K1 always reads 0, as K0 BLTOUCH reads 1000 when I activate it....
Is there something else to do?

Thank you so much for engagement, I feel now I'm not alone anymore.

BTW I figured out a Workaround for my Homeing Zero Problem.

1. After Homing... all Axes did not Zero so I put a M92 X0Y0 and magically it zeroed....
2. Relative move down to test BED with BLTOUCH.
3. BLTOUCH updated correct 0(at least in the middle) so I do not crush the BED anymore..

Don't know how you do it but my homeing looks like that:

; Use relative positioning
G91

; Move all towers to the high end stopping at the endstops (first pass)
G1 H1 X750 Y750 Z750 F3500

; Go down a few mm
G1 H2 X-5 Y-5 Z-5 F2500

; Move all towers up once more (second pass)
G1 H1 X50 Y50 Z50 F500

; Go down a few mm
G1 H2 X-2.5 Y-2.5 Z-2.5 F2500

; Move all towers up once more (third pass)
G1 H1 X50 Y50 Z50 F100

G92 X0Y0
; Move down a few mm so that the nozzle can be centred
;G1 X-25 Y-25 Z-25 F5000 H2

;G1 X50 Y50 Z50 F1000 H3

; Reset BL-Touch
M280 P0 S160 I1 ; Clear any Alarms of BLTOUCH
M280 P0 S90 I1 ; Pen up

G1 X0 Y-20 Z-500 F10000
; Switch back to absolute positioning and go to the centre

G90

Over and out ... waiting for feedback

@oliof I really thought about that... but makes no sense does it? I tell you why. Yesterday my desktop computer died and believe it or not, I took my new laptop and connected via wifi to my router at home and no disconnect issues anymore.

This leads me to the following. The network card must have had a glitch or the port on the switch which my desktop was connected. Strange thing about is that no other connection was showing problems, only those to the printer. I also connected via a desktop switch... no difference.

Anyways thanks for the engagement. I was so suprised that for such a long time it must have had to sit and wait and all of a sudden a major problem solved, without DUET2 interaction.

All the best

Hi,
I bought Duet 2 Ethernet before Wifi was available many years ago. I ran 1.xx on it for a long time. Then life got difficult and it sat in my basement for many years. Last year in summer I upgraded to 3.xx which was not easy at all but I got it on the machine. Since then I was unable to configure and always have network errors or disconnection issues.

This is very difficult since anytime you edit a file on the webinterface everything is gone - sooo time consuming.

Yesterday I started again in hope that time would have solved many issues but I got struck by reality again, so I upgraded to 3.4.5, which actually stuck at the very end (maybe the cause of a network disconnect)... anyway I had to do it 3 times until it worked fully through all the files and I was able to click the Update the uploaded files. Anyways it succeeded then flawlessly.

Did a clean config.g
Setup everything hardware, BL-Touch, Heaters, Extruder and Motors, but that did not brought me forward a single inch...

BTW, I operate/pet a TEVO Little Monster (Delta), which I upgraded with stronger belts, a new BLTOUCH, new gears etc. so hardware is basically new and printed only a couple of boats... thats it.

Why I do have so many Issues? I don't know, but I noticed the following:
When I do Home all axis, there is no effect on the Status of the machine. It depends where the head is located relative to the machine.

I. As I set the height at 520, and the head went down to the bed by gravity. It happily adds 520 to the way the head moves up to the homing switches. Then the machine reports X, Y, Z status added to the way it had to move up. As you can imagine the values are different all the time.

II. I have a M501 at the end of the config.g file which does not affect anything, except I delete config-override.g, then it complains, but if it is there it is not loaded. I have to do a manual M501 in order to load the config-override.g settings. only then the machine starts to update the status settings.

In the meantime my bed looks like the moon surface since the head with the probe crushed so many times the bed that I actually thought about throwing the machine into the bin.
This is my last attempt to find a way to make 3D printing happen, since I can not go back to 1.02... also my paneldue 1.22(b28) is also reporting all kind of errors which I can not even find somewhere...
for instance, heater 0 not found and so on.

I have no Idea what else I could do... and I'm open to any leads or ideas

All the best