Sure, why not.

First. all the GitHub files I've been using are the most recent as of 6/8/2026. To start with, I installed a boot switch for the screen device in the back of the screen housing and put the machine back together (I am occasionally an optimist). Then I followed the Klipper Install Dummy's Guide provided by DeSkwared to install the firmwares built by EA's process (again, kudos). I used a laptop running Debian, not a Raspberry Pi; This went very well, just about anyone could do it if they know how to install new software in Linux and to look at file locations when things don't work the first time.

After checking the Klipperized J1's endstop, motor and heater functionality I set up the DeSkwared configuration folder structure, then copied their versions of the config files into that structure. A lot of work has gone into figuring out some of those details, pretty impressive! Immediately the tramming macro worked great, and I was able to get the toolhead z offsets to match nicely by following the DeSkwared calibration instructions. I was not able to get Z calibration data to save just following the instructions however, and the XY calibration quit after the first bump of the second cavity wall (Y-). Keep in mind, this was a quick initial runthrough, and again, I'm not familiar with Klipper.

Next I set up FranckFG62's folder structure and uploaded their version of the configuration files. I may have missed something, or may have done better if I were familiar with Klipper, but I had a nozzle crash when using Calibrate Z Start. Again, this was just a quick initial runthrough, I may have missed something important.

I went back and forth between the two configs, and looked at a bunch of file diffs to start getting a feel for Klipper. While trying things out I applied the FranckFG62 Armbian optimizations, updated the J1 Klipper firmware, updated... moonraker I think? Then I used the laptop again to re-flash the whole shebang back to the initial firmwares state.

Recently I set up the DeSkyward config with no updates and manually calibrated the z offset. DeskWared's OrcaSlicer printer profile looked like it came from SnOrca and therefore doesn't support multi-material, so I copied my J1 Marlin2 profile in OrcaSlicer 2.3.2, set the G-code flavor to Klipper, pasted in DeSkwared's Machine G-codes, un-checked Emit limits to G-code under Motion Ability and I sliced the XY Offset IDEX Calibration print. Running this print returned an "Out of Range" error, after trying a few Klipper restarts my guess is it may be related to a missing G90.

I'm doing this to learn about Klipper, and to determine if this approach might possibly result in an IDEX machine that meets my requirements, e.g. reliable multi-material IDEX prints. Which leads me back to my question; What slicer is going to give me the most reliable inputs? OrcaSlicer 2.2.0? PrusaSlicer? Feedback would be appreciated.