Software version 3.6.0-beta.3 now available

chrishamm

On behalf of the Duet3D team I am happy to announce the availability of our next prerelease software bundle v3.6.0-beta.3.
This version features many bug fixes and improvements. Please refer to the changelogs for further details:

Users in standalone mode can obtain the latest builds from here. Users in SBC mode can upgrade using M997 S2 provided the unstable package feed is activated. This can be done using M997 S2 F"unstable". Please note that M997 S2 is NOT available on the meanwhile outdated Debian Buster build of DuetPi. Please check out this guide if you are still using an old DuetPi installation.

If no further serious issues of this build are reported, this beta will form the basis of the next release candidate, which will eventually become the next stable version. If you do encounter problems, please report them here on the forum with [3.6.0-beta.3] in the title.

DaveA

@chrishamm

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