-
-
Notifications
You must be signed in to change notification settings - Fork 2
Limitations
The profiles control the machine sequence before and after a print. They do not control every factor that affects the finished result.
This page explains the main interpretation limits without changing the normal installation or printing workflow.
S, L-Lite, L, and XL describe relative sequence length and preparation style.
They are not quality scores.
- S minimizes preparation.
- L-Lite reduces purge.
- L balances preparation and time.
- XL uses the most extensive sequence.
The most appropriate profile depends on the print and the user’s preferred balance.
Profile runtime changes with:
- current printer temperature;
- whether adaptive probing runs;
- material loading and unloading;
- the selected profile.
For that reason, the documentation uses relative terms such as shortest, balanced, and longest rather than one fixed time.
A fixed purge sequence cannot produce the same clearing result for every color and material transition.
S and L-Lite use less purge. L and XL use more. Transition-specific flush settings in the slicer remain useful when changing between strongly contrasting materials or colors.
L-Lite, L, and XL contain the adaptive probing block, but the slicer and firmware determine whether the block is entered for a particular job.
The custom script does not calculate a separate numerical mesh-validity score.
S omits the new probing request by design.
The start profile contributes heating, probing, compensation, nozzle cleaning, and priming.
The first layer also reflects the ordinary printing conditions managed elsewhere: build-surface preparation, filament settings, printer calibration, and the sliced model.
P1S-GCODE is an alternative machine sequence rather than a line-for-line revision of the stock script.
The stock reference includes operations that the custom profiles reorganize or omit, while the custom profiles provide selectable preparation and cleanup levels.
This is why the repository keeps both stock and custom files available for comparison.
Several commands are specific to the Bambu firmware, and the scripts also use slicer-provided variables.
A future software update can change how a command or condition is interpreted. The project’s validation date and source files provide the reference point for the documented behavior.
A modified script represents a local variant.
Its behavior can still be compared easily by keeping the original project preset alongside it.
P1S-GCODE
Start here
Understand the profiles
Help