Quote:
Originally Posted by ericthegeek
The spec for ACK_TIMER has some ambiguity, so not everyone implements it the same way. I generally recommend avoiding ACK_TIMER and only using it if you absolutely have to.
This older thread has a lot of discussion about scheduling EEPROM write.
http://rdmprotocol.org/forums/showthread.php?t=1218
Specifically, see the paragraph in my post that starts with "Some people feel this way..."
|
thread is usefull thanks.
I didn't use ACK_TIMER at first, set address is successful but the controller (XMT-350) shows warning after setting address, I traced and found out its because of EEPROM write delay.
warning is annoyning , I will try use queue to handle that
seems a little complicated but it worths !
I also plan to implement SET DEVICE_LABEL, it is 32 bytes and write delay will be up to 100ms,