Many problems with 3.5.2

3DOeste

I recently upgraded my Duet2 ethernet from 3.5.1 to 3.5.2 and sice then I have some issues.
The most annoying is that connnection to the web server is lost all the time when simulating a file.
Printer is slow to respond, if I try to move it from panel due it responds almost a second later.
Accelerometer is mostly never found, that happens some time but now is 90% of the time.
BLtouch won't probe multiple times, only one and message says probe already trigger, but that's not what happening, the probe works ok, is becasue of the slow react time that this error occurs.
I include my config.g file, but it didn't change from 3.5.1.config.g

gloomyandy

@3DOeste Please post the output from running M122

3DOeste

@gloomyandy M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1FJ-3S86T-12ZMW
Used output buffers: 3 of 26 (26 max)
=== RTOS ===
Static ram: 23384
Dynamic ram: 70716 of which 312 recycled
Never used RAM 15084, free system stack 108 words
Tasks: NETWORK(1,ready,33.3%,181) ACCEL(6,nWait 5,0.0%,345) HEAT(3,nWait 5,0.1%,292) Move(4,nWait 5,3.4%,258) MAIN(1,running,63.1%,718) IDLE(0,ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 04:57:38 ago, cause: reset button or watchdog
Last software reset at 2024-07-16 09:21, reason: User, Gcodes spinning, available RAM 15924, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x14
Aux0 errors 0,0,0
MCU temperature: min 18.4, current 41.2, max 41.8
Supply voltage: min 23.7, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/9, heap memory allocated/used/recyclable 2048/1228/668, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: ok, SG min 0
Driver 1: ok, SG min 0
Driver 2: standstill, SG min 0
Driver 3: ok, SG min 0
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-08-06 14:29:52
Cache data hit count 4294967295
Slowest loop: 1390.97ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 250.0ms, write time 568.1ms, max retries 0
=== Move ===
DMs created 83, segments created 33, maxWait 1026836ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00
next step interrupt due in 48 ticks, disabled
Moves shaped first try 104888, on retry 24746, too short 95483, wrong shape 524445, maybepossible 14011
=== DDARing 0 ===
Scheduled moves 352551, completed 352511, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 12], CDDA state 3
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X153.209 Y155.89 F12000" 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
=== Network ===
Slowest loop: 569.00ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex
Socket states: 1 2 2 2 2 2

3DOeste

@3DOeste Also, If I try to get a response from M122 while simulating, it constinuosly disconnect and it's almost imposible for the response to appear on the console.

Phaedrux

Have you tried rolling back to 3.5.1 to verify that things go back to normal?

3DOeste

@Phaedrux No.. Do I just flash previus firmware or do I need to do some steps?

droftarts

@3DOeste said in Many problems with 3.5.2:

SD card longest read time 250.0ms, write time 568.1ms, max retries 0

Your longest read and write times don't look great. I think this is an SD card issue. Copy the files off the SD card onto your PC, reformat the SD card, then copy the files back on. If you want to test the SD card first, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
For formatting, or replacement, see earlier on the above page.

Ian

Phaedrux

@3DOeste said in Many problems with 3.5.2:

@Phaedrux No.. Do I just flash previus firmware or do I need to do some steps?

You'd upload the firmware zip file from the release you want.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.1/Duet2and3Firmware-3.5.1.zip

3DOeste

Well, it took me some time since I needed to finish some jobs, but I changed the SD card, although I couldn't find anything wrong with the old one. I was trying the .dummy upload with a large file, and it disconnect after a short while. I I run M122 after it reconnect I can see 250ms for longest read time, but inmediately after if I run M122 again it shows 5.2ms.
It's worth mentioning that I have absolutely no problems while printing. I didn't have a single print failure even after 3 days of continuous printing.

Also while writing this I tried to do a large simulation and it did it ok without disconnections.

3DOeste

I reflashed 3.5.1 and all the awkward delays are gone. Commands from panel due are instantaneous.
With 3.5.2 everything works, but has a delay before commands are executed.
So for now I'll stay with 3.5.1.

droftarts

@3DOeste Did you update DWC to 3.5.2 as well? Possibly old DWC files in the SD card /www folder are causing an issue. Also worth clearing browser cache for DWC and the ip address of the printer, and reloading the page in the browser. It is possible that there was some problem with the flash to 3.5.2, so worth redownloading 3.5.2 fresh and reflashing, if/when you want to update.

Ian

3DOeste

Hi, I'm sure DWC was on 3.5.2, and also try again from 3.5.1 to 3.5.2 and I have the slow response from commands from panel due (and also from DWC), back to 3.5.1 again and everithing runs fine.

droftarts

@3DOeste A suggestion from @chrishamm is to update to 3.5.2 and disconnect the PanelDue, and see if that makes a difference to the responsiveness of DWC. How is the PanelDue connected? By 4-wire cable, ribbon cable, or both?

Ian

3DOeste

It's connected with a 4-wire cable. I'll test disconnecting the PanelDue as soon as the current print is finished.

dc42

@3DOeste instead of disconnecting the PanelDue it is sufficient to leave it displaying its Setup page.

3DOeste

@dc42 Hi, I tried that, and it works ok. Today I installed 3.5.3, same behaviour as 3.5.2, but if after homing, I enter the panel due setup page, and then back to status, everything works as it should, without weird delays. It doesn't happen with 3.5.1.

dc42

@3DOeste thanks for the feedback. We added a check in 3.5.2 to reduce the chance of consistently running our of buffers when both PanelDue and DWC are active. It appears that this check is having a side-effect in your system. I have created this issue https://github.com/Duet3D/RepRapFirmware/issues/1047.