viewit/KX-Bridge-Release
9
13
Fork 6
Code Issues 4 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

All filaments syncing as generic #38

New Issue
Closed
opened 2026-05-31 08:28:35 +02:00 by gangoke · 11 comments
gangoke commented 2026-05-31 08:28:35 +02:00
Contributor
Copy Link

Slot 4 set as SUNLU PLA+ 2.0 on bridge
image.png

Syncs as Generic PLA
image.png

SUNLU PLA+ 2.0 is availble in Orca
image.png

Slot 4 set as SUNLU PLA+ 2.0 on bridge <img width="257" alt="image.png" src="attachments/acc8d1b2-60f0-4bac-a59d-038ee34a72eb"> Syncs as Generic PLA <img width="428" alt="image.png" src="attachments/75be895e-7d16-4bef-a3ef-a2511b18962d"> SUNLU PLA+ 2.0 is availble in Orca <img width="380" alt="image.png" src="attachments/db68a204-ab64-40bd-9225-e2bc3d59d5f0">
image.png
20 KiB
image.png
20 KiB
image.png
34 KiB
harrygeier commented 2026-05-31 09:04:10 +02:00
Copy Link

Afaik you need to install teh neweer build of ORCA KX to have it working

Afaik you need to install teh neweer build of ORCA KX to have it working
viewit added the
known-issue
 label 2026-05-31 10:03:25 +02:00
gangoke commented 2026-05-31 10:06:35 +02:00
Author
Contributor
Copy Link

Afaik you need to install teh neweer build of ORCA KX to have it working

I'm using latest OrcaSlicer-KX v2.4.0-alpha-kx1

> Afaik you need to install teh neweer build of ORCA KX to have it working I'm using latest OrcaSlicer-KX v2.4.0-alpha-kx1
viewit commented 2026-05-31 20:28:23 +02:00
Owner
Copy Link

Status update for v0.9.18:

The bridge side is done — the AMS payload going to OrcaSlicer now carries filament_vendor, filament_name, preset, filament_id, tray_info_idx and tray_sub_brands per slot. You can verify with:

curl -s 'http://<bridge>:7125/server/database/item?namespace=lane_data&key=lanes'

For an overridden slot the response should show filament_vendor=SUNLU, filament_name=SUNLU PLA+ 2.0, etc.

Why it still syncs as Generic in OrcaSlicer-KX v2.4.0-alpha-kx1: the receive-side patch in MoonrakerPrinterAgent.cpp is not in that build yet. Upstream Orca ignores the new fields and falls back to filament_id_by_type(tray.tray_type), which returns the first visible PLA preset alphabetically — that is what you see.

A small additive patch (~20 lines) for that exists locally: it reads filament_id from the lane JSON directly, falls back to a preset-name lookup via find_preset(), falls back to the existing type-based mapping. The bridge already sends both fields, so once that patch is in OrcaSlicer-KX the round-trip works without further config.

Next step is to bake the patch into a fresh OrcaSlicer-KX-v2.4.0-alpha-kx2 AppImage. Leaving this issue open until that build is out.

Status update for v0.9.18: The bridge side is done — the AMS payload going to OrcaSlicer now carries `filament_vendor`, `filament_name`, `preset`, `filament_id`, `tray_info_idx` and `tray_sub_brands` per slot. You can verify with: ``` curl -s 'http://<bridge>:7125/server/database/item?namespace=lane_data&key=lanes' ``` For an overridden slot the response should show `filament_vendor=SUNLU`, `filament_name=SUNLU PLA+ 2.0`, etc. **Why it still syncs as Generic in OrcaSlicer-KX v2.4.0-alpha-kx1:** the receive-side patch in `MoonrakerPrinterAgent.cpp` is not in that build yet. Upstream Orca ignores the new fields and falls back to `filament_id_by_type(tray.tray_type)`, which returns the first visible PLA preset alphabetically — that is what you see. A small additive patch (~20 lines) for that exists locally: it reads `filament_id` from the lane JSON directly, falls back to a `preset`-name lookup via `find_preset()`, falls back to the existing type-based mapping. The bridge already sends both fields, so once that patch is in OrcaSlicer-KX the round-trip works without further config. Next step is to bake the patch into a fresh `OrcaSlicer-KX-v2.4.0-alpha-kx2` AppImage. Leaving this issue open until that build is out.
gangoke commented 2026-06-03 07:31:48 +02:00
Author
Contributor
Copy Link

Tested 0.9.19 with my own build of OrcaSlicer v2.4.0-alpha with PRs #13372, #13719, #13315
Properlly syncs filament profiles, including custom imported profile.
Recommend closing when updated OrcaSlier-KX is released

Tested 0.9.19 with my own build of OrcaSlicer v2.4.0-alpha with PRs #13372, #13719, #13315 Properlly syncs filament profiles, including custom imported profile. Recommend closing when updated [OrcaSlier-KX](https://gitea.it-drui.de/viewit/OrcaSlicer-KX) is released
viewit commented 2026-06-04 20:10:59 +02:00
Owner
Copy Link

please test hot fix of kx bridge and orca kx2 in repo .

please test hot fix of kx bridge and orca kx2 in repo .
Alex_M commented 2026-06-05 10:37:18 +02:00
Copy Link

Latest OrcaSlicer-KX v2.4.0-alpha-kx2 and KX-Bridge v0.9.19.1, still Generic PLA or PETG for me.

{1BA002A1-62A6-4C19-A4B7-A347215B2B60}.png {0E5B9C0B-70CF-45C4-B640-B2B5D8F81E49}.png {B799C63B-8256-4F86-9194-1004E882BDBC}.png

The database looks correct:

{"result": {"namespace": "lane_data", "key": "lanes", "value": {"ams": [{"id": "0", "info": "0002", "tray": [{"id": "0", "tag_uid": "0000000000000000", "tray_info_idx": "OGFL03", "tray_type": "PLA", "tray_color": "DBC194FF", "tray_sub_brands": "eSUN", "name": "eSUN PLA+", "vendor_name": "eSUN", "filament_id": "OGFL03", "filament_vendor": "eSUN", "filament_name": "eSUN PLA+", "preset": "eSUN PLA+"},...

I also noticed that updating KX-Bridge from GUI does not update the program properly in docker container, the slot editing screen was left behind in version. To fix this I had to update the entire container.

Latest OrcaSlicer-KX v2.4.0-alpha-kx2 and KX-Bridge v0.9.19.1, still Generic PLA or PETG for me. <img width="383" alt="{1BA002A1-62A6-4C19-A4B7-A347215B2B60}.png" src="attachments/8571349a-e99d-4916-a916-989a0b405ad6"> <img width="270" alt="{0E5B9C0B-70CF-45C4-B640-B2B5D8F81E49}.png" src="attachments/80592725-3ea4-4d30-91e6-07c98e533498"> <img width="281" alt="{B799C63B-8256-4F86-9194-1004E882BDBC}.png" src="attachments/12838e8e-a06f-4d93-9324-7fdc82ee2718"> The database looks correct: {"result": {"namespace": "lane_data", "key": "lanes", "value": {"ams": [{"id": "0", "info": "0002", "tray": [{"id": "0", "tag_uid": "0000000000000000", "tray_info_idx": "OGFL03", "tray_type": "PLA", "tray_color": "DBC194FF", "tray_sub_brands": "eSUN", "name": "eSUN PLA+", "vendor_name": "eSUN", "filament_id": "OGFL03", "filament_vendor": "eSUN", "filament_name": "eSUN PLA+", "preset": "eSUN PLA+"},... I also noticed that updating KX-Bridge from GUI does not update the program properly in docker container, the slot editing screen was left behind in version. To fix this I had to update the entire container.
{1BA002A1-62A6-4C19-A4B7-A347215B2B60}.png
56 KiB
{0E5B9C0B-70CF-45C4-B640-B2B5D8F81E49}.png
22 KiB
{B799C63B-8256-4F86-9194-1004E882BDBC}.png
28 KiB
gangoke commented 2026-06-05 10:53:25 +02:00
Author
Contributor
Copy Link

0.9.19.1 and kx2 is still syncing as Generic, Must be issue with KX2 build cause it's working in my OrcaSlicer v2.4.0-alpha + PRs #13372, #13719, #13315 build is syncing correctly.

image.png
0.9.19.1 and kx2 is still syncing as Generic, Must be issue with KX2 build cause it's working in my OrcaSlicer v2.4.0-alpha + PRs #13372, #13719, #13315 build is syncing correctly. <img width="925" alt="image.png" src="attachments/fc1ded70-f120-4077-a25a-737e07d21e15">
image.png
81 KiB
viewit commented 2026-06-06 21:58:41 +02:00
Owner
Copy Link

0.9.19.1 and kx2 is still syncing as Generic, Must be issue with KX2 build cause it's working in my OrcaSlicer v2.4.0-alpha + PRs #13372, #13719, #13315 build is syncing correctly.

image.png

I took a quick look at your log and the problem. I'm surprised by the version listed in Orca. The current version looks like this in the "About" dialog:

> 0.9.19.1 and kx2 is still syncing as Generic, Must be issue with KX2 build cause it's working in my OrcaSlicer v2.4.0-alpha + PRs #13372, #13719, #13315 build is syncing correctly. > > <img width="925" alt="image.png" src="attachments/fc1ded70-f120-4077-a25a-737e07d21e15"> I took a quick look at your log and the problem. I'm surprised by the version listed in Orca. The current version looks like this in the "About" dialog:
orca version.png
58 KiB
orca version.png
viewit commented 2026-06-06 22:17:47 +02:00
Owner
Copy Link

Thanks for the report!

The issue has two causes:

  1. Wrong Windows build in the release: The Windows ZIP in v2.4.0-alpha-kx2 unfortunately contained the old dev build (2.4.0-dev) without the filament sync fixes — the build agent reused a cached old checkout. We have identified this and started a clean rebuild.

  2. Missing entries in orca_filaments.json: SUNLU PLA+ 2.0 may not be in the bridge filament list yet, or the name differs from the OrcaSlicer preset name.
    nWe will update this issue once the new release is available.

Thanks for the report! The issue has two causes: 1. **Wrong Windows build in the release**: The Windows ZIP in `v2.4.0-alpha-kx2` unfortunately contained the old dev build (`2.4.0-dev`) without the filament sync fixes — the build agent reused a cached old checkout. We have identified this and started a clean rebuild. 2. **Missing entries in `orca_filaments.json`**: SUNLU PLA+ 2.0 may not be in the bridge filament list yet, or the name differs from the OrcaSlicer preset name. nWe will update this issue once the new release is available.
viewit commented 2026-06-06 23:32:40 +02:00
Owner
Copy Link

Update: The Windows build has been fixed and the release has been updated.

The previous Windows ZIP in v2.4.0-alpha-kx2 contained the old dev build — this has now been replaced with a correct build that includes all filament sync fixes.

Please re-download OrcaSlicer-Windows-x64.zip from the release page.

Note: The SUNLU PLA+ 2.0 matching issue may still require an update to orca_filaments.json in the bridge — this is being worked on separately.

**Update:** The Windows build has been fixed and the release has been updated. The previous Windows ZIP in `v2.4.0-alpha-kx2` contained the old dev build — this has now been replaced with a correct build that includes all filament sync fixes. Please re-download `OrcaSlicer-Windows-x64.zip` from the [release page](https://gitea.it-drui.de/viewit/OrcaSlicer-KX/releases/tag/v2.4.0-alpha-kx2). Note: The SUNLU PLA+ 2.0 matching issue may still require an update to `orca_filaments.json` in the bridge — this is being worked on separately.
gangoke commented 2026-06-07 00:07:04 +02:00
Author
Contributor
Copy Link

Confirmed your updated zip is now the real alpha build and is syncing filament. Reccomend creating a new gitea release as kx2.1. Others might check for an update but wont check to see the updated zip.

Also, SUNLU PLA+ 2.0 is already in the bridge. No changes needed there

Keep up the great work!

image.png image.png
Confirmed your updated zip is now the real alpha build and is syncing filament. Reccomend creating a new gitea release as kx2.1. Others might check for an update but wont check to see the updated zip. Also, SUNLU PLA+ 2.0 is already in the bridge. No changes needed there Keep up the great work! <img width="1164" alt="image.png" src="attachments/f4da9017-6538-4db1-9c71-4f1a7804e6aa"> <img width="234" alt="image.png" src="attachments/f1d521be-62b3-4dc4-992a-be763fa8518e">
image.png
76 KiB
image.png
15 KiB
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
known-issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
viewit
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#38
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?