volatile

[woleda]

Dear ckoern,
thank you for your hard work on this and for sharing!
I think I'm correct on this but not 100% sure:

packets.h:
// DP5_P2_TEXTCONFIG_REQUEST_SET = 0x02 changed to
// DP5_P2_TEXTCONFIG_REQUEST_SET = 0x04 LEIF
enum PID2_SUBTYPE_TEXTCONFIG_REQUEST{
DP5_P2_TEXTCONFIG_REQUEST_SET = 0x04,
DP5_P2_TEXTCONFIG_REQUEST_GET = 0x03,
};
Set PID2 to 0x04 to get volatile functionality (and not to ware out flash)

Best regards,
Leif Adelöw

ref: https://www.amptek.com/-/media/ametekamptek/documents/resources/products/user-manuals/amptek-digital-products-programmers-guide-b3.pdf?la=en&revision=1c16e5f8-448a-4fbb-a619-888600356971&hash=A94AE3AA759CA497018281C0A89848F7

[ckoern]

Hi Leif,

yes, there is a trade-off between wearing out the flash or storing the configurations between power-cycles. For our application we decided to rather store the configuration. The manual that you referenced also mentions that this is fine for most use cases (chapter 6.4). The flash should be able to sustain many thousends of read/write cylces.

Unfortunately, I changed jobs and have no longer access to the hardware, so I do not want to modify the code without being able to test it. If you need the volatile feature, I suggest you create a fork and change the request byte to x04 as you proposed.

[woleda]

Christian,
I was pretty sure you knew this. Made the comment to indicate for new cloners that this may become issue if always calling new config on start-up etc. I just cloned your work, made the change in local code and 'pip installed'. If you need access to hardware let me know. Let's leave it like this for know. Thanks again, Leif