Provide the included probe cfg as well, please.
Here it is.
klicky-macros.cfg (44.6 KB)
klicky-probe.cfg (720 Bytes)
klicky-screws-tilt-calculate.cfg (1.2 KB)
klicky-variables.cfg (6.4 KB)
and the rest of them
klicky-bed-mesh-calibrate.cfg (1.3 KB)
klicky-z-tilt-adjust.cfg (1.2 KB)
Ok, tried a brand new sd card, completely fresh install of both the CB1 and the Manta M5P, nothing klicky loaded, and went with the example config for a print_start macro and that gcode file from the klicky variables is still over riding my macro. I have no idea how. I have ordered a new CB1 to remove the one thats in there and put a new one in. Somehow, somewhere that gcode has buried itself onto a board and has locked out the ability to change the print_start macro. It’s like there is a virus on my printer that I cant get rid of. I have no idea what to do from here other than replace the entire manta and cb1.
klippy (11).log (248.7 KB)
printer cfg
printer (3).cfg (9.6 KB)
This voodoo will only affect your bank account but nothing else. We are talking about computers here and not about Ouija boards, so if you take the same approach as with your current CB1, you will end up with the exact same result.
But if you should suffer from too much money, I can provide you my PayPal address.
In these Klicky macros there is nothing that could override your PRINT_START macro.
Just to be on the very same page: Please provide the full path of your printer.cfg file, e.g. like /home/bla/blubb/printer.cfg
2 Likes
Ok, this looks good and I think I have found the issue:
You have stray blanks in your cfg and this messes up Klipper’s parsing.
1 Like
well holy sh!t, I just changed that and now its working. All of that over 1 space at a line. Well that was a learning experience. Thank you so much for your help.
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.