WWVB Atomic Clock GUI Part 2

The 26-bit time word is encoded into a 31-bit code-word, by
calculating five additional parity bits that are appended to it
because of the error-correcting linear block code Hamming(31, 26),
based on the equations provided below. This codeprovides the receiver
with the capability to correct one error and to detect up to two
errors in the 31-bit word. time_par[0] = sum(modulo 2){time[23, 21,
20, 17, 16, 15, 14, 13, 9, 8, 6, 5, 4, 2, 0]} time_par[1] = sum(modulo
2){time[24, 22, 21, 18, 17, 16, 15, 14, 10, 9, 7, 6, 5, 3, 1]}
time_par[2] = sum(modulo 2){time[25, 23, 22, 19, 18, 17, 16, 15, 11,
10, 8, 7, 6, 4, 2]} time_par[3] = sum(modulo 2){time[24, 21, 19, 18,
15, 14, 13, 12, 11, 7, 6, 4, 3, 2, 0]} time_par[4] = sum(modulo
2){time[25, 22, 20, 19, 16, 15, 14, 13, 12, 8, 7, 5, 4, 3, 1]}
The sum(modulo 2) operation is equivalent to an exclusive OR logic
operation. The 31-bit word is placed in the time frame in locations
{time_par[4], time_par[3],＃time_par[0], time[25],time[24],＃time[0]},
corresponding to bits 13-28, 30-38, and 40-46, as shown in Table 1.
The LSB, bit time[0], is repeated on bit 19, which is a marker in the
legacy protocol (i.e., the duration of its high power portion is only
200 ms).
6
4.4. Indications for Daylight Saving Time (DST) and Leap Second The
5-bit word {dst_ls[4], dst_ls[3]＃ dst_ls[0]} in locations 47-48 and
50-52 is used to indicate whether DST is in effect or not or whether
itis starting or ending today, and is also used to indicate whether a
positive or negative leap-second is scheduled at the end of this month
(at minute 23:59 UTC). These four different possible indications for
the DST state and the three for the leap second are all merged into a
single 5-code word that allows for the detection of errors,
particularly for the two most common combinations to be found in this
5-bit field (highlighted in Table 4). Table 4 maps each of the 12
legitimate values for the 5-bit dst_ls word into the corresponding
values of the 2-bit indication dst_on and the 2-bit indication
leap_sec. Table 5 and Table 6 list the significances for the various
values of these two fields respectively. Table 4 - Decoding table for
DST and leap second indication word {dst_ls[4], dst_ls[3]＃ dst_ls[0]}
DST and leap second code word
dst_ls[4] 1 2 3 4 5 6 7 8 9 10 11 12 0 1 0 1 0 1 0 0 1 1 1 1 dst_ls[3]
1 0 0 0 0 0 1 1 1 1 1 1 dst_ls[2] 0 1 0 1 1 0 1 1 0 0 1 1 dst_ls[1] 0
1 1 0 0 0 0 1 0 1 1 0 dst_ls[0] 0 0 1 1 0 0 1 0 1 0 1 0
significance (DST and leap second bits)
dst_on[1] 0 1 1 0 0 1 1 0 0 1 1 0 dst_on[0] 0 0 1 1 0 0 1 1 0 0 1 1
leap_sec[1] 0 0 0 0 1 1 1 1 1 1 1 1 leap_sec[0] x x x x 0 0 0 0 1 1 11
Bits {dst_on[1], dst_on[0]}, which are to be extracted from the dst_ls
word according to the decoding scheme provided by Table 4, indicate
the DST state, as shown in Table 5 and explained as follows: Bit
dst_on[1] is set to 1 at 00:00 UTC on the first Sunday of the DST
period (in the spring) and is reset at00:00 UTC on the last Sunday
ending the DST period (in the fall). It is to be noted that since
00:00 UTC occurs a few hours before midnight in all time zones in the
United States, and the DST transitions are to be implemented after
midnight, the transitions in the dst_on[1] bit occur a number of hours
before a receiving device is required to make the appropriate 1-hour
correction, depending on which time zone the device is in. For this
reason, the second bit, dst_on[0], serves to identify the period of
time in which dst_on[1] has indicated that the DST period has started
(or ended), but this change is not to take effect yet, since the time
for that (currently set at 2 AM on a specific Sunday) has not yet been
reached. In the absence of this second bit, a devicethat first
receives the time in the afternoon/evening on the last Saturday of the
DST period (or the last one before a DST period starts), after 00:00
UTC, which is still before 6PM PST, for example, might incorrectly
apply the DST timechange a few hours prematurely. Bitdst_on[0] follows
the transitions onbit dst_on[1] with a delay of 24 hours (i.e., at
midnight UTC between Sunday and Monday), in alignment with the
corresponding 2-bit indication of the legacy AM/PWM protocol. The
state of dst_on[0] allows the receiver to determine whether the DST
state indicated by dst_on[1] has been valid for over a day, in which
case the appropriate time correction is tobe implemented immediately.
If dst_on[0] indicates that the first day since the last DST
transition is not over yet, then the RCC should not apply the new DST
state in its time calculation until the appropriate time is reached
(currently set at 2 AM in the local time zone).
7
Table 5 - DST state/transition word {dst_on[1], dst_on[0]}
dst_on[1] 0 1 1 0 dst_on[0] 0 0 1 1 significance
DST has not been in effect for over a day Apply standard time
correction with respect to UTC. Next transition is into DST DST starts
today Do not apply the 1 hour DST correction until the appropriate
time has been reached.* DST has been in effect for more than a day
Apply one hour less of time correction with respect to UTC. Next
transition is out of DST. DST ends today Continue to apply the DST
correction and return to standard time only once the appropriate
instance has been reached. *
* The combinations 01 and 10 can only be present for 24 hours
(duringthe entire Sunday of the transition).
Bit leap_sec[1], when set to 1, indicates that a leap second is
scheduled at the end of the current month, as indicated in Table 6. At
00:00 UTC at the beginning of each month its value is reset to zero if
no leap second is scheduled for that month (i.e. all minutes will be
of 60 seconds), or is set to 1 atthat instance if the last minute of
that month is to be either extended to 61 seconds or shortened to 59
seconds. Historically, only the months of June and December have been
occasionally extended by one second, but the broadcast format can
accommodate a leap second in any month, which may be positive
ornegative. Table 6 - Leap second advance notification bit leap_sec
leap_sec[1] 0 1 1 leap_sec[0] x 0 1significance no leap second at the
end of this month negative leap second scheduled for the last minute
of this month positive leap second scheduled for the last minute of
this month
For the case of a positive leap second, the time frame representing
the extended 61-second minute, starting at 23:59:00 UTC, will have bit
59 repeated (a marker in the legacy broadcast and a ※0§ in PM), after
which bit leap_sec[1] will be reset to 0. For the case of a negative
leap second the time frame representing the shortened minute will have
bit 59 removed, such that bit 0 of the next minute (i.e. minute00:00
UTC of the first day of next month) will follow immediately after bit
58. The timing of minute-frame 00:00 UTC on the first day of the month
following the implementation of the leap second, as well as the timing
of the subsequent frames, will reflect the corrected time, and no
further indication will be found inthem for the leap second that has
been implemented (the UT1 time correction information that is
available in the legacy frame in the AM/PWM modulation is not
providedin the PM signal).
4.5. Notice Bit Bit 49, which is a marker in the legacy AM/PWM signal,
indicates when a notice fromNIST is posted at the website, as
specified in Table 7. When set to 1,it may indicate that a change is
imminent, a temporary shutdown is planned, or whatever other message,
the details of which may be found at
http://www.nist.gov/pml/div688/grp40/wwvb.cfm.It is expected that most
consumer market products will ignore this bit.Table 7 - Notice Bit
(bit 49)
Notice 0 1 significance nothing to report notice regarding WWVB
broadcast may be found at NIST website
8
4.6. Advance Notification for Next DST Transition Bits 53-58,
{dst_next[5], dst_next[4]＃dst_next[0]}, usually represent one of eight
possible schedules for the upcoming DST transition (i.e., either when
the DSTperiod is to start or end), but may also convey one of 8 other
possible
messages, as specified in Table 8. When DST is in effect, as is the
case during the summer, the DST schedule word provides advance
notification for the end of the DST period in the fall, whereas when
DSTis not in effect, as is the case in the winter, the DST schedule
word provides advance notification for the beginning of the next DST
period in the upcoming spring. The start/end times for the DST period
are always during the night betweena Saturday and a Sunday, but the
specific Sunday has changed over the years and may change again in the
future. As can be seen in Table 8, 24 combinations of day and time are
supported for possible start/endtimes for the DST period, resulting in
a total of 48 different 6-bit combinations. Historically, the DST
transition in the US is to be implemented at 2 AM (local time), but
combinations have been reserved for the possibility of this time being
set at 1 AM or 3 AM, asis done in other countries. A total of eight
Sundays are covered by the24 combinations, both for the beginning as
well as for the end of the DST period. For combinations 49-56 the
dst_on state has no relevance, as these do not represent specific
start/end times. Message 49 is reserved for the case of a new DST
schedule being defined that is not among the 24 predefined ones,
message 50 is reserved for the possibility of DST being cancelled,
while maintaining standard time, and message 51 hasbeen reserved for
the case of DST being permanently on (i.e., ahead ofstandard time by
one hour). Additionally, five different words (messages 52-56) have
been reserved, for which specific messages may be defined in the
future, such as emergency messages.
9
Table 8 - DST transition schedule word (and reserved messages)
dst_on [1]
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
50 51 52 53 54 55 56 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 x x x x x x x x
DST schedule word dst_next time and action for implementation (or
reserved message) of next DST transition [5] [4] [3] [2] [1] [0] day
time (local)
1 1 1 0 1 0 1 1 1 0 0 0 0 0 0 1 0 1 1 1 1 0 1 0 1 0 1 0 1 1 1 1 0 0 1
0 0 0 0 1 1 1 0 0 1 1 1 0 1 0 1 1 1 0 1 1 1 0 0 1 1 1 1 1 0 1 0 0 0 0
0 0 0 0 1 0 1 1 1 1 1 1 1 1 0 1 0 1 0 0 0 0 1 0 0 0 1 0 0 1 0 1 1 1 0
0 0 1 0 1 1 1 0 0 0 0 1 0 0 1 1 1 1 0 0 1 1 1 0 0 0 1 1 0 0 1 0 0 0 0
0 1 0 1 1 0 1 1 1 0 1 1 0 1 0 0 0 1 0 1 0 0 1 0 0 0 0 0 0 1 1 1 1 1 1
1 0 0 1 0 0 0 1 0 1 0 1 1 0 0 0 1 1 1 0 1 1 1 1 1 1 0 0 0 0 0 1 0 0 1
1 0 0 0 1 1 0 1 1 0 1 1 1 1 0 1 0 0 1 1 1 0 1 1 1 0 1 0 0 0 0 0 0 0 0
0 1 0 1 0 0 1 1 1 0 0 0 0 1 0 1 1 1 0 1 0 0 0 0 0 0 0 1 1 1 0 0 0 1 0
1 0 1 1 0 0 1 1 0 1 0 1 0 0 1 1 0 0 0 0 0 0 0 0 1 1 1 0 0 0 1 1 1 1 0
0 1 0 0 1 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 1 1st Sunday of March 2nd
Sunday of March after 0:59AM, 3rd Sunday ofMarch skip from 4th Sunday
of March 4th Sunday since ※M§ 1:00AM to 5th Sunday since ※M§ 2:00AM
6th Sunday since ※M§ 7th Sunday since ※M§ 1st Sunday of March 2nd
Sunday of March after 1:59AM, 3rd Sunday of March skip from 4th Sunday
of March 4th Sunday since ※M§ 2:00AM to 5th Sunday since ※M§ 3:00AM
6th Sunday since ※M§ 7th Sunday since※M§ 1st Sunday of March 2nd
Sunday of March after 2:59AM, 3rdSunday of March skip from 4th Sunday
of March 4th Sunday since ※M§ 3:00AM to 5th Sunday since ※M§ 4:00AM
6th Sunday since ※M§ 7th Sunday since ※M§ 4th Sunday before ※N§ 3rd
Sunday before ※N§ after 0:59AM, 2nd Sunday before ※N§ instead of 1st
Sunday before ※N§ 1:00AM move 1st Sunday of November back to 2nd
Sunday of November 0:00AM 3rd Sunday of November 4th Sundayof November
4th Sunday before ※N§ 3rd Sunday before ※N§ after 1:59AM, 2nd Sunday
before ※N§ instead of 1st Sunday before ※N§ 2:00AM move 1st Sunday of
November back to 2nd Sunday of November 1:00AM 3rd Sunday of November
4th Sunday of November 4th Sunday before ※N§ 3rd Sunday before ※N§
after 2:59AM, 2nd Sunday before ※N§ instead of 1st Sunday before ※N§
3:00AM move 1st Sunday of November back to 2nd Sunday of November
2:00AM 3rd Sunday of November 4th Sundayof November DST transition
occurs at different time* no DST period scheduled this year DST in
effect for this whole year reserved 1 reserved 2 reserved 3 reserved 4
reserved 5
x = either 0 or 1, "M"=first Sunday in March, "N"=first Sunday in
November * DST transition to occuroutside of defined schedules, so no
advance notification available.
10
5. Bit Allocation in Message Frame
Table 9 specifies the bit allocation for the message frames. The
message frame starts with a 13-bitsynchronization word, as defined in
subsection 4.2. The LSB of the time word, time[0], is available on bit
19 (marker) in message frames too, as in time frames. This allows
receivers that are resolving timing uncertainties only below one
minute to be able to use message frames for that purpose, assuming
that they are experiencing sufficiently high SNIR for this single 200
ms symbol to suffice. The Notice bit in location 49 (marker),
functions in message frames as defined for timeframes in subsection
4.5. The 42 bit word in the remaining locations, {data[41], data
[40],＃data[0]}, defines the contents of the message and may contain
fields indicating the address to which the message is intended, the
total length of the message (may extend over multiple frames), etc.
Table 9 - Allocation of bits in one-minute message frame - (legacy
protocol inblack, PM in blue)
Second 0 1 2 3 4 5 6 7 8 9 LegacyAM/PWM Marker min_40 min_20 min_10 0
min_8 min_4 min_2 min_1 Marker Phase sync_M[12] sync_M[11] sync_M[10]
sync_M[9] sync_M[8] sync_M[7] sync_M[6] sync_M[5] sync_M[4] sync_M[3]
Second 10 11 12 Legacy AM/PWM 0 0 hour_20 Phase sync_M[2] sync_M[1]
sync_M[0] Second Legacy AM/PWM Phase Second Legacy AM/PWM Phase 20 0
data[35] 30 day_8 data[26] 21 0 data[34] 31 day_4 data[25] 22 day_200
data[33] 32 day_2 data[24] 13 hour_10 data[41] 23 day_100 data[32] 33
day_1 data[23]

--
President of The United States
Guy Ralph Perea Sr President of The United States
Weatherdata1046am0426 a Discussion Group of
Weatherdata<http://groups.google.com/group/weatherdata1046am0426>
USFMSC
http://www.cityfreq.com/ca/avalon/>
QUALIFY QICP
OCCUPS
http://www.occupationalinfo.org/02/025062010.html
goldlandabstracts; link check
own search engine - The United
States International Policies
http://apps.facebook.com/faceblogged/?uid=1340855784
http://lnk.ms/8d5gl aol
http://groups.google.com/group/united-states-of-american
http://cmt1.blogspot.com
http://twitter.com/guyperea
http://twitter.com/ptusss Federal Communication
Commission<http://columbiabroadcast.spaces.live.com/>

Ambassador Chevy Chase; Kevin Corcran; Jack Nickolas; Cher; Shirley Temple
Black; Liza Minnille; Ansari; Ernest Tascoe; Food, Drug and Cosmetic Act
Agent Jodie Foster; Department of Veterans Affairs Director George H.W. Bush
Title 22 USCS section 1928 (b) The e-mail
transmission may contain legally privileged information that
is intended only for the individual or entity recipient, you are hereby,
notified that any disclosure, copying, distribution, or reliance upon the
contents of this E-mail is strictly prohibited. If you have received this
E-mail transmission in error, please reply to the sender, so arrangements
can be made for proper delivery. Title 42
USCS section 192 etseq Margie Paxton Chief of Childrens Bureau
Director of The United States Department of Human Services; Defendant
Article IV General Provisions Section 2
(Supreme Law of The Land) The Constitution of The United States "Any thing
in The Constitution or Laws of any State to the Contrary Notwithstanding"
Contrary to Law (of an act or omission) illegal;
https://plus.google.com/100487463984952448443
https://twitter.com/presidentus1