peac
October 26, 2022, 3:54pm
1
Hi,
I’ve been redirected from the discord to discourse to ask that this stale issue is reopened :
opened 10:36PM - 22 Jan 22 UTC
closed 12:07AM - 07 Mar 22 UTC
Stale
I'm not sure if this is a bug or a feature request, or something in between.
… I have a custom system with several (2, but possibly more) MCUs attached to a Raspberry pi. The ability to easily integrate multiple MCUs is, IMO, one of the strongest "selling" points for klipper!
Today I tried to tidy up my configuration using the [board_pins] feature. Based on my reading of the docs, I tried the following in my printer.cfg (highly abbreviated):
[board_pins mcu_pins]
mcu: mcu
aliases:
extruder_heater=PA7
[board_pins mcu1_pins]
mcu: mcu1
aliases:
extruder_sensor=PA1
[extruder]
heater_pin: extruder_heater
sensor_pin: extruder_sensor # Nope
This does not work. Klipper looks for and cannot find an alias 'extruder_sensor' on the first MCU ('mcu'), even though it was explicitly declared to be on 'mcu1' I had to modify all the references to mcu1 aliases to explicitly indicate mcu1, as follows:
[extruder]
heater_pin: extruder_heater
sensor_pin: mcu1:extruder_sensor # Works, but not so nice...
In this form it works. But this means that in order to use pin aliases, one must still explicitly reference some details of the hardware setup. This kind of ruins the nice abstraction that could otherwise be achieved.
I don't know if this was an oversight, a bug, a well-thought-out policy, or a "get-to-it later" situation. But thanks for listening!
Thank you
I am using the Manta M8P V2 and the Oribiter SO3 toolboard. The problem is the SO3 config uses aliases for the tool board and the Manta has many of these same pins which is a problem for klipper as the alias pins form the SO3 tool board should belong to SO3 and Manta pins to the Manta not both or shared!