Re-printing from dashboard cache targets wrong/empty filament slot #84

New Issue

Alex_M · 2026-07-03T14:22:03+02:00

Alex_M commented

2026-07-03 14:22:03 +02:00

Description

When initiating a print retry/re-print directly from the KX-Bridge dashboard cache, the backend appears to reuse the cached filament slot mapping array from the previous job without re-validating the live physical ACE slot states. If a filament spool is removed or an intermediate slot becomes empty between the first print and the cached re-print, the slot indices shift, causing the printer to load from an empty/wrong slot.

Steps to Reproduce

Load filaments into Slot 1, Slot 2, and Slot 3 (Slot 4 empty). Properly sync them between the Bridge and OrcaSlicer.
Send a direct print from OrcaSlicer with the model assigned to Slot 3. The print starts and completes successfully using the correct spool.
During or right after the print, physically remove the filament from Slot 2 (leaving it empty).
Go to the KX-Bridge dashboard and click the Print button to print another copy of the same model directly from the Bridge cache.
The print starts, but the printer incorrectly attempts to load filament from Slot 2 (which is now empty) instead of Slot 3, causing a print pause/error.

Expected Behavior

When starting a print from the dashboard cache, the Bridge should re-validate the current live ACE slot configuration against the G-code demands (or trigger the Slot Mapper/validation gate) to ensure the index mapping adjusts to the newly emptied slot.

Actual Behavior

The Bridge reuses the old mapping index or shifts the array index dynamically based on the previous cache layout, leading the machine to target an empty physical slot (Slot 2).

Environment

KX-Bridge Version: 0.9.28-nightly13
OrcaSlicer Version: 2.4.1-kx1
Operating System: Windows 11
Installation: Docker

## Description When initiating a print retry/re-print directly from the KX-Bridge dashboard cache, the backend appears to reuse the cached filament slot mapping array from the previous job without re-validating the live physical ACE slot states. If a filament spool is removed or an intermediate slot becomes empty between the first print and the cached re-print, the slot indices shift, causing the printer to load from an empty/wrong slot. ## Steps to Reproduce 1. Load filaments into Slot 1, Slot 2, and Slot 3 (Slot 4 empty). Properly sync them between the Bridge and OrcaSlicer. 2. Send a direct print from OrcaSlicer with the model assigned to **Slot 3**. The print starts and completes successfully using the correct spool. 3. During or right after the print, physically remove the filament from **Slot 2** (leaving it empty). 4. Go to the KX-Bridge dashboard and click the **Print** button to print another copy of the same model directly from the Bridge cache. 5. The print starts, but the printer incorrectly attempts to load filament from **Slot 2** (which is now empty) instead of Slot 3, causing a print pause/error. ## Expected Behavior When starting a print from the dashboard cache, the Bridge should re-validate the current live ACE slot configuration against the G-code demands (or trigger the Slot Mapper/validation gate) to ensure the index mapping adjusts to the newly emptied slot. ## Actual Behavior The Bridge reuses the old mapping index or shifts the array index dynamically based on the previous cache layout, leading the machine to target an empty physical slot (Slot 2). ## Environment - KX-Bridge Version: 0.9.28-nightly13 - OrcaSlicer Version: 2.4.1-kx1 - Operating System: Windows 11 - Installation: Docker

Alex_M added the

bug

label 2026-07-03 14:22:03 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#84