Here is my Device page, showing PLA in Slot 4 and TPU in the External. However, when I attempt to Sync, it won’t read in what is shown in Device page. This happens all the time. Thoughts to fix/resolve?
You sure? You didnt share a screenshot of your current palette, but Im guessing it goes: 1BlackPETG 2GreyPETG 3WhitePETG 4PinkPETG <<<< 5GreenPETG<<<<
which is why the row 1 in the UI looks as it does
It could be more clear, if the UI in row 2 also included the filament type of the AMS filament… but just click ok
The leftmost pic shows the “current palette” configuration (in the Devices) page.
the spools in order (which match the leftmost pic) are
PETG (black), PETG (grey), PETG (White), PLA (pink), TPU (green, external)
it never seems to pull in the PLA or TPU
I expect that whatever is set up in the AMS, on the Device page, will update the palette panel upon pressing “Sync Info” and then Synchronize Now.
If this does not do it, I wonder what the he77 the Synchonize Now button is for!
Hit “ok” on the dialog on your third screenshot. [overwriting, with the way you have it documented] Did it work? If not, take a screenshot of the resulting project pallette
it did not. Seems that you expect it to work just as I do, but it didn’t.
I’ve since completely uninstalled Bambu Studio, deleted all user presets etc. and started over, and it’s now pulling in the PLA and TPU per the Device page. As expected.
I’ve had this issue before, sometimes it works sometimes it doesn’t. Today it would not work NO MATTER WHAT. Had to take drastic measures.
Please let me know which printer and which AMS you’re using. There’s actually a very rare combination that causes synchronization issues. Then I could check it out on GitHub.
This primarily affects the H2 and AMS2 but extremely rarely. What’s your combination?
P1S with Original AMS
adding more characters here to meet the 25 character limit
Okay, I just checked on GitHub: Your specific error hasn’t been reported to the developers yet. While there are all kinds of synchronize errors, there isn’t anything that comes close to what you’re experiencing.
The only clue that comes even a tiny bit close is when users have cloud synchronization turned on but the connection to the cloud can’t be established. That sometimes causes the software to freeze up.
That’s a bit of a stretch, though - but hey, it takes less than two minutes to switch it over for a test. However, I’ll say this right away: I don’t think that’s the cause.
