Add an Dashboard Panel for ACE Pro

[DerDoubleD]

Requested feature:

View ACE Pro temperature
ACE Pro filament management
ACE Pro configuration
Start drying process

Solves the following problem:

Very Nice to have!
You no longer need the Next-Slicer

Additional information:

**Get information about the box**
curl -X POST -H "Content-Type: application/json" -d '{}' http://192.168.xxx.xxx:7125/printer/filament_hub/info

**Get values about the box**
curl -X POST -H "Content-Type: application/json" -d '{}' http://192.168.xxx.xxx:7125/printer/objects/query?filament_hub

**Get information on consumables**
curl -X POST -H "Content-Type: application/json" -d '{"id": 0, "index": 0}' http://192.168.xxx.xxx:7125/printer/filament_hub/filament_info
curl -X POST -H "Content-Type: application/json" -d '{"id": 0, "index": 1}' http://192.168.xxx.xxx:7125/printer/filament_hub/filament_info
curl -X POST -H "Content-Type: application/json" -d '{"id": 0, "index": 2}' http://192.168.xxx.xxx:7125/printer/filament_hub/filament_info
curl -X POST -H "Content-Type: application/json" -d '{"id": 0, "index": 3}' http://192.168.xxx.xxx:7125/printer/filament_hub/filament_info

**Turn on drying-function**
curl -X POST -H "Content-Type: application/json" -d '{"id": 0, "temp": 60, "fan_speed": 50.0, "duration": 2}' http://192.168.xxx.xxx:7125/printer/filament_hub/start_drying

**Stop drying function**
curl -X POST -H "Content-Type: application/json" -d '{"id": 0}' http://192.168.xxx.xxx:7125/printer/filament_hub/stop_drying

**Get Feed box configuration**
curl -X POST -H "Content-Type: application/json" -d '{}' http://192.168.xxx.xxx:7125/printer/filament_hub/get_config

**Set Feed box configuration**
curl -X POST -H "Content-Type: application/json" -d '{"auto_refill": 0, "flush_multiplier": 0.5, "flush_multiplier_editable": 0.9, "flush_volume_max": 801, "flush_volume_min": 105, "runout_detect": 1}' http://192.168.xxx.xxx:7125/printer/filament_hub/set_config

[meteyou]

hey! thx for your request, but something looks wrong to the urls. Normally Moonraker (the port 7125 is Moonraker) only have /printer/query and /printer/list urls. Do you have a link from the moonraker plugin you need for an ACE Pro?

[DerDoubleD]

@meteyou
Thanks for your reply!

I'm using it on my Kobra 3 with ACE Pro Rinkhals. => https://github.com/jbatonnet/Rinkhals
I've tested all the links and they work. Everything is documented here. => https://github.com/ANYCUBIC-3D/Kobra3/blob/91d9771204b00242668a02586cf317a58a1aa26f/klipper-go/docs/N033%E6%96%99%E7%9B%92%E9%80%9A%E4%BF%A1%E5%8D%8F%E8%AE%AE.md

Do you see any chance of integrating it?

To avoid confusion, the screenshot in the first post is from the Next Slicer.

Thank you and best regards.

[meteyou]

@DerDoubleD thx for the links! i checked the anycubic3d/kobra3 and the rinkhals repo and it looks like a complete different klipper version on this printer (klipper rewrite in go) and to install this, I would need this printer (or at least the SBC from this printer).

But to be honest, this is very far away from generic klipper, so I dont think i will implement this, but i will let this FR open and maybe a user from this printer can implement this and make a PR.

Just as an information for the contribute, who want to implement this, pls double check if you can also use the websocket, to send these commands instead of the http requests.

[swilsonnc]

@meteyou I have a different driver (https://github.com/agrloki/ValgACE) for the Ace Pro running on my rooted K1 Max. The mmu connection is basically just a serial connection and uses gcode commands to get and send info. The Extruder panel in mainsail does show the 4 available spools as T0, T1, T2, T3 while using this driver. The driver includes a separate web-interface that uses moonraker websocket to query the info that gcode macros pull from the MMU. I don't think it would be impossible but I would really not have a clue where to start (I'll research it) so this info might help the next person.

[meteyou]

@swilsonnc Thanks for the link!

After reviewing this, I have to decline the integration for now. The ValgACE driver is a community project and not an official driver from Anycubic. While it looks like a solid project, we generally don't integrate support for community-maintained drivers directly into Mainsail.

Some reasons for this:

• We'd need to maintain compatibility as the driver evolves
• Users would expect us to support issues that might be driver-specific

We prefer to wait for official manufacturer APIs/drivers when possible. So if Anycubic releases an official API/driver, we'd be happy to reconsider this feature request.

Thanks for understanding!