Krupski:
Well, I see what you are saying, but I find it hard to believe that Dallas / Maxim would allow a possible read error like that to ever occur.
The old fashioned way to deal with changing values like this is to read everything twice and then compare. Maxim provided another option. I have a pressure sensor that works the same way, requiring a burst read to insure that the data is read atomically. One could imagine ways to latch the data other than on the falling edge of CS.
Krupski:
So, what I plan to do is setup a test where I set the time to something like 23:59:59 and then just keep reading it as fast as the Arduino can and see if a misread ever occurs.
Be wary of the false negative result.
Krupski:
If it does, then I guess my driver will have to do a read, wait "some" amount of time (TBD) then read again and compare the two to prevent that problem from ever happening.
Why would you do that instead of reading the registers all at once?