Software bundle 3.5.0-beta.4 now available

[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.