Map the P-series model codes to the right printers

C11 is the P1P, C12 the P1S, C13 the X1E and N7 the P2S, as the virtual
printer and a real P1P 3MF already say. The frontend map had them shifted,
so discovery pre-filled a P1S as a P1P and an X1E as a P2S. The backend
map read C11/C12 as X1C/X1 and lacked N7, the firmware check sent C13 to
the P2S line, and the capability lists never matched BL-P001 because
their lookup strips the dash.

-----

Post work PR #3134
This commit is contained in:
maziggy
2026-09-29 16:43:04 +02:00
parent 2b6dbe5ae5
commit ad3b5f1982
14 changed files with 224 additions and 104 deletions
+9 -4
View File
@@ -13,17 +13,22 @@ export function mapModelCode(ssdpModel: string | null): string {
'BL-P001': 'X1C',
'BL-P002': 'X1',
'BL-P003': 'X1E',
'C13': 'X1E',
// X2 Series
'N6': 'X2D',
// A2 Series
'N9': 'A2L',
// P Series
'C11': 'P1S',
'C12': 'P1P',
'C13': 'P2S',
// P Series. A real P1P 3MF carries C11 next to "Bambu Lab P1P"; the
// backend's PRINTER_MODEL_ID_MAP and the virtual printer use the same codes.
'C11': 'P1P',
'C12': 'P1S',
'N7': 'P2S',
// A1 Series
'N2S': 'A1',
'N1': 'A1 Mini',
'A11': 'A1',
'A12': 'A1 Mini',
'A04': 'A1 Mini',
// Direct matches
'X1C': 'X1C',
'X1': 'X1',