Wired Connection Klipper Configuration

Notice

• The STM32F072 needs to be flashed with firmware before connecting to Klipper, otherwise wired connection operations will not be supported.

Start Compilation

• A host machine with the installed klipper service is required Connect via SSH over the network
• Make sure the device is connected to the host machine
• Note: Please use a regular host machine, such as a Raspberry Pi FLY board, etc. If it's a modified host machine (e.g., WiFi stick, Redmi, etc.), due to too many issues, we cannot provide technical support for these machines

warning

• To switch from the ROOT user to a regular user, you can enter the command below
• Do not use the ROOT user
• For the fly user, you can directly enter: su fly. For non-fly users, please replace <your host machine username> with your host machine's username!

su <your host machine username>

::: tip

• Please ensure that the host machine can connect to the network normally.
• Before compiling the firmware, use SSH to log in to the host machine via the network.
• Do not use a serial port tool to log in to the host machine.

:::

Klipper Firmware Compilation and Configuration Page Operation Instructions

::: tip

Please make sure that the keyboard input method is in half-width mode, i.e., English mode.

:::

1. The key ↑ (up arrow) and ↓ (down arrow) on the keyboard are used to move the cursor up and down to select menu items.
2. The confirm key Enter or spacebar Space is used to check the menu or enter a sub-menu.
3. The exit key ESC is used to return to the previous menu.
4. The Q key is used to exit the Klipper firmware configuration page.
5. When exiting the Klipper firmware configuration page and there is a prompt, press the Y key to save the configuration file.

::: warning

If there are fewer options in the configuration page, please first check [ ] Enable extra low-level configuration options to display some hidden options.

:::

Below is an introduction on how to compile the firmware:

• After connecting to SSH, enter the following command 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 to compile the firmware. After execution, the following interface should appear:

  

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

  

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

  

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

  

• Select Bootloader offset, select: (No bootloader)

  

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

  

• Press Q key, and when Save configuration appears, press Y key

  

• The configuration should now be saved and you should exit to the command line interface

• Input make -j4 to start compilation, it takes some time

  

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

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

Enter Burning Mode

• With the AirClick powered off, press and hold the STM32's BOOT pin and connect the STM32's programming port to the host computer via Type-C
  

Confirm Whether Entering Burning Mode

• Please ensure that the host machine can connect to the internet normally.

• Please ensure that the data cable connecting the lower-level machine to the host machine has data transfer functionality.

• After SSH connecting to the host machine, input lsusb and press enter. The following three scenarios may occur:

  • It will display the recognized USB devices.
  • It will prompt that there is no ls command; you can execute this command to install it:

    sudo apt-get install usbutils

  • There is no error message, but also no other information (a system issue requires replacing the system).

• If there is no reaction after entering lsusb, this is a system issue, and we are unable to help; you need to replace with a confirmed normal system.

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

  

• 0843:df11 belongs to the device you will be using this time. You do not need to worry about the subsequent prompts as they may not fully display or may not display at all due to system issues.

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

Note

Proceed to the next step only if there is 0843:df11.

Burn Firmware

1. Install the burning tool

• No need to execute the installation of the burning tool for the FLY upper computer
• If you need to install, please note: The upper computer needs to be able to access the internet to install normally
• If already installed, no need to install

sudo apt update
sudo apt install dfu-util -y

2. Execute the following command to check if the connection is successful.

lsusb

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

• Due to system version issues, it may display other names. If 0483:df11 is shown, it indicates entering burning mode

  

3. Burn the firmware

• Execute the code below to start burning

sudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/klipper/out/klipper.bin

4. If the content shown at the arrow in the following image is File downloaded successfully, then the burning is successful

tip

After burning, the main board needs to be completely powered off once.

Search USBID

• Connect the AirClick's programming port to the host computer's USB port, do not press the BOOT button otherwise the ID cannot be searched
  

Search USB Tutorial

Precautions Before Searching for Devices

• Please connect to SSH before searching for the USB ID Connect to SSH
• Please note that you need to ensure that you log in to SSH via the network rather than via serial port
• Please ensure that the mainboard with the flashed USB firmware is connected, and the data cable connecting to the host computer has data transmission function

Search for Devices

• Ensure that the host computer can connect normally to the network, and ensure that the data cable connecting the downstream device to the host computer has data transmission function.
• After SSH connection to the host computer, 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 feedback at all, this is a system problem with the host computer. We are unable to help. You need to replace it with a confirmed normal system or replace the host computer.
  • If the prompt says there is no lsusb command, you can execute the following command to install:

    sudo apt-get install usbutils

    
• 1d50:6177 belongs to the device you will use this time.
  • Some host computers may not display fully or not display due to system issues.
  • If the lsusb command can display the device but does not show 1d50:6177, please try replacing the data cable and connecting the mainboard to another USB port on the host computer.
• If you have executed the above steps before and successfully burned the Klipper firmware, the mainboard is running normally, and you just need to update the Klipper firmware, please directly refer to the Firmware Update section in the right-hand menu bar of this page.

Note

You must query the 1d50:6177 device before proceeding to the next step

Search for USBID

ls /dev/serial/by-id/*

• Enter the command below and press Enter. If everything is normal, one blue ID will appear. (The following is for reference only)

• If no ID appears after entering the command below, but lsusb shows the device, please replace the host computer or the host computer system.

Note

If multiple IDs appear, please select the corresponding ID based on your mainboard's MCU model.

Fill in the USB ID into the configuration

• Open the printer web interface, find printer.cfg under the configuration option in the left sidebar: fluidd is {...}, mainsail is Machine, click to enter.

  

• Copy the blue ID and paste it into the serial: field under the [mcu] node in the printer.cfg configuration file. 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 thermistor properly, configure the thermistor and output pins for the nozzle and heated bed, then save and restart.

  

dangerous

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