Oleksandr ShyshatskyiandClaude Opus 5 a29fd1913d HelixScreen's filament panel now acts on the tool you picked
v0.99.115-creator5.4. The screen was built for a printer with one hotend --
one nozzle reading, a Load button that never said which head it meant -- and
on this machine that was not merely thin: preheat resolved "the nozzle" to the
ACTIVE extruder, so selecting T2 and pressing preheat heated T0. Every nozzle
target now goes to the selected tool's own heater, cooldown builds its heater
name the same way, and where no heater resolves the command is dropped with a
log line rather than sent to the wrong hotend. The panel above it is a row of
tool chips, and the reading, the graph and the presets follow the selection.

HELIX_PKG_VERSION MOVES WITH THE TAG, which is the whole reason the two lines
are neighbours in versions.env: `_p4` for `-creator5.4`. The upstream release
title calls this build 5; the tag's own revision is 4 and that is what a
package version can be ordered by.

Measured: `make packages PKG=helixscreen` builds anvil-helixscreen
0.99.115_p4-r1 against the new tarball, whose sha256 is the one the release's
own SHA256SUMS publishes, and qa/static passes at 319.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017rgrDeu9YAUuMM2G7gKTpL
2026-09-01 15:40:01 +03:00

Reforge

Custom firmware for the FlashForge Creator 5 and Creator 5 Pro.

It installs the way a normal FlashForge update does: copy one file to a USB stick, plug it in, power the printer on. No jailbreak, no soldering, no opening the case, no ssh needed to get started — the printer's own updater does the work.

Packages are published on the Releases page — two files per release, one per model, marked pre-release while the mod is young. Help and support: the Discord.

Unofficial and unaffiliated with FlashForge. It voids your warranty and you are responsible for your machine. See Status for what has actually been tried on hardware before you flash anything.


Status

It runs on a real printer — a Creator 5 Pro, flashed and printing:

HelixScreen mid-print on the Creator 5 Pro: T2 mounted, layer 2 of 173 HelixScreen's bed-mesh screen showing a probed 10x10 mesh

A checked box happened on that machine; an empty one has not, yet.

For everyone:

  • Install and migration from stock firmware — the printer's own updater does it; your unit's factory calibration imports itself on the first boot
  • Printing — gcode straight from the slicer, nothing edited
  • Toolchanges — a current Klipper with real toolchanger support, in place of the 0.12-era tree FlashForge ships
  • Nozzle-offset calibration
  • Mainsail at http://<printer-ip>/, with a current Moonraker behind it — anything that speaks the Klipper API works
  • Camera — mjpg-streamer, already on the printer; the mod just starts it
  • Wifi
  • HelixScreen on the printer's own screen
  • Chamber heater
  • Creator 5 (non-Pro) — its package builds and passes the same replica test suite, but has not touched hardware
  • Going back to stock — proven on the printer replica, not yet needed on the machine. The stock package restores everything it carries; Moonraker is not in it, so the mod's build stays and keeps working — see Support

For the tinkerer:

  • ssh as root — a random password is chosen on the first install and written to anvil-password.txt on your stick; updates keep it (make passwd bakes in your own)

What you give up

FlashForge's application is one binary, and replacing it takes everything that lived inside it: the network API on :8898, and with it FlashPrint, Orca's FlashForge profile and the mobile app. Moonraker's API takes over. Flashing the stock package brings them back.

If your prints already come out the way you want and you like the printer's own screen, this mod is not for you. It trades FlashForge's polish for Klipper's reach, and it expects you to be comfortable with a Klipper config and an ssh session when something breaks — Is this for you is the honest version of that question.


Get it

Creator 5 and Creator 5 Pro are not interchangeable. The printer refuses a package built for the other model — the most common reason a flash "does nothing". Yours is in Settings → About.

Your printer The file on the Releases page
Creator 5 Creator5-anvil-<date>.tgz
Creator 5 Pro Creator5Pro-anvil-<date>.tgz

Download the stock FlashForge package for your model before you begin. It is the undo button: flashing it back puts the printer as it was.


Start here

Is this for you Who should flash this, who should stay on stock, and what it asks of you
Installing The flash, the first boot, your root password
Your first print The go/no-go checks, calibration, and the two verification files
Support The logs, and the way back to stock

The full manual is at reforge.readthedocs.io. If you want the insides — one file, firmwareExe, with the stock boot scripts, updater and recovery path left untouched — How it works is under For contributors.


Credits

Built on the work of others: ghzserg/FF publishes the stock packages and factory image everything here starts from; Mainsail, Moonraker and HelixScreen are shipped as released; the toolchanger status API follows viesturz/klipper-toolchanger so tool-aware UIs work unchanged.

S
Description
Custom firmware for the FlashForge Creator 5 / Creator 5 Pro: Klipper, Mainsail, ssh and HelixScreen, installed by copying one file to a USB stick
Readme
6.5 MiB
0 Stars 1 Watchers 0 Forks
2026-09-24 11:56:02 -05:00
Languages
Python 59.6%
Shell 26.2%
C 11%
G-code 1.9%
Makefile 1.3%