Software bundle 3.5.0-beta.4 now available

dc42

On behalf of the Duet3D team I am please to announce the release of firmware 3.5.0-beta.4. As well as fixing bugs in beta 3, this release brings some new features:

HTTP sessions keys in standalone mode, to resolve issues (e.g. with message boxes) when a Duet has multiple HTTP clients
Support for driving Neopixel LED strips from multiple ports and from CAN-connected expansion boards
Event generation when a Duet 3 main board detects that a CAN-connected expansion board has stopped communicating or has reset
Experimental support for WiFi WPA Enterprise authentication modes
Reduced motor noise when the EXP1HCL board is used to run a motor in closed loop mode, and introduced a new assisted open loop mode for even more noise reduction and simpler tuning
Improvements to the Monaco code editor in DWC

RRF release notes: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta#reprapfirmware-350-beta4
DWC release notes: https://github.com/Duet3D/DuetWebControl/wiki/Changelog-DWC-3.x-Beta#version-350-beta4
DSF release notes: https://github.com/Duet3D/DuetSoftwareFramework/wiki/Changelog-DSF-3.x-Beta#version-350-beta4

Users of Duets in standalone mode, use the files at https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0-beta.4. Users of Duet with SBC, upgrade from the unstable feed f the package server as usual.

My thanks to Team Gloomy and the forum users who tested pre-release firmware binaries for us over the past few weeks.

Don't forget that you can use the ReleaseMgr plugin https://github.com/MintyTrebor/ReleaseMgr/releases/tag/1.1.19 to highlight the changes that apply to your system.

dc42

If you upgraded to RRF 3.5.0-beta.4 in standalone mode prior to this announcement and you are using a WiFi-equipped Duet, please note that the DuetWiFiServer files in the Github RRF release were incorrect until this morning. If M122 reports the WiFi firmware version as 2.1beta4 then you are running the correct WiFi firmware.

Exerqtor

@dc42 said in Software bundle 3.5.0-beta.4 now available:

If you upgraded to RRF 3.5.0-beta.4 in standalone mode prior to this announcement and you are using a WiFi-equipped Duet, please note that the DuetWiFiServer files in the Github RRF release were incorrect until this morning. If M122 reports the WiFi firmware version as 2.1beta4 then you are running the correct WiFi firmware.

Does this new WiFi fw version contain a potential fix for the reset issues btw?

dc42

@Exerqtor I'm sorry, it doesn't. I'll reply in your thread about this issue.

tristanryerparke

@dc42 Where can we find some details on the assisted open loop mode, other than the release notes?

dc42

@tristanryerparke said in Software bundle 3.5.0-beta.4 now available:

@dc42 Where can we find some details on the assisted open loop mode, other than the release notes?

I am working on the documentation for that. It already has mentions at https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m569-set-motor-driver-direction-enable-polarity-mode-and-step-pulse-timing and https://docs.duet3d.com/User_manual/Tuning/Duet_3_1HCL_tuning.

ctilley79

This seems related to beta 4 but I'm in the middle of a bed pid tune, and it seems to be in an infinite loop on phase 3. It's been measuring for 35 minutes now. I've never had a tune take that long.

jay_s_uk

@ctilley79 I've had it take an hour or more. Just sit it out, have a beer and see what happens

ctilley79

@jay_s_uk Now ya tell me after I cancelled it lol

ctilley79

@jay_s_uk I've never received this warning before. I will say usually I don't PID tune at a temp this low. 2 hours though!!

jay_s_uk

@ctilley79 yea, I've had that before. 9 times out of 10 it'll just work after saving the value

dc42

@ctilley79 it's because the data was inconsistent that it took so long - it ran for the maximum 25 cycles (the minimum is 5). Inconsistent data can be caused by noise in the temperature reading, or by a change in the ambient temperature as the tuning is being done - for example, if the printer is enclosed and the bed is heating the machine and its chamber.

As @jay_s_uk says, use the values it reported despite the warning.