Latest 3.5 post rc3 firmware builds

dc42

I have put new firmware builds at https://www.dropbox.com/scl/fo/6afk7iewlw1ycldb8dc4u/h?rlkey=21rm8jcz6aqy3gh523wkmxro7&dl=0. We intend to use these as the basis for the imminent 3.5.0-rc.4 release unless any serous issues are found with it. If you are using 3.5 beta or rc binaries and running in standalone mode, please try updating to these and report any issues.

The main board binaries report version 3.5.0-rc.3+8. The expansion board binaries report 3.5.0-rc.3+6.

For the changes since rc3 see https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#changes-since-rc3.

OwenD

@dc42
I've tried the power fail changes and note a couple of minor issues

I get an error saying the SD card has open files each time.
The object names are not restored. So If the print has two power failures the print objects had no name, then I get an M486 error because the name is empty.
If a print that has had an object cancelled has a power failure, the object cancellation is not respected when the print is resurrected.

Error: in file macro line 5 column 12: M486: expected a non-empty string
Error: in file macro line 6 column 12: M486: expected a non-empty string
Error: in file macro line 7 column 12: M486: expected a non-empty string
Error: SD card has open file(s)
Running resurrect prologue

dc42

@OwenD, thanks for your report. I have a couple of questions:

When does the message about open files appear? From your snippet above I'm guessing that it is when resurrect.g is run - is that correct?
Did resuming a print from which an object had been cancelled definitely work for you in a previous release, if so which release was that?

dc42

@OwenD PS:

I have reproduced the "SD card has open files" error but not the M486 error messages. Please provide a resurrect.g file that provokes those messages.

OwenD

@dc42
The M486 errors only appear if I cut power twice on the same print.
However I checked the object model after the first power off and the names were an empty string after resurrection, so either they're not being saved or not being restored.

As far as the cancelled object, I can't say I've ever checked for that before so it could be it's always been that way.

I'll run another round of tests and save all the files.

dc42

@OwenD please try firmware 3.5.0-rc.4 which we intend to release today or tomorrow. I believe it fixes these issues:

SD card has open files error message
Build object names not restored when resuming after power fail
Error message when resuming after power fail if build object names were not provided