Originally Posted by n0qcu
Your clocks are off today because DAYLIGHT SAVING TIME begins in exactly one month from today.
The clocks will reset tomorrow and be correct until one month before DST ends.
Its a bug in the software in the way it handles DST.
It is not a bug on the receiver side but a bug in the way stations handle the change.
I have been following this and complaining (to the stations and the FCC) about this for several years now. During the DST transition the station is supposed to set a field (DS_day_of_month) to the day of the change. Because the month isn't included in the data it is vital that this not happen too soon yet the stations (mostly because Triveni insists that their PSIP hardware is correct) set it a day early. So they set it to 9 and the receiver notices that today is the 9th. Therefore it is DST transition time. At midnight the date will roll over to the tenth and since they haven't also changed DS_status, the time will return to normal.
I had noticed that the standard that covers this (ATSC A/65) and is required to be followed by the FCC was not as clear as it should be. I pointed this out to ATSC and last August it was revised. It still isn't as clear as I would like but it is better.
This is not new as I found a web site for the Society of Broadcast Engineers
from 2008 that discussed this problem.
If you dig down to the diagnostics screen the "Next" field shows the next DST change. Check Monday and you will see that most say 9/3/2014.
Complain to both your local stations and the FCC. If I am the only one doing it, then I am just a crank.