ScottW514
b7a595ced7
FORGEFIRM_RELEASE takes 0.0.3. The file sits outside the layer content hash, so the bump changes the version and invalidates no acceptance result. releases/v0.0.3 carries the artifact the bench exported for this image: campaign c-20260911182256-078f on 20260911172215 (dev), manifest identity fb24c3f4508ae54592f8d0b98ed0b2a07a933274980d8c1e4e5a967618ef9bd8, 83 tests, 83 satisfied (57 inherited), 0 required, release authorized. The release gate recomputes every catalog test's domain fingerprint from the manifest inside the release rootfs and signs only when the recorded results agree. The release carries, since v0.0.2: the lens frame in one place, so every Z a commissioning card sends comes from the settings the controller opens its Z limit from (the tail at the head's reference, the focus window written before the card's controller starts, every program judged against the reach before its first line goes out); the commissioning sheet acceptance test run as a fresh machine's; and the CPU percent on /status that holds across a status read inside the same scheduler tick as another reader's. Components: forgectrl 0.1.20, grblhal-glowforge 0.1.11, forgefirm-app 0.1.28+git, kernel-module 0.0.5, meta-openglow ced2af2.
OpenGlow / ForgeFIRM firmware for Glowforge
BETA
ForgeFIRM is in beta. Every release below 0.1.0 is a beta release. Expect problems, and expect frequent updates. Upgrade whenever a newer release is available, and report what you find on the community forum.
Open firmware for Glowforge brand CNC lasers. ForgeFIRM replaces the cloud-dependent factory software on the stock control board, with no hardware modification, and gives the machine a local controller, a local web control panel, and a standard Grbl interface. The factory cloud experience stays available as an option.
This repository is the base of the build and of the release: the
meta-forgefirm Yocto layer, the kas configuration, the image recipes, the
install and release scripts, the acceptance tool (forgetest/), the bench
tools (scripts/bench/), the bench actuator firmware (fixture/), and the
release artifacts (releases/).
Start here
https://docs.forgefirm.org/ is the documentation, and the source of truth for every fact about the machine and the firmware.
| Read this first | Safety |
| Put it on a machine | Installation |
| Use it | Usage, LightBurn |
| How the machine works | Technical |
| How ForgeFIRM works with it | ForgeFIRM internals |
| Build, test, release | Developers |
| Downloads | Releases |
| Questions | Community forum |
Build
kas build kas/forgefirm-glowforge.yml
Build covers the host setup, the two images, the source variant and the debug kernel. Release flow covers the pins, the push order and the signing pipeline.
Test
cd forgetest && python3 -m unittest discover -s tests -v
The acceptance catalog that gates a release, and the bench tools, are on Acceptance and The bench.
Contributing
AGENTS.md carries the rules for this repository and for the project: safety ordering, proof before done, the push order, and the writing rules. They apply to human contributors too, and Contribute is the same set on the site.
What this costs
Nothing. ForgeFIRM is free in both senses, under MIT and GPL licenses. There is no paid tier, no license key, no subscription and no Pro edition. If someone offers to sell it to you, the licenses allow it, but what you take home is their build rather than this one: get it from the source.
Safety
These machines contain a CO2 laser: it burns, blinds, and starts fires. Never defeat the lid switches or the interlock. Never leave a running job unattended. Keep a fire extinguisher within reach. Read Safety before you cut your first job, and Regulatory and legal before you install.
This is experimental software. Use of it could seriously maim or kill you or others, and it may void your warranty. Use it at your own risk.
This project is not affiliated with or endorsed by Glowforge.