Avoid errors if a secondary MCU is not connected

General Discussion
1

Basic Information:

Printer Model: Custom designed Cuore 3D printer
MCU / Printerboard: Octopus
Host / SBC: Raspberry pi 5, including nvme disk unit
klippy.log N/A

Dear all in some of my machines I use a shaping detector based on a MCU, in some printers I use two simultaneously, one for each axis to be tested, then, if I have no the sensors connected, I need to have the line where I call the related macros commented, otherwise I’ll get an error trying to start without the sensors, at opposite, if need to use the sensors, I’ll need to uncomment the aforementioned lines in order to make them working, then my question is, is there any way to avoid this currently, will it be implemented in a nead future, does it exist any way to override or avoid this error with some code in a macro?

2

Currently, Klipper requires all defined and used MCUs to be online when Klipper starts.
AFAIK, there is nothing in the pipeline or planned to change this behavior. The best advice is to work with some include statements and (un)comment as needed.

1 Like
3

This is exactly what I currently do, but I’m looking for something better