Best posts made by rschlachter

I started by trying to go through the upgrade steps for firmware as recommended.
I continued to have an issue where I couldn't stay connected to DWC.

I eventually found myself down to fallback #2.
I was able to flash 3.5.4 successfully via that method.
M115 spits out

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.4 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-11-24 10:43:42

I ran M122 and saw the wifi module is disabled. Fine.
M552 S0.

ok 
WiFi module is started

I noticed my blue light never came on and it never connects to anything.
I ran a M587 and can see my networks.

Remembered networks:
TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
GoPackGo IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
GoPackGoGuest IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0

Ok...
So I thought maybe I should look at fallback #1.
I've got the SD card set up with a firmware folder containing only Duet2CombinedFirmware.bin and DuetWiFiServer.bin. Then in the sys folder I only have Duet2_SDiap32_WiFiEth.bin. The other folders exist and I put the contents of DWC.zip into the www folder. Looks similar to my backup card, but with less stuff in sys.

I ran m997 s1

Trying to connect at 230400 baud: success, found ESP8266
Erasing 8192 bytes...
Erasing 690688 bytes...
Uploading file...
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful
ok

The blue light had a faint flicker so I figured ok that must have worked.
M552 S0 and no light, just ok wifi module started.

So I found a command to enable debugging. M111 S1 P14.
I did an M552 S-1

WiFi module stopped
ok

Followed by another M552 S0.

m552 s0
WiFi: 
WiFi:  ets Jan  8 2013,rst cause:2, boot mode:(3,6)
WiFi: 
WiFi: load 0x40100000, len 5548, room 16 
WiFi: tail 12
WiFi: chksum 0xf7
WiFi: ho 0 tail 12 room 4
WiFi: load 0x3ffe8008, len 24, room 12 
WiFi: tail 12
WiFi: chksum 0x1e
ok
WiFi: ho 0 tail 12 room 4
WiFi: load 0x3ffe8020, len 2412, room 12 
WiFi: tail 0
WiFi: chksum 0x2a
WiFi: csum 0x2a
WiFi: phy_version: 1163.0, 665d56c, Jun 24 2020, 10:00:08, RTOS new
WiFi module started
ESP reported status change
ESP reported status change

Wondering where I've gone wrong. I noticed that in the SD Card docs (can't post link due to rep) it says the Duet2_SDiap32_WiFiEth.bin should be in the firmware folder and says nothing about the DuetWiFiServer.bin file.

Hoping I'm closer after that infuriating DWC disconnect mess. I understand that the issue may be related to my network. GoPackGo is 5Ghz/2.4Ghz with a different router than I had previously. I was hoping I could maybe try to connect to GoPackGoGuest which is strictly 2.4Ghz and used for other IoT devices in my house.

Just wanted to come back here to post the results and close the loop. Overall, I was able to tune things and get things looking good. Here are the after pics https://imgur.com/gallery/Ogqr8lM

I did switch the order of the walls.
I printed the pressure advance test here https://forum.duet3d.com/topic/6698/pressure-advance-calibration/18 and adjusted accordingly. This made a nice improvement.
I lowered my print temp to 230. Might play around a little with this just to see.
I turned off combing. I did this more so because retraction on this extruder is tiny.
I also lowered my flow to 98%, lowered the speed of the walls to 60%, and turned on my cooling fan 30% after layer 3. For bridging I jumped the fan to 100%.

I've still got some slight ringing, but I'm going to tighten the belts a little and see how that plays out. They seem like maybe they are just a touch loose.

Just want to say thanks to @jens55 and @Phaedrux . Your tips definitely helped.

FWIW, I pulled the SD card out and checked it again, popped it in and it connected back to my GoPackGo network. I was able to navigate to the DWC with the provided IP, however it quickly disconnected me again.

So I did an M588 S"GoPackGo" to force it to switch to GoPackGoGuest.

And it did.
So I switched to GoPackGoGuest on my PC and navigated to the displayed IP and.... nothing. It just times out.

So here's my m122 now. I'm going to bed and I'll see if sleep helps.

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JTDJ-3SD6M-KDT8F
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 70940 of which 0 recycled
Never used RAM 19048, free system stack 186 words
Tasks: NETWORK(1,ready,26.8%,239) HEAT(3,nWait 5,0.0%,378) Move(4,nWait 5,0.0%,361) MAIN(1,running,73.2%,501) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:09:18 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU temperature: min 26.9, current 29.7, max 30.2
Supply voltage: min 1.6, current 1.7, max 1.8, 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
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2025-02-06 22:21:18
Cache data hit count 4294967295
Slowest loop: 99.26ms; fastest: 0.14ms
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 3.8ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -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 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
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: 17.02ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 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 60:01:94:2e:9a:74
Module reset reason: Turned on by main processor, Vcc 3.43, flash size 4194304, free heap 46064
WiFi IP address 192.168.101.88
Signal strength -48dBm, channel 5, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

@droftarts Thank you for the upvotes!

And thank you for the response. I moved the files accordingly and downloaded the new WiFi firmware and updated it and it currently holding a connection.

First headache over.

Now, I'm left wondering if I should update to 3.6 Beta straight away or get it all running on 3.5.4. I'm leaning towards the latter.

I am seeing some errors in the DWC console, but those may disappear as I work my way through as I imagine I'll need a new config, etc.