Greetings Citizens of Rinkhalsvania!
This is a fifth test build on the way to the next release. It has everything from 20261118_01_test, plus one fix that matters a lot if you use the Klipper (vanilla) app.
What's new since 20261118_01_test
-
A reboot with Klipper (vanilla) running no longer leaves the printer stuck (#249). With real Klipper in charge, a plain reboot left the printer's control boards set up for Klipper. At the next boot, Anycubic's own firmware starts first, couldn't take the boards over, and hung. Rinkhals then gave up waiting... you got error 11407 on the screen, no apps, and the boot after that came up without Rinkhals at all. Only switching the printer off and on fixed it. This also happened on the reboot at the end of a Rinkhals update. Rinkhals now notices, resets the control boards and starts Anycubic's firmware again, and the boot carries on.
This fix is for the Kobra S1 only. It needs to know how to reset the control boards, and the S1 is the only model where we do. On the Kobra 3 family and the S1 Max, keep switching the printer off and on instead of rebooting while Klipper (vanilla) or a tunneled Klipper is enabled.
If you use Klipper (vanilla) or a tunneled Klipper and you're on an older build: updating to this one ends with a reboot, which is exactly the case that hangs. If the printer comes up with error 11407 after the update, switch it off at the power switch and on again. On a Kobra S1 it only happens that one last time.
Please help us test
- Does Rinkhals start normally, and does the Rinkhals entry in Settings open the Rinkhals menu?
- Kobra S1 with Klipper (vanilla): reboot the printer from Mainsail or the web portal, without switching it off. Does it come back up by itself, with Klipper running again after a minute or so?
- Do your apps still start at boot like before, and can you enable and disable them from the touch screen and the web portal?
- Do Mainsail or Fluidd connect, and does a print from your slicer start and finish normally?
We tested the reboot on our Kobra S1 with Klipper (vanilla) running. A normal boot is unchanged, since the new step only runs when Anycubic's firmware hasn't started after 15 seconds.
If something doesn't work, a debug bundle from the Management page of the Rinkhals web portal (http://<printer-ip>:8090) would help a lot.
Known issues
These are open and not fixed in this release.
- A reboot with Klipper (vanilla) or a tunneled Klipper running still hangs on the Kobra 3 family and the Kobra S1 Max, as described above.
- The new app dependency messages on the touch screen and in the web portal's Apps page haven't been tried on a printer yet.
- On the Kobra S1 with 2.7.3.7, the Mainsail and Fluidd Heightmap shows the saved mesh instead of the live one during a print. The live view stays limited to 2.7.2.7 until we've checked it on the new firmware.
- #205 - on the Kobra S1 Max, the head still stays over the last probe point after a calibration started from Mainsail. It doesn't affect the mesh.
Report findings to https://github.com/rinkhals-community/Rinkhals/issues with a debug bundle.
Full Changelog: 20261118_01_test...20261118_02_test