Skip to main content

Wired Connection Klipper Configuration

Notice
  • The STM32F072 needs to be flashed with firmware and connected to klipper; otherwise, the wired connection operation is not supported.

Start Compiling​

  • A host computer with the klipper service installed is required. Connect SSH via network
  • And the device should be well connected to the host computer.
  • Note: Please use a common host computer, such as Raspberry Pi, FLY Pi, etc. If it is a modified host computer (such as WiFi stick, Redmi, etc.), due to too many problems with this type of host computer, technical support cannot be provided for you.
Precautions
  • Please do not use the ROOT user.
  • Command to switch users
su fly
tip
  • 请确保上位机可以正常联网
  • 固件编译前需要使用SSH通过网络登录上位机
  • 请不要使用串口工具登录上位机

Klipper固件编译和配置页面操作说明​

tip

请确保键盘输入法为半角模式，即英文模式

  1. 键盘上键↑，下键↓，用于上下移动光标来选中菜单项
  2. 确认键Enter 或 空格键Space，用于勾选菜单或进入子菜单
  3. 退出键ESC，用于返回上一级菜单
  4. Q键，用于退出Klipper固件配置页面
  5. Y键，在退出Klipper固件配置页面时，如果有提示，则点击Y键保存配置文件
warning

如果配置页面选项比较少，请先勾选[ ] Enable extra low-level configuration options，用于显示部分隐藏选项

Below is the guide on how to compile the firmware:

  • After connecting to SSH, enter the command below and press Enter:

    cd ~/klipper && rm -rf ~/klipper/.config && rm -rf ~/klipper/out && make menuconfig

  • Where rm -rf ~/klipper/.config && rm -rf ~/klipper/out is to delete previous compilation data and firmware, and make menuconfig is for compiling the firmware. After execution, the following interface should appear:

  • Select Enable extra low-level configuration options and press Enter

  • Go into the menu Micro-controller Architecture and then select STMicroelectronics STM32 and press Enter

  • Go into the menu Processor model, select STM32F072 and press Enter

  • Select Bootloader offset, choose: (No bootloader)

  • Communication interface, choose: USB (on PA11/PA12)

  • Press the Q key, and "Save configuration" appears. Then press the Y key.

  • Now the configuration should be saved and you have exited to the command line interface.

  • Enter make -j4 to start compiling. It takes a bit of time.

  • If the following content is finally output, the compilation is successful.

    Linking out/klipper.elf
    Creating hex file out/klipper.bin

Enter the Burning Mode​

  • With the AirClick powered off, press the BOOT of the STM32 and connect the burning port of the STM32 to the host computer through the Type-C.

Confirm Whether to Enter the Burning Mode​

  • Ensure the host machine can connect to the internet normally.

  • Ensure the data cable connecting the lower-level machine to the host machine has data transmission capabilities.

  • After SSH connecting to the host machine, enter lsusb and press enter. One of the following three situations may occur:

    • Displays USB devices that have been recognized.
    • Prompts that there is no ls command, you can execute this command to install it: 
      sudo apt-get install usbutils
    • No error message, no other information (a system issue requires replacing the system).

  • If there is no reaction after entering lsusb, this is a system issue and cannot be resolved here; you need to replace a confirmed normal system.

  • If the information circled in the image below appears, you can proceed to the next step.

  • 0843:df11 belongs to the device you will use this time. Ignore the subsequent prompts as system issues may cause them to display incompletely or not at all.

  • If not, check whether the data cable is properly connected or if the motherboard has entered DFU.

Note

Proceed to the next step only if you have 0843:df11.

Burn the Firmware​

  1. Install the flashing tool
  • No need to install the flashing tool for the FLY GUI.
  • If you need to install it, please note: The GUI needs to be connected to the internet to install properly.
  • If you have already installed it, no need to install again.
sudo apt update
sudo apt install dfu-util -y
  1. Execute the following command to check if the connection is successful.
lsusb

  • If there is no DFU device, please try to re-enter flashing mode.

  • Due to system version issues, other names may be displayed. If 0483:df11 is shown, it indicates that the flashing mode has been entered.

  1. Flash the firmware
  • Execute the code below to start flashing.
sudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/klipper/out/klipper.bin
  1. If the following content is shown at the arrow as File downloaded successfully, the flashing is successful.
tip

After flashing is complete, you need to power off the motherboard completely.

Search for USBID​

  • The burning port of AirClick needs to be connected to the USB port of the host computer. Do not press the BOOT button; otherwise, the ID cannot be searched.

Search for USB Tutorial​

Precautions before searching for devices​

  • Before searching for the USB ID, please first connect to SSH
  • Please note that it is necessary to ensure that the SSH is logged in using the network rather than the serial port.
  • Please ensure that the motherboard with the USB firmware flashed is connected, and ensure that the data cable connecting the upper computer has a data transmission function.

Search for devices​

  • Please ensure that the upper computer can be connected to the network normally, and ensure that the data cable connecting the lower computer to the upper computer has a data transmission function.
  • After connecting to the upper computer via SSH, enter lsusb and press Enter. If the information circled in the image below appears, you can proceed to the next step.
    • If there is no information feedback, this is a system problem of the upper computer, and we are powerless. You need to replace the system with a confirmed normal one or replace the upper computer.
    • If the lsusb command is not found, you can execute this command to install it: 
      sudo apt-get install usbutils
  • 1d50:6177 is the device you need to use this time. The suffix OpenMoko, Inc. stm32f407xx has a certain reference value, but it is not used as a judgment basis.
    • Some upper computers may have incomplete or no display due to system problems.
    • If the lsusb command can display the device, but there is no 1d50:6177, please try to change the data cable and try to connect the motherboard to other USB ports of the upper computer.
  • If you have previously performed the above steps and successfully burned the Klipper firmware, and the motherboard is operating normally, but only need to update the Klipper firmware, please directly view the Firmware Update chapter in the right sidebar of this page.
Precautions

The next step can only be performed after the 1d50:6177 device is found.

Search for USBID​

ls /dev/serial/by-id/*
  • Enter the following command and press Enter. If everything is normal, a blue ID will appear in the following line. (The following is just for reference)
  • If there is no ID after entering the following command, but there is a device in lsusb, please replace the upper computer or the upper computer system.
Precautions

If multiple IDs appear, please select the corresponding ID according to the MCU model of your motherboard.

Fill in the USB ID in the configuration​

  • Open the printer web interface, find in the configuration options on the left sidebar: for fluidd: {…}; for mainsail: Machine, click to enter, and you can find printer.cfg.

  • Copy the blue ID and fill it in the serial: of the [mcu] node in the printer.cfg configuration. After saving and restarting, the motherboard can be connected. If Klipper prompts ADC out of range, it is a normal phenomenon. Connect the heated bed and the thermistor, configure the thermistor pins and output pins of the nozzle and the heated bed, and then save and restart.

dangerous

Note: All IDs appearing in the document are examples. The actual ID of each motherboard is different. Please modify and fill in according to the ID actually obtained.