Duet 2 Ethernet disconnect when printing and paneldue connected

dc42

@Shoki I'm guessing that the PanelDue might be generating excessive traffic, overloading the Duet output buffers. If that's the case then if you switch to the PanelDue Setup screen, DWC may reconnect.

Shoki

@dc42 I don't need to do anything for it to reconnect. It comes back on it's own after a few seconds. It's just very annoying and sometimes the disconnection are so frequent I don't have time to send gcode commands manually in the console of the DWC, which is very annoying.

So you think it's something that can't be fixed : too much information displayed on the PanelDue because it's a Toolchanger ?
I tried to disable all my tools except one in my config.g. So that only a single tool was displayed on the PanelDue and I still had the problem...

I guess if it can't be fixed I will just add an on/off switch next to the screen so that I can power it on when I need it and leave it off when I don't.

Phaedrux

I'd be curious to see what happens if you went back to an older version of the PanelDue firmware like 1.24

https://github.com/Duet3D/PanelDueFirmware/releases/tag/1.24

edsped

@Phaedrux Not so sure it will help. I believe I went through just about every firmware when I was fighting this. The only thing I didn't do was update over USB until I got the 6HC. I'm going to follow this as I putzed with it for almost a year before tossing in the towel.

Shoki

@Phaedrux I will not be able to try this before mid november as I have vacation and then I will see you at Formnext.

edsped

Now I'm racking my brain to think of anything I did differently going from the wifi to the 6HC and the only other thing I can think of and it may be minor is that I switched from a flat 4 wire cable to a twisted left over from a stepper motor. That being said I switched between the 4 wire and the ribbon cable when trying to troubleshoot the WiFi but I did not use new wires for the 4 wire setup. What I'm currently running...

dc42

All, thanks for reporting this. I suspect that something is causing PanelDue to repeatedly retry a request for the object model, causing the GCode processor to be overloaded with M409 requests. We are looking into it. Meanwhile, if anyone encounters this please report:

RRF firmware version on the main board
PanelDue firmware version
What baud rate you are using for the PanelDue (the default 57600, or something else)
What status the PanelDue is showing after it happened (Idle, Connecting, something else, or alternating between two or more values)
Anything you did (e.g. command you sent to the machine) that appeared to trigger this happening.

dc42

All, please download and install the appropriate build of PanelDueFirmware from https://www.dropbox.com/scl/fo/krqc6189we080r638jrwn/h?rlkey=80p7daqhs67630djtfs2pqwlj&dl=0 and see if it solves the problem.

edsped

@dc42 said in Duet 2 Ethernet disconnect when printing and paneldue connected:

All, please download and install the appropriate build of PanelDueFirmware from https://www.dropbox.com/scl/fo/krqc6189we080r638jrwn/h?rlkey=80p7daqhs67630djtfs2pqwlj&dl=0 and see if it solves the problem.

Sorry if I wasn't clear but I've moved from the Duet 2 WiFi to the Duet 3 6HC with SBC and the problem seems to be resolved. That being said no printing information is displayed in the 7i console.

Also, I always ran the 7i with standard baud rate. Let me know if you still want me to install the firmware above.

Shoki

@dc42 I will try it when coming back after Formnext. See you there.

Leonard03

@dc42 for me seems that made a big difference. Not a single drop in DWC into a 7 hours print so far

edsped

@Leonard03 Keep me posted as if the firmware fixes your issue then my Duet 2 WiFi should be okay and

dc42

@Leonard03 thanks for that.

@Shoki please let me know when you have had a chance to test the new PanelDueFirmware.

Shoki

@dc42 I just tried it.
This did not make a difference for me.
The firmware was correctly installed and the name displayed on the Paneldue corresponds to the one you provided.

edsped

@dc42 Has there been any more work on this? I switched from a 6HC w/SBC to 6HC standalone and sure enough the disconnects are back. Unlike using the built in WiFi on the Duet 2 that was giving me disconnects I have the 6HC connected to a Trendnet AC1200 Wireless bridge via ethernet. The big difference between SBC and non SBC is that the PanelDue reports all activity in the console in standalone mode and reported nothing in SBC mode.

Shoki

@edsped I have added an on/off switch on my PanelDue so I turn it off when I don't use it. Hardware solution to a software problem.