Greetings Citizens of Rinkhalsvania!
This is a special test build, outside the usual test series. It changes one thing under the hood, and we need people on every printer model to tell us whether it works before it goes anywhere near a normal release.
If you just want a working printer, stay on 20261118_03_test or the stable release. This one is for people who are happy to test and report back.
What's different
Rinkhals adds its menu to the printer's touch screen by patching two of Anycubic's programs each time the printer starts. Until now, every supported firmware version needed its own hand-made patch, 72 of them, and a new Anycubic firmware meant waiting for someone to make the next one.
In this build a small program on the printer works out the patch by itself. It finds the Support row in the settings menu and turns it into the Rinkhals entry, the same change as before.
- For firmware we already support, nothing should look different. Rinkhals still checks the result against a known checksum for your exact firmware, and if it doesn't match, it starts Anycubic's screen without the Rinkhals entry instead of taking a chance. On most firmware versions the result is byte for byte what the old patches produced.
- It never modifies Anycubic's files. It writes a patched copy, like before.
- It's the groundwork for supporting new firmware sooner. A firmware version Rinkhals doesn't know still won't start by itself, that hasn't changed.
This build also has everything merged since 20261118_03_test:
- Moonraker now reports its version, so Mainsail and Fluidd stop complaining about it (#251)
- The Tool Mapping dialog in Mainsail opens and can edit the map (#253, thanks @kpaaro)
- An ACE change is no longer missed by one client when another one loads at the wrong moment (#244, thanks @Gubir34)
- No more repeated G-code file reads after a print on printers that report the G-code folder without a trailing slash (#260, thanks @DiegoDeMauro)
- A hanging light command can no longer freeze Moonraker for good, and the free space check before an update reads the right number (#257, #258, thanks @hohol1)
Please help us test
We've run it on our Kobra S1 (firmware 2.7.3.7, which reports itself as 2.7.3.5): it boots, the Rinkhals entry is where it should be and opens the menu, with Klipper (vanilla) and HelixScreen running too. Every other model has only been checked on a computer against the firmware files, not on a printer. That's what we need you for... especially on the Kobra 3, Kobra 3 Max, Kobra 3 V2, Kobra S1 Max and Kobra 2 Pro.
After installing, please check:
- Does Rinkhals start, and is the Rinkhals entry in Settings where Support used to be?
- Does tapping it open the Rinkhals menu, and does closing the menu bring you back?
- Do the other rows in that settings list still open their own pages? This is the one we care most about. If a different row opens Rinkhals, or the Rinkhals row opens Anycubic's support page, tell us.
- Do Mainsail or Fluidd connect, and does a print from your slicer start normally?
Then tell us your printer model and firmware version, and what you saw, even if it's just "all fine". A report that everything works on a model we haven't tested is as useful as a bug report.
If something is off, please attach a debug bundle from the Management page of the Rinkhals web portal (http://<printer-ip>:8090). It includes the log of what the patcher found.
Good to know
- If the Rinkhals entry is missing after the update, Rinkhals decided not to patch the screen. Nothing is broken... the printer works, and Mainsail, Fluidd and the web portal are all still there. Send us a debug bundle and install 20261118_03_test again to get the entry back.
- Four firmware versions couldn't be checked beforehand because nobody has a copy of them anymore: Kobra 3 2.4.6.4, Kobra 3 V2 1.1.2.5 and 1.1.2.7, and Kobra S1 2.7.0.7. Rinkhals still patches them, but without a checksum to compare the result with. If you're on one of these, your report is especially welcome.
- Klipper (vanilla) on anything but a Kobra S1: updating ends with a reboot, and a reboot with Klipper running still hangs on those models. If you get error 11407 after the update, switch the printer off at the power switch and on again.
Report findings to https://github.com/rinkhals-community/Rinkhals/issues with a debug bundle.
Full Changelog: 20261118_03_test...20261122_01_patcher