@phaedrux I reinstalled the files on the SD card and that seems to have fixed the issue. Not sure what was wrong with the card. Thank you.

@phaedrux thanks alot, after some searching around in the router settings I managed to find the mac address and set it. Originally the entire reason I wanted to set the address manually is because of my new router the printer ip doesnt show up in the client list for whatever reason. There was a mac address in the client list that wasnt in the ip list which I assumed was the printer and worked. Before I had to check it each time via a usb cable. Thank you

@phaedrux thanks alot, after some searching around in the router settings I managed to find the mac address and set it. Originally the entire reason I wanted to set the address manually is because of my new router the printer ip doesnt show up in the client list for whatever reason. There was a mac address in the client list that wasnt in the ip list which I assumed was the printer and worked. Before I had to check it each time via a usb cable. Thank you

@phaedrux this is exactly what I followed. Ive been using my duet for a few years now and just now decided to put it on a stable ip.

@norder Hello as the title says this is wifi not ethernet

@phaedrux I am using yat via USB terminal yes. I sent M122 and got the following
"=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later<LF>Board ID: 08DJM-9178L-L2MSD-6JTD2-3SN6K-KTHQR<LF>Used output buffers: 1 of 24 (23 max)<LF>=== RTOS ===<LF>Static ram: 23876<LF>Dynamic ram: 75180 of which 176 recycled<LF>Never used RAM 12328, free system stack 114 words<LF>Tasks: NETWORK(ready,65.2%,231) HEAT(delaying,1.4%,314) Move(notifyWait,4.8%,313) MAIN(running,27.0%,441) IDLE(ready,1.6%,29), total 100.0%<LF>Owned mutexes: WiFi(NETWORK) USB(MAIN)<LF>=== Platform ===<LF>Last reset 19:39:04 ago, cause: power up<LF>Last software reset at 2022-06-28 20:45, reason: User, GCodes spinning, available RAM 12328, slot 1<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Step timer max interval 0<LF>MCU temperature: min 37.8, current 38.0, max 48.9<LF>Supply voltage: min 0.0, current 24.0, max 24.2, under voltage events: 1, over voltage events: 0, power [Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]"

When I enter
"M552 S1 P192.168.1.14"
I get the following in response
"Error: M552: expected string expression<LF>ok<LF>"
I am running version 3.3
Not sure if im doing something wrong or if this is a glitch.

@deckingman I appreciate that was more of what I was looking for. I am aware of the risks and am not worried about that. Ill try tweaking around with the parameters more in the upcoming days

@siam M308 gives a error of "sensor number out of range"
my H0 is the bed, and H1 is the extruder.

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 10:18:18 GMT-0400 (Eastern Daylight Time)

; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"My Printer"                             ; set printer name

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

; Drives
M569 P0 S1                                     ; physical drive 0 goes forwards
M569 P1 S1                                     ; physical drive 1 goes forwards
M569 P2 S1                                     ; physical drive 2 goes forwards
M569 P3 S1                                     ; physical drive 3 goes forwards
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 E220.00              ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1500 E1500                   ; set motor currents (mA)
M84 S0                                         ; Disable motor idle current reduction

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X300 Y300 Z220 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                                     ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P5 C"^!zprobe.in" H5 F120 T6000              ; set Z probe type to switch and the dive height + speeds
G31 P500 X45 Y-12 Z3
M557 X30:260 Y15:300 S20

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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 S120                                   ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138  ; 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

; 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
M307 H0 A100  ; Heater Bed Temp Setting to avoid heating too slow error
M307 H1 A100 C302 D5.8 B1  ; Heater Extruder Temp Setting

M143 H1 S420 ; extruder max temp

@siam Yes I did the PID tuning. Ill be honest I might have missed something so just to be sure I did it right here is what I did:
1: type "M303 H1 S240" in console
2: type "M303" in console
3: Copy results
4: Post results at the end in #config

I am using a duet wifi
firmware 3.2

@t3p3tony I tuned the heater however there are two fundamental flaws with the duet software
1: Any sort of environmental change such as difference in temperature or a fan turned on will cause the firmware to fault due to "heating too slowly". Why is this setting set so tight is beyond my understanding.
I have been able to fix this problem by changing the heating parameter

2: I upgraded to a volcano hotend and the temperature delay is somewhat significant and even though it shuts off the heater the temperature still rises and a "temperature exceeds 15c" error comes up. idk what the issue with this is and am simply frustrated with the countless problems I am getting with this board.

If you have any suggestions I would be glad to hear, otherwise im about to throw away this junk controller.

Ive already burnt my fingers significantly trying to change some things to figure out the problem and am very frustrated with this entire platform. I am about to return back to a ramps board as the duet software is the biggest missed opportunity and loaded with so much crap. seems like nothing can be made with quality anymore and every single little thing needs to be DIY'ed.

How do I disable all heater fault failures