ScottW514
c978e76b4c
Rule 17's ^X mid-move goes out during G1 X120 F3000 instead of G1 X30 F600, and the plausibility bound on the distance the abort kept widens to the new move's length. Every other line of the rule stays. At $100 = 213.333 the F600 move cruises at about 2133 steps/s. The core's step smoothing puts a rate between 2000 and 4000 steps/s at level 2: four interrupt callbacks per step period, and only one in four carries an X step. The core counts a step one interrupt callback ahead of the pulse start that outputs it, so a reset leaves a pending step only when its idle lands on a callback that carries one, one run in four at F600. On the null sink the shipped backlog is empty by the time the reset runs and the residue is zero, so that pending step is all the position check can see, and the check is the harness's only proof of the driver's hand-over of the step at the idle and of the read-back correction. At F3000 the move cruises at 10667 steps/s, above the 8000 steps/s cutoff of level 0, where every callback carries a step and every reset owes one. The ^X goes out 0.5 s after the move reports Run and lands near 56 mm of the 120, inside the move. Proof: python3 -m py_compile and pyflakes 4.0.3 are clean on scripts/bench/laser_lifecycle_test.py. Against the null-sink build of the grblHAL-glowforge default branch head, configured as its CI configures it (-DGFMCODE_WAIT_S=5.0), rule 17 passes 10 runs in 10 and the harness passes whole. Two scratch mutants of that tree's driver.c, each built the same way: (a) readback_position keeps sys.position as the core counted it, with the position_lost handling kept; (b) stepperGoIdle hands the engine no pending step, the step and direction bits passed to gf_stream_go_idle forced to 0. With this change each fails rule 17 in 5 runs of 5, every time on the position check with MPos one step past the stream (17104.0 steps against 17103 for (a), 17197.0 against 17196 for (b), in their first runs). With the parent's F600 the same mutants pass rule 17 15 runs in 20 (a) and 14 runs in 20 (b). The harness runs in grblHAL-glowforge CI, step "Armed-window lifecycle" (python3 forgefirm/scripts/bench/laser_lifecycle_test.py build/grblHAL_glowforge), from the head of this repository's default branch. Acceptance: none. scripts/bench/ is outside every covers map.
OpenGlow / ForgeFIRM firmware for Glowforge
BETA
ForgeFIRM is in beta. Every release below 0.1.0 is a beta release. It's stable, but you may still hit the occasional bug, 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.
Glowforge is a trademark of Glowforge, Inc. This project is not affiliated with, authorized by, or endorsed by Glowforge, Inc.