[3.6.0-beta.3] Duet 2 issues, lost communication

DaveA

Has there been any reports of this release causing problems? For the first time in years an update has left me with a dead printer.
I have a Duet2 on a delta. After the update I've lost any ability to connect via DWC. There is something alive as the extruder fan spins for a few seconds on power up. I can also do a G28 from the Panel but it doesn't home right. It does go to the top but then jerks around for 3 or 4 times then stops.
I was updating from beta2+4 I think.
I don't have time to do more investigating right now but I guess I need to brush up on Bossa to get back.

Phaedrux

@DaveA Getting some information from a USB terminal would be your first stop.

https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

droftarts

@DaveA Is the diag light on? That's usually the first sign the board has lost it's firmware. If the fan spins up and then stops, I'd guess that the config.g is running, and it's the WiFi firmware update that's failed. Connect via USB. If the firmware is running, send M997 S1 to update the WiFi module.

Ian

Notepad

@DaveA Quick question, did you remember to update your PanelDue firmware? I remember there was a possible change where the PanelDue could stop connection to DWC.

droftarts

@Notepad @dc42 wrote this on Discord:

The issue was that the object model got larger with every firmware release, especially on complex machines like tool changers where the OM was especially large. At the default PanelDue baud rate of 57600b some OM requests on a toolchanger took 750ms for the response to be transmitted, and then PD requested the OM again immediately. This meant that RRF was forever sending M409 responses to PD, which used up all the output buffers, leaving none available for HTTP.
In PanelDueFirmware 3.5.1 we only allow a new M409 request to be sent when the receive data line has been idle for 200ms, which gives RRF time to respond to HTTP object model requests without running out of buffers before DWC times out. We also add an extra flag to identify the requester as PanelDue. RRF 3.6beta3 recognises this flag and avoids returning data that PanelDue doesn't need, which shortens the response from 750 to 300ms.

@DaveA If you have a PanelDue connected, either disconnect it or switch it to the 'Setup' page (it doesn't communicate with the Duet on this page) while updating firmware. Also update the PanelDue firmware with the latest release: https://github.com/Duet3D/PanelDueFirmware/releases/latest

Ian

DaveA

@droftarts

A little more info. I pulled the SD card and copied 3.6.0-beta.2 into the firmware directory. No matter how many time I ran M997 S0 on reboot it aways reported 3.6.0-beta.3 when I entered M115 and there is no DWC connection. I did an erase and used bossa to write the beta.2. file. On boot M115 reports 3.6.0-beta.2 and I have a DWC connection. I then used the system update from DWC to update again to beta.3. Same results with no DWC connection.

So something is awry with either the duet2combinedfirmware.bin file or my system. I didn't see anything obvious in the release notes that I need to update anything else first.

I'm away for some time but I'll try any tests later today.

droftarts

@DaveA Do you have a particularly old iap (In App Programmer) file? The last released version for Duet 2 is "Duet2_SDiap32_WiFiEth.bin" in the 3.5.4 release: https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.4
However, I'd think this was more likely an issue with the WiFi module firmware. What version is it currently running? It should be in the M122 report, at the end.

Ian

DaveA

@droftarts

New results. With beta.3 I can get results from M115 but M122 just hangs for maybe 15 seconds then the Duet reboots. I did have a recent Duet2_SDiap32_WiFiEth.bin but I noticed that the 3.54 release area had a few hours old version so I put it on the SD card. No change. I'm hardwired so no wifi in use. I'm back to beta.2 via bossa and M122 works fine.

Are there known instances of stand alone duet2 boards working with this release?

tas

@DaveA
Yes. I have two printers running Duet2 boards stand alone. The latest release is working very well.

I have not come across any issues as yet. Just make sure you use the latest version.

dc42

@DaveA please provide your config.g file, then I can try it here and see whether it works for me.

droftarts

@DaveA said in [3.6.0-beta.3] Duet 2 issues, lost communication:

I'm hardwired so no wifi in use.

So this is an Duet 2 Ethernet? Please post your M122 as well.

Ian

DaveA

@dc42
Here's the config file. Last changed on 8/24.

config.g

DaveA

@droftarts
I'd like to include the M122 output but I can't. When I issue M122 I get no text on TeraTerm for about 15 seconds then the board reboots.
If I issue M115 I immediately get the board name and firmware version.
So something is running.

droftarts

@DaveA It doesn't have to be from beta.3, do it from beta.2 if it works there.

Ian

DaveA

@droftarts
Here is the beta 2 M122
Beta2M122.txt

dc42

@DaveA I've reproduced a fault, it appears to be a networking issue in 3.6beta3 on Duet 3 Ethernet. I am investigating it.

dc42

@DaveA please try the 3.6.0-beta.3+1 build at https://www.dropbox.com/scl/fo/bx70c7u0bshq79ez83mnn/AKMj4UCEimtQuGYxRj_d0ew?rlkey=7yiq3x5fcae3v2ogslfocx1op&dl=0.

DaveA

@dc42
Bingo! DWC comm is back. I had to pull the printer apart to get to the Duet so I can't try a print for a while. Thank you for the quick response.

3DOeste

Hi, I have the same problem. I'm trying to update through paneldue console, I send M997 S0, it says firmware updating, connection is lost, I reset the board but firmware file is not changed, is it possible to do it this way or only through USB?

T3P3Tony

@3DOeste please try by USB