-
Klipper does not have an official plugin system. Discussions about this are ongoing, but nothing tangible yet. Without such a system, the hotplugging of MCUs and associated configurations seems like targeting unknown modifications and their behavior, finally putting the burden of failure and maintenance on Klipper.
-
As far as my understanding goes, the host and the MCUs perform an intricate handshake at startup to also validate the same protocol and feature sets, etc. While surely not impossible, switching this into a hotplugging architecture sounds like complex work.
-
For simpler MCUs like the quoted ADXL, an easy workaround exists: Put its configuration into an included cfg. (Un)commenting this is only minimal work and usually not done regularly.
My personal view:
- Yes, it is an interesting feature, but with a low priority
- Working on fundamental improvements like overhauling the homing system or providing a general plugin interface seems a lot more rewarding with a much higher user impact.
- Unfortunately, the developers here refuse to dedicate 120% of their time (including the night) to Klipper despite having been called to do so numerous times.