(EBB) Add ability to give an EBB a 'name'

[EmbeddedMan]

It would be really slick if, on a given computer, you could have multiple EggBots, AxiDraws and WaterColorBots all plotting away from separate instances of Inkscape at the same time.

To support this, some way of choosing which EBB a given Inkscape connects to is needed. I have no idea how to do this in Inkscape, or if it's even possible. But no matter what, EBB will need a unique identifier.

So, this feature request is to add a new set of commands. One for writing down a new 'name', and one for reading back that name. This name string will of course need to be stored in Flash, as these parts have no true EEPROM, but that's not a big deal. (I think)

Many bonus points if this name also shows up in the device manager. :-)

[oskay]

I'd like to get this wrapped up soon if we can; AxiDraw multi-machine support is almost ready and this would help. So far as I can tell, this feature is working and usable.

We should likely add a note in the docs discouraging programmatic setting of the name tag (flash lifetime yada yada). Also, it might be good to use some example without an apostrophe, since those don't translate as well in the com port listings.

[EmbeddedMan]

So, you say the feature is working and usable - but we haven't added an EBB firmware command to support the naming yet, have we? I don't see it in the release notes. Can you clarify what's left to be done?

[oskay]

Look at the changes in the EBB_naming branch that you created?

[EmbeddedMan]

I think I'd forget the names of my kids if they didn't remind me. So, if the only thing to do just merge the branch and build a new version?

…

On Tue, May 8, 2018, 9:18 PM Windell Oskay ***@***.***> wrote: Look at the changes in the EBB_naming branch that you created? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#83 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAbeCNy5G--DpvwRftcCSn7rjYcCmoIDks5twlH3gaJpZM4O1aqe> .

[oskay]

I think that the firmware is built (but please double check)-- we'd need to merge, make those little updates to the docs, and build the windows updater program. I've already built a Mac updater for 2.5.4 -- please let me know if there is any reason not to make EBF_v254.unified.hex the new version.

(Also on the topic of updater programs: please update your the "Updating Your Firmware" section on your main EBB page, with a link to the much-easier-for-most-people version at: https://wiki.evilmadscientist.com/Updating_EBB_firmware )

[EmbeddedMan]

Ahh! Yes, that's a very good idea. Will do.

…

On Tue, May 8, 2018 at 9:56 PM, Windell Oskay ***@***.***> wrote: I think that the firmware is built (but please double check)-- we'd need to merge, make those little updates to the docs, and build the windows updater program. I've already built a Mac updater for 2.5.4 -- please let me know if there is any reason *not* to make EBF_v254.unified.hex the new version. (Also on the topic of updater programs: please update your the "Updating Your Firmware" section on your main EBB page, with a link to the much-easier-for-most-people version at: https://wiki.evilmadscientist. com/Updating_EBB_firmware ) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#83 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAbeCFOJpIv21RqwJstCbZ03VptQ3pXBks5twlrWgaJpZM4O1aqe> .

[EmbeddedMan]

The branch has been merged. The windows updater has been updated. The SchmalzHaus EBB documentation page has been updated. I see no reason why 2.5.4 should not be the new version.

[oskay]

Fantastic. Thank you!

[oskay]

I'm not seeing the Windows app. I'd expect it to be called EBBUpgraderGUI_v254.exe?