My printer just threw this at me and now it keeps telling me anything I print will be “printed using spool colours”. Seems it’s had a falling out with the CFS and they’re not talking any more…anyone know how to fix? I’ve already tried turning it off and on again…
OK this was odd but I think I’ve fixed it. Had to go into “Device”, and there was a list of files. The last one had a comma in it, which apparently the printer or the software doesn’t like. Deleted that file from the list and CFS is available again.
I have not had this issue but my file listing shows files sent from CP6 have a comma in the spaces between words. Within the windows file system they just have spaces. So I guess CP6 is inserting them.
The files supplied by Creality all have underscores.
This is interesting and worthy of experimentation if you get issues with a print.
It may not be a comma specifically, but a si called “special character”, ie not A to Z or 0 to 9. Haven’t done any more testing but I did see at least one post with a similar problem. Can’t find it now…may have been in Reddit…
I have reasoned out that the commas come from the stl file loaded into the 3mf file.
The print file name is made up of stl name first then the saved 3mf name.
CP6 inserts a comma if there is a space in the windows stl name.
I replaced the spaces in the stl file to underscores and that populate thru to print file. i.e. no spaces
2 Likes
Jumping in this thread quick - I also just received the [2514] Unknown exception error code and thankfully I found this post. I thought it was first a problem with the CFS because I kept using the same slot, then I thought it was a problem with the file(s) I downloaded. But…based on the info in this post, I can confirm that, prior to sending it to printer, the gcode filename in Creality Print had a hasthag/pound symbol in the name, which seemed to be the culprit. Renaming it before sending fixed the problem…
Kudos to you guys for finding this obscure problem and hopefully this confirms that the gcode filename is the root cause…
This problem with special characters ‘#’ and ‘;’ has its roots in klipper. That was fixed in klipper last year: gcode: Improve handling of extended g-code commands with '*;#' charac… · Klipper3d/klipper@d45b9c9 · GitHub
That fix has not been ported to the Creality klipper version yet. I’ve asked Creality support when we can expect a more current klipper version in the Creality firmware but they could not tell me any date.