Duet2 Ethernet connection Problems

qurt

The Web HMI sometimes randomly stops working on the Duet2 Ethernet Board.

The via Ethernet connected Raspberry Pi than starts to show a blue "Verbinde..." message. When reloading the page without caching the browser shows a "ERR_CONNECTION_REFUSED" error and the HMI/Printer is not reachable.

At the Same time, I still get ping responses.

It looks like the WebControl HMI/Server crashed...

This happens randomly on some of the duet2 Machines.

After restarting the Board: everything works fine.

Is this a software issue of DWC 3.4.*? (Sorry we can't upgrade at the moment).
Is it a hardware Issue?
This Problem so fare never occurred on Duet3 Boards.

Is it worth replacing the Network port?

droftarts

@qurt Please send M122 to the board, and post the response, so we can see exactly what firmware version you are using. This will also show some diagnostic information.

Are you connecting more than one browser screen to the Duet? If so, it may help to increase the "Number of maximum AJAX retries" setting to 4 in Settings > Machine-Specific > Communication, and increase "Time to wait between AJAX retries (ms)" to 250.

Otherwise, I think this may be a failing SD card. You can check by running the commands and tests documented here: https://docs.duet3d.com/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
Please run those and post the results.

Ian

qurt

@droftarts Thank you.
The M122 response (i did it twice within maybe a minute):

M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet Ethernet 1.02 or later + DueX5v0.11<LF>Board ID: 0JD2M-9F8TA-GJ4TD-6J9DD-3S86N-9RPY6<LF>Used output buffers: 1 of 26 (26 max)<LF>=== RTOS ===<LF>Static ram: 23896<LF>Dynamic ram: 76556 of which 0 recycled<LF>Never used RAM 8772, free system stack 170 words<LF>Tasks: NETWORK(ready,142.2%,211) HEAT(notifyWait,28.4%,286) Move(notifyWait,0.5%,363) DUEX(notifyWait,0.0%,24) MAIN(running,117.1%,436) IDLE(ready,0.1%,30), total 288.3%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 117:45:12 ago, cause: power up<LF>Last software reset at 2024-08-14 13:50, reason: User, GCodes spinning, available RAM 7888, 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: 0x04<LF>Step timer max interval 0<LF>MCU temperature: min 28.4, current 30.2, max 32.7<LF>Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: [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...].]`

and again:

M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet Ethernet 1.02 or later + DueX5v0.11<LF>Board ID: 0JD2M-9F8TA-GJ4TD-6J9DD-3S86N-9RPY6<LF>Used output buffers: 1 of 26 (26 max)<LF>=== RTOS ===<LF>Static ram: 23896<LF>Dynamic ram: 76556 of which 0 recycled<LF>Never used RAM 8772, free system stack 170 words<LF>Tasks: NETWORK(ready,21.8%,211) HEAT(notifyWait,0.2%,286) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,78.0%,412) IDLE(ready,0.0%,30), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 117:48:03 ago, cause: power up<LF>Last software reset at 2024-08-14 13:50, reason: User, GCodes spinning, available RAM 7888, 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: 0x04<LF>Step timer max interval 0<LF>MCU temperature: min 29.5, current 29.8, max 30.6<LF>Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, [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...].]

Here are the AJAX settings that have been on the machine.

I adjusted them to the following new settings:

Also I couldn't find any SD Card issues.

M39
SD card in slot 0: capacity 31.90GB, partition size 31.89GB, free space 31.04GB, speed 20.00MBytes/sec, cluster size 32kB<LF>ok<LF>
M122 P104 S10
Testing SD card write speed...<LF>SD write speed for 10.0MByte file was 2.00MBytes/sec<LF>Testing SD card read speed...<LF>SD read speed for 10.0MByte file was 1.21MBytes/sec<LF>ok<LF>

Restarting the network with:

M552 S0  ; Turn off network interface
M552 S1  ; Restart network interface

solved (like a restart also) temporary the issue.

Are the new Ajax time intervalls and settings correct?

Do you have any further ideas or recomendations?

droftarts

@qurt I think you are using YAT to send the M122 command, and you haven't changed the line endings (as explained here https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#yat-settings), so the response is truncated, and the WiFi information at the end of the report is missing. Please either send M122 from the DWC console, or send from YAT with the line endings corrected.

Are the new Ajax time intervalls and settings correct?

No. Change "Number of maximum AJAX retries" setting to 4 (20 is too high). Change "Time to wait between AJAX retries (ms)" to 250.

Ian

qurt

@droftarts Thank you. Just to make sure: where can i find the Change "Time to wait between AJAX retries (ms)" to 250. parameter?

do you mean the Extended status update interval?

droftarts

@qurt I think the name has changed since DWC 3.4.x. I think 'Time to wait between AJAX retries (ms)' (3.5.3) is the same as 'Extended status update interval' (3.4.x).

Set 'Extended status update interval' and 'Update interval (ms)' to 250ms. 20ms is definitely too short. The default should be 200ms, so it seems that a zero may have been deleted, and might be the cause of your issues.

The defaults in 3.5.3 are:

If you want do return to the defaults, delete sys/dwc-settings.json (you can do this in DWC) and reload the page in your browser. A new dwc-setting.json will be created as soon as you change anything.

Ian