Something in my klicky macros is creating a MCU unable to connect issue.

[bcharle10]

Trying to get Klicky installed and working, but have run into an issue that has had me stuck and scratching my head for several days and I am not sure what to try next. Not sure if I have a setting wrong that I am unaware of? Some weird conflict with my hardware?

I have a working Mercury one printer with SKR Mini e3 V2.0 board until I imported the Klicky macros. Klicky Variables, Macros, Probe, bed mesh calibrate. After several different USB cables and a complete delete and re-install of Klipper, Moonraker, Mainsail, and reflashing the printer, the printer works again but ONLY if I comment out [include klicky_probe.cfg] or [include klicky_macros.cfg] inside klicky_probe.cfg.

[include klicky_macros] = MCU unable to connect error -> Klippy (7).log

[include klicky_macros] = working printer -> Klippy (6).log

Any suggestions?

klippy (7).log klippy (6).log

[jlas1]

well, to diagnose klipper issues, check if you have /dev/serial/by-id/usb-Klipper_stm32f103xe_34FFD8054D42373923560243-if00 when you try to include klicky macros. It needs to be there, klipper sometimes does not find it, then it does not start, but that's possibly a operating system issue, not a klipper one.

[bcharle10]

Thanks for the quick respond. I am not quite sure what you mean by check if I have /dev/serial/by-id/usb-Klipper_stm32f103xe_34FFD8054D42373923560243-if00. It is there when I check in kiauh, and also when I run "ls /dev/serial/by-id/ *".

So I tried a few more things last night, and realized that if I start up mainsail with the printer powered on then power cycle my printer (manually power off then on), klipper connects automatically and works fine. But connecting at mainsail startup, Restart, and Firmware_Restart options do not work like they used to. It just seems strange that the klicky macros trigger this odd behavior. Is there a size limit for klipper config files that could be messing with the connection? Are some setups not able to process nested config files?

At least I am back up and printing, and working on finishing my klicky setup.

[bcharle10]

There must be something in the Linux MX laptop that I am using that was causing this strange behavior. I picked up a raspberry pi 2 and after getting it set up, I have had none of the original firmware restarting issues.