Skip to content

Conversation

ianalexis
Copy link
Contributor

@ianalexis ianalexis commented Aug 31, 2025

Description

Enable the possibility of loading more than one PA according to the nozzle, as it has a direct relationship.

imagen

Useful for avoiding multiple profiles just for nozzle changes, but also for new machines with tool changes that allow for nozzle changes while maintaining the material.

  • "Legacy” value with a single value and no nozzle, take that value as before.
  • Single value (e.g., 0.4,0.2), it is taken as legacy.
  • If there is a value without a incomplete value ("0.5," || ",0.2") is ignored.
  • If nozzle does not match the listed values:
    • 1 PA value = using that value
    • Multi PA values = linear interpolation

Nowdays Prusa do this by:

    "filament_start_gcode": [
        "M572 S{if nozzle_diameter[filament_extruder_id]==0.4}0.02
			{elsif nozzle_diameter[filament_extruder_id]==0.5}0.018
			{elsif nozzle_diameter[filament_extruder_id]==0.6}0.015
			{elsif nozzle_diameter[filament_extruder_id]==0.8}0.01
			{elsif nozzle_diameter[filament_extruder_id]==0.25}0.09
			{elsif nozzle_diameter[filament_extruder_id]==0.3}0.065
			{else}0{endif} ; Filament gcode\nM142 S40 ; set heatbreak target temp"
    ],

+240 Prusa profiles that could be converted into 41 profiles analyzed in a logarithmic table.
imagen

Fix

It also fix \n not being displayed for PA and APA unless they are written by the user:
Before

imagen

After

imagen

Adaptive Pressure Advance:
I just adapt when it takes the PA value but maybe we have to:

  • add the nozzle size to it as a value = Nozzle, PA, flow, acceleration
    • Using multiple APA models.
    • interpolate it's resulting values with a potential curve based in the PA.
  • use it as it is and do not adapt it

If this is merged

  • I will edit it if this PR is merged
  • Prusa profiles could be readapted to use this structure and no longer have the values in filament_start_gcode.

@ianalexis ianalexis force-pushed the multiple-pa branch 4 times, most recently from 3a5ca70 to 1346bd6 Compare September 3, 2025 15:58
@ianalexis ianalexis marked this pull request as ready for review September 3, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant