[time-nuts] prn30 set healthy very soon
I've been monitoring prn30 since its launch 2-20-14. Yesterday (4-6-14) they zeroed the clk bias around 2221 utc. I predict they will set prn 30 healthy and online today (4-7-14) around the same time 2221 utc. This will be the 5th latest generation gps block II-F satellits in orbit and operational. prn-1 prn-24 prn-25 prn-27 prn-30 all block II-f with the best clocks. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] new gps sat prn30 svn64
I've done the math subtracting both skips and my clock bias's and frequency drifts from sirf msg30 (prn30) that were posted on timenuts earlier this week; 1.3331348485e-006 3.6930953087e-012 my data 1.3294251003e-006 3.6977287551e-012 skips .0037097482e-006 -.0046334464e-012 3.709748ns -4.633446e-015 Skip's gps clock is 3.7 nanosec slower than my gps clock. And our gps internal oscillators differ in frequency by -4.633446e-15. this could be a timenuts first. Gps common mode time and frequency comparison. skip and I are using sirf-4 gps receiver and sirfdemo software ver. 3.87 downloadable from the web. the receiver is a global sat (sirf-4) bu-353s4 mag mount usb gps receiver. ubtained from gps city in las vegas. They have an online store. My first bu353-s4 was purchased from ebay from someone in utah. It had bad sensivity. My holux gr-213 sirf III receiver which has the best sensitivity was from ebay china 5 or 6 years ago.. It has the sbas satellites (old prn sbas sats) hardcoded in firmware and will not receive any current sbas sats.. I believe the holux gr-213 sirf-3 mag mount usb gps are still sold. But must certainly have the new sbas satellites hardcoded correctly ? The holux gr-213 sirf-3 generated rfi so If your a hf ham radio operator you might not want a sirf-3 holux gr-213 receiver. Sincerly Tom. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] new gps sat prn30 svn64
I better explain how to interpet my programs output.
(parser of msg 30 and 41)
My C programming (turbo C for dos) isn't so great.
My program that parses out msg 30 and has wrap around problems in a dos window.
here is the latest data.
prn clk bias freq driftdelta of delta of lastclk bias time
of
# 2nd value 1st Value update correction
correction
01 2.444682e-06 1.805289e-12 2.008604e-14 2.1064e-10 0624 2.851728e-08 0221
02 4.822064e-04 -6.994180e-13 -2.559389e-14 -1.8880e-11 1247 3.825469e-07 0608
3 3.338170e-04 -1.446530e-13 1.442900e-14 -3.0300e-12 0243 3.337789e-04 2209
04 5.925871e-06 -7.702133e-13 2.525866e-14 -3.0809e-12 1022 5.002867e-08 0413
05 -3.857823e-04 1.898869e-12 8.883085e-15 5.6970e-11 1313 2.585686e-07 0825
07 3.205445e-04 1.948962e-12 5.041540e-15 3.3130e-11 0524 -3.924453e-07 2140
08 1.216586e-05 -4.228136e-12 9.215718e-15 -1.0147e-10 0629 -2.275090e-07 2302
09 3.099688e-04 5.749916e-124 3.590357e-14 6.3250e-11 0643 1.115118e-08 0333
10 -1.169125e-04 -3.732148e-12 2.896208e-14 -1.3153e-10 1127 1.717084e-08 0635
11 -4.694415e-04 -7.678278e-12 1.505740e-14 -1.8699e-10 0515 -4.693428e-04
12 1.902726e-04 3.823995e-12 -5.947500e-15 1.0672e-10 1229 2.884730e-07 0558
3 2.347145e-05 -3.571864e-12 3.864378e-14 -3.9759e-10 0338 2.359677e-05 2029
14 1.933203e-04 -3.774090e-12 -1.775706e-14 -7.1700e-11 2109 1.933391e-04
15 -1.665138e-04 -4.073153e-12 3.193192e-15 -1.2275e-10 1313 -1.699136e-08 1053
16 -2.290333e-04 2.271270e-125 1.784684e-14 6.8390e-11 1313 6.469004e-08 1219
17 -7.363667e-05 -4.552428e-12 -2.088173e-14 1.3657e-11 0925 -7.360009e-05 0211
18 3.055097e-04 6.184127e-12 2.091990e-14 1.8347e-10 1313 3.054834e-04 1054
19 -4.427305e-04 -2.738411e-12 2.424970e-14 -3.8340e-11 0351 -1.456134e-08 2302
20 1.671745e-04 3.410605e-12 -1.810003e-12 2.2216e-10 0731 8.188247e-08 0608
21 -3.475306e-04 4.271788e-124 -1.902558e-14 1.2182e-10 1313 -3.475719e-04 0944
22 2.174910e-04 3.388278e-12 1.535512e-14 1.0165e-10 1313 1.195895e-07 1224
23 -1.140106e-06 -5.962289e-12 8.155802e-15 -9.0458e-11 0226 -1.053358e-06
24 -2.442550e-05 -1.579095e-13 -8.446098e-15 -1.1050e-12 1011 -2.441198e-05 0435
25 1.728555e-05 2.677246e-12 -7.713015e-16 8.0317e-11 1313 6.543547e-08 0737
26 1.475605e-04 -1.760653e-11 -1.706621e-14 -5.2820e-10 1313 -7.660844e-08 1040
7 -1.999184e-05 -5.801356e-13 3.546626e-14 -4.8282e-10 0209 -1.998046e-05 2213
28 3.372821e-04 -3.165018e-13 -4.157156e-14 -1.3070e-11 0758 3.371151e-04 0005
29 5.157496e-04 3.405173e-12 -2.445526e-15 1.0216e-10 1313 5.156916e-04 0800
30 1.999639e-06 3.570054e-12 -3.170207e-16 1.0710e-10 0209 5.961562e-07 0110
31 3.336638e-04 2.788489e-124 -2.070761e-14 3.5211e-10 1140 3.336265e-04
32 -4.751391e-04 9.189593e-12 -9.305317e-14 1.7504e-09 2332 -1.024028e-07 1930
36 41 1782 306881000 03 05 2014
13:14:25000
76135 78583 051 02240 cli04 hed00
hpe522 vpe104 ck 307542303 dft 1832300
cder0 dist0 derr0 hder0 sats9 hdop4 dop0
line three (above) is supposed to be prn 03 a wrap around of the second line
erased the zero of prn 03.
My previous post I tried to clean up the wrap around effect for prn numbers and
typed a 1 instead of zero for prn 4.
09 3.099688e-04 5.749916e-124 3.590357e-14 6.3250e-11 0643 1.115118e-08 0333
line 9 second item (frequency drift) 5.749916e-124 should be interpeted; was
-x.xe-14 in a previous printf statement;
the current drift is actually 5.749916e-12 but hours or even minutes earlier it
would have been something like -1.23456xxe-14
The negetive symbol takes up a valuable space in my limited dos window. When a
value changes from a negative to positive
number it frees up a space and the frequency drift value gets shifted left one
space leaving a previous digit visiable.
I will clean this up someday. but I find it somewhat usefull.
line prn 25
25 1.728555e-05 2.677246e-12 -7.713015e-16 8.0317e-11 1313 6.543547e-08 0737
The last value (line 25) 0737 utc time of first correction and reception of
prn25. 6.543547e-08 0737 = The svn's first daily
clock bias (which agrees with usno's daily gps report) This last value is the
same as the first value only on the first
initial days prn reception (because it usually contains a major clk bias
correction) as received from the gps receiver.
This last value shows large changes (corrections) in the svn clock bias example
(actual code not the complete code);
else if ((daily_drift -.0001) (daily_drift -.001)) {
gotoxy(63,sat_num);
printf(%9le %02d%02d ,daily_drift,hour,minute);
sound(500);
delay(125);
nosound();
}
8.0317e-11 1313 (fourth item) change from previous sample of the first item
(clock bias 1.728555e-05) at 1313 hrs utc.
Summary of prn25 (line25);
25 1.728555e-05 2.677246e-12 -7.713015e-16 8.0317e-11
[time-nuts] new gps sat prn30 svn64
Looking at my previous post today I see that I should point out something else in my parsing programings output The last colume I labled a clk bias corrections is somewhat misleading. numbers displayed x.xxxe-7 x.xxxe-8 are corrections. numbers displayed as x.e-3 x.e-4 x.e-5 x. e-6 are simply numbers carried (not clk corrections) over from the 1st item (clk bias) after a restart of my parser program (or new sat aquisition). last colume is current clk bias subtracting previous clk bias. If no previous clk data then the current clk bias (item one) is displayed in the clk correction colume. I stop and start old and new loging each day around 7am. I start my parser display program many times daily till it reached end of file. Which could be eof for live loging (most allways) or eof for old logs. the last colume of my parsers display is a subtraction of item one (clk bias) from the previous received item one. So when I start my parser on the current log. all clock corrections (last item) are exact copies of the first item. As the parser encounters a new satellite where no previous data was recorded the last colume is duplicated from the first item. To finalize this explaination. last colume numbers x.xe-3 x.xe-4 x.xe-5 are the result of the parser not having any previous data for the satellite so the utc time stamp will indicate parser start time or first sat reception time. easly seen when first and last items are nearly equal or equal. (unintended artifact not intended but usefull) I may have labeled the last item in a misleading way.. last item data x.xe-7 x.xe8 are clk bias corrections/updates current parser program restart; prn clk bias freq driftdelta of delta of lastclk bias time # 2nd value 1st Value update correction 01 2.525953e-06 1.631754e-12 6.486673e-15 4.8961e-11 1800 3.286320e-07 1724 03 3.340867e-04 8.056584e-12 3.874245e-14 -1.5889e-10 1800 3.340513e-04 11 -4.695983e-04 -6.476012e-12 1.412759e-14 -9.3290e-11 1800 -4.695533e-04 1619 ^C 1.930643e-04 -8.978439e-13 -2.771871e-15 -2.6940e-11 1800 1.930712e-04 D:\ 18 3.055987e-04 7.472895e-13 -3.550567e-14 2.2420e-11 1800 3.055796e-04 19 -4.428422e-04 4.888999e-135 1.240197e-14 -4.9387e-10 1800 -4.428375e-04 21 -3.475654e-04 -8.740432e-12 -2.151404e-14 -2.5348e-10 1741 -3.475278e-04 22 2.175630e-04 3.054865e-12 -1.646469e-14 9.1440e-11 1800 2.175378e-04 24 -2.445189e-05 -7.379998e-13 4.726525e-15 -4.8765e-11 1747 -2.444636e-05 27 -2.002264e-05 -2.966025e-13 -8.847632e-16 -8.9070e-12 1800 -2.002083e-05 31 3.336526e-04 -2.108104e-12 9.688647e-15 -3.0425e-10 1800 3.336634e-04 1645 32 -4.747259e-04 5.652165e-12 2.742468e-14 1.7002e-10 1800 -3.687709e-07 1619 36 41 1782 32407 03 05 2014 18:00:54000 77429 79876 000 28728 cli00 hed00 hpe422 vpe110 ck 1829842956 dft 1832604 cder0 dist0 derr0 hder0 sats10 hdop4 Notice identical items in first and last columes where time stamp is This means parser had to previous data to subtract from item 1 and probably no message 41 to get time from. Also around line 13 I (ctrl C) broke out of dos program to copy and past latest data. I find lots of usefullness leaving the last item as is. but thought I better try to explain it to everyone. Notice not many recorded satellites yet in todays log. Note prn30 is turned off so far today..interesting. (19:00utc) It should have been in the above example. I have a alot of clean up programming to make this parser presentable. Hope this helps.. Tom ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] new gps sat prn30 svn64
Hi Skip, Your message 30,30 is nearly identical to mine on 3-2-14 2:00mst I just realized I been putting my time stamps as pdt should be pst (pacific standard time). Anyway the supperb time rate from svn64 prn30 changed from execellant to average. Compareable to the other sats on 2/26/2014 01:34:33 pst here is my data. 3.8706945954e-010,-2.7224445300e-01402/25/2014 14:25:20 3.8088047897e-010,-2.8666966126e-01402/25/2014 14:28:50 3.8088047897e-010,-2.8666966126e-01402/25/2014 14:28:50 3.7882484806e-010,-3.0106044610e-01402/25/2014 14:30:20 3.7575403151e-010,-3.0106044610e-01402/25/2014 14:31:50 -7.6402494734e-007,3.6402148657e-01202/26/2014 01:34:33 -7.6389389961e-007,3.6402148657e-01202/26/2014 01:35:33 -7.6336994898e-007,3.6386020065e-01202/26/2014 01:37:33 I'm at somewhat of a loss to explain this change in clock rate (stability). Perhaps the military signal is derived from the better clock ? and the civilians get a less stable clock rate/signal ? I haven't rulled out dopplar shift or my mis-understanding of how gps works and what msg 30 really means. Perhaps the sat is broadcasting the bias and drift every minute and the gps receiver is dummer than I thought ? Here is my data from the approximate time as your data. GeoNav PC Time=1393793993 03/02/2014 12:59:53 30,30,7.5566999e+004,-1.0512244642e+007,-2.0403662041e+007,1.3915637457e+007,1.4887479321e+003,8.9976062727e+002,2.4431245733e+003,1.3331348485e-006,3.6930953087e-012,4,4.096000e+005,1.081600e+004,1.5091755390e+000 I would have thought our messages would be more exact to each other as I've run two receivers from my location running sirf twice on the same pc with both sirf III and sirf IV receivers simotainiously logging and the comparied messages are within 2 or 3 least significant digits of each other.. PRobably are location differences are the reason for a less equal comparison. sunday 3-2-14 the sat passed nearly overhead at my location which would have presented the maximum dopplar shift. but that wouldn't explain the dramitic shift in the clock stability seen on 2-26-14. I will be logging the data daily hoping to see the prn30 clock go back to the better stability. I put and sd card in my laptop pc and now run sirfdemo from the sd card and log to that sd card. I feel it puts less where on my harddrive.. I can easily see prn30 orbit moving westwardly each day across the sat mapping screen. very cool !! I also have written a program to parse out the clock bias and drift. here is its output. prn clk biasclk drift 30sec drift 30sec clk bias next orbit clk bias update utc 01 5.419324e-07 1.939370e-1213 1.350894e-14 2.4980e-10 0714 3.056667e-08 0316 02 4.801467e-04 -6.812491e-13 -2.547918e-14 -7.5000e-12 1332 1.832122e-07 0619 03 3.292035e-04 -7.611533e-14 1.553618e-14 -2.2900e-12 1529 -1.075634e-07 150 14 5.685252e-06 -6.154375e-13 2.511121e-14 -8.2501e-12 1112 5.062425e-08 0459 05 -3.874342e-04 2.121078e-123 8.206977e-15 9.7660e-11 1433 3.457315e-08 0838 06 2.857013e-04 1.634064e-11 5.935703e-14 4.9022e-10 1529 6.195851e-07 1344 07 3.165876e-04 1.958476e-12 5.030264e-15 7.9590e-11 0610 -5.385762e-07 222 08 1.200872e-05 -4.117289e-12 1.142446e-14 -3.7056e-11 0723 -3.790054e-07 234 09 3.072839e-04 5.659474e-125 3.575135e-14 8.4890e-11 0728 3.072825e-04 0025 10 -1.154085e-04 -3.748887e-12 2.945560e-14 -4.8740e-11 1212 -1.017679e-08 075 11 -4.664052e-04 -7.469855e-12 1.838373e-14 -1.1952e-10 0611 -1.192491e-08 021 12 1.880373e-04 3.790502e-12 -6.092783e-15 9.0580e-11 1316 1.010878e-07 0640 13 2.713727e-05 -3.561521e-12 1.282676e-14 -6.0546e-11 0424 2.726619e-05 2116 14 1.961350e-04 -3.153479e-12 1.802226e-14 -9.4600e-11 1529 -2.227599e-07 144 15 -1.645517e-04 -3.145682e-12 1.313034e-14 -7.8620e-11 1529 -1.402962e-08 113 16 -2.304940e-04 3.668937e-125 9.299852e-15 1.0947e-10 1529 5.328928e-08 1304 17 -7.047949e-05 -4.629986e-12 -2.057078e-14 -3.1959e-10 1008 -7.042604e-05 030 18 3.034303e-04 7.149177e-123 -5.420144e-15 2.1093e-10 1529 7.296043e-08 1140 19 -4.404313e-04 -2.519745e-12 1.712601e-13 -9.5182e-10 0445 -1.502963e-08 235 20 1.639282e-04 3.410605e-12 -1.746089e-12 2.3873e-09 0822 8.219745e-08 0635 21 -3.453992e-04 4.039002e-134 -4.799720e-14 1.0840e-11 1529 -1.898633e-07 102 22 2.150482e-04 4.723546e-12 6.304853e-15 1.4105e-10 1529 1.237934e-07 1302 23 1.918922e-06 -6.003539e-12 4.613150e-14 -6.0035e-12 0306 2.001197e-06 1931 24 -2.378059e-05 -1.316009e-12 -5.128276e-16 -3.9554e-11 1529 1.192998e-08 1507 25 1.573178e-05 2.737902e-122 -1.925977e-15 5.2020e-11 1416 6.875391e-08 0820 26 1.577180e-04 -1.734294e-11 2.159037e-14 -4.5705e-10 1521 -7.768384e-08 112 27 -1.932695e-05 -8.357383e-13 1.904347e-15 -2.5027e-11 1529 -3.765017e-08 140 28 3.344866e-04 -3.703717e-13 -8.318476e-14 -3.8030e-11 0842 3.343273e-04 0104 29 5.130142e-04 3.020466e-12 -4.085924e-15 9.0540e-11 1529 1.704589e-07 0854 30
[time-nuts] new gps satellite prn30 svn64
I discovered today with one of the online sat trackers (www.n2y0.com/?s=39533) that the new gps is in a 12719 mile orbit above earth. Putting it in a basic gps orbit all ready! There for I must conclude all the frequency drift I've been raving about is merely doppler shift! And not relitivistic gravitional effects! Anyway it looks as if the atomic clock on this new satellite are keeping excellant time. .037ns over 12hrs .011ns over 36hrs .018ns over 48hrs My estimation of the stability would be near 2e-16 ?? Someone else might want to pull out the calculator and check me on this. (to lazy to pull out my own calc. after all the cutting and pasting hehe) My first reception was at 23:32:22pdt gps time error freq-drift date time pdt 4.4716290517e-010,-1.1166002510e-014@ 02/21/2014 23:32:22 2.7434175598e-010,-5.1373205549e-014@ 02/22/2014 00:57:22 2.7264644019e-010,-5.1373205549e-014@ 02/22/2014 00:57:52 2.7202887741e-010,-5.2401886405e-014@ 02/22/2014 00:58:22 2.7003760573e-010,-5.2401886405e-014@ 02/22/2014 00:58:52 2.6877996045e-010,-5.2401886405e-014@ 02/22/2014 00:59:22 2.6416859445e-010,-5.2401886405e-014@ 02/22/2014 01:00:52 2.5693992947e-010,-5.3422655975e-014@ 02/22/2014 01:02:52 2.5624543494e-010,-5.3422655975e-014@ 02/22/2014 01:03:22 2.5421537401e-010,-5.3422655975e-014@ 02/22/2014 01:03:52 2.4365104104e-010,-5.4384875238e-014@ 02/22/2014 01:06:52 2.4196987886e-010,-5.5335398671e-014@ 02/22/2014 01:07:22 2.3208415713e-010,-5.6217685129e-014@ 02/22/2014 01:10:22 2.3084736806e-010,-5.6217685129e-014@ 02/22/2014 01:10:52 2.1308972996e-010,-5.7062414147e-014@ 02/22/2014 01:15:52 2.1229085616e-010,-5.7062414147e-014@ 02/22/2014 01:16:22 2.1024898532e-010,-5.7873397372e-014@ 02/22/2014 01:16:52 1.7422816710e-010,-6.0095673013e-014@ 02/22/2014 01:26:52 1.4985197051e-010,-6.1364392842e-014@ 02/22/2014 01:33:52 -8.2096225744e-011,-6.4458299267e-014 @ 02/22/2014 02:33:22 -8.7252889686e-011,-6.4458299267e-014 @ 02/22/2014 02:34:52 -8.8348680774e-011,-6.4458299267e-014 @ 02/22/2014 02:35:22 -1.0635115866e-010,-6.3795634899e-014 @ 02/22/2014 02:39:52 -1.0947714477e-010,-6.3795634899e-014 @ 02/22/2014 02:40:52 -1.2733387921e-010,-6.2957112939e-014 @ 02/22/2014 02:45:22 4.1019065602e-010,-2.6931360042e-014 @ 02/22/2014 12:11:52 (beggining reception for this sat pass) omitted about 20 readings here (to lazy to cut an past) 2.8165598456e-010,-5.0887679487e-014 @ 02/22/2014 13:04:22 (ending reception for this sat pass) 4.3603246331e-010,-1.6790847616e-01402/23/2014 12:07:52 4.3593171822e-010,-1.6790847616e-01402/23/2014 12:08:22 4.3174004663e-010,-1.8414870662e-01402/23/2014 12:11:52 4.3034051646e-010,-1.8414870662e-01402/23/2014 12:13:22 4.2869713019e-010,-2.0026462652e-01402/23/2014 12:14:22 4.1581271863e-010,-2.4775827210e-01402/23/2014 12:23:52 4.1281643054e-010,-2.6318389403e-01402/23/2014 12:25:52 4.0926344797e-010,-2.6318389403e-01402/23/2014 12:27:52 4.0478960091e-010,-2.7851801947e-01402/23/2014 12:30:52 3.9935083907e-010,-2.9374723140e-01402/23/2014 12:33:52 3.9419403312e-010,-3.0861188035e-01402/23/2014 12:36:22 3.7487843100e-010,-3.5255679669e-01402/23/2014 12:45:52 3.7015489306e-010,-3.6675906588e-01402/23/2014 12:47:52 3.6828442183e-010,-3.6675906588e-01402/23/2014 12:48:52 3.6575238324e-010,-3.8055713095e-01402/23/2014 12:49:52 3.6331681760e-010,-3.8055713095e-01402/23/2014 12:50:52 3.6305042761e-010,-3.8055713095e-01402/23/2014 12:51:22 3.4513124556e-010,-4.0722789453e-01402/23/2014 12:58:22 3.3345738644e-010 -4.3288038898e-01402/23/2014 13:02:52 3.3311108214e-010,-4.3288038898e-01402/23/2014 13:03:22 3.0597744159e-010,-4.6912604687e-01402/23/2014 13:12:52 2.9199553517e-010,-4.9187274398e-01402/23/2014 13:17:52 2.8347651083e-010,-5.0266031843e-01402/23/2014 13:20:52 4.2985792512e-010,-2.453659e-01402/24/2014 00:22:21 3.9619769439e-010,-3.0869905699e-01402/24/2014 00:43:51 2.7843215833e-010,-5.0366500114e-01402/24/2014 01:30:51 2.6696754744e-010,-5.1414151121e-01402/24/2014 01:34:51 2.6696754744e-010,-5.1414151121e-01402/24/2014 01:34:51 2.5655241979e-010,-5.3399281253e-01402/24/2014 01:37:51 2.3977925547e-010,-5.4335815090e-01402/24/2014 01:42:51 1.5593235232e-010,-6.0487530783e-01402/24/2014 02:06:51 1.3662021621e-010,-6.1631397956e-01402/24/2014 02:12:21 9.1330613763e-011,-6.3442815183e-01402/24/2014 02:24:21 7.4941924493e-011,-6.3779697127e-01402/24/2014 02:28:51 6.8642013947e-011,-6.4078001802e-01402/24/2014 02:30:21 5.9060884222e-011,-6.4327788430e-01402/24/2014 02:32:51 -6.6260772297e-011,-6.4416503273e-014 02/24/2014 03:04:51 -7.7866533308e-011,-6.4184273944e-014 02/24/2014 03:07:51 -8.4434374222e-011,-6.3902103552e-014 02/24/2014 03:09:51 -8.7629479398e-011,-6.3902103552e-014 02/24/2014 03:10:21
[time-nuts] new gps sat prn30 svn64
svn64 alive and well Using sirfdemo pc software coupled with sirf iv gps receiver I picked up the first signal from svn64 (now assigned prn30). The sat was launched from cape canavral (airforce station) florida last thursday evening 2-20-14 about 17:55pdt. The gps control people seem to be turning on the satellites transmitter intermittantly. The new satellite will not be in its final orbit for approximately 30 days and not usable till about 36 days from its launch date. My first reception was at 23:32:22pdt gps time error freq-drift date time pdt 4.4716290517e-010,-1.1166002510e-014@ 02/21/2014 23:32:22 2.7434175598e-010,-5.1373205549e-014@ 02/22/2014 00:57:22 2.7264644019e-010,-5.1373205549e-014@ 02/22/2014 00:57:52 2.7202887741e-010,-5.2401886405e-014@ 02/22/2014 00:58:22 2.7003760573e-010,-5.2401886405e-014@ 02/22/2014 00:58:52 2.6877996045e-010,-5.2401886405e-014@ 02/22/2014 00:59:22 2.6416859445e-010,-5.2401886405e-014@ 02/22/2014 01:00:52 2.5693992947e-010,-5.3422655975e-014@ 02/22/2014 01:02:52 2.5624543494e-010,-5.3422655975e-014@ 02/22/2014 01:03:22 2.5421537401e-010,-5.3422655975e-014@ 02/22/2014 01:03:52 2.4365104104e-010,-5.4384875238e-014@ 02/22/2014 01:06:52 2.4196987886e-010,-5.5335398671e-014@ 02/22/2014 01:07:22 2.3208415713e-010,-5.6217685129e-014@ 02/22/2014 01:10:22 2.3084736806e-010,-5.6217685129e-014@ 02/22/2014 01:10:52 2.1308972996e-010,-5.7062414147e-014@ 02/22/2014 01:15:52 2.1229085616e-010,-5.7062414147e-014@ 02/22/2014 01:16:22 2.1024898532e-010,-5.7873397372e-014@ 02/22/2014 01:16:52 1.7422816710e-010,-6.0095673013e-014@ 02/22/2014 01:26:52 1.4985197051e-010,-6.1364392842e-014@ 02/22/2014 01:33:52 -8.2096225744e-011,-6.4458299267e-014 @ 02/22/2014 02:33:22 -8.7252889686e-011,-6.4458299267e-014 @ 02/22/2014 02:34:52 -8.8348680774e-011,-6.4458299267e-014 @ 02/22/2014 02:35:22 -1.0635115866e-010,-6.3795634899e-014 @ 02/22/2014 02:39:52 -1.0947714477e-010,-6.3795634899e-014 @ 02/22/2014 02:40:52 -1.2733387921e-010,-6.2957112939e-014 @ 02/22/2014 02:45:22 This is a complete list of all that was received from the new prn30 satellite (so far). perhaps there saving power till solar pannel deployment? or are saving power to charge batterys after just deploying solar pannels? The numbers were cut an pasted from message id 30 (nl sv state data) from the sirfdemo pc software logging feature. I've been monitoring this information for the last 8 weeks logging many days of satellite data. It appears that gps time error gets updated from the satellite broadcast navagation message at least daily. I believe that the gps receiver then computes the satellite frequency drift (including doppler shift) and computes gps time error till the next satellite navagation broadcast message updates the accumulated time error. Atomic clocks in gps orbit run 45us fast perday due to less gravity but loose 8 us per day do to there high velocity. the net result is 37us per daily. It looks like the new satellite clock is keeping excellant time for not being in orbit yet.. perhaps it is allready high enough above earth to not experience the slower time of earths gravity? The old Prn30 has been flagged unusable for years. but data was still received and logged with sirfdemo. This is the last data from the old satellite prn30 (norad number 34661) whose transmissions became intermittant the last week (control operators turning it off and on). gps time error frequency drift 6.7348954278e-004,2.8731554896e-012 @ 02/21/2014 11:21:28 = last intermittant message from the old prn30 satellite. My gps receiver is a bu-353s4 (sirf-4) usb dongle that is available on ebay for about $40 dollars. My old sirfIII worked a little better (globalsat holux gr-213u). the new sirf IV spitts unwanted data randomly into log file. random data labeled unk:hexadecimal strings no help on internet but many complaints.. sirfdemo software is still downloadable from the internet. Nothing else has been received sense 02:45. I dont know if the sat is still visable to the usa right now or if the transmissions have been disabled .. There isn't any information on the internet yet.. No norad satellite numbers (svn64) published for tracking it yet. Enjoy. hope my tabs and spaces keep data aligned.. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] new gps
I picked up prn30 signal for the second time around 11:30pdt but did not get any data till 12:11pdt All though my sirf receiver is advertised to track some rediculous amount of sat's at once (something 32 or is it 48 sats) the sirfdemo software only allows 12 sat's to be tracked at once.. The sirfdemo had 11 channels tracking strong high altitude sats, the 12th channel was toggling between two low horizon sats and prn30 and couldn't lock on either. Prn30 had good signal strength about 20db out of 35db (sirf receiver is indoors) the software saw it as unuseable and kept trying to aquire other low horizion sats. Around 12pdt the low horizon sats fell below the horizon freeing up two more channels. This is about the time I received the good prn30 data. The gps clock timing received looks very similar to last nights clock data except the rate doesn't go negitive. It looks to me like mission control shut power off to the sat between last nights and todays data? or they tested a second new ribidum clock today? Anyway todays clock data looks a little more stable than last nights clock / data. I've cut and pasted only todays (noon time) first reception and todays last reception. 4.1019065602e-010,-2.6931360042e-014 @ 02/22/2014 12:11:52 2.8165598456e-010,-5.0887679487e-014 @ 02/22/2014 13:04:22 I'm expecting the negative drift to stabilize as the spacecraft gets further from earth. I did find the norad satellite tracking numbers; prn30 svn64 39533 delta 4 r/b 39534 but I haven't put the norad numbers into sat tracking program yet. Having fun Tom... ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] gps jamming in las vegas
___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] gps jamming in las vegas
I noticed the jamming begin at 0542 today 7-4-12. It's precisely at 5 minute intervals and lasting 75 seconds each time My loss of signal is 1 second after each 5 minute interval (using atomic PDT). Signal returns 75 seconds later at 17 seconds after the next minute. Date 7-5-12 los = loss of signalaos aqusition of signal all times pdt ** exact times of loss of signal losaos 0542 0547 0557 15 0602 54 -- 0603 23 0607 05 -- 0608 19 0612 05 -- 0613 18 0617 05 -- 0618 18 0622 01 -- 0623 17 ** 0627 02 -- 0628 18 0632 02 -- 0633 18 0637 02 -- 0638 17 0642 01 -- 0643 17 ** 0647 01 -- 0648 17 ** 0652 01 -- 0653 17 ** 0657 01 -- 0658 17 ** 0702 01 -- 0703 17 ** 0707 01 -- 0708 17 ** 0712 01 -- 0713 17 ** 0717 01 -- 0718 17 ** I'm using sirf III sirf demo all satelites signals drop from high 30's to the teens complete loss of signal.. My magellan explorist 500 however looses only half the satellites every 5 minutes in exact syncronization with total loss of satellites on holux sirf III receiver. Must be lightsquared wireless I've noticed wierd satellite reception on magellan explorist several months ago and wondered if it was lightsquared jamming... I'm sure of it now. exact same behavier from explorist today that I've seen it the past.. I havent monitored gps for months till today ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] gps jamming source found
It turns out my lacross projection, atomic, external temperature transmitter, clock is the source of the jamming.. Apparently its trying to communicate with its external temp sensor which has had a dead battery for months.. The projection clock is powered from ac mains and transmitts for long intervals looking for external temperature sensor... It transmitts around 433mhz Sorry for any previous post.Well be carfull of wireless weather, temperature equipment around gps ... I do hope government puts an end to lightsquared frequency allocations near gps frequencies ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] 60hz west coast electric grid gone berserk
My 60 hz clocks in las vegas gained 4minutes and 45 seconds approximately. At 6pm pacific daylight time I ran grid monitoring program which gets time updates from somewhere in washington state. It showed the grid frequency at 60.06 hz.. the grid was at 60.06 from 6:00 to 6:15 and mostly likely much earlier than 6pm when I heard the news and looked at the grid frequency. Power engineers say 60.05hz is where masive power failures woulld prevail. at around 6:18 frequency was back in tolerance around +.025 hz. This is most likely to do with massive power outage in southern california, arizona, seen as far as new mexico.. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] west coast did not lose and time I apoligise false alarm
the grid frequency was quite fast from at least 6pm to 6:15 pm probably resulting in only a second or too of gain .. I am very sorry for my incorrect post saying the grid gained 4 min and 45 seconds. Not true I have a malfunction clock... ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] lightsquared test in las vegas
I live in las vegas and drove to the coordinates given for the las vegas lightsquared transmitter on three consecutive nights from 12 am to 3 am durring there test period. In my opinion lightsquared never keyed there las vegas test transmitter durring the total 9 hours I was present, over three different days, during the test period, while I was located at ground zero! I had a garmin etrex and magellan sportrak gps receivers.A 29dbw signal would have knock out reception at the given lightsquared antenna site had they keyed there transmitter. I would question if lightsquared ever turned on there test transmitter anytime within the two week test period ? They certainly did not activate there las vegas test transmitter while I was at there site.. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] light squared test
The local NBC news in las vegas reported tonight (5-18-11) that next week, piolets flying at night may find gps unreliable or unuseable do to lightsquared testing broadband internet equipment in a frequency band adjacent to gps frequency. And that las vegas falls within a 350 mile radius of this testing.. Anybody have anymore info on this test. I've been reading posts here on timenuts about likely interference to gps receivers . And the fcc rushing license's for lightsquared. But I wasn't aware of any tests. Does anyone know where lightsquared is testing its transmitters that las vegas would fall within lightsquared's 350 mile radius. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] lightsquared test
Thanks for the replies, I'de been searching internet for about an hour not finding much. I finally did find some info same as the replies here. Here are some additional links about the testing . The third link givs lat and long. http://www.avweb.com/avwebflash/news/FAA_Warns_Lightsquared_Tests_204654-1.html?CMP=OTC-RSS http://www.ainonline.com/news/single-news-page/article/rep-raps-lightsquared-faa-to-begin-interference-tests-29631/ https://www.faasafety.gov/files/notices/2011/May/Light_Square_-BVU_Flight_Advisory.pdf I will be monitoring with my gps here in las vegas to check for interferience.. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] 60hz disciplined watch follow up
My orignal post that 60hz light flicker received at citizen ecodrive solarcells is used to discipline the watchs rate, needs a little correction to my post as brought to my attention by the replies. Yes it is actually 120hz flicker 60 positive cycle flickers and 60 negative cycle flickers per second thus 120 flickers per second. But I will suggest the idea that positive cycle flicker and negative cycle flicker probably presents different voltage levels for positive and negative cycles at the solarcell? Not to mention probable phase changes in the light itself caused by the positive and negative cycles? Anywhy let me continue to reference 60hz disciplineing rather 120hz disciplineing. Now imagine an algorithm for disciplineing the watchs reference (32767 xtal), which simply looks for stable 60hz. Lets say for example 120 stable consecutive cycles of 60hz (2 seconds) occur consecutively. The watch could easily detect this stable instance and deposit its sample in a high quality storage bin. Conversly the watch with its inexpensive reference oscillator could also detect unstable 60hz samples at its solarcell and deposit those samples in a trash bin for disposal. My estimate of the citizen ecodrives automatic rate adjustment occures at 10 day intervals. How many consecutive cycles of precise 60hz ac occur in 10 day of sampleingno one knows. maybe it happens thousands of times(in 10 days) but each time only for 1 second duration or 60 consecutive cyles... who knows. One would assume this happens sometime. Maybe in 10 days of 60hz sampling from the watches solarcell there are instances where 600 consecutive precise cycles occur ? And what if the watch could store those longer consecutive cycles in a higher quality storage bin (for latter averageing). Eventually the watch says I've observed many instances of (short duration) precise rate flickers. But none at exactly 60.? hz. Then the watch says its my reference that is off frequency not the precision instances of 60hz that I've observed. So the watch corrects its reference, empties its storage bins and starts a new 10 day cycle. No one could be more amazed than myself to discover that my citizen stainless skyhawk holding time within 13 milliseconds day by day for weeks (measurements taken approximately at 11am +- 2hours). I noted handling this watch with my hot hands caused a 1 milisecond per minute (estimated) additional error as the watch temperature increased. Thus during all subsequent measurements I handled the watch by its band as briefly as possible to eliminate temperature errors. The only thing citizen watch company could do to make me more happy is a 60hz frequency alarm feature to alert me of disturbances on the power grid ! ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] 60hz disciplined watch
Most if not all Citizen ecodrive watches are disciplined by 60hz light flicker that average the 60hz light flicker over approximately 10 days before a rate adjustment is preformed. I have four citizen ecodrives; Plain jane quartz analogue ecodrive with mechanical calendar that is 60hz disciplined. Stainless steel skyhawk ecodrive ana-digital that is 60hz disciplined. I've monitored this one for over a week it was holding 13 miliseconds for over a weeks duration (off the wrist mode) compaired to my cesium and ribidium references and got distracted from futher measurements of this citizen skyhawk as I was consumed with other measurements and comparisons between loran gps cesium ribidium and other watches. Blue angles citizen skyhawk ana-digital that half the time seems to be 60hz disciplined and other times unsure. This blue angles citizen skyhawk has the same movement as the stainless steel skyhawk which is definately 60hz disciplined. I suspect this blue angles skyhawk that I purchased out of the country could have 50hz and 60hz dicipline modes? My fourth citizen ecodrive is the stars stripes forever yacht timer ana-digital which is 60hz diciplined. This watch reboots every feb 28th at midnight to utc time zones and jan 1 2004 (not sure of the exact year is crashes to) some kind of leap year bug! Only unexpected temperature changes experienced by the ecodrive citizen watches produce significant error (.5 to 1 second over several days of temperature varation) there rate will correct after an approximate 10 day time constant. Many wrist watch forums make reference to citizen ecodrive rate accuratces remarking that citizen uses some propriatary rate techniques. It's simply 60hz light flicker received at the ecodrives solarbattery/photocell. I would recomend when setting your citizen ecodrive watches to set them 2.5 to 3 seconds fast if worn continous because that is approximately how much time will be lost before its rate gets compensated the first time. A Great Day to All , Tom ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] solar flares and cesium drift
We've had several solar flares this past week. My cesium standard has lost about 200ns as compared with fallon loran and gps. I was showing approximately 10 to 30 nanoseconds cesium drift the previous weeks when solar activity was quiet. I'm assuming all the drift I'm observing is my cesium standard (5061) and not loran or gps especially because loran is steered by gps and gps is steered by usno-amc. Has anyone else noticed any extra cesium drift this week? I'm assuming this drift is due to changes in the earth geomagnetic field due to solar activity? - Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. ___ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
[time-nuts] solar flares and cesium drift
I dont know about the cesium, but I can advise that in my opinion there have not been any major geomagnetic storms in the past few days. In fact nothing different to what has been happening for most of the last month. If anything it is relatively quiet. Solar flares do not produce an magnetic effect, they are purely radiation. What often happens is the emission of an associated CME and the currently active area #960 was right on the limb of the visible disc when the flares occured so any CME missed us. I supose it is possible that the radiation has affected the accuracy of GPS as received after passing through the ionosphere, but surely this would have been corrected very quickly? Cheers de Alan G3NYK Hi Alan What I was looking at was the xray events this past week from sunspot #960 There has been about 40 medium size xray events and I assumed that geomagnetic events went hand in hand with xray events and thought it was an explanation for my cesium/loran drift. I was wondering what specific dates you had this observation? I'd like to compare that data, against some of the data I have. Raimond Melkers Hey Raimond here is my data please sent yours if possible. From 17:26pdt on 6-04-07 To 07:20pdt on 6-05-07 I lost 40 to 50ns and continuing To 21:38pdt on 6-05-07 I lost another 10ns to 20ns and continuing To 05:23pdt on 6-06-07 I lost another 100ns to 110ns (strong winds ) continuing To 06:13pdt on 6-07-07 I lost another 50ns and continuing To 17:45pdt on 6-08-07 I gained 90ns could today gain be a gps correction? Happy Time keeping: Tom My orignal posting: We've had several solar flares this past week. My cesium standard has lost about 200ns as compared with fallon loran and gps. I was showing approximately 10 to 30 nanoseconds cesium drift the previous weeks when solar activity was quiet. I'm assuming all the drift I'm observing is my cesium standard (5061) and not loran or gps especially because loran is steered by gps and gps is steered by usno-amc. Has anyone else noticed any extra cesium drift this week? I'm assuming this drift is due to changes in the earth geomagnetic field due to solar activity? - Need a vacation? Get great deals to amazing places on Yahoo! Travel. ___ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
[time-nuts] solar flares and cesium drift
Ive answered my own question about my apparent cesium drift. I went to the usno web site cut pasted there loran measurements into notepad. The unso is measuring about 4 loran stations but not the fallon station. My conclusion; usno is as good as it gets and the steering at loran stations is not averaged enough. Fallon time equipment is the same as all other usa loran stations using the exact same timing equipment, 3X 5071cesiums, and redundant tsc gps steering. All loran stations that USNO monitored this week did exactly what fallon did as compared with my 5061.. My data from june 4-7 showed loss consistantly so did USNO's data. You can even see todays correction in both mine and USNO's data. Here is USNO's data; 25 MAY 2007 GPS -2 24 5930 450 7980 800 8970 910 9960 580 26 MAY 2007 1 day change GPS -1 25 5930 480 -30 7980 830 -30 8970 930 -20 9960 610 -30 missing 5-29 28 MAY 2007 2 day change GPS -3 27 5930 440 +40 7980 830 0 8970 920 +10 9960 590 +20 30 MAY 2007 1 day change GPS -4 29 5930 450 -10 7980 830 0 8970 920 0 9960 610 -30 31 MAY 2007 1 day changes GPS -4 30 5930 440 +10 7980 840 -10 8970 940 -20 9960 630 -20 01 JUN 2007 1 day change GPS -4 31 MAY 5930 470 -30 7980 860 -20 8970 930 +10 9960 600 +30 02 JUN 2007 1 day change GPS -3 01 5930 430 +40 7980 840 +20 8970 910 +20 9960 590 +10 03 JUN 2007 1 day change GPS -2 02 5930 420 +10 7980 820 +20 8970 940 -30 9960 600 -10 04 JUN 2007 GPS -3 03 5930 460 -40 7980 860 -40 8970 960 -20 9960 620 -20 05 JUN 2007 GPS -3 04 5930 470 -10 7980 890 -30 8970 980 -20 9960 650 -30 06 JUN 2007 GPS -4 05 5930 460 -10 7980 860 -30 8970 950 -30 9960 570 -80 07 JUN 2007 GPS -5 06 5930 440 -20 7980 840 -20 8970 910 -40 9960 530 -40 08 JUN 2007 GPS -5 07 5930 480 +40 7980 900 +60 8970 960 +50 9960 600 +70 See my data below! Tom I dont know about the cesium, but I can advise that in my opinion there have not been any major geomagnetic storms in the past few days. In fact nothing different to what has been happening for most of the last month. If anything it is relatively quiet. Solar flares do not produce an magnetic effect, they are purely radiation. What often happens is the emission of an associated CME and the currently active area #960 was right on the limb of the visible disc when the flares occured so any CME missed us. I supose it is possible that the radiation has affected the accuracy of GPS as received after passing through the ionosphere, but surely this would have been corrected very quickly? Cheers de Alan G3NYK Hi Alan What I was looking at was the xray events this past week from sunspot #960 There has been about 40 medium size xray events and I assumed that geomagnetic events went hand in hand with xray events and thought it was an explanation for my cesium/loran drift. I was wondering what specific dates you had this observation? I'd like to compare that data, against some of the data I have. Raimond Melkers Hey Raimond here is my data please sent yours if possible. From 17:26pdt on 6-04-07 To 07:20pdt on 6-05-07 I lost 40 to 50ns and continuing To 21:38pdt on 6-05-07 I lost another 10ns to 20ns and continuing To 05:23pdt on 6-06-07 I lost another 100ns to 110ns (strong winds ) continuing To 06:13pdt on 6-07-07 I lost another 50ns and continuing To 17:45pdt on 6-08-07 I gained 90ns could today gain be a gps correction? Happy Time keeping: Tom My orignal posting: We've had several solar flares this past week. My cesium standard has lost about 200ns as compared with fallon loran and gps. I was showing approximately 10 to 30 nanoseconds cesium drift the previous weeks when solar activity was quiet. I'm assuming all the drift I'm observing is my cesium standard (5061) and not loran or gps especially because loran is steered by gps and gps is steered by usno-amc. Has anyone else noticed any extra cesium drift this week? I'm assuming this drift is due to changes in the earth geomagnetic field due to solar activity? - Choose the right car based on your needs. Check out Yahoo! Autos new Car
[time-nuts] common mode loran comparisons
I'm getting great results monitoring daily phase changes of the fallon loran master station. I don't have any computer logging from my austron 2100's but manual readings taken several times a day show 10 to 30 nanosec of phase change throughout the day and about 0 to 10 ns day to day and about 0 to 30ns week to week. I have an hp-5061 providing reference for two seperate 2100's one f model the other is the timing type.both austrons readings agree with each other. I also have sirf type 1pps gps receiver that agrees with the long term phase changes of all the above. The reading are good enough to participate in common mode measurements with fellow time-nuts that have cesium and austron 2100 loran monitors. I'm using a funaro 80 marine loran as an antenna pre-amp for the 2100's coupled by capacitors.to the austron. Any old loran that has two wire antenna coupler could be used as a preamp for the austron 2100. The austron 2100 does not provide power for said coupler so you should use matching receiver thats belongs with antenna coupler. My antenna is indoor and works fairly well without preamp but works better with furano loran preamp. I've never owned the orignal antenna designed for the austorn 2100 but assume it works well. My recent data; Time loran1 loran2 gps date doy 12:24 -013 -025 772 5-27-07 147 15:00 -011 -024 784 5-27-07 147 06:13 -014 -026 759 5-28-07 148 09:43 -014 -026 771 5-28-07 148 14;07 -010 -023 799 5-28-07 148 20:11 -009 -022 807 05:28 -013 -025 775 5-29-07 149 10:25 -014 -028 743 18:06 -016 -029 739 21:40 -013 -026 760 05:27 -015 -028 745 5-30-07 150 06:14 -016 -028 754 5-31-07 151 07:25 -018 -031 722 6-01-07 152 07:13 -014 -027 777 6-02-07 153 I would enjoy comparing this measured loran data with someone elses. Nist unso aren't monitoring chain 9940 so I need help from fellow time-nuts. - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. ___ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
[time-nuts] loran C searchlight station
Did anyone notice lorsta searchlight (chain 9940) drift on the 4th of july 2006 at approximately 0715am pdt my 2100f showed a phase gain of 150ns that seemed to corect itself by 0930 pdt. This also happened june 7th 2006 at approximately 1400 pdt with a phase shift 180ns and was apparently corrected by 1800 pdt of the same date. My 2100F reference is a hp-5061 which is continously compared with rubidium frs-c. Also my frs-c rubidium and hp5061 are contimously compared with sirf gps 1pps. My confidence of this loran searchlight skew is about 94% Thats why I would like some confirmation of this from anyother time-nuts with atomic frequency standards. I've found government web sites that log loran stability completely inaccurate and usless (wwv site) (uscgs) for monitoring the searchlight station. - Want to be your own boss? Learn how on Yahoo! Small Business. ___ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
