Pad7 banner

Bigtreetech Pad 7: Guide to the best all-in-one for Klipper

Bigtreetech enters fully into Klipper solutions all in one with its Pad 7.

If a few weeks ago we enjoyed a similar solution, the Raspberry Pad 5, which left us an excellent taste in our mouths, which we have controlling two of our laboratory machines. Now Bigtreetech has launched its big sister Pad 7 that make it a perfect all-in-one solution.

image 22

As always before continuing with the article, remind you that you can join 3DWork in our Telegram channel full of deranged by 3D printing, or in our social networks FacebookTwitterInstagram.

Below you can see more details of its characteristics, as well as how it behaves.

Bigtreetech Pad 7

The Bigtreetech Pad 7 has an imposing 7″ screen in addition to mounting its CM4 module, in our case a CB1 module based on an Allwinner H616 chip, which is a perfect solution for running Klipper.

image 23

To complete the device we have excellent relatively compact housing in which we have easy access to the multitude of available connections that we will detail later.

In the software part and depending on the CM4 module that we use we will have access to different distributions of Linux / Raspberry Pi OS that will allow us to enjoy a perfect experience with Klipper. Something that in other similar devices of other brands has ended up being a big headache … Again Bigtreetech thinks about the maker community that is always appreciated!!


As usual in Bigtreetech the Pad 7 comes with excellent hardware features:

  • 7″ touchscreen
    • 1024*600 and 60 Hz refresh
    • 5-point touch with touch vibration function
    • 178º viewing angle
    • 500 Cd/m2 brightness
    • Illumination sensor for automatic brightness adjustment
spaces%2F MTqLw6KI5FruaRNEMZD
  • CM4 socket for SBC module compatible with
    • Bigtreetech CB1 v2.2 (normally included in the kit), Allwinner H616 quad-core Cortex-A53 processor, Mali-G31 MP2 GPU, 1GB RAM, 802.11 b/g/n WiFi support
    • Raspberry Pi CM4, Broadcom BCM2711 quad-core Cortex-A72 processor, VideoCore IV GPU, 1 to 8 GB RAM, 0 to 32GB eMMC memory, Wifi 5 and Bluetooth 5 depending on version
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FalrfeOD2Vur9GKp75jwQ%2Fimage
  • MicroSD socket, the kit includes a SanDisk microSD with Bigtreetech’s CB1 OS based on Debian OS and with Klipper and its components installed
  • Expansion ports
    • 10/100M ethernet port (if we use CB1) or Gigabit (if we use CM4)
    • as for USB ports, we have 3 USB 2.0 ports and 1 Type-C to install the system in the case of using a Raspberry Pi CM4 module
    • we have a CANbus port (MCP2515) for the expansion of MCUs with Klipper
    • SPI connector for use of the ADXL345 accelerometer included in the kit
    • Built-in speaker with buttons for volume control, we also have a 3.5 mm jack output which will allow us to connect external speakers
  • RGB LED for notifications
  • Power
    • power supply 12V/2A DC
    • Approximate consumption of 7.3W

About CANbus and SPI:

Since the CANbus interface and the SPI are shared, simultaneous use of these is not possible.

Here are some diagrams of Pad 7:

image 24
image 25
image 26


As we anticipated in the specifications, the Pad 7 comes prepared with several expansion/improvement connections that we can use to expand its functionalities such as the use of accelerometers, CANbus, etc …

The installation of ADXL345 accelerometer, included in our kit, can not be simpler and once adjusted the configuration of our system will simply connect it to the SPI port of our Pad 7

image 27

In the previous diagram we can find the order of pins of the connector in case we want to use another accelerometer.

Our Pad 7 has a CANbus connection that can be very interesting for many machines greatly simplifying the wiring to our print head.

spaces%2F MTqLw6KI5FruaRNEMZD

In the above diagram you can find the order of pins of the connector.

Bigtreetech CB1 modules are, in terms of quality/price, probably the best choice today for use with Klipper.

In any case we have the option to use Raspberry CM4 modules in our Pad 7.

  • We will disconnect the power of our Pad 7
  • In the back we will remove the two screws that you can see in the following image to remove the bottom cover
PAD7 CB1 1
  • Then we will remove the screws from the heatsink of the CB1/CM4 module to be able to remove it as you can see below
PAD7 CB1 2
  • We will take out, with great care, the antenna of our CB1 module and remove the CB1 module from our Pad 7
PAD7 CB1 3
  • Now we can place our new CM4 module, it is important that you place the CM4 module as you see in the following image. Once the module is installed, we will connect the antenna.
PAD7 CB1 4
  • We will replace the heatsink with its screws
PAD7 CB1 5
  • We will have to adjust the microswitches as you can see in the following image… selecting USB-Choose to CM4-OTG and CS-Choose to CM4.
PAD7 CB1 6
  • We will reinstall the bottom cover
PAD7 CB1 7
  • We can now proceed to install the system for our CM4 module that you will find below!!

Klipper System Installation

Bigtreetech has always been very aware of users, so it is one of the few brands that support projects related to Klipper which ensures a better experience in its use.

That is why, and depending on the CM4 module we use, we will have different options of Klipper distributions to install:

Next we will proceed to install the Klipper system in our CB1 module, we have two options:

  • Using the generic distribution of Bigtreetech
  • Using RatOS you have some advantages, and disadvantages depending on your level of knowledge in Klipper, such as pre-installation of various components, and compatibility with various electronics and printers with pre-configured and default macros.
  • Once we have downloaded the Klipper distribution that we like the most, we will use Raspberry Pi Imager or balenaEtcher to transfer the Klipper image to our SD card. A card of at least 16-32Gb is advisable. For this guide, we will use RatOS which is the Klipper distribution that we usually use.
spaces%2F MTqLw6KI5FruaRNEMZD
spaces%2F MTqLw6KI5FruaRNEMZD
  • After the process and from the explorer of our computer we will access our SD where we will have a partition called BOOT.
  • In this we will find a system file.cfg where we will adjust the network name for our Klipper host:

Configuration files:

We remind you that normally in this type of configuration the # symbol and everything that is after that symbol is considered a comment and will not be taken into account when processing the configuration file.

  • Regarding the WiFi configuration, in case you do not use your Pad 7 with a network cable, we will return to our system file.cfg where we will adjust our WIFI_SSID and WIFI_PASSWD:
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2F6npbHY70u8JUymcYvtbg%2Fimage
  • Following in the system file.cfg where in this case we will adjust the specific options for our Pad 7
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FsEnfFNIhBukrtADqjprh%2Fimage

system.cfg settings:

BTT_PAD7=”ON” # Enables the required scripts for a Pad7
TOUCH_VIBRATION=”OFF” # OFF: Deactivates vibration before pulsations ON: Enables vibration
TOUCH_SOUND=”ON” # OFF: Turn off sound before keystrokes ON: Enable sound
AUTO_BRIGHTNESS=”ON”# OFF Turn off automatic brightness adjustment ON: Enable automatic adjustment

Pad 7 special options:

Of the previous options, we are going to make a note in reference to the vibration before the screen presses. 
KlipperScreen, the component used to display the Klipper interface on our Pad 7, does not currently have a management API to enable vibration.

In the event that we do not use a distribution of the Bigtreetech system, we must make the following changes to use the fork created by Bigtreetech of KlipperScreen if it implements this functionality:

– We will open our moonraker.conf from our Mainsail web interface:


– We will change the KlipperScreen update_manager as follows:

– Once the configuration change is made, it is advisable to restart the system. Once restarted we will go to our Mainsail/Machine/Update Manager we will give the refresh icon, and we will do a Hard Recovery in the KlipperScreen component:


– When the process is finished, the response by vibration when pressing the screen should work correctly.

  • Next, we will configure the specific options for our Pad 7 in this case we will do this on our BoardEnv file.txt where we will adjust the following:
spaces%2F MTqLw6KI5FruaRNEMZD

BoardEnv.txt settings:

ws2812: Habilita los leds de notificación que se encuentran en la esquina superior derecha de nuestra Pad 7
light: Habilita la retroiluminación de pantalla
mcp2515: Habilita el conversor MCP2515 SPI a CAN, que habilita el uso de CAN en nuestra Pad 7
spidev1_1: Habilita spidev1_1 permitiendo que el puerto SPI pueda contactar con el acelerómetro ADXL345
IMPORTANTE!!! el uso de CANbus y el puerto SPI de la Pad 7 no se pueden utilizar de forma simultánea.

overlays=ws2812 light mcp2515 spidev1_1
  • Enable CANbus, as we discussed in the previous point, enabling mcp2515 in our BoardEnv file.txt will enable CANbus in our system in case we use it
  • Adjustment of the CAN interface, if in the previous step, we enable CAN in this step we will configure its interface. Using sudo nano /etc/network/interfaces.d/can0 we will add or adjust this file as you have below:
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FaGMvjBWztKE3362L1UZo%2Fimage
allow-hotplug can0
iface can0 can static
  bitrate 1000000
  up ifconfig $IFACE txqueuelen 1024
  • Enabling an ADXL345 accelerometer, as with CANbus with enabling the option spidev1_1 our system will enable access to the SPI port of our Pad 7. 
    Learn more about accelerometers in our Input Shaper guide. In this case, we will need to adjust the following settings in our printer.cfg or any of its includes:
# Enable our CB1 as a secondary MCU
[mcu CB1]
serial: /tmp/klipper_host_mcu
cs_pin: CB1:None
spi_bus: spidev1.1
axes_map: z,y,-x  # Modify according to the actual orientation of the ADXL345 installed on the printer.

To install the Klipper system in our CM4 module, we recommend two options:

  • Using the generic MainsailOS distribution
  • Using RatOS you have some advantages, and disadvantages depending on your level of knowledge in Klipper, such as pre-installation of various components, compatibility with various electronics and printers with pre-configured and default macros.

Once downloaded the Klipper distribution that we like the most, we will perform the same steps that we described with the CM1 module to apply the OS to our CM4, we advise you to go through the installation guide of the Bigtreetech Pad 5 where you will have more detail of the process.

As is done with a CB1 module we must make some adjustments in the configuration:

  • Settings in serial communications, for this we will modify:
    • /boot/cmdline.txt where we will delete console=serial0,115200 if it exists
    • /boot/config.txt where we will delete enable_uart=1 if it exists
  • Backlight, we will edit again our file /boot/config.txt where we will add the following lines:
  • Adjusting the resolution and touch, we will add the following lines to our /boot/config.txt :
hdmi_cvt 1024 600 60 6 0 0 0
  • USB, some systems can disable USB ports for energy saving to avoid this we will modify the file /boot/config.txt adding the following lines to ensure that the USB HID used by our Pad 7 does not affect this energy saving:
  • SPI and CAN, again in our /boot/config.txt we will add the following configuration lines:
  • Adjustment of the CAN interface, if in the previous step we enable CAN in this step we will configure its interface. Using sudo nano /etc/network/interfaces.d/can0 we will add or adjust this file as you have below:
allow-hotplug can0
iface can0 can static
bitrate 1000000
up ifconfig $IFACE txqueuelen 1024
  • Enabling an ADXL345 accelerometer, as with CANbus with enabling the mcp2515-can0 option our system will enable access to the SPI port of our Pad 7. Learn more about accelerometers in our Input Shaper guide. In this case we will need to adjust the following settings in our printer.cfg or any of its includes:
# Enable our CM4 as a secondary MCU
[mcu CM4]
serial: /tmp/klipper_host_mcu
cs_pin: CM4:None
spi_bus: spidev0.1
axes_map: z,y,-x # Modify according to the actual orientation of the ADXL345 installed on the printer.


Once we have installed our operating system on Pad 7 we will start this. If all goes well, the screen will show the KlipperScreen interface which will inform us of an error for not finding our printer.cfg with the configuration of our printer.

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2Fd192NOZZRwy1JNHIgWLL%2Fimage

Do not panic, we simply do not have any configuration enabled and therefore tells us that our Klipper found an error. 
To start with the configuration we will connect to the web interface (Mainsail) from our web browser using http://btt-pad7.local or if we customize this name during the configuration we will use the custom one.

In order to find the IP of our Pad 7 we can use Fing which is a cross-platform application that will scan us and list all the devices in our network. It should appear with the hostname btt-pad7 or the one defined in our system.cfg above.

spaces%2F MTqLw6KI5FruaRNEMZD

What to check if we have network issues?

In the event that we do not find the IP we will connect the SD back to our computer and review the system file.cfg looking for any failure when adding our WiFi data.

Once our IP is identified, we will go to our browser and use it to access the Klipper web interface… We advise you that the first thing to do is an update of all Klipper components:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FCpyeqRceuGR2nzBqIeR0%2Fimage

Already with access to the interface we only have to create and apply the Klipper firmware to our MCU (electronics) and find our serialID, you have information about these steps here.


Some of these steps will require us to connect our Pad 7 to our MCU using a USB or CAN cable!!

Once we have applied the firmware to our MCU and with the communication serialID we only have to create and adjust our Klipper machine configuration, connection, and macros that we want to use.

If everything has gone well, our Pad 7 can already connect to our MCU and our screen will show a control interface of this!!

We advise you to follow the steps described in our Klipper configuration guides. Some of them you can launch from the screen options themselves, we advise you to follow the configuration guides in order to make sure we leave everything perfect.

Input Shaper

You have more detailed information about this process in our Input Shaper guide, in any case, we will guide you through the process using our Pad 7.

We will start by connecting our ADXL345 included in the kit to the SPI port.

spaces%2F MTqLw6KI5FruaRNEMZD

We will update our printer.cfg adding as a second MCU our CB1 and we will define the accelerometer (in our case for a CB1, remember that in CM4 this configuration is slightly different)

[mcu CB1]
serial: /tmp/klipper_host_mcu

cs_pin: CB1:None
spi_bus: spidev1.1
axes_map: z,y,-x # Modify according to the actual orientation of the ADXL345 installed on the printer.

In our case we are going to launch the process in one of our Cartesian printers, so we must place the sensor on the X axis (print head) and after making the measurements anchor it to our Y axis (bed). In the event that we have a CoreXY printer anchoring it in the print head is enough.

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FJCdynMkVK9hDHZOAwy67%2Fimage
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2Fn9wk4mJGfy3YcZPNiBNB%2Fimage

For more information about the process, we advise you to follow our Input Shaper guide.

You can also perform the process from the Printer/Configuration/Input Shaper/Auto-calibrate screen.

Slicer settings

Klipper is an incredibly flexible and powerful 3D printer firmware as we have seen, an important aspect is its integration and configuration of our slicer.

An important aspect is to make sure that our slicer generates the laminate or g-code (G-code flavor) valid for it to be interpreted by Klipper
Today slicers such as PrusaSlicer/SuperSlicer and Bambu Studio/OrcaSlicer support the generation of the g-code for Klipper for which they are usually the most advisable.

Other slicers can be used without problem, since Klipper can process g-codes generated for Marlin or Smoothiware, but may need certain adjustments to avoid including g-codes that are not supported by Klipper
Similarly, generating g-code for other systems can cause similar issues, for example, selecting Marlin2.

In this case, it is advisable to review the configuration of our laminator and select to generate the slice in Klipper, Marlin or Smoothiware format… In this order, ideally.

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FRwlhTjD484Si6Q8zJ7OE%2Fimage
Example of G-code flavor configuration in OrcaSlicer

Another important aspect is to adjust our start and end of print g-codes, at least, for the use of Klipper macros instead of the traditional and limited g-codes. You can find more information and details in the Klipper configuration guide in laminators. By way of example:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FLobq1EoY1y4ZXZcabTJb%2Fimage
Example of G-codes start and end in OrcaSlicer

The use of macros in Klipper will allow us to raise the control and customization of our machines to incredible levels.

Another great improvement is that we can upload our g-codes directly from the laminator, something that is very comfortable. Moonraker emulates the Octoprint API, something very useful to make it compatible with any tool that uses Octoprint:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FvCVgiZX4hdYdJI7fNBh0%2Fimage
OrcaSlicer integration for sending g-codes directly from the rolling mill

Control multiple printers

As we have already mentioned on many occasions, Klipper is an extremely versatile system that together to a host like our Pad 7 can allow us to control several printers simultaneously.

Next, we are going to guide you through the process to have multiple instances of Klipper on our Pad 7 which will allow us to control our machines centrally.

How many printers can it support my Pad 7?

In our tests we have controlled up to 3 printers simultaneously without major performance problems, but without using any webcam for image processing, and by the load of the system we believe that it could control 4 printers.

We will start by connecting to our Pad 7 using an SSH client, launching an ls -l command we will see what we have installed on our Pad 7:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FI0OYcvbUTnt77hz3QN19%2Fimage

It is possible to install our Klipper instances manually, but we prefer to use Kiauh
Kiauh is a sensational module for Klipper which allows us to easily launch different actions from a simple menu system. Let’s proceed to install it by launching the command:

cd ~ && git clone
spaces%2F MTqLw6KI5FruaRNEMZD

Once we have Kiauh installed we will launch it with the following command that will show us the Kiauh menu system :

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FzPlP9JlSfnijpRLomguS%2Fimage

As we see in the previous screenshot, in our case we have 1 instance of Klipper, Moonraker as well as KlipperScreen or Crowsnest
Then we will proceed to uninstall Moonraker, clicking on option 3 (Remove) and then 2 (Moonraker) … During the process, we will be asked for the password of our user:

spaces%2F MTqLw6KI5FruaRNEMZD

Once the process is finished, press 1 (Klipper) to delete our Klipper instance:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FC0oRqSAplPmJvflSBCbg%2Fimage

Posibles errores durante la instalación:

Depending on the distribution we use to initially install our Klipper system on our Pad 7 we can find that Kiauh is not able to uninstall the Klipper service correctly, throwing Permission denied errors.
We can perform the uninstallation by launching these two commands:

sudo ~/klipper/scripts/<br>sudo rm -rf ~/klippy-env ~/klipper

If everything has gone correctly Kiauh will show us that we do not have instances of Klipper and Moonraker:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FNu3Mre9Mq7NQddDac9Rb%2Fimage

Now we will proceed to install Klipper using option 1 (Install), 1 (Klipper) and 1 (Python 3.x)… it will ask us for the number of instances we want to install, in our case we will use our Pad 7 to control 2 printers. 
Before installing the instances it will ask us if we want to assign each instance a custom name, our advice is that we do NOT customize the instances since later we can do it on the other hand that will prevent our Klipper instances from using a non-standardized name structure:

spaces%2F MTqLw6KI5FruaRNEMZD

Once the process is finished, and if everything worked as expected, we will go to the main menu of Kiauh (B) that we have our 2 installed instances:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FlKtnFewOUTAfrFnvfOkF%2Fimage

Next we are going to install our Moonraker instances by pressing 1 (Install) and 2 (Moonraker)… Kiauh itself will detect our Moonraker instances and suggest the number of these to install:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FjPn76CR4zSNockIR8aTb%2Fimage

Once the process is finished, and in the main menu of Kiauh, we will be able to see our Moonraker instances… It is very important that we write down the port of each of our instances since later it will be necessary:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FDNlfXuHrII4CXTz4WcnC%2Fimage

We already have all our instances installed, we only have to leave Kiauh and restart our Pad 7 with the sudo reboot command. We will reconnect by SSH to our Pad 7 and we will launch the ls -l command again to verify that we have our configuration directories for each of our instances:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FgpfPRctf1lHcf4zzXY2W%2Fimage

We will continue with the following steps to perform from our web interface, in our case Mainsail, where we will open our favorite web browser on our computer / tablet using its IP or hostname where it will ask us to add a printer:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FrAdZVf455OyZOCj3c6Co%2Fimage

Adding our instances of Moonraker, and remember the information of the instances that Kiauh previously provided us:

spaces%2F MTqLw6KI5FruaRNEMZD
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FKduhokg0FuFfR539SKGB%2Fimage

We will enter our instances and change the name, and also from UI_SETTINGS we can customize the color of the logo, to be able to identify each instance clearly. We can also use the drop-down to choose between one instance or another:

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FEyqPWBkmlXrv6WnoIpNw%2Fimage
spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FO5uzKQYqozWvjwngITpJ%2Fimage

Now you will have to configure each of our instances with its own printer.cfg and includes that we have for our printers.

How to manage the connection when using multiple instances?

Normalmente en instalaciones de una sola instancia se aconseja que la configuración para conectar a nuestra/s electrónicas se realicen por serial_id. En el caso de utilizar múltiples instancias, aconsejamos el uso by-path, donde asociaremos cada uno de los puertos USB de nuestra Pad 7 a nuestras máquinas. Importante!!! Recordar que al usar by-path nuestra impresora siempre ha de estar conectada al mismo puerto de nuestro host!!!
Lanzaremos el comando ls /dev/serial/by-path/* para ver que no tenemos ningún dispositivo conectado: spaces%2F MTqLw6KI5FruaRNEMZD
We will connect our printer, in this case we use the upper rear USB connector, and relaunch the command ls /ls /dev/serial/by-path/*:
spaces%2F MTqLw6KI5FruaRNEMZD
We will use this connection string in our [mcu] section of the instance that corresponds to the connected printer.
We will do the same process to connect the rest of the printers. 
In our example, we were as follows:

serial: /dev/serial/by-path/platform-5200000.usb-usb-0:1.2:1.0-port0
restart_method: command


serial: /dev/serial/by-path/platform-5200000.usb-usb-0:1.3:1.0
restart_method: command

The next step will be to configure our KlipperScreen so that we can connect to our instances to be able to manage them comfortably from the screen of our Pad 7. To do this, we will have to return to our SSH client to edit the KlipperScreen configuration file:

sudo nano KlipperScreen.conf

And we will copy the following settings, adjust the names of printers and ports of Moonraker to your own installation:

job_complete_timeout: 0
job_error_timeout: 0
#default_printer: ElegooN3Max
use_default_menu: True

[printer ElegooN3Max]
moonraker_host: localhost
moonraker_port: 7125
moonraker_api_key: False

[printer Voron01]
moonraker_host: localhost
moonraker_port: 7126
moonraker_api_key: False

To finish, we will press CTRL + X and Y to exit and save the changes and restart KlipperScreen with the following command sudo service KlipperScreen restart . If all has gone correctly, our screen will show access to our two printers, being able to change from one to the other by clicking on the icon of the two crossed arrows.

Final assessment

During the last months we have tested all kinds of solutions for Klipper and without a doubt if you plan to switch to Klipper, if you do not use it already, Bigtreetech electronics are the best option we have tried.

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2F2wwOjUploiPGliKztmnR%2Fimage

In the case of the Bigtreetech Pad7, and after being delighted with the Pad 5, it is an ideal team to get started in Klipper, since we have everything in the same device, with a very competitive price, and also being able to freely use Klipper.

spaces%2F MTqLw6KI5FruaRNEMZD

In addition, the inclusion of tools, screws, and accessories such as the accelerometer help to make the start-up and use of Klipper relatively simple.

spaces%2F MTqLw6KI5FruaRNEMZD

With a great screen, perhaps sometimes too big although our tired eyes appreciate it, a good handful of connections and a very correct finish, the colleagues of Bigtreetech have made a great product.

In addition, as always with Bigtreetech we will find abundant documentation and good support from both the manufacturer and the community, which often helps… Especially if you are new to Klipper because it is a new world totally different from other firmwares for 3D printer.

spaces%2F MTqLw6KI5FruaRNEMZD 887967055%2Fuploads%2FiwZv2Mje0g4kF44X9ZHZ%2Fimage


Below we help you solve some problems that we can find with our Pad 7.

Although Klipper increasingly improves the processes sometimes we may find that our accelerometer does not work correctly, in these cases we advise you to review the following points:

  • On the back of our Pad 7 we have micro-switches that allow us to adjust the hardware configuration. Make sure you have them in the correct positions:
In the event that we use a CB1 module
If we use a CM4 module
  • Make sure you connected the cable correctly between your Pad 7 and the accelerometer as indicated at the beginning of this guide, especially check the wiring if you do not use a Bigtreetech accelerometer.
  • From SSH we will check that our SPI channel is working correctly by launching the command ls /dev/spi … in the case that we have a CB1 module we will see a spidev1.1 device and if we use a CM4 module spidev0.1

The use of CANbus, in certain machines and circumstances, can be a great-added value that allows us to simplify the wiring of our machine a lot. 
On the other hand, it will add more complexity to our configuration and more points of failure. We give you some tips to keep in mind for our Pad 7:

  • On the back of our Pad 7 we have micro-switches that allow us to adjust the hardware configuration. Make sure you have them in the correct positions:
In the event that we use a CB1 module
If we use a CM4 module
  • Make sure you connected the cable correctly between your Pad 7 and your CANbus device as indicated at the beginning of this guide.
  • From the SSH terminal we will launch the command dmesg | grep can where it should indicate MCP2515 successfully initialized.
  • Again from the SSH terminal we will execute the command sudo nano /etc/network/interfaces.d/can0 to verify that our CAN interface configuration is correct.
allow-hotplug can0
iface can0 can static
bitrate 1000000
up ifconfig $IFACE txqueuelen 1024
  • Also from the terminal we can launch the ifconfig command to see if our can0 interface exists.
spaces%2F MTqLw6KI5FruaRNEMZD
  • For more information on troubleshooting CANbus check out our guide.
3D enthusiasts