viewit/KX-Bridge-Release
3
2
Fork 2
Code Issues 5 Pull Requests Actions Packages Projects Releases 25 Wiki Activity

OrcaSlicer filament sync (Sync from AMS) shows wrong or empty data #10

New Issue
Closed
opened 2026-04-29 13:26:11 +02:00 by viewit · 1 comment
viewit commented 2026-04-29 13:26:11 +02:00
Owner
Copy Link

The "Synchronize filament list from AMS" button in OrcaSlicer 2.3.2 does not correctly transfer filament data from the bridge.

Root cause: OrcaSlicer bug in build_ams_payload() — get_my_machine(dev_id) returns nullptr for non-Bambu Moonraker printers, so the filament data is never written to the internal DevFilaSystem.

Fix: OrcaSlicer PR #13372 — not yet merged.

Workaround: Assign filament slots manually in OrcaSlicer.

Reported by: u/Nerdinat0r

The "Synchronize filament list from AMS" button in OrcaSlicer 2.3.2 does not correctly transfer filament data from the bridge. **Root cause:** OrcaSlicer bug in `build_ams_payload()` — `get_my_machine(dev_id)` returns `nullptr` for non-Bambu Moonraker printers, so the filament data is never written to the internal `DevFilaSystem`. **Fix:** OrcaSlicer PR [#13372](https://github.com/OrcaSlicer/OrcaSlicer/pull/13372) — not yet merged. **Workaround:** Assign filament slots manually in OrcaSlicer. **Reported by:** u/Nerdinat0r
viewit added the
bug
known-issue
 labels 2026-04-29 13:26:11 +02:00
viewit commented 2026-04-29 14:48:15 +02:00
Author
Owner
Copy Link

The KX-Bridge side is implemented — the bridge responds to OrcaSlicer's filament sync request and returns AMS slot data in the correct BBL-AMS format.

However, the sync button currently does nothing visible in OrcaSlicer because of a bug in OrcaSlicer itself: the build_ams_payload() function calls get_my_machine(dev_id) which returns a null pointer for non-Bambu printers (Moonraker connections). This causes the sync dialog to never open.

A fix is pending in OrcaSlicer PR #13372. This issue will be resolved once that PR is merged into OrcaSlicer. No further action on the bridge side needed.

The KX-Bridge side is implemented — the bridge responds to OrcaSlicer's filament sync request and returns AMS slot data in the correct BBL-AMS format. However, the sync button currently does nothing visible in OrcaSlicer because of a bug in OrcaSlicer itself: the `build_ams_payload()` function calls `get_my_machine(dev_id)` which returns a null pointer for non-Bambu printers (Moonraker connections). This causes the sync dialog to never open. A fix is pending in OrcaSlicer PR #13372. This issue will be resolved once that PR is merged into OrcaSlicer. No further action on the bridge side needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
bug
documentation
duplicate
This issue or pull request already exists
enhancement
New feature
enhancement
help wanted
Need some help
invalid
Something is wrong
known-issue
question
More information is needed
wontfix
This won't be fixed
No Label
bug
known-issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
viewit
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#10
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?