RepRapFirmware 3.01-RC6 released

Hernicz

@ChrisP I think it will be something else.

wardialer@Wardialer-X5SA:~ $ cd /etc/apt/sources.list.d
wardialer@Wardialer-X5SA:/etc/apt/sources.list.d $ ls
duet3d.list  raspi.list
wardialer@Wardialer-X5SA:/etc/apt/sources.list.d $ sudo apt-get update
[sudo] password for wardialer: 
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease                                                   
Hit:2 http://archive.raspberrypi.org/debian buster InRelease                                                      
Ign:3 https://pkg.duet3d.com stable InRelease          
Get:4 https://pkg.duet3d.com stable Release [2,286 B]
Get:5 https://pkg.duet3d.com stable Release.gpg [228 B]
Fetched 2,514 B in 43s (58 B/s)                                                                                                       
Reading package lists... Done
wardialer@Wardialer-X5SA:/etc/apt/sources.list.d $ sudo apt-get install duetsoftwareframework
Reading package lists... Done
Building dependency tree       
Reading state information... Done
duetsoftwareframework is already the newest version (1.2.4.0).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
wardialer@Wardialer-X5SA:/etc/apt/sources.list.d $

Right now I'm using Raspbian with manual install (unstable skipped), but I've tried DuetPi + RC6 with same results. RC5 works well on Raspbian, haven't tried DuetPi

As a sidenote: Please rename DuetPi to DuetOS or whatever. Cannot google it, I get results about DietPi...

ChrisP

No, it's not something else, it because you need to be on the unstable list to be able to what you're trying. Your options are to revert your firmware back or switch to unstable.
Tbh, your DCS version is not even recommended for RC5 you have 1.2.4.0 and 1.2.5.0 is recommended.

Hernicz

@ChrisP Added unstable to the list update/upgraded an installed RC8.
Now if I edit config.g save and reset then machine name reverts back to My Duet and heaters disappear from Dashboard graph.
The only way to get these displayed properly after config edit is by unplug the whole thing and restrart.

ChrisP

@Hernicz
That's pretty interesting. I haven't update my config.g since I' update to RC8, however, at least a few of us have experienced the issue you describe since updating to RC8. We get it when the emergency stop is pressed (for eg.), but the reset after config update would likely do the same. I suggest, you add a comment on this thread, so that other methods or re-creating the issue are recorded.

Hernicz

@ChrisP Done