Daylight Savings Time trouble - AVS Forum
Forum Jump: 
 
Thread Tools
post #1 of 7 Old 03-03-2012, 07:09 AM - Thread Starter
Member
 
schultdw's Avatar
 
Join Date: Mar 2008
Location: DFW
Posts: 85
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 13
Once again I have been tilting at the early DST change windmill. The problem happens (mostly) exactly one month prior to the scheduled change on most DFW area stations. (The ones I watch anyway.) This time around I was presistant enough so that a local station (the only one that ever responded) actually pushed this probelm upstream to their hardware provider.

I was amused at the response which was:

1) A correct implementation would work.
2) It can't be a serious problem because we haven't heard about it.

1 is obviously false to anyone who can read the ATSC specification. (annex A of A/65) The system time table provided in the OTA data stream includes the current date and time plus three values to control the DST switch. While the day of month and hour is provided, the month isn't. So when the station starts broadcasting the day of the change as being the 11th on 11 Feb. it should be expected that receivers will change on 11 Feb. (The error goes away on 12 Feb. because the DST status flag hasn't changed and the day of month no longer matches.)

2 is hilarious because it took a lot of persistance on my part before the local station forwarded my complaint to Triveni. It wasn't too hard to find threads here about this problem so it isn't the case that no one has seen it. It is just the case that complaints haven't filtered up to the hardware manufacturer.

But at this point Triveni appears uninterested in fixing what they perceive as a non-problem.
schultdw is offline  
Sponsored Links
Advertisement
 
post #2 of 7 Old 03-03-2012, 08:32 AM
AVS Special Member
 
Scooper's Avatar
 
Join Date: Nov 2000
Location: Youngsville, NC USA
Posts: 5,062
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 3 Post(s)
Liked: 15
You're really late to this party - so let me give you the party line -

You're problem is probably caused by the firmware of your ATSC receiver (be it TV, DVR, set top box, whatever) not correctly intrepreting the code for DST.

You CAN put antennas on your owned and/or controlled property...
http://www.fcc.gov/mb/facts/otard.html

Being A Beacon of Knowledge in the darkness of FUD
Scooper is offline  
post #3 of 7 Old 03-03-2012, 09:12 AM - Thread Starter
Member
 
schultdw's Avatar
 
Join Date: Mar 2008
Location: DFW
Posts: 85
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 13
Quote:
Originally Posted by Scooper View Post

You're really late to this party - so let me give you the party line -

You're problem is probably caused by the firmware of your ATSC receiver (be it TV, DVR, set top box, whatever) not correctly intrepreting the code for DST.

Then please explain to me how a receiver is supposed to know you mean 11 March when you set day of month to 11 on 11 February?

From Annex A of A/65:

Quote:


When the transition into daylight saving time is within less than one month,
the DS_day_of_month field takes the value day_in, and the DS_hour field
takes the value hour_in. The DS_status bit is 0 indicating it is not yet
daylight saving time. (The transition is to occur on the day_in day of the
month at hour=hour_in; for example, if the transition were on April 15 at
2:00 a.m., then day_in=15 and hour_in=2).

schultdw is offline  
post #4 of 7 Old 03-03-2012, 10:56 AM
DAP
AVS Special Member
 
DAP's Avatar
 
Join Date: Mar 2001
Location: San Jose, CA
Posts: 1,226
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 13
I have yet to see any PVR handle daylight savings time correctly.
At least on MythTV, it only screws up the wakeup time for the first recording after the transition, so one recording once a year (the other error has the system wake up an hour early, so it goes back to sleep and wakes up at the correct time. It is only when it wakes up an hour late that it screws up a recording).
DAP is online now  
post #5 of 7 Old 03-03-2012, 04:27 PM
AVS Special Member
 
spwace's Avatar
 
Join Date: Jan 2002
Location: Colfax, CA
Posts: 3,760
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 3 Post(s)
Liked: 20
Quote:
Originally Posted by schultdw View Post

Then please explain to me how a receiver is supposed to know you mean 11 March when you set day of month to 11 on 11 February?

From Annex A of A/65:

Quote:


When the transition into daylight saving time is within less than one month

As indicated, the value would not be set to 11 until at least the 12th of February, otherwise it would be set to 0.
spwace is online now  
post #6 of 7 Old 03-03-2012, 06:48 PM - Thread Starter
Member
 
schultdw's Avatar
 
Join Date: Mar 2008
Location: DFW
Posts: 85
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 13
Quote:
Originally Posted by spwace View Post

As indicated, the value would not be set to 11 until at least the 12th of February, otherwise it would be set to 0.

My complaint is that it was set to 11 on the 11th by most stations in the DFW area. Triveni thinks that is just fine and so far refuses to even consider the possibility of thinking about changing it.
schultdw is offline  
post #7 of 7 Old 02-14-2014, 01:47 PM
Advanced Member
 
Pete-N2's Avatar
 
Join Date: Jun 2009
Location: Lynchburg, VA
Posts: 553
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Liked: 21
On your post on the on the DTVPal thread last week you stated that you had complained to the FCC. What was the basis of your complain. What data did you submit.
Pete-N2 is offline  
Reply HDTV Technical

User Tag List

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off