Legacy SteinWipe Motion Control For X1 Series & Bambu Studio (Discontinued)

First formally-named Core release; introduced Core 0.

- Established the SWMC naming and testing system. First release shipped under the [Month].[Day].[Version].[Year] format.
- New: reusable wipe macro architecture ({template_custom_gcode}). Every gcode section that needs a wipe calls one macro instead of duplicating scrub code. End G-code drops from 268 lines to 90; Pause drops from 94 to 68.
- First appearance of chute tapping in SWMC. Taps the chute door at end of startup purge to knock down stuck purge material.
- Sidestepping purges; shifts left-to-right for more uniform purge distribution.
- Work light purge cycles; toolhead light activates during purges so the chamber camera can see what's happening.
- PA test line moved over build plate QR code (safety).
- Completely rewritten material change code; 15-20% reduction in flushing volume.
- Improved first-layer scanning; stock routine was dragging purge into prints; Core 0 hijacks it for a clean scan.
- User offsets at template level; enter calibration values once, applied across all prints.
- New "Cool Plate" definitions; better startup sequences for cool plate users.
- First-layer travel optimization; reduces stringing carried onto the print.
- Full Orca 2.2.0 / BBS 1.10.1.50 support.

This is the ORIGINAL Core 0 beta release; the first formally-named Core under the new naming and testing system. Feb.15.1.2025 established the architecture that every later Core 0 and Core 1 release refines.

Most users will want the Feb.15.2.2025 stable release that shipped two months later. Feb.15.2 adds the ams_detour SteinSwitch, flips the fan cover alarm to ON by default, upgrades the Template Custom G-code to arc-based wipe moves, and fixes a batch of user-reported bugs from this beta cycle.

Feb.15.1 remains available for users who bought into this release during its beta window, for users who want the historical baseline, and for anyone tracing the project's development history. The release works; it just has known issues that the stable successor resolved.

If you're deciding which release to run, the stable is the recommended path. Full user manual for this beta release is linked in the Resources section above and includes the complete known issues list so you can decide with full information.

If you're on Feb.15.1 and wondering whether to upgrade, check the Feb.15.2 manual's "What's fixed" list against the issues you've encountered. If any match, upgrading is worth your time.