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

Bambu TPU for AMS not reconized #7934

Open
2 of 3 tasks
Scoutcreed opened this issue Jan 5, 2025 · 0 comments
Open
2 of 3 tasks

Bambu TPU for AMS not reconized #7934

Scoutcreed opened this issue Jan 5, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Scoutcreed
Copy link

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.2.0

Operating System (OS)

Windows

OS Version

Windows 11 pro

Additional system information

Processor AMD Ryzen 9 9900X 12-Core Processor 4.40 GHz
Installed RAM 64.0 GB (61.6 GB usable)
GPU: Zotac GeForce RTX 4080 Super
System type 64-bit operating system, x64-based processor

Printer

Bambu P1S with standard AMS

How to reproduce

  1. Load TPU for AMS
  2. Open Orca Slicer and have it resync AMS.

If you try Bambu studio or Orca 2.3.0 Developer version this will be fixed on power restart of printer.
However if Orca 2.2.0 is opened it breaks the view on all other versions.

Actual results

? shows up in the slot if TPU is loaded

Expected results

TPU for AMS should Appear in the slot

Project file & Debug log uploads

Project I was working on that had said issue.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

I was just trying to create a rubber foot on a support brace using a the Bambu TPU for AMS as the rubber foot in AMS slot 1 and Bambu's sparkle PLA in AMS slot 3. Something I tried but was unsuccessful was I took the profiles from the developer 2.3.0 version and uploaded specifically the files for the P1P into the Bambu Filament file in the 2.2.0 version. This failed probably because I didn't know what I was doing more than the files them self. This seems to be an easy fix if a new stable version is released, but I would recommend instead of having all of the additional functionality of 2.3.0, just to create a 2.2.1 version or something with all of these new filaments ported over.

@Scoutcreed Scoutcreed added the bug Something isn't working label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant