Daylight savings time ends on 1 November which means that stations should begin sending PSIP data to that effect on 2 October. The details on how this process should be managed are in ATSC A/65, Annex A and FCC regulations require that all except low power stations follow the standard.
Going against past performance, things seem to have improved. Only three stations started the process early (yesterday):
KDTN (RF 29)
KFWD (RF 9)
KDTX (RF 21)
Keep this up and I may be able to stop updating this page twice a year. On the other hand, just four stations began the process today as they should:
KTXA (RF 18)
KTVT (RF 19)
KXAS (RF 24)
KXTX (RF 36)
Several more join the party today. A day late but this isn't a big problem since nobody sends a months worth of schedule data.
WFAA (RF 8)
KERA (RF 14)
KTXD (RF 23)
KPXD (RF 25)
KMPX (RF 30)
Too many stations are just not bothering at all: KODF, K07AAD, KHPK, KBOP, KNAV, KDFI, KAZD, KDAF, KUVN, KDFW. May low power so technically exempt but a few full power stations thata aren't.
KUVN finally jointed the party today:
KUVN (RF 33)
(While that happened, they did strange things to their time data.)
Today is the day to "fall back". A couple of stations did this stupidly and wrong. The way it is supposed to go is that after all locations within the broadcast area have completed the transition (only an issue close to time zone dividing lines) the station set DS_day and DS_hour to zero and DS_status to zero as well to indicate out of daylight savings time. Since DFW is far from a time zone boundary, that was at 2AM DST.
Two stations (KDTX, KFWD) zeroed out DS_day and DS_hour yesterday at 9PM then dropped DS_status at 2AM this morning. This would cause a problem if you were checking their program guide data during that time as the times would be incorrect. Here is the data from KDTX:
KDTX (RF 21)
The remaining stations, at least those that didn't ignore this completely, changed over between 2AM and 4AM (DST).
I noticed that 4 stations did the DST change in the stupidest way possible: they shifted the time they were transmitting by 3600 seconds. (Now an hour slow, more or less.) This doesn't work. KODF-LD, K07AAD, KHPK-LD, and KNAV-LD (all low power stations) get the booby prize here. (They of course never changed DS_status which remained firmly zero or out of DST.)
This is how things ended up. (My raw time data from the system time table packets.)
stt: -1, 8vsb:7, 1604346949, -3618.346, 1288378549, 18, 0, 0, 0 stt: -1, 8vsb:8, 1604346951, -18.422, 1288382150, 17, 0, 0, 0 stt: -1, 8vsb:9, 1604346952, -0.890, 1288382170, 18, 0, 0, 0 stt: -1, 8vsb:10, 1604346954, -3619.360, 1288378553, 18, 0, 0, 0 stt: -1, 8vsb:14, 1604346964, -11.001, 1288382171, 18, 0, 0, 0 stt: -1, 8vsb:18, 1604346966, -0.700, 1288382184, 18, 0, 0, 0 stt: -1, 8vsb:19, 1604346968, -1.178, 1288382185, 18, 0, 0, 0 stt: -1, 8vsb:20, 1604346969, -1205696526.838, 82685658, 15, 0, 0, 0 stt: -1, 8vsb:21, 1604346971, -0.832, 1288382188, 17, 0, 0, 0 stt: -1, 8vsb:22, 1604346973, -3618.370, 1288378573, 18, 0, 0, 0 stt: -1, 8vsb:23, 1604346975, -7.101, 1288382168, 0, 0, 0, 0 stt: -1, 8vsb:24, 1604346977, -1.258, 1288382194, 18, 0, 0, 0 stt: -1, 8vsb:25, 1604346979, -2.452, 1288382194, 17, 0, 0, 0 stt: -1, 8vsb:27, 1604346984, -0.979, 1288382202, 18, 1, 0, 0 stt: -1, 8vsb:29, 1604346987, -1.133, 1288382202, 16, 0, 0, 0 stt: -1, 8vsb:30, 1604346988, 27618.188, 1288409825, 18, 0, 0, 0 stt: -1, 8vsb:31, 1604346990, -17.918, 1288382190, 17, 0, 1, 0 stt: -1, 8vsb:32, 1604346992, -0.779, 1288382210, 18, 0, 0, 0 stt: -1, 8vsb:33, 1604346994, -19.328, 1288382193, 18, 0, 0, 0 stt: -1, 8vsb:35, 1604346996, -34.349, 1288382180, 18, 1, 1, 0 stt: -1, 8vsb:36, 1604346997, -18.798, 1288382197, 18, 0, 0, 0
The DST data is in the final three columns: DS_status, DS_day, and DS_hour. Two stations (KDFI, KDFW) still have DS_status as in DST and a couple (KAZD, KDFW) have a DS_day of 1. All full power stations that should know better and are required by FCC regulations to get it correct. Not that anyone at the FCC cares.
