Claudio Prezzi

@openhardwarecoza If I understand your code correctly, you use the smoothie sd card via the mounted device, not over USB serial commands, right?

@DouglasPearless Thank you for the information. That makes sense. Setting the environment variable with export only survives in the same terminal session.

Yes, I also prefer not to use USB MSD as it's better to switch that off for performance reason (also less disconnect problems). I already have the USB implementation (mostly)...

I belief that the user should always initiate the connection because on some machines it's not save to connect without user knowing it (i.e. eleksmaker machine activates laser on connect!).

The planned getFeatureList command could be easily extended by featuresLaser, featuresMilling or a "serial number" if I can detect those infos somehow. What about having a firmware configuration dialog in...

If we can detect some machine serial number, we could name that machine and show that name in the COM-Port dropdown.

The problem with reading the config (like laser module, spindle module, laser mode...) from the firmware is, that we don't know if the user has configured the firmware correctly.

What do you think about that: - If the user would have to define a machine profile for every machine, not one profile per machine type, we could store the...

And the other way around: - If the user selects a machine profile, we could try to open the last known port for this machine.

On grbl, the user can store an idetification string with $I=xxxxx, but Smoothieware and TinyG don't have such a feature, as far as I know.