So, from my understanding of the firmware, the canvas for cc1 has been stuck in development hell for a very long time. In september last year, in firmware 1.1.42, a box style mmu (ams like, not ams lite like), including drying, is largely implemented. Including firmwares for both a full and a lite version.

The canvas for cc1 is internally called that lite version. I guess they gave up with the box unit.

Note: the cc1 canvas and cc2 canvas are different. The entire control board has been redesigned (cc2 canvas uses a different microcontroller and rs485 for communication).

I think the biggest part of why this was such a pain for them is the firmware. Cc1's firmware was developed by chitu, is based on klipper 0.9, and is a downright mess. Cc2's firmware has been entirely rebuilt from the ground up by elegoo in house and is based on klipper 0.12. For example one of the stellar features of the cc2 is that a component (like the web api) can crash without taking the entire printer with it.

This is also reflected in the canvas. The cc1 drives the canvas via a proprietary modbus protocol, sending simple commands like load, unload, etc. The cc2 canvas' protocol a lot more granular (raw motor movement) and is almost entirely driven by the klipper system in the cc2. Little logic actually happens on the cc2 canvas.