@chrishamm I tried installing 3.6-beta4 on our test rig.
M997 S2 F"unstable" whilst under 3.5.4 did not switch to unstable, so I did this to switch:
sudo rm -f /etc/apt/sources.list.d/duet3d.list
sudo bash -c "echo 'deb https://pkg.duet3d.com/ unstable armv7' > /etc/apt/sources.list.d/duet3d.list"
sudo apt update
sudo apt upgrade
All board firmware, DSF, and DWC installed without intervention.
After a power cycle, I could not get into the DWC webpage. I kept getting the blue Connecting banner and the Red could not connect banner at the bottom of the screen.
I reset the board a few times and powered down and back up and kept getting the same thing.
Another thing I noticed is that the CAN interface did not "come up". All boards were "quick" flashing the Status LED as if they weren't talking CAN to the 6HC ("slow" flash).
To revert back to 3.5.4, I performed:
sudo rm -f /etc/apt/sources.list.d/duet3d.list
sudo bash -c "echo 'deb https://pkg.duet3d.com/ stable armv7' > /etc/apt/sources.list.d/duet3d.list"
sudo apt update
rm -f ./reprapfirmware*.deb
apt download reprapfirmware/stable
sudo dpkg -i --force-depends ./reprapfirmware*.deb
sudo apt install -y --allow-downgrades duetsoftwareframework/stable duetcontrolserver/stable duetwebserver/stable duetpluginservice/stable duettools/stable duetruntime/stable duetwebcontrol/stable duetpimanagementplugin/stable
But... when the firmware update tried to run
sudo dpkg -i --force-depends ./reprapfirmware*.deb
it failed waiting for transfer pin ready
DSF, DWC did revert to 3.5.4 with the last command without issue.
A reboot after that still didn't allow a connection with DWC (3.5.4 DSF/DWC and 3.6.beta4 firmware)
I had to use Bossa to revert the board back to 3.5.4
A reboot after that allowed a connected to DWC.
The Machine-Specifics Electronics showed everything at 3.5.4 except the 3 3HC boards which were at 3.6.beta4
I ran an M997 on B1, B2, and B3, and pushed 3.5.4 to the 3HCs.
After a reboot there, the system is back to 3.5.4 and fully functional.
I'm going to try 3.6.beta4 on my test bench board to see what happens there. Then I can add 3HCs to the mix to see if/where it breaks. If it works there, I'll try the the system again. Maybe there was a glitch updating the 6HC firmware on the first go-around.
If you need me to run specific tests, let me know.
