Software Upgrades
There are two independent pieces of software, and they update separately.
| Download | Slot | Guide | |
|---|---|---|---|
| Mainboard | monitor.bin | Mainboard SD slot | MainBoard Updates |
| Screen | monitorHMI.tft | Screen SD slot | Screen Updates |
Both update from the SD card. No programmer, no cables, and no software on your computer.
Putting the right file in the wrong slot does nothing at all. It is safe, but it is easily the most common source of confusion, so check which slot you are using.
Where to get firmware
The two links above are the current release, hosted here so you can download and copy them straight to a card.
The full source is on the Clura Enclosure repository . It is open source, so if you want to change something, change it and build it yourself.
See the Changelog for what is in each release.
Updating cannot brick your board
The bootloader validates the whole image before it erases anything. It checks the size, reads the file fully from the card, checks the header, and only then erases, programs, reads back and verifies. If any step fails, you get a failure page and your existing firmware is untouched.
That means a corrupt download or a flaky SD card costs you a retry rather than a board.
Your settings survive
Settings, calibration and the filament library live in the mainboard’s own memory rather than on the SD card. A firmware update does not erase them.
A firmware update can reset the data.clu tuning values to their defaults. Leaving
data.clu on the card means it re-applies itself on the next boot, which is why keeping the
card in permanently is the recommended setup. See Configuration.