Network problem after upgrade to 3.5.4 duet 2 maestro

pma_

Just upgraded my duet 2 maestro from 2.05 via 3.0 and 3.3 to 3.5.4 and started regretting upgrade.

On 2.05 I never ever had any network issue but after upgrade I see connection lost after few minutes to half an hour of use.
To get connection back I have to power cycle or reboot from local menu.

What is maybe interesting after reboot I cannot connect back to page where I was i.e. /Console I have to start from basic address.

Looks like a software bug.

FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.5.4 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2024-11-24 10:48:18

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.5.4 (2024-11-24 10:48:18) running on Duet Maestro 1.0
Board ID: 08DAM-9F9DA-MWNS0-6JTDA-3SW6N-145YW
Used output buffers: 1 of 26 (22 max)
=== RTOS ===
Static ram: 23712
Dynamic ram: 71412 of which 0 recycled
Never used RAM 20912, free system stack 218 words
Tasks: NETWORK(1,ready,30.7%,228) HEAT(3,nWait 5,0.1%,338) Move(4,nWait 5,0.0%,402) TMC(4,nWait 5,1.8%,108) MAIN(1,running,67.4%,778) IDLE(0,ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:03:03 ago, cause: software
Last software reset at 2024-12-17 22:53, reason: User, Gcodes spinning, available RAM 20936, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 39.6, current 40.3, max 40.6
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
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: standstill, read errors 0, write errors 0, ifcnt 27, reads 20611, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, read errors 0, write errors 0, ifcnt 27, reads 20611, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, read errors 0, write errors 0, ifcnt 24, reads 20611, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, read errors 0, write errors 0, ifcnt 24, reads 20611, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, read errors 0, write errors 0, ifcnt 24, reads 20611, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-12-17 22:56:09
Slowest loop: 14.12ms; fastest: 0.20ms
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: 15.0MBytes/sec
SD card longest read time 3.4ms, 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 0 -1, chamber heaters -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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 idle 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
=== Filament sensors ===
check 0 clear 582880
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 7.53ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 3 of 8
Interface state active, link 100Mbps full duplex
Socket states: 1 2 2 2 2 2

droftarts

@pma_ I've restored this topic, in case other Maestro owners have problems.

It's a big jump to go from 2.05 to the latest RRF 3.x, and involves many config changes. Please post your 2.05 and 3.x config.g files. There have been changes to the network code, but they shouldn't affect connections, and I haven't had problems with my Maestro in testing.

Some suggestions:

The network code in the firmware has been changed, and causes a different MAC address to be generated. If your router has MAC address filtering, you may need to update this on the router.
If you're using the original SD card that was supplied with the Maestro, it's probably quite old and slow. Newer versions of DWC do make more demands on the SD card. Test your current SD card; see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues. Replacing it with a faster card may help, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card
Do you have other network protocols enabled, ie FTP, Telnet? If you don't use them, disable them.
In DWC Settings > Machine-Specific > Communication, increase "Number of maximum AJAX retries" setting to 4. Change "Time to wait between AJAX retries (ms)" to 250.
Don't have multiple browser pages across multiple devices connected to DWC at the same time.

Ian