@R006 What is the bed surface? It needs to be metal on, or near the surface (under a PEI sheet is okay), ie not have glass on top.

Are you setting the M558.2 calibration with the SZP coil around 4mm from the bed?

When you say "the value is fluctuates between 0, 9097, and 999999" are these the only three readings? Or does it give other readings? I'd usually expect to see readings in the range 1500 (Z6) to 15000 (Z0.3). You shouldn't get 0 or 999999 readings.

Random 999999 readings can be caused by:

Interference on the SZP ribbon cable (from SZP to coil). Makes sure to route the SZP ribbon cable away from the coil, ie make sure it doesn't go over the coil Poor ribbon cable contact. Ensure it is FULLY inserted into the tiny connector, at both ends. Try reseating this if you continue to get erratic readings Make sure there is no metal in the 30mm ABOVE the coil, or it will pick this up and give false readings

What firmware version are you running on the 6HC and SZP?

Ian

the final config.g

; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu May 27 2021 13:17:12 GMT+0300 (Eastern European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"CoreXY500" ; set printer name M669 K1 ; select CoreXY mode ; Network M552 P192.168.1.27 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet G4 S2 ;wait for expansion boards to start ; Drives M569.1 P50.0 T3 E4:8 S400 R40 I1500 D0.05 V400 A200000 H10 ; Configure the Duet 3 Expansion 1HCL board at CAN address 50 with a Duet 3 magnetic encoder, warn if 1 fullstep threshold exceeded, error if 2 full steps threshold exceeded. M569 P50.0 D4 S1 ; ;M569 P0.0 S1 ; physical drive 0.0 goes forwards ;M569 P0.1 S0 ; physical drive 0.1 goes forwards M569.1 P51.0 T3 E4:8 S400 R40 I1500 D0.05 V400 A200000 H10 ; Configure the Duet 3 Expansion 1HCL board at CAN address 50 with a Duet 3 magnetic encoder, warn if 1 fullstep threshold exceeded, error if 2 full steps threshold exceeded. M569 P51.0 D4 S0 M569 P0.3 S0 M569 P0.4 S1 M569 P0.5 S1 ; physical drive 0.2 goes forwards M569 P121.0 S1 ; physical drive 121.0 goes forwards M584 X50.0 Y51.0 Z0.3:0.4:0.5 E121.0 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z8280.00 E395.70 ; set steps per mm ;M350 X32 Y32 Z16 E16 I1 M566 X300.00 Y300.00 Z50.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z150.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z20.00 E500.00 ; set accelerations (mm/s^2) M906 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M906 X1700 Y1700 I30 M84 S30 ; Set idle timeout ; Axis Limits M208 X-26 Y0 Z0 S1 ; set axis minima M208 X500 Y330 Z365 S0 ; set axis maxima ; Endstops M574 X1 S4 ; configure sensorless endstop for low end on X M574 Y1 S4 ; configure sensorless endstop for low end on Y M574 Z1 S2 ; configure Z-probe endstop for low end on Z ;M574 E1 S1 ;Filament sensor BTT E1 M591 D0 P2 C"io8.in" S1 ;configure BTT smart filament sensor ; Z-Probe M671 X-31.39:250:531.36 Y-18:433.3:-18 S10 ; Locations left, center, right M558 P8 C"121.io2.in" H3 F1000 T6000 A20 S0.005 ; PINDA set Z probe type to switch and the dive height + speeds ;M308 S2 P"121.temp1" A"PINDA" Y"thermistor" T100000 B3950 ;M950 H2 C"out1" T2 ; create nozzle heater output on 121.out0 and map it to sensor 1 ;M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ;M141 H2 ;M143 H2 S90 ; set temperature limit for heater 1 to 280C G31 P500 X30 Y0 Z1.48 ; set Z probe trigger value, offset and trigger height M557 X20:450 Y5:320 P5 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 Q10 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S130 ; set temperature limit for heater 0 to 120C M308 S1 P"121.temp0" Y"thermistor" T100000 B4725 C7.060000e-8 ; configure sensor 1 as thermistor on pin 121.temp0 M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S290 ; set temperature limit for heater 1 to 280C M308 S2 A"Chamber" P"temp2" Y"thermistor" T100000 B4725 C7.06e-8 M950 H2 C"out2" T2 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H2 R0.001 A11 C99999 D4000 B1 ; disable bang-bang mode for heater and set PWM limit M141 H2 M143 H2 S70 ; Fans M950 F0 C"121.out1" ; create fan 0 on pin 121.out1 and set its frequency M106 P0 S0 B0.5 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"121.out2" Q500 ; create fan 1 on pin 121.out2 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z-0.15 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined M955 P121.0 I05 ;Accelerometer on Toolboard ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M572 D0 S0.045 ; PA for ABS GD filament 0.4 nozzle M501 ; load saved parameters from non-volatile memory M911 S22.5 R23.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss ``'

@axiom only create a bed mesh of the area of the print: https://forum.duet3d.com/topic/37242/mesh-bed-leveling-only-in-printing-area-using-orca-slicer

Ian

@dc42

I just ran into the same thing... 2 of my drivers were complaining about over heating...yikes!
This is on a Duet 3 Mini 5 with 6 active stepper motors.

So, I'm off to print a backing plate with taller stand-offs and a mount for a blower fan. My stepper motors are all fairly cool, but the amperage draw makes sense. My FLIR ONE camera came in handy yet, again! ; )

Cheers!

@axiom 1736183041163-flow.jpg

@stuartofmt Thank you for the answers, everything actually works if I simply copy the IP address from Motion....sadly my new raspberry 5 said goodbye after 1 hour...despite the expensive original fan and expensive power supply

@HugoZM My guess is that you have mis-wired the endstop switch so that when it is triggered, it shorts out the 3.3V rail or the 5V rail. If that's the case then you will see the red 5V or green 3.3V LED go out when you trigger the endstop switch.

@Arkadiusz it sounds like a power supply problem to me. Send M122 a couple of times to reset the record of minimum VIN voltage; then command movements that cause the motor to stall; then send M122 again and look at the current and minimum VIN voltage in the report.

@axiom octoprint can be run on an rpi5 https://community.octoprint.org/t/raspberry-pi-5-octoprint/60487/2

@engikeneer thank you very much, then I will just print a few tests

@jay_s_uk
wow, thank you so much! That was the solution, now I just have to figure out the input shaping....have a nice Sunday, cheers, Don

@Phaedrux
Homeall.g

G91 G1 H2 Z2 F100 G1 H1 X-300 Y-300 F600 G1 H2 X5 Y5 F1000 G1 H1 X-300 Y-300 F200 G1 H2 Z-5 F100 G1 H1 Z304.1 F300 G1 H2 Z-2 F100 G1 H1 Z304.1 F100 G92 X0 Y0 G90 G92 Z304.1

homex.g

G91 G1 H2 Z2 F100 G1 H1 X-300 F600 G1 H2 X5 F600 G1 H1 X-300 F200 G1 H2 Z-2 F100 G92 X0 G90

homey.g

G91 G1 H2 Z2 F100 G1 H1 Y-300 F600 G1 H2 Y5 F600 G1 H1 Y-300 F200 G1 H2 Z-2 F100 G92 Y0 G90

homez.g

G91 G1 H2 Z2 F300 G1 H1 Z304.1 F360 G1 H2 Z-5 F240 G1 H1 Z304.1 F200 G90 G92 Z304.1

config.g

M552 S1 ;M552 S-1 M586 P0 S1 M586 P1 S0 M586 P2 S0 ; Drives M569 P0 S1 M569 P1 S1 M569 P2 S1 M569 P3 S1 M569 P4 S1 M569 P5 S1 M584 X0 Y1 Z2:3:4 E5 M350 X32 Y32 I0 M350 Z16 E16 I1 M92 X160.0 Y160.0 Z2133.33 E932.00 ;change as per machine M566 X720.00 Y720.00 Z300.00 E600.00 M203 X8400.00 Y8400.00 Z420.00 E8400.00 M201 X3000.00 Y3000.00 Z30.00 E250.00 ;M-curr M906 X1600 Y1600 Z1600 E800 I50 M84 S30 ; Axis Limits M208 X0 Y0 Z0 S1 M208 X300 Y300 Z304.1 S0 ; filament Sensor M591 D0 P7 C"exp.e3stop" R15:300 L7 E17 S1 ; Endstops M574 X1 S1 P"xstop" M574 Y1 S1 P"ystop" M574 Z1 S1 P"zstop+e0_stop+e1_stop" ; Z-Probe M950 S0 C"exp.heater3" M558 P9 C"^zprobe.in" H5 F120 T6000 G31 P500 X0 Y0 Z1.038 ; Auto level, coordinates as per motor order in M584 M671 X-17.66:297.34:140.00 Y-5.00:-5.00:327.61 S5.0 F1.2 ; define mesh grid M557 X30:300 Y30:300 S20 M376 H5 ; End Limits M950 J1 C"exp.e4stop" M581 P1 T2 R0 S1 M582 T2 M581 P-1 T2 M581 P1 T0 R0 S1 ;PA M572 D0 S0.045 ; Bed Heater M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 M950 H0 C"bedheat" T0 M307 H0 B0 S1.00 M140 H0 M143 H0 S105 ; Extuder Heater M308 S1 P"e0temp" Y"pt1000" M950 H1 C"e0heat" T1 M307 H1 B0 S1.00 M143 H1 S320 ; cooling Fans M950 F0 C"fan0" Q500 M106 P0 S0 H-1 M950 F1 C"fan1" Q500 M106 P1 S0 H-1 ; Tools M563 P0 D0 H1 F0 G10 P0 X0 Y0 Z0 G10 P0 R0 S0 M575 P1 S1 B57600 M501 M911 S21 R22.5 P"M913 X0 Y0 G91 M83 G1 Z5 E-5 F1000" M929 S3 P"/macros/SERVICE/log/STPL_DEBUG.txt"

@flopo76 I have recently built the Mercury One zeroG Hydra 1.1 conversion of an Ender 5. I have RPI driving Duet mini 5+ and a HUVUD tool board running CAN from duet USB-Can bridge.

Everything has flashed fine but I am having intermittent issues. When I try to move the bed in large movement all three Z stepper get way out of sync. I am wondering if the USB speed from RPI to Duet is limited and causing communication issues. I really want to use this board but it has been one headache after another.

@droftarts

OK thanks for your reply

Hi, I'm having the same problem, except I'm stuck in a reconnecting / /connected / disconnected loop. Refreshing or closing firefox , and deleting all sites data , doesn't work.
It happens after a somehow long operating time (~ 2 weeks)

Irecently upgraded everything to 3.5.3

@oliof We are mixing absolute and relative mode, as we produce a set of identic representations. So, for start of each representation we set the position absolute, but for producing the representation we switch to relative mode.

@MartinMV

a) probably best to keep to your own thread rather than re-opening three year old ones.
b) check the new docs site at https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

(Bonus tip, dont hit enter on the search bar there if you type search terms)

Have you tried the 3.6 beta release?

@Phaedrux
okay
Thank you