Calibration Features - PA Pattern #1040

New Issue

MrUnknownDE · 2026-04-05T16:43:34+02:00

MrUnknownDE commented

2026-04-05 16:43:34 +02:00

Originally created by @BenBlake79 on 1/18/2026

Is there an existing issue for this feature request?

I have searched the existing issues

Hi, first of all - thank you for the adaptive pressure advance feature, I was waiting for that for a long time already - it is a huge leap forward. Maybe I've got a few Ideas to further improve on it.
I (X1C) just migrated from Bambu Studio a few weeks ago and am still getting used to OS but like it already as though I am still migrating an reoptimising my profiles so I only scratched the surface so far.
1.1 I use the PA Pattern for calibration of adaptive PA and it is kind of hard to find exactly the best corner and best filling level as the 1st layer is the same colour as the calibration layers and after a few seconds wished for a color contast between the bottom and the calibration layers. Why do you use three calibration layers? Is there an issue if you used only one?
1.2

These are the values für a PLA+-calibration. As you can see the k-values change more for smaller values of speed and acceleration so imho the best result would be accieved if the s/a-values for calibration are distributed logaritmically equidistantly (same factors between values) with a small (20-30% of factor?) leftover for extrapolation to the desired peak value. 1.3 Because of the pretty large range of values I made an LO-spreadsheet for a two-pass-calibration, where the 1st run finds a range for each s/a-combination to make a second run with a narrower range to find exact values and put them together so it can be made with as few prints as possible. I guess this could be automated in the slicer as now I am forced to pack the values in a way that is not optimal as in the OS-calibration I only can make groups that share the same range. I guess this could make this great feature applicable for more users as the matter becomes pretty complex pretty quickly. My spreadsheet is in a very rough wip state, but if it helps I could refine it for your use (or the use of of the community, which would make an VBA-automation necessary) and my solution would still be awkward. Unfortunately I have almost no clue of c++, only a little Excel-VBA, but maybe I could provide you with an optimised algorithm for you to "translate"? 1.4 from what I heard and read there can be easy confusion about print speed, volumetric speed and acceleration, at least you always have to wrap your head around it to make no mistakes. 1.5 Question just out of interrest: Do you have any experience on how temperature (=>viscosity) influences pressure advance? Do you provide any further information on how the interpolation is made?

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

1.1 Add an option to print the PA pattern with two different colors (bottom layer/calibration layers) on multicolor printers for better contrast.
1.2 If you share my opinion in this point, than imho at least this should be described in the wiki - who is allowed to write there? The cherry on the icing would be an automatic distribution of the values: min/max speed and acceleration IN => calibration points OUT
1.3 Some way to combine patterns for the 2nd calibration run to use different k-ranges on every every pattern according to the 1st pass and thus printing two plates for the 1st calibration run and two for the 2nd for optimisation and it would save a little filament as well. And LO-spreadsheet for better understanding and maybe an algorithm could be provided by me.
1.4 better presentation in the input mask: Input print speed and show nozzle width and volumetric speed and other parameters as I think this would help to better understand what one's doing and avoid mistakes
1.5 If there's a significant infuence of temperature on preasure advance, is it possible to put it into the filament parameters in a simple way? This would avoid complex recalibration if a temperture change is necessary. If you have no data on this matter I could run tests but like it to do with 1.1 implemented.

Describe alternatives you've considered

As this is some sort of an optimisation matter I mentioned a few thoughts in the previous points - I would like to work together with you to maybe find better solutions and of course I am available if there are any questions.

Additional context

No response

*Originally created by @BenBlake79 on 1/18/2026* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? Hi, first of all - thank you for the adaptive pressure advance feature, I was waiting for that for a long time already - it is a huge leap forward. Maybe I've got a few Ideas to further improve on it. I (X1C) just migrated from Bambu Studio a few weeks ago and am still getting used to OS but like it already as though I am still migrating an reoptimising my profiles so I only scratched the surface so far. 1.1 I use the PA Pattern for calibration of adaptive PA and it is kind of hard to find exactly the best corner and best filling level as the 1st layer is the same colour as the calibration layers and after a few seconds wished for a color contast between the bottom and the calibration layers. Why do you use three calibration layers? Is there an issue if you used only one? 1.2 <img width="981" height="1148" alt="Image" src="https://github.com/user-attachments/assets/8428dec3-f1eb-4453-ba8b-9864545a7eaa" /> These are the values für a PLA+-calibration. As you can see the k-values change more for smaller values of speed and acceleration so imho the best result would be accieved if the s/a-values for calibration are distributed logaritmically equidistantly (same factors between values) with a small (20-30% of factor?) leftover for extrapolation to the desired peak value. 1.3 Because of the pretty large range of values I made an LO-spreadsheet for a two-pass-calibration, where the 1st run finds a range for each s/a-combination to make a second run with a narrower range to find exact values and put them together so it can be made with as few prints as possible. I guess this could be automated in the slicer as now I am forced to pack the values in a way that is not optimal as in the OS-calibration I only can make groups that share the same range. I guess this could make this great feature applicable for more users as the matter becomes pretty complex pretty quickly. My spreadsheet is in a very rough wip state, but if it helps I could refine it for your use (or the use of of the community, which would make an VBA-automation necessary) and my solution would still be awkward. Unfortunately I have almost no clue of c++, only a little Excel-VBA, but maybe I could provide you with an optimised algorithm for you to "translate"? 1.4 from what I heard and read there can be easy confusion about print speed, volumetric speed and acceleration, at least you always have to wrap your head around it to make no mistakes. 1.5 Question just out of interrest: Do you have any experience on how temperature (=>viscosity) influences pressure advance? Do you provide any further information on how the interpolation is made? ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like 1.1 Add an option to print the PA pattern with two different colors (bottom layer/calibration layers) on multicolor printers for better contrast. 1.2 If you share my opinion in this point, than imho at least this should be described in the wiki - who is allowed to write there? The cherry on the icing would be an automatic distribution of the values: min/max speed and acceleration IN => calibration points OUT 1.3 Some way to combine patterns for the 2nd calibration run to use different k-ranges on every every pattern according to the 1st pass and thus printing two plates for the 1st calibration run and two for the 2nd for optimisation and it would save a little filament as well. And LO-spreadsheet for better understanding and maybe an algorithm could be provided by me. 1.4 better presentation in the input mask: Input print speed and show nozzle width and volumetric speed and other parameters as I think this would help to better understand what one's doing and avoid mistakes 1.5 If there's a significant infuence of temperature on preasure advance, is it possible to put it into the filament parameters in a simple way? This would avoid complex recalibration if a temperture change is necessary. If you have no data on this matter I could run tests but like it to do with 1.1 implemented. ### Describe alternatives you've considered As this is some sort of an optimisation matter I mentioned a few thoughts in the previous points - I would like to work together with you to maybe find better solutions and of course I am available if there are any questions. ### Additional context _No response_

Sign in to join this conversation.

No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#1040