@jay_s_uk

Wow, DWC feels now MUCH more responsive!

Thank you!!!

Let's hope that will solve the 2nd issue too.

@dc42 seems to work for me too!

Had also ftp/telnet enabled and strange connection issues.

@dc42 seems to work for me too!

Had also ftp/telnet enabled and strange connection issues.

@jay_s_uk

Wow, DWC feels now MUCH more responsive!

Thank you!!!

Let's hope that will solve the 2nd issue too.

@derBruchpilotPro

Okay, I thought connecting the Laptop via Ethernet solved the problem, but here is another one.

After some more clicking on the DWC I got completely disconnected, so I tried to connect via USB (without rebooting the duet).

Interesting thing is M587 says:

Failed to retrieve network list: another SPI transfer is pending

Here is the output of M122:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3 (2024-01-24 17:56:24) running on Duet WiFi 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6JKFJ-3S86K-12ZVX
Used output buffers: 1 of 26 (24 max)
=== RTOS ===
Static ram: 23224
Dynamic ram: 72012 of which 184 recycled
Never used RAM 14700, free system stack 132 words
Tasks: NETWORK(1,ready,38.6%,212) HEAT(3,nWait 5,0.0%,379) Move(4,nWait 5,0.4%,301) MAIN(1,running,60.9%,699) IDLE(0,ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:56:36 ago, cause: power up
Last software reset at 2024-01-30 00:29, reason: User, Gcodes spinning, available RAM 14700, 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
MCU temperature: min 34.5, current 36.2, max 39.7
Supply voltage: min 24.3, current 24.4, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/24/24, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
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: 2024-02-01 11:04:56
Cache data hit count 4294967295
Slowest loop: 303.09ms; 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 101.0ms, write time 130.4ms, max retries 0
=== Move ===
DMs created 83, segments created 7, maxWait 1867110ms, bed compensation in use: none, height map offset 0.000, max steps late 1, 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 1546, completed 1546, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 14], 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 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: 332.61ms; fastest: 0.07ms
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 4886, noresp 1
Failed to get WiFi status
Socket states: 0 6 0 0 0 0 0 0

Hello everyone,

I faced some very similar connection problems after upgrading from 3.4.x to 3.5rc3.

AP (Mikrotik) is about 1m away from the CNC (RSSI -27db) and the Macbook, ping and telnet seems to work well but
DWC fails to load.
After connecting my Macbook via Ethernet to the AP it started to work as expected, so I suspect its some kind of WIFI interference since updating the Duet 2 (rev. 1.02).

Maybe this Info could help to track the issues down.