Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to handle post-processing scripts #1098

Closed
johnmbaughman opened this issue Jan 17, 2023 · 3 comments
Closed

Add ability to handle post-processing scripts #1098

johnmbaughman opened this issue Jan 17, 2023 · 3 comments
Assignees
Labels
feature New feature or request

Comments

@johnmbaughman
Copy link

johnmbaughman commented Jan 17, 2023

Is your feature request related to a problem? Please describe.
To enhance the output handling of a gcode file, the application needs a Post-processing script option similar to PrusaSlicer. This will help make tasks such as filament calibration with temperature and retraction towers easier, faster, and more consistent.

Describe the solution you'd like
As part of advanced or expert options, there needs to be an option to plug in a script handler that will modify the generated code file in place.

Describe alternatives you've considered
Handling the gcode file manually after slicing and exporting the gcode file.

Additional context
In PrusaSlicer this option is located here under the Print Settings tab.
image

@johnmbaughman johnmbaughman added the feature New feature or request label Jan 17, 2023
@lanewei120 lanewei120 self-assigned this Mar 2, 2023
@lanewei120
Copy link
Collaborator

could you give more details for how to use the postscripts to improve "filament calibration with temperature and retraction towers"

@johnmbaughman
Copy link
Author

johnmbaughman commented Mar 2, 2023

Some implementation of what PrusaSlicer does.

https://help.prusa3d.com/article/post-processing-scripts_283913

I currently have a couple of models that are dynamic in size depending on the settings used to generate them in OpenSCAD that are used for retraction and temperature calibration. I use a formatted string along with the layer number inserted during the slicing/exporting of the gcode file. This file is then passed into a .Net application that inserts necessary changes for the calibration (i.e. temperature or speed changes) based on the formatted string.

Being able to continue using this feature would make this process easier as I don't have to manually run the application after exporting the file.

I'm sure others have similar uses for this functionality as it allows some "non-standard" modification to the gcode to meet personal needs, that the slicer doesn't handle and probably shouldn't handle.

For reference, SoftFever has added this functionality in version 1.4.3: https://github.com/SoftFever/BambuStudio-SoftFever/releases/tag/v1.4.3

-John

@SaltWei
Copy link
Collaborator

SaltWei commented Apr 18, 2023

Has been included in v1.6 public beta

@SaltWei SaltWei closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants