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

**URL:** <https://klipper.discourse.group/t/idex-nozzle-position-calibration-with-a-second-load-cell-probe/25922>\
**Category:** Features\
**Created:** [May 6, 2026, 12:10pm UTC](https://klipper.discourse.group/t/idex-nozzle-position-calibration-with-a-second-load-cell-probe/25922 "2026-05-06T12:10:04Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [May 10, 2026, 6:42pm UTC](https://klipper.discourse.group/t/idex-nozzle-position-calibration-with-a-second-load-cell-probe/25922/11 "2026-05-10T18:42:22Z")

</div>

I missed

> [@Klipper RPC Shim library](https://klipper.discourse.group/t/klipper-rpc-shim-library/25404):
>
> 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?

---

_[View the full topic](https://klipper.discourse.group/t/idex-nozzle-position-calibration-with-a-second-load-cell-probe/25922)._