Latest Korba S1 firmware 2.5.3.8 and latest Rinkhals release 20250706_02 - ACE Pro is missing color information, can't start printing.

[Art531]

Describe the bug

Using latest S1 firmware and latest Rinkhals release found a bug - can't start any print (new or sliced earlier gcode) - printer gives an error "Failed to obtain matching color information, please check read and write permissions". And there is no any filament colors on the left side of ACE setup panel on a printer's screen (see attachments).

Printer setup

• Printer version - Kobra S1
• Firmware version - 2.5.3.8 (latest)
• Rinkhals version - 20250706_02 (latest)

Repro steps

Steps to reproduce the behavior:

1. Try to start printing via screen
2. Go to ACE filament settings
3. See that there is no any filament on the left panel to compare it in ACE

[C-Freeze]

I can second this issue. Brand new Rinkhals install, swapped over to OrcaSlicer's default profile, and I am unable to print via the screen. Purely conjecture as I haven't had a chance yet to look at G-Code files, but these seems to likely be more of an OrcaSlicer issue and not this project specifically.

[C-Freeze]

I should have just looked before replying. At the bottom of the G-Code output from NEXT you'll find a section that looks roughly something like this:

; ams_info = begin
; paint_info = [{"material_type":"PLA","paint_color":[33,39,33],"paint_index":0}]
; project_info = {"flush_multiplier":1.0,"flush_volumes_matrix":[0.0,518.0,317.0,429.0,190.0,0.0,273.0,264.0,155.0,523.0,0.0,424.0,165.0,417.0,249.0,0.0],"flush_volumes_vector":[140.0,140.0,140.0,140.0,140.0,140.0,140.0,140.0]}
; ams_info = end

; statistics = begin
; used_filament = 14.30
; print_time = 1h 58m 52s
; model_size = 140.67,171.63,3.00
; total_layers = 15
; statistics = end

This section is missing in the Orca Slicer outputs. Copying over just the AMS section was enough for the S1 to actually allow the print to happen from the touchscreen. This can probably be solved by changing the end print macro to include these comment, I haven't tried that yet.

Probably needs its own issue opened, but if we get a AMS "selector" in the Mainsail (or Fluidd) interface when starting a print via the WebUI or at least a tool to try and automatically fix files based of the information based on what Orca does provide that would be sick.