Simplify finding MCU IDs

[iamthesoy]

Is your feature request related to a problem? Please describe

With preconfigured OS images and pre-flashed boards becoming more and more common in printer kits, the only reason to SSH into the host is to run ls /dev/serial/by-id/* It works fine, but it would be cool if this wasn't needed, and would simplify the process for newbies.

Describe the solution you'd like

I was thinking that when editing .cfg files, an option in the right click menu that lists possible connected MCUs (which can be inserted when clicked on) would be a reasonably elegant solution - see poorly made mockup image This could be set to only appear on lines starting with serial: to reduce clutter.

Describe alternatives you've considered

No response

Additional information

No response

[pedrolamas]

Hi @iamthesoy, thank you for submitting this feature request.

Fluidd is just a web app that runs in the browser (client side) and uses Moonraker as the server-side data provider.

In order for Fluidd to implement such feature, Moonraker will first have to provide this data to Fluidd.

[matmen]

FWIW this just got merged: https://github.com/Arksine/moonraker/pull/798

[pedrolamas]

FWIW this just got merged: Arksine/moonraker#798

Assuming these changes indeed provide the data we require, I guess we can now indeed start working on providing this feature! 🙂

[pedrolamas]

Parallelly to this, I have been considering a startup wizard for when there is no printer.cfg file, where the user could just select one of the sample configs that are included with Klipper, and we would create the initial printer.cfg for the printer!

Now I guess we can also check the printer MCU address and add that to the generated printer.cfg file! 😁

[pedrolamas]

I just checked... and I'm impressed!!