@phaedrux Which fan should be which? Should hotend cooling fan be fan 1 and part cooling fan be 0? I am still learning Reprap and using the configurator, coming from Marlin and Klipper. Thank you for your help

I switched cura to say fan 1 was the part fan and it functions fine turning it on now which it did not before.

As far as the homing error, it seems to happen randomly at the start of prints occasionally, but not every time it homes. a second home always resolves it.

This is an FL Sun Super Racer, with a build volume of 330 mm by 260. The carriage travel section was unclear to me in the configurator so I may have gotten that wrong.

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jun 21 2022 15:09:53 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H1 X337 Y337 Z337 F2500 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F3600 ; go down a few mm
G1 H1 X10 Y10 Z10 F250 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jun 21 2022 16:50:21 GMT-0400 (Eastern Daylight Time)
M561 ; clear any bed transform
G28 ; home all towers
; Probe the bed at 10 peripheral and 6 halfway points, and perform 8-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y130.9 H0 Z-99999
G30 P1 X76.94 Y105.9 H0 Z-99999
G30 P2 X124.49 Y40.45 H0 Z-99999
G30 P3 X124.49 Y-40.45 H0 Z-99999
G30 P4 X76.94 Y-105.9 H0 Z-99999
G30 P5 X0 Y-130.9 H0 Z-99999
G30 P6 X-76.94 Y-105.9 H0 Z-99999
G30 P7 X-124.49 Y-40.45 H0 Z-99999
G30 P8 X-124.49 Y40.45 H0 Z-99999
G30 P9 X-76.94 Y105.9 H0 Z-99999
G30 P10 X0 Y65.4 H0 Z-99999
G30 P11 X56.64 Y32.7 H0 Z-99999
G30 P12 X56.64 Y-32.7 H0 Z-99999
G30 P13 X0 Y-65.4 H0 Z-99999
G30 P14 X-56.64 Y-32.7 H0 Z-99999
G30 P15 X-56.64 Y32.7 H0 Z-99999
G30 P16 X0 Y0 H0 Z-99999 S8
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

Slicer:
G21 ; millimeter units
G90 ; absolute coordinates
M82 ; E absolute
M140 S{material_bed_temperature}
M104 S{material_print_temperature}
M190 S{material_bed_temperature}
M109 S{material_print_temperature}
G28 ; home axis
G29 S1 ; enable mesh leveling
; Lower nozzle and move to start position
G1 Z150
G1 X-130 Y0 Z0.4 F3000
; Extrude about 40 mm by printing a 90 degree arc
G3 X0 Y-130 I130 Z0.3 E40 F2700
; Retract and move nozzle up
G92 E0
G1 E-1.5 F3000
G0 Z0.5
G1 E0 F1000

I am not sure what I am doing incorrect in the slicer to turn off the fans at the end of the print, I also receive an occasional Insufficeint axis's home. config below, I have tried both M107, and M106 in my end gcode in cura slicer and neither seem to stop the fan. I suspect the homing issue has something to do with my delta config but other wise a second home and it prints fine.

; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jun 21 2022 15:09:53 GMT-0400 (Eastern Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Delta" ; set printer name
M665 R151.67 L315 B132 H330 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them

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

; Drives
M569 P0.0 S1 D3 V0 ; physical drive 0.0 goes forwards
M569 P0.1 S1 D3 V0 ; physical drive 0.1 goes forwards
M569 P0.2 S1 D3 V0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 D3 V0 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E526.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z3000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1250 Y1250 Z1250 E650 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z-25 S1 ; set minimum Z

; Endstops
M574 X2 S1 P"io4.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io4.in
M574 Y2 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io2.in
M574 Z2 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin io1.in

; Z-Probe
M558 P5 C"^!io3.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z17.17 ; set Z probe trigger value, offset and trigger height
M557 R130 S15 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.439 K0.389:0.000 D3.07 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out2" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

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

; 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

; Custom settings are not defined

; Miscellaneous
T0 ; select first tool
M501 ; config override

@droftarts Ah I used v40 from another post, but V0 makes sense and I will update

I figured this out after a couple days of pulling my hair out. On to pressure advance and input shaping.

So I am still learning and have tried to not be that person to not look but I am not understanding and seeing clear answers when I search.

I have an FL Sun Super Racer that I decided to convert over since I already had the Duet board. I have it running, and everything is working, but I do not understand what I am reading at the link below.

https://duet3d.dozuki.com/Wiki/Tuning_Stepper_Motor_Drivers

M569 P0
Drive 0 runs forwards, active low enable, timing fast, mode spreadCycle, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 210

This printer came with a MKS Nano V3 that had stealthchop enabled and it worked okay, but I had a driver die and a few other issues with the board. I know the documentation says its not recommended at higher printing speeds to use stealthchop but I used it with Klipper and Marlin without an issue so I'd like to at least try it.

How do I determine starting values? Example, This is set by the M569 V parameter. Lower values increase the speed at which the driver will switch over to spreadCycle. M569 with just a P parameter will translate the existing tpwmthrs to mm/sec belt speed for you.

I really don't want it to ever switch over to spread cycle but its not even clear what a good starting value is for tpwmthrs to tune from.

Is there another guide I've missed in searching, with klipper I just turned on the microstepping and then interpolation and used a 999999 threshold and it appears this will be a bit more involved.

@phaedrux They have responded asking me to provide a link to my post authorizing a return. Which I obviously don't have here yet so any help would be appreciated. When I touch, its not even really pressing down its like I am helping either reception or grounding. But I don't have to keep touching it in order for the web interface to keep working, only on the first load. super weird I know.

@phaedrux I am able to ping it, see results below.

Pinging 192.168.1.89 with 32 bytes of data:
Reply from 192.168.1.89: bytes=32 time=3ms TTL=255
Reply from 192.168.1.89: bytes=32 time<1ms TTL=255
Reply from 192.168.1.89: bytes=32 time=1ms TTL=255
Reply from 192.168.1.89: bytes=32 time=1ms TTL=255

I did finally get connected to the interface, by touching the top of the wifi module the page suddenly loaded when I was checking the antenna to make sure it was secure. After a bunch of testing every time I apply an update in UI, it reboots and then I can't connect until I touch the module again. I think there is a ground short or something in the chip.

I have emailed printed solid to get an exchange as its clearly hardware related.

Hello, I am needing some help with trying to figure out what issue I have. I have a Duet 3 Mini 5 and I can't connect to the web interface. Below are my results. Strangely enough, my router shows an IP address but I get a refused to connect, I have searched for hours trying to figure this out and I am at a loss.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 0XLDH-W296U-D65J0-40KM6-MJ03Z-7G7VP
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 109516 of which 256 recycled
Never used RAM 28256, free system stack 150 words
Tasks: NETWORK(ready,6.8%,466) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.0%,123) MAIN(running,92.3%,281) IDLE(ready,0.0%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:36 ago, cause: software
Last software reset at 2022-01-23 14:52, reason: User, GCodes spinning, available RAM 34624, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 276296, completed 276296, timed out 0, errs 0
Step timer max interval 696
MCU temperature: min 27.7, current 29.4, max 29.6
Supply voltage: min 1.0, current 1.4, max 1.4, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 594729675
Slowest loop: 100.01ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.5ms, 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
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 ===
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 ready with "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 2484, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 1381/0/0
Tx timeouts 0,0,1380,0,0,1102 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1.31ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

• WiFi -
  Network state is changingMode
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.26
  WiFi MAC address d8:bf:c0:15:09:5e
  WiFi Vcc 3.36, reset reason Power up
  WiFi flash size 2097152, free heap 27712
  WiFi IP address 192.168.1.89
  WiFi signal strength -72dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0
  ok

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-06-01 21:07:06
ok
M997 s1
T0:-273.1 /0.0 B:-273.1 /0.0
Trying to connect at 230400 baud: failed
Trying to connect at 115200 baud: failed
Trying to connect at 74880 baud: failed
Trying to connect at 9600 baud: failed
Error: Installation failed due to comm write error
ok