KCM Config issue (Co Print Klipper Colour Module)

[MCBriers]

Basic Information:

Printer Model: Ender 3 V3 Plus with Co Print KCM
[KCM Configs.zip|attachment]
MCU / Printerboard: Creality (Stock)
Host / SBC Creality (Stock)
(upload://tJ1ZT3aUqzFhB6QOzKvSKy2Z6g6.zip) (637.6 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

I have just installed the KCM hardware, but while attempting to configure the printer to the new status, I have the following error:

{“code”: “key341”, “msg”: “Section ‘servo cp1’ is not a valid config section\n\nOnce the underlying issue is corrected, use the "RESTART"\ncommand to reload the config and restart the host software.\nPrinter is halted\n”, “values”: [“servo cp1”]}

The [servo cp1] definition is in the chroma_head.cfg file, and is named in the printer.cfg as [include chroma_head.cfg].

The configs are the supplied configs from Co Print on their Github, and seem to work fine in their instruction Youtube video.

I am aware that this is a Co Print support issue, I will greatly appreciate it if someone here can assist me though. It probably is an ID10t error, but I am so new to Klipper I can hardly spell it correctly.

Thanks for helping an old man out

MC

[EddyMI3D]

Hello @MCBriers !

@MCBriers

(upload://tJ1ZT3aUqzFhB6QOzKvSKy2Z6g6.zip) (637.6 KB)

Please try again. Did not work.

[MCBriers]

KCM Configs.zip (637.6 KB)

Here we go, sorry about that.

[flowerysong]

Git version: '09faed31-dirty'

This is Creality’s modified version of Klipper. Support requests should be addressed to Creality, not the Klipper community.

This is also discussed in an open issue in Co Print’s GitHub repo. Section 'servo cp1' is not a valid config section · Issue #7 · coprint/configs · GitHub

[MCBriers]

Thank you very much! And I know support is the domain of the vendor, but the community is orders of magnitudes faster, cleverer an less hesitant to call a spade a spade!

Issue is resolved now, I will crawl back into my hole