Fully functional Klipper Firmware for Snapmaker J1/J1s is here! 🚀

Hi everyone,

I decided to pick up the idea of running Klipper on the Snapmaker J1 / J1s and took it all the way to completion!

All original features from Snapmaker’s stock firmware are now integrated into Klipper and fully tested on my own J1.

Key Highlights:

  • Easy Installation: You can switch from stock firmware to Klipper easily via a standard USB flash drive (no EDL mode required).

  • Easy Rollback: Returning to the original stock firmware can also be done via USB stick at any time.

  • Full Functionality: All calibrations, sensors, and dual-extruder features are working as expected.

Check out the GitHub repository for all files, documentation, and installation steps:

:link: GitHub - Nimrasol/KlipperSnapmakerJ1 · GitHub

Hope this brings your J1 / J1s as much joy as it does for me! Enjoy printing! :partying_face:

I am not intimate to the J1 - was it on Marlin before, or was it Klipper-ish from the beginning on?

The Snapmaker J1 originally runs on firmware based on Marlin, not Klipper. The touchscreen itself runs on Android. So this is a real Klipper port, not just a modification of the existing firmware. The goal is to unlock the full potential of the J1 with Klipper’s features and flexibility.

Ah, interesting! I was wondering how complicated such a thing is - I think the venerable SM 2.0 would benefit from a firmware refresh on Klipper basis also. And now with vibe coding making things faster, I am tempted to try this out, but perhaps looking at your project is the better way… how complicated was it after all? The SM 2 has CAN-bus-architecture and an RTOS basis - is this the same with the J1? Did this add complications?

The J1 actually has a somewhat different architecture. It also runs Marlin with Snapmaker-specific RTOS modifications, but unlike the SM 2.0, its main controller handles most of the hardware directly rather than communicating with separate modules over CAN bus.

One of the biggest challenges was reverse-engineering the original firmware, understanding the hardware, and adapting Klipper to work with the J1’s components.

Since the J1 touchscreen runs Android, I was able to use it as the Klipper host, eliminating the need for an external Raspberry Pi.

I think the Snapmaker 2.0 could also benefit a lot from Klipper! Some parts of my J1 port might be reusable, especially the general approach and software integration. However, the CAN bus architecture of the SM 2.0 would likely require additional development.

Unfortunately, I don’t own an SM 2.0, so I can’t say how much of the existing work could actually be adapted.

It would definitely be an interesting project to investigate!

In case of questions or ideas, join the Discussions board on github and talk with me and the other project members. We’d love to hear from you!

Hi, what to do if Updating has stopped at 60 %? The updating took 20 minutes now…

Thank you for any advice :wink:

I am upgrading originally from Evil Azrael’s Klipper, which is reflashed via EDL with v2.6.2 stock version.

So, problem solved.

What do you need is to flash MCU with Evil Azrael’s Klipper directly via back USB B port. What do you need is:

  1. Serial Port Assistant from Snapmaker (it is in Chinese but AI helps with translation)
  2. MCU FW like J1_MC_APP_V2.2.11_20231019.bin (about 400kB file)

Than - printer off, prepare Serial port assistant with binary file, connect the printer to PC with USB cable. You have just 6 seconds for start transfer of FW to printer after switching printer on.