This is related to my previous post, where I'm loosing position data on controller power off. It seems that in v295, in the setup(), it's "moving" the data to the next EEPROM section by setting the validdata flag to 0 in the current block. However, it doesn't write the new block immediately like it did in v294. This results in a period of time (after setup() and before the next EEPROM write), that there is no EEPROM data block that is marked as valid.
Long story short, a line was removed in v295 to do a writeEEPROMNow() in the setup. Please see attached compare screen shot and advise.
I did that because in normal use, the focuser will be operated by focusing moves extra, so it became redundant. On the next call that enables an eeprom write then that will trigger a valid flag.
I have done 296 now which restores it. Apologies
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is related to my previous post, where I'm loosing position data on controller power off. It seems that in v295, in the setup(), it's "moving" the data to the next EEPROM section by setting the validdata flag to 0 in the current block. However, it doesn't write the new block immediately like it did in v294. This results in a period of time (after setup() and before the next EEPROM write), that there is no EEPROM data block that is marked as valid.
Long story short, a line was removed in v295 to do a writeEEPROMNow() in the setup. Please see attached compare screen shot and advise.
I will take a look
I did that because in normal use, the focuser will be operated by focusing moves extra, so it became redundant. On the next call that enables an eeprom write then that will trigger a valid flag.
I have done 296 now which restores it. Apologies