[IDEX] Nozzle position calibration with a second load cell probe

[DeB_ITA]

Hello to everyone!
We are modding a big home made IDEX printer (two toolheads) with klipper, by now everything works ok, we added load cells under the bed for a nice zeroing.

We also have already prepared a second load cell for fine adjustement of the 2 nozzle offsets.

We took sime time experimenting but it looks like klipper cant manage more load cells.
Is there any chance to use direclty klipper connected to the second ADC/Load Cell or we need to use a second MCU and simulate a simple endstop?

Thank you every one!
Marco

[hcet14]

@DeB_ITA

a big home made IDEX printer

How big is it? Could you please post a picture?

[DeB_ITA]

it’s a 66x33x80

[hcet14]

width x height x length?

photo?

[DeB_ITA]

[hcet14]

Wow! Nice.

I’m quite sure that Klipper supports just one probe! Community, please correct me if this statement is wrong.

You could use an attachable probe like Klicky-Probe GitHub - jlas1/Klicky-Probe: Microswitch probe with magnetic attachement, primarily aimed at CoreXY 3d printers · GitHub and do something like this

GitHub - oldfar-t/Side-Swipe-Magnetic-Probe: Welcome to the Side Swipe Magnetic Probe for Voron...

or

GitHub - chestwood96/SlideSwipe

for both of your toolheads to automate the probing process.

Or you could switch between your two load cells electronically.

[Tinman-FP]

I ran into the same issue. I have built a Rat Rig 500 IDEX. I needed to use 2 Beacon bed scanners for nozzle offset calibration. The standard klipper only allows one z probe instance. I modified Klipper to allow me to use both beacons for what I needed. Feel free to use my mod, but please let me know how it works for you and use it at your own risk. GitHub - Tinman-FP/Klipper-Modifications: Modified versions of Klipper · GitHub

Tinman

[hcet14]

I like your approach (This fork starts from upstream Klipper and vendors Beacon into the tree so that Beacon can support multiple configured sensors without forcing every workflow to address them with SENSOR= every time. Klipper-Modifications/docs/tinman_multi_beacon.md at tinman/dual-z-probe · Tinman-FP/Klipper-Modifications · GitHub ) to implement two z probes in Klipper.

I guess your klippy.log is dirty, which brings me back to New proposal for Klipper "extension" support .

Does anybody know if there is any development for an easy handling of extensions and still being “not dirty” with genuine Klipper?

[Tinman-FP]

I don’t believe it is. It would be nice if it were, I would like to have a “clean”. Install myself. I have seen similar issues and requests going back to 2022 and I wanted mine to work now.

[3dcoded]

The closest I’ve seen to a functional plugin system was this. I tested it a while ago and it looks promising, but it’s not “official”

Klipper RPC Shim library

Shortly speaking, sometimes I think custom extensions can live outside of the Klippy/Klipper process. Here is the API, and it should be enough for most basic stuff. I see the Moonraker as the perfect example of a klipper extension. This library is supposed to be used as part of the daemon/service that connects to the Klipper socket. Declares supported functions and probably loads macros to call those methods. Some missing pieces, for now: Macros should be loaded by the external installe…

[hcet14]

I missed

Klipper RPC Shim library

Shortly speaking, sometimes I think custom extensions can live outside of the Klippy/Klipper process. Here is the API, and it should be enough for most basic stuff. I see the Moonraker as the perfect example of a klipper extension. This library is supposed to be used as part of the daemon/service that connects to the Klipper socket. Declares supported functions and probably loads macros to call those methods. Some missing pieces, for now: Macros should be loaded by the external installe…

Thank you.
Interesting, what do you think @Tinman-FP?