Add CLI option to disable safety parameter clamping (cli_safe_params) #6969
+9
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new configuration option cli_safe_params (default: true) which controls whether the CLI applies built-in safety limits to machine parameters such as acceleration.
Motivation:
Power users may want to apply custom values beyond the default safety limits (e.g., machine_max_acceleration_x = 12000) for experimental or performance-driven use cases.
Until now, the CLI forcibly clamped such values (e.g., to 6000) even if they were explicitly set in machine.json.
What this adds:
• New config entry cli_safe_params (type: bool)
• When set to false, the CLI will skip the safety check and use the values defined in config files as-is.
• Default behavior remains unchanged to protect less experienced users.
Example usage:
BambuStudio --cli_safe_params=false --load machine.json --load process.json --export_gcode