Web Control keeps disconnecting

Aurimas

Hi,

so I have 6XD
connected directly to the laptop via ethernet cable.
The interface keeps loosing connection - sometimes for fair few times in a row

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6XD version 3.5.0-rc.2 (2023-12-14 10:33:00) running on Duet 3 MB6XD v1.01 or later (standalone mode)
Board ID: 0JD2M-999AL-D2PS0-6J9D2-3SJ6Q-15M33
Used output buffers: 13 of 40 (40 max)
=== RTOS ===
Static ram: 153284
Dynamic ram: 119200 of which 208 recycled
Never used RAM 70300, free system stack 146 words
Tasks: NETWORK(1,ready,78.1%,182) ETHERNET(5,nWait,0.1%,321) HEAT(3,nWait,0.0%,353) Move(4,nWait,0.0%,216) CanReceiv(6,nWait,0.1%,772) CanSender(5,nWait,0.0%,329) CanClock(7,delaying,0.0%,351) MAIN(1,running,21.6%,444) IDLE(0,ready,0.0%,30), total 100.0%
Owned mutexes: LwipCore(NETWORK)
=== Platform ===
Last reset 00:33:18 ago, cause: power up
Last software reset at 2023-12-23 17:44, reason: User, Gcodes spinning, available RAM 71172, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 34.7, current 38.9, max 39.3
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.3, current 12.3, max 12.4, under voltage events: 0
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/36/12, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok
Driver 1: ok
Driver 2: ok
Driver 3: ok
Driver 4: ok
Driver 5: ok
Date/time: 2024-01-02 19:44:31
Slowest loop: 28.12ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.9ms, write time 17.3ms, max retries 0
=== Move ===
DMs created 125, segments created 6, maxWait 354786ms, bed compensation in use: none, height map offset 0.000, max steps late 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 278, completed 278, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 106], CDDA state -1
=== DDARing 1 ===
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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000080
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 10899, received 256276, lost 0, errs 0, boc 0
Longest wait 3ms for reply type 6018, peak Tx sync delay 276, free buffers 50 (min 34), ts 9994/9993/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 49.66ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(2) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 1 0
Socket states: 3 5 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

Phaedrux

@Aurimas said in Web Control keeps disconnecting:

The interface keeps loosing connection

What exactly are you seeing happen?
What browser?
When you can't connect, are you still able to ping the Duet IP?

Aurimas

@Phaedrux interface says "disconnected"
reconnects then after some time looses connection again
nothing to do with IP or the network - connected directly to the board and the board keeps running.
it just interface keeps resetting/relaoding

Phaedrux

Can you confirm that the DWC version is also 3.5-rc2?
What browser?
When you can't connect, are you still able to ping the Duet IP?
Can you open a command prompt window and have a continuous ping to the duet IP running? When you get a disconnection does the ping continue normally or does it fail as well?

Aurimas

@Phaedrux yes it is 3.5-rc2 - all firmware matching
it is not IP that is lost - its the DWC that throws an error when status changes from idle to disconnected and then refreshes page by itself. its not the IP. if it would be IP issue as I understand I would have to hit refresh in the browser
browser is always Chrome.

Phaedrux

Are you able to roll back to 3.4.6 for firmware and DWC and see if the disconnects still happen?

Aurimas

@Phaedrux not really - i think older version will not support my setup. I have 16 axis setup right now using 16x 1XD

Phaedrux

Yes I understand, but I'm trying to determine if the issue is hardware related or with the firmware/DWC release candidate. This is why I ask to see if the ping succeeds or fails when the disconnects are happening.

chrishamm

@Aurimas It looks like your board runs out of output memory, @dc42 and I need to look into it:

Used output buffers: 13 of 40 (40 max)

Do you only have a single web interface tab open when this happens? Is there a PanelDue or other display connected to your machine as well? Would you mind sharing your whole config.g file?

Aurimas

@chrishamm No screen connected, the pc is directly connected to the board via ethernet cable - so no hub or anything in between.
Config file has paneldue configured, but it is not connected at this stage

here is the config file:

; Default config.g template for DuetPi
; Replace this with a proper configuration file (e.g from https://configtool.reprapfirmware.org)

; Enable network
if {network.interfaces[0].type = "ethernet"}
    M552 P169.254.112.5 S1
else
    M552 S3
    
;Enable PanelDue
M575 P1 S1 B57600
G4 S2

M584 R0 X20.0 Y21.0 U31.0 V40.0 A41.0 B50.0 C51.0 D60.0 'a61.0 'b30.0 'c70.0 'd71.0 'e80.0 'f81.0 'h90.0 'i91.0 


M569 P21.0 S1                                        ; physical drive 0.0 goes forwards
M569 P20.0 S0                                        ; physical drive 0.1 goes forwards
M569 P31.0 S1 
M569 P30.0 S0
M569 P41.0 S1 
M569 P40.0 S0
M569 P51.0 S1 
M569 P50.0 S0
M569 P61.0 S1                                        ; physical drive 0.0 goes forwards
M569 P60.0 S1
M569 P71.0 S1                                        ; physical drive 0.0 goes forwards
M569 P70.0 S1
M569 P81.0 S1                                        ; physical drive 0.0 goes forwards
M569 P80.0 S1
M569 P91.0 S1                                        ; physical drive 0.0 goes forwards
M569 P90.0 S1


M92 X26.67 D26.67 V26.67 B26.67 'b26.67 'c26.67 'e26.67 'h26.67 Y80 U80 A80 C80 'a80 'd80 'f80 'i80 

M566 X2000 D2000 V2000 B2000 'b2000 'c2000 'e2000 'h2000
M566 Y4000 U4000 A4000 C4000 'a4000 'd4000 'f4000 'i80000

M203 X10000.00 Z10000 Y10000.00 U10000.0 V10000.0 A10000 B10000 C10000 D10000 'i80000;max speed

M201 X2000 D2000 V2000 B2000 'b2000 'c2000 'e2000 'h2000  ;max acceleration
M201 Y4000 U4000 A4000 C4000 'a4000 'd4000 'f4000 'i4000    ;max accelertion

M574 X2 S1 P"!20.io1.in"
M574 Y1 S1 P"!21.io1.in"
M574 'b2 S1 P"!30.io1.in"
M574 U1 S1 P"!31.io1.in"
M574 V2 S1 P"!40.io1.in"
M574 A1 S1 P"!41.io1.in"
M574 B2 S1 P"!50.io1.in"
M574 C1 S1 P"!51.io1.in"

M574 D1 S1 P"!60.io1.in"
M574 'a1 S1 P"!61.io1.in"
M574 'c1 S1 P"!70.io1.in"
M574 'd1 S1 P"!71.io1.in"
M574 'e1 S1 P"!80.io1.in"
M574 'f1 S1 P"!81.io1.in"
M574 'h1 S1 P"!90.io1.in"
M574 'i1 S1 P"!91.io1.in" 

M208 S1 X-90 Y-62 U-58 V-90.0 A-76 B-90 C-76 D-90.0 'a-60 'b-90.0 'c-90.0 'd-60 'e-90.0 'f-60 'h-90.0 'i-62
M208 S0 X90 Y150 U150 V90.0 A150 B90 C150 D90.0 'a150 'b90.0 'c90.0 'd150 'e90.0 'f150 'h90.0 'i150

Aurimas

@Phaedrux I have been pining target and had disconnect - ping had no issues at all.

soare0

@Phaedrux
Unfortunately I am ”able” to report the same problem.

6XD+3HC and Panel Due, all updated from 3.4.6/1 to 3.5.0 rc2.

With 3.4.6, there was not any problem in DWC, it started only after updates. Updates were really necessary, because of some other bugs, most related to Panel Due it seems.
DWC works, but it keeps disconecting. Closing web browser, rerstarting computer, did not help.

Usually I am working on Chrome, but it seemed to be the same on Opera or Firefox. In fact, I was not able to fully connect with those too, but the same was with Chrome, after restarting the computer.

I am on Win11 Pro, I3-12100 and 32G RAM, however, I think that they are not an issue... by far.

The problem is just annoying, is is possible to work... barely.

L.E. I updated DWC to 3.5.0 rc2 too. The problem seems to be solved.

agmeadows

I am also having a similar issue. I am on 3.5.0 b4. Uploading files is hit or miss. DWC will disconnect and refresh. If I keep retrying it will eventually work. The larger the file, the more I need to retry. It was fine when I was on 3.4.5. I upgraded firmware to address other issues.

Running 3.5.0 rc2 causes layer shifts when using input shaping so upgrading is not an option