I’m sorry I don’t have answer for you. I just want to rant a bit.
TLDR;
This is one big reason I don’t like BS apart from the bambu connect.
Pressure Advance (or factor K as bbl calls it) values stored in the “calibration table” which, I think, links to filament IDs and some how those calibration values automatically apply to a print job that uses those filaments. I remember I had to go to device monitor and change those PA values manually for each AMS slot before each every frigging print and some how those PA values kept popping back to default values. I really don’t know where those PA values are stored, BS on PC or SD card on P1S. But since it kept switching back to default PA values, I was really pissed and frustrated.
Somehow I had the impression that BS didn’t apply PA value to the gcode but only after sending to the cloud, and gcode sent back from the cloud had PA applied. For an example like this, I make change to PA of AMS slot 1 (BBL PLA basic) using BS then I use bambu handy to print something from makerworld using same AMS slot 1. In order to print correctly, the modified value must be applied yeah? So it must be stored in the printer or at least on the cloud then slices by the cloud and send directly to the printer with modified PA applied to G-code.
If modified PA values stored in the printer then PA could be applied on the fly but I doubt ESP32, the brain of P1S, have the grunt to do this.
I understand most of the time default PA value of a given filament type is very good or almost spot on, but that is, you are using bbl filaments. I don’t use BBL filament and the filaments I’ve been using is quite very much off compare to BBL filament profiles or generic profiles.
I had started using orca in parallel with BS because of where PA is set in BS: device monitor → AMS instead of inside filament profile. Then the bambu connect happened on X1C. I knew sooner or later P1S would follow so I gave up on BS totally and used orca only.
Since I made the switch to orca slicer, I never look back.
I really can’t suggest you to make the swich to orca, as for now, orca + bb connect is still a hot mess and it won’t be solved. Orca team said they won’t touch bb connect. If you stick with orca, it means you are giving up on new firmware updates (stay at 1.07 forever), turn on LAN mode, and you won’t be able to use AMS2 or AMS HT. That also means no more bambu handy, no more cloud printing, no more camera view over cloud.