I believe what I pulled out (in my desperation) was a statement that starts Klipper without any front end and produces a socket to connect to.
If I try klipper-repl
with /tmp/klippy_uds
I get:
but, if I look at the /tmp
directory, I see that there’s klipper_host_mcu
which, when run with klipper-repl
, I get:
Which never returns.
I’m posting this in the hope this tweaks on somebody.
@hcet14 I’m surprised that you would consider a two year old package as “quite old” - it says a lot regarding how much has been done to Klipper over what I would consider a little while.