#mcu 'mcu': Unable to connect

6 messages · Page 1 of 1 (latest)

lament sail
#

Keep getting mcu 'mcu': Unable to connect when I'm looking at Mainsail. Seems Klipper can't find the printer.

Ender 3 v2 running Klipper firmware with an Odroid C2 running Ubuntu command line. Used KIAUH to install Klipper, Moonraker, Mainsail and Crowsnest on the Odroid.

Had everything working with Octoprint, wanted to switch, so I saved my printer.cfg file using Visual Studio Code. I made sure to add [include mainsail.cfg] to the printer.cfg file.

I double checked the port the printer is connected to by running ls /dev/serial/by-id/*

Verified it was the same in printer.cfg:

[mcu]
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method: command

Posted klippy.log and a txt version of my printer.cfg below

Where did I mess up?

#

Apparently it doesn't want my .cfg file directly here so I'll conver it to text...

lament sail
#

Welp, I ended up fixing it by logging in via SSH, and running these commands to rebuild the firmware:

cd ~/klipper/

make menuconfig

I specified the settings at the top of the printer.cfg file with a little exta:

#

[*] Enable extra low-level configuration options
Micro-controller Architecture (STMicroelectronics STM32) --->
Processor model (STM32F103) --->
[ ] Only 10KiB of RAM (for rare stm32f103x6 variant)
[ ] Disable SWD at startup (for GigaDevice stm32f103 clones)
Bootloader offset (28KiB bootloader) --->
Clock Reference (8 MHz crystal) --->
Communication interface (Serial (on USART1 PA10/PA9)) --->
(115200) Baud rate for serial port
() GPIO pins to set at micro-controller startup