Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    Which Arduino...? Commented Sep 18, 2018 at 22:17
  • Please tell what the ID is for (add the extra information to your question). Reading the eeprom does not wear it. With Option 1, the arduino dumps data by itself. That is odd. There are at least 10 other options. An other option is to include a .h file that has a generated ID. The compiler can put the compilation date and time in the sketch. The smallest arduino board can still do some decrypting, so you might put an encrypted ID in the arduino. Some arduino boards have a microcontroller that has an ID of its own. All the 1-Wire devices have an ID, just add a 1 dollar 1-Wire device. and so on. Commented Sep 19, 2018 at 2:19
  • I have added some examples to the top post. And about the eeprom I was talking about constantly rewriting the eeprom that it might wear it, every new sketch would have its own data set that would be readable from the Arduino using the computer. Commented Sep 19, 2018 at 6:00
  • Option 1 and 3 are kind of identical. Commented Sep 19, 2018 at 9:37
  • Option 3 would eliminate the need to setup a serial connection in every sketch. And I don't know if its possible to dump the hex file from every Arduino model. But beyond these points yes, option 1 and 3 are almost identical. I did not try option 3 in practice yet, but I think that it is possible to achieve a working edit/write/read/decode process. Commented Sep 19, 2018 at 13:01