Search the Community

I have been converting my Voron 2.4 from many-cables-to-the-toolhead, into a single can-cable (4 wires) system. Even though I saw here that many people really did not like the CAN bus on their printers, mainly because it was new and unknown. The problem of the web is and always has been, that you never hear the 'satisfied' people. Only the very unhappy, the very happy and the sales-people. I hope this script will make it easier for some to make the step to the 'new'. I have never been afraid of new things. The problem was finding a way to find the set up I needed. From one came the other and what happened was, that I was able to combine information from a few sites / github pages I visited, and was able to write a simple script that did all the work. Actually very much like every software / game in the pre-windows 95 era, came with its own 'set-up' disk, with config.bat / setup.bat files. As long as I do not have a Klipper '95, I think this script will do for me. I tested it, and it takes 3 to 4 minutes to update the mainboard and toolhead PCB. Faster than 5 minutes I heard mentioned before. I will paste the script down here, with all the comments and the instructions. and attach as an attachment also. If there is a better way, let me know. It is information gathered mainly from Esoterical's guide. You will need information from this guide to set up your own script. -------------------------------- SCRIPT flashCAN.sh ------------------------------------------------------------------ #!/bin/bash ### without the extensive documentation and work of Esoterical, this would never have been possible. ### Besides Esoterical, this script builds standing on shoulders of: ### Eddie the engineer. https://www.youtube.com/watch?v=1P4UrJxChL8 Thanks! ### cruiten https://github.com/cruiten/Voron-Related/blob/main/CANbus/Documentation/SB2040_CAN/flash_klipper_script.md Thanks! ### uses # https://docs.kernel.org/kbuild/kconfig.html KCONFIG_CONFIG is used to define an alternative config file... ### to define a separate config file for mainboard (eg Octopus) or for a canbus toolhead PCB. For both cases one for katapult and one for klipper. ### the make menuconfig commands use the Esoterical github provided 'mainboard/common_hardware and toolhead_flashing/common_hardware maps provided image options ### https://canbus.esoterical.online/mainboard_flashing/common_hardware.html ### https://canbus.esoterical.online/toolhead_flashing/common_hardware.html ### HOW TO USE: Follow Esotericals guide, starting at the begin: https://canbus.esoterical.online/Getting_Started.html ### it will lead you through setting up a can network on your Klipper running os. ### I skipped the part about dedicated can_boards, and continued with the klipper USB 2 CAN bridge provided by my mainboard: https://canbus.esoterical.online/mainboard_flashing ### will go through flashing your mainboard for CAN. go through EVERY step. and DO NOT skip the STOP warnings. This will install katapult. USB2CANbus bridge ### afterwards it will assist you through flashing your toolhead: https://canbus.esoterical.online/toolhead_flashing ### like with the mainboard, you will install katapult and then the klipper can interface on it. ### when you are finished, you get advise on how to finish it: https://canbus.esoterical.online/Final_Steps.html ## You are happy and you see an update from Klipper in mainsail. You push the update button and your whole system is unaccessable, ## because your hardware is no more up to date with the latest klipper... ## in that case you can follow the "so you clicked the update button???" : https://canbus.esoterical.online/Updating.html ## because I did not want to go through the same repetitive steps, I made this below script. ## If I did not think this would be faster than the 5 minute update teamfdm.com @mvdveer needs to update his printers, I would have kept it to myself. ## -------------------------------------------------------- HOW TO USE ----------------------------------------------------------- ## save this document and copy to your klipper system into the /klipper directory. ## give it a name (eg. flashCAN.sh) ## ssh into your system. go to your klipper directory and run the command: sudo chmod +x flashCAN.sh ## now you can run the script by typing the following command in ssh ## ~/klipper/flashCAN.sh ## make sure to fill in your OWN values for ## - usb-katapult_your_mainboard_usb_id ## - yourmainboarduuid ## - yourtoolheaduuid # these are values for me! # yourmainboardUUID=403544310df5 # katapult_your_mainboard_usb_id = usb-katapult_stm32f446xx_200035000851313133353932-if00 # yourtoolheaduuid =21c36fa97c26 ## while installing CAN the first time, note your usb-katapult-mainboard-usb-id, mainboard UUID, toolhead UUID. ## or if you have a functioning CAN network, run ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0 to see a list of installed CAN devices. ## the UUID for mainboard and toolhead you need to put in your printer.cfg file, so you can retrieve it from there. ## But the USB serial ID you have to obtain after you put the mainboard into katapult boot flash mode (STEP 2 A below). ## after the command python3 ~/katapult/scripts/flashtool.py -i can0 -u yourmainboarduuid -r ## you will need to type: "ls /dev/serial/by-id" and it will give you your USB serial ID. ## once you have run through this script, comment out (put a # in front of the line) the line which has the "make menuconfig" in it. ## and the next time you have a klipper update that breaks your CAN, all you have to do, is to run this script once. #-------------------------------------FINAL WORDS-------------------------------------------------- # this script is for me and my set up. # HARDWARE # Raspberry Pi 4B, 8mb # Voron 2.4, 350 # Octopus Pro mainboard # SB2209 (RP2040) Big Tree Tech 2 part Toolhead PCB # Cartographer 3D Eddy Probe in CAN mode # with built in accelerometer / resonance tester # The Octopus functions as a CAN bridge. Cartographer 3D is connected to The SB2209 (RP2040). # The CAN bus is terminated at the Cartographer 3D probe. # SOFTWARE: # OS: Raspbian GNU/Linux 11 (bullseye) # Distro: MainsailOS 1.2.1 (bullseye) # klipper: v0.12.0-114-ga77d0790 # if you are not using this script on my system then anything can happen which I am not responsible for. echo "STEP 1 - UPDATE KATAPULT FROM GIT if needed" test -e ~/katapult && (cd ~/katapult && git pull) || (cd ~ && git clone https://github.com/Arksine/katapult) ; cd ~ echo "STEP 2a - FLASH MAINBOARD KATAPULT so we can flash it easily" cd ~/katapult make clean KCONFIG_CONFIG=config.mainboardKatapult # cleans old files make menuconfig KCONFIG_CONFIG=config.mainboardKatapult # this can be commented out for automation AFTER you have filled out correct fields for your card. or leave it in to have some control make KCONFIG_CONFIG=config.mainboardKatapult # this creates a deploy.bin python3 ~/katapult/scripts/flashtool.py -i can0 -u yourmainboarduuid -r # puts mainboard in katapult flash mode python3 ~/katapult/scripts/flashtool.py -f ~/katapult/out/deployer.bin -d /dev/serial/by-id/usb-katapult_your_mainboard_usb_id # flashes katapult to mainboard echo "STEP 2b - FLASH MAINBOARD so it works as a CAN BRIDGE, over KATAPULT" cd ~/klipper make clean KCONFIG_CONFIG=config.mainboardUSB2CANbb # cleans old files make menuconfig KCONFIG_CONFIG=config.mainboardUSB2CANbb # configuration for klipper-U2CBB. comment this line for automation make KCONFIG_CONFIG=config.mainboardUSB2CANbb # this creates klipper.bin sudo service klipper stop # mainboard still in katapult forced flash mode. so feel free to flash klipper can bridge on it! python3 ~/katapult/scripts/flashtool.py -f ~/klipper/out/klipper.bin -d /dev/serial/by-id/usb-katapult_yourmainboardusbid # flashes klipper-U2CBB to MAINBOARD sudo service klipper start echo "STEP 3a UPDATE TOOLHEAD KATAPULT so we can flash it easily" cd ~/katapult make clean KCONFIG_CONFIG=config.toolheadKatapult # clean old files make menuconfig KCONFIG_CONFIG=config.toolheadKatapult # comment out for full automation after once filled out! make KCONFIG_CONFIG=config.toolheadKatapult # build katapult deployer.bin python3 ~/katapult/scripts/flashtool.py -i can0 -u yourtoolheaduuid -r # put toolhead board into katapult flash mode python3 ~/katapult/scripts/flashtool.py -i can0 -u yourtoolheaduuid -f ~/katapult/out/deployer.bin # flash the katapult binary echo "STEP 3b UPDATING TOOLHEAD KLIPPER over KATAPULT" cd ~/klipper make clean KCONFIG_CONFIG=config.toolheadKlipper make menuconfig KCONFIG_CONFIG=config.toolheadKlipper make KCONFIG_CONFIG=config.toolheadKlipper sudo service klipper stop python3 ~/katapult/scripts/flashtool.py -i can0 -u yourtoolheaduuid -f ~/klipper/out/klipper.bin sudo service klipper start echo " The Klippper update flash script has finished. Hopefully all is working again :-)" flashCAN.sh