When i started using the BIGTREETECH CB1* on the BIGTREETECH E3EZ* i quickly got into the trouble of mapping all the pin descriptions to gpio numbers. Luckily i’m not alone and i found a solution here . The BIGTREETECH CB1 uses a custom IO pinout for the pins which consists of PA, PB….PG and a number. To calculate a GPIO Number, you need to use the following formula: 1 2 [(PG - PA)*32] + {Pin Number} Where PA = 1, PB =2…....
When i started using the BIGTREETECH CB1* i noticed that the system time was almost always wrong. Solution There are different solutions for this but the following one worked the best for me: First remove NTP: 1 sudo apt remove ntp and install the systemd-native timesync service: 1 sudo apt install systemd-timesyncd This should automatically install the service and start it. To make sure, you can check that systemd-timesyncd.service is active (running):...
I’m an owner of a Orbiter 1.5 Extruder where there i discovered that an official filament sensor is available. Unfortunately it is a bit more tricky than with the Orbiter 2.0 Extruder. Originally i discovered the filament sensor on thingiverse and already was about to hit the slicer when i saw in one of the comments that the files are not the latest ones. These actually can be found on the page of the author - make sure to pick the latest files (currently version 2....
While setting up a new board on my 3D Printer, i had the requirement to run a move of a stepper without homing first. Initially i added the following directive to the printer.cfg of klipper: 1 2 [force_move] enable_force_move: True but that didn’t help until I manually set a kinematic position through the console: 1 SET_KINEMATIC_POSITION X=10 Y=10 Z=10 Which is as per documentation perfectly correct. Nevertheless I wanted to move without any previous checks or settings....
Recently i had to recompile for the Creality* Ender 3v2 (not NEO!) a new Klipper firmware based off the Klipper 0.11. As per the instructions of the installation of Klipper you will have to flash the microcontroller as follows: 1 2 cd ~/klipper/ make menuconfig During “make menuconfig” select the following settings: Enable extra low-level configuration options Micro-controller Architecture (STMicroelectronics STM32) Processor model (STM32F103) Bootloader offset: (28KiB bootloader) Communication Interface: (Serial (on USART1 PA10/PA9)) Once you have compiled the firmware using make you can flash it by copying the file out/klipper....
While trying to flash the klipper firmware to an Bigtreetech EBB36, i ran into the following error: 1 2 3 4 5 6 23:29:04 : Erasing memory corresponding to segment 0: 23:29:04 : Not flash Memory : No erase done 23:29:04 : File segment @0x08000000 is not 255-bytes aligned. It will be aligned to @0x07FFFFF8 23:29:04 : Download in Progress: 23:29:05 : Error: failed to download Segment[0] 23:29:05 : Error: failed to download the File After fiddeling around a bit i finally stumbled across two solutions....
After having implemented KAMP (Klipper Adaptive Meshing) on my Klipper instance, no print worked anymore as i always got the following message in the Klipper Console: 1 bed_mesh: min/max points too close together The reason is relatively simple - it is a bug in my currently used slicer, OrcaSlicer . It appears to be related to having multiple build plates visible in the slicer - hence it might not happen to you immediately as long as you do not use that feature....
On Multi-Object Prints in Klipper , you might see the message: 1 Unknown Command "M486" To me that happened when i switched to Superslicer . Thankfully it is easy to solve: Open Superslicer Open your Print Settings Search for “Label Objects” (should be in “Output Options”) Uncheck the tickbox That solves it ;)