[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
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
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-
Re: [time-nuts] new gps sat prn30 svn64
"tom jones" wrote: > 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 ? I believe message 30 is about the local clock in the GPS receiver. This has nothing to do with the clocks in the GPS satellites themselves. The SV atomic clock bias and rate is reported by the a0, a1, a2 parameters. See SiRF message ID 14, 15, or 70 or the GPS ICD for details. > prn clk bias clk 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 The second number is suspect: "1.939370e-1213" really? Since the table includes all 32 SV it looks more like ephemeris or almanac data than something to do with your receiver. Then again, clock bias and drift numbers (e.g., for prn 14) of 5.685252e-06 and -6.154375e-13 translate to 5.6 us bias and 5.3e-8/day frequency drift so that would certainly be a cheap quartz oscillator not an atomic clock. What SiRF message(s) did it come from? I'll track down some of the other questions you've posted recently. What make/model SiRF receiver are you using? Internal or external antenna? What version of SiRFDemo are you using? Thanks, /tvb ___ 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 -1.2733
Re: [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 errorfreq-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-01402/22/2014 02:33:22 > -8.7252889686e-011,-6.4458299267e-01402/22/2014 02:34:52 > -8.8348680774e-011,-6.4458299267e-01402/22/2014 02:35:22 > -1.0635115866e-010,-6.3795634899e-01402/22/2014 02:39:52 > -1.0947714477e-010,-6.3795634899e-01402/22/2014 02:40:52 > -1.2733387921e-010,-6.2957112939e-01402/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.. > > Hello Tom, Just wondering if we are looking at the same data? I have been using SiRFDemo with a BU353S4 and looking at the Message 30 output. Currently (2pm MT 2Mar2014) PRN30 clock bias is 1.3294214026e-006 sec and rate is 3.6977287551e-012 sec/sec. Entire output of the message is - 30,30,7.4562999e+004,- 1.1858809451e+007,- 2.1249722627e+007,1.1326906314e+007,1.1932198375e+003,7.7622948298e+002,2.7 047409217e
[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 -9.4
[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] 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.
Re: [time-nuts] New GPS module
Lesson learned. Will not use the tiny URLs again. On Kickstarter and Indigogo you pay thru PayPal and get the money back if it doesn't fund. Of course, I'm the guy that put $500 non-refundable down on a car where the mfg hasn't even built the plant! http://eliomotors.com N0UU ___ 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.
Re: [time-nuts] New GPS chips on Indegogo
It's ok, even preferred, to use real URL's (many of us don't make a habit of clicking on t.cn links). The link is: http://www.indiegogo.com/projects/navspark-arduino-compatible-with-gps-gnss-receiver /tvb - Original Message - From: "Alberto di Bene" To: Sent: Thursday, January 16, 2014 3:28 AM Subject: Re: [time-nuts] New GPS chips on Indegogo > Don't know what happened... my previous message was relayed with an almost > empty body... > Here it is again. > > 73 Alberto I2PHD > > = > > On 1/14/2014 8:05 PM, lstosk...@cox.net wrote: > >> /This isn't drawing lots of attention, but really looks promising: >> >> //http://bit.ly/1dBpits// or//http://t.cn/8FvCEX7// >> >> Regular GPS or Chinese version or RAW. The first two presently Arduino >> compatible. >> >> For not much money. >> >> Hope it gets funded./ > > What happens with those fund raising projects if the goal is not reached ? > Do you receive your money back, or you must consider it a lost bet ? > > 73 Alberto I2PHD ___ 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.
Re: [time-nuts] New GPS chips on Indegogo
Don't know what happened... my previous message was relayed with an almost empty body... Here it is again. 73 Alberto I2PHD = On 1/14/2014 8:05 PM, lstosk...@cox.net wrote: /This isn't drawing lots of attention, but really looks promising: //http://bit.ly/1dBpits// or//http://t.cn/8FvCEX7// Regular GPS or Chinese version or RAW. The first two presently Arduino compatible. For not much money. Hope it gets funded./ What happens with those fund raising projects if the goal is not reached ? Do you receive your money back, or you must consider it a lost bet ? 73 Alberto I2PHD ___ 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.
Re: [time-nuts] New GPS chips on Indegogo
do you have a link? On Wed, Jan 15, 2014 at 2:10 PM, Alberto di Bene wrote: > > ___ > 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. > -- --Eric _ Eric Garner ___ 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.
Re: [time-nuts] New GPS chips on Indegogo
___ 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 chips on Indegogo
This isn't drawing lots of attention, but really looks promising: http://bit.ly/1dBpits or http://t.cn/8FvCEX7 Regular GPS or Chinese version or RAW. The first two presently Arduino compatible. For not much money. Hope it gets funded. N0UU ___ 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 App.
http://www.army.mil/-news/2011/03/29/53988-picatinny-fields-first-precision-guided-mortars-to-troops-in-afghanistan/index.html -John = ___ 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 Configuration: 24+3=Win/Win
Three existing SVs to be moved to provide better coverage - details - http://www.gpsworld.com/gnss-system/gps-modernization/new-gps-configuration- 243winwin-9369 John, K1AE ___ 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.
Re: [time-nuts] new gps timing receiver
That's the one I meant, Ed. Wi125. Just saw a writeup in a trade mag. Don - Original Message - From: "Ed Palmer" To: "Discussion of precise time and frequency measurement" Sent: Friday, October 30, 2009 10:41 AM Subject: Re: [time-nuts] new gps timing receiver Do you mean the TiMax Wi125? It appears to be a relabelled version of the Navsync CW25 module with some customized software. They also sell a TiMax Ti125 module which appears to be the same hardware with slightly different software. The CW25 costs $68 each (for one unit) and the CW12 module that's based on the CW25 but is easier to connect to costs $84. Ed Don Latham wrote: I'm pretty sure the list members are aware of this, but the Connor-Winfield corp (conwin.com) announced a gpsw timing module, $40 in bulk, that maintains phase alignment between the 10 MHz and 1 PPS signals, put out a synthesized frequency up to 30 MHz, and has a position hold feature for one-satellite timing. I have not loked yet, but this looks to be a useful device. Don ___ 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 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.
Re: [time-nuts] new gps timing receiver
Do you mean the TiMax Wi125? It appears to be a relabelled version of the Navsync CW25 module with some customized software. They also sell a TiMax Ti125 module which appears to be the same hardware with slightly different software. The CW25 costs $68 each (for one unit) and the CW12 module that's based on the CW25 but is easier to connect to costs $84. Ed Don Latham wrote: I'm pretty sure the list members are aware of this, but the Connor-Winfield corp (conwin.com) announced a gpsw timing module, $40 in bulk, that maintains phase alignment between the 10 MHz and 1 PPS signals, put out a synthesized frequency up to 30 MHz, and has a position hold feature for one-satellite timing. I have not loked yet, but this looks to be a useful device. Don ___ 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 timing receiver
I'm pretty sure the list members are aware of this, but the Connor-Winfield corp (conwin.com) announced a gpsw timing module, $40 in bulk, that maintains phase alignment between the 10 MHz and 1 PPS signals, put out a synthesized frequency up to 30 MHz, and has a position hold feature for one-satellite timing. I have not loked yet, but this looks to be a useful device. Don -- Dr. Don Latham AJ7LL Six Mile Systems LLP 17850 Six Mile Road POB 134 Huson, MT, 59846 VOX 406-626-4304 www.lightningforensics.com www.sixmilesystems.com ___ 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.
Re: [time-nuts] New GPS Signals
>> F0 is 10.23 MHz. >> >> Björn > > On earth. In the birds it's 10.2299543 MHz. > > Sam. That's switchable... or used to be... ;-) -- Björn ___ 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.
Re: [time-nuts] New GPS Signals
MOSEL Sam skrev: >> F0 is 10.23 MHz. >> >> Björn > > On earth. In the birds it's 10.2299543 MHz. Actually it is closer to 10.229954326 MHz... but only measured as such when the bird is on ground. This adjustment is done just before launch to compensate for the fact that the gravitational pull is slightly less on the birds fligthpath. Relativistics makes the clock go faster up there, so tune it sour before letting it go will but it right when in place. If you where to measure it at its place in the bird, it is 10,23 MHz. Cheers, Magnus ___ 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.
Re: [time-nuts] New GPS Signals
> F0 is 10.23 MHz. > > Björn On earth. In the birds it's 10.2299543 MHz. Sam. Disclaimer : The contents of this e-mail including any attachments are intended only for the person or entity to which this e-mail is addressed. If you are not, or believe you may not be, the intended recipient, please advise the sender immediately by return e-mail, delete this e-mail and destroy any copies. The Company does not warrant nor guarantee that this email communication is free from errors, virus, interception or interference. ___ 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.
Re: [time-nuts] New GPS Signals
Brooke, bro...@pacific.net skrev: > Hi Magnus: > > The reason F0 = 1.023 MHz is that it's also used as the basis for the data > bit rates. The L1C/A code is 1 ms long @ F0 rate. > The L2CM (Moderate) code will be 20 ms long @ F0/2 > The L2CL (Long) code will be 1.5 sec long @ F0/2, > so maybe F0 should be 511.5 kpbs? In that case you should be using 50 Hz... since that is the rate of the C/A data modulation. But your reasoning is broken... you are attempting to find even multiplication rates, but this is not the way to get the fundamental frequency. ICD-200 clearly indicates 10,23 MHz. The basic rate of GPS is 10,23 MHz for the P-code. The flimsy C/A code is a 10th of that rate... and L2CM and L2CL is a further division by 2... > I discovered that the Trimble p/n 16768-80 Trimpack GPS receiver has a > graphics capability, which none of the others have, and wanted to know > why. So I'm in the process of reverse engineering and repairing it. > There's still a power supply problem that's making the LCD extreamly hard > to read, but now I know the reason for the graphics is to switch between > English and Arabic for all the displays. > http://www.prc68.com/I/Trimpack.shtml#GraphicsTP > > My interest in the GPS Link frequencies and codes is related to the > Polaris Guide (civilian version of the current military DAGR GPS receiver) > and possible firmware upgrades. I've just got off the phone with Rockwell > and they say the Polaris guide only has L1 capability (I was expecting > that it also had L2 since the DAGR has L2). > http://www.prc68.com/I/DAGR.shtml#Pol Kind of expected. It is only lately that we got any L2C coverage to be meaningfull. Codeless P-code tracking of some sort is still king for civilian uses. Especially with GLONASS added. > I'm in the process of adding a LF differential beacon receiver interface > to the Polaris Guide. Also have the connector on order to add Have Quick > time fill to the O-1814 Rb Time and Frequency standard. > http://www.prc68.com/I/O1814.shtml Cheers, Magnus ___ 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.
Re: [time-nuts] New GPS Signals
> Hi Magnus: > > The reason F0 = 1.023 MHz is that it's also used as the basis for the da > bit rates. The L1C/A code is 1 ms long @ F0 rate. F0 is 10.23 MHz. -- Björn ___ 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.
Re: [time-nuts] New GPS Signals
Hi Magnus: The reason F0 = 1.023 MHz is that it's also used as the basis for the data bit rates. The L1C/A code is 1 ms long @ F0 rate. The L2CM (Moderate) code will be 20 ms long @ F0/2 The L2CL (Long) code will be 1.5 sec long @ F0/2, so maybe F0 should be 511.5 kpbs? I discovered that the Trimble p/n 16768-80 Trimpack GPS receiver has a graphics capability, which none of the others have, and wanted to know why. So I'm in the process of reverse engineering and repairing it. There's still a power supply problem that's making the LCD extreamly hard to read, but now I know the reason for the graphics is to switch between English and Arabic for all the displays. http://www.prc68.com/I/Trimpack.shtml#GraphicsTP My interest in the GPS Link frequencies and codes is related to the Polaris Guide (civilian version of the current military DAGR GPS receiver) and possible firmware upgrades. I've just got off the phone with Rockwell and they say the Polaris guide only has L1 capability (I was expecting that it also had L2 since the DAGR has L2). http://www.prc68.com/I/DAGR.shtml#Pol I'm in the process of adding a LF differential beacon receiver interface to the Polaris Guide. Also have the connector on order to add Have Quick time fill to the O-1814 Rb Time and Frequency standard. http://www.prc68.com/I/O1814.shtml Have Fun, Brooke Clarke http://www.PRC68.com > bro...@pacific.net wrote: >> Hi: >> >> There are three new civilian GPS signals, L1C, L2C and L5. >> http://www.prc68.com/I/DAGR.shtml#GPSs >> The original civilian signal, L1 is at 1575.42 MHz (154 * 10 * F0, >> F0=1.023 MHz). >> > f0 should really be set to 10,23 MHz. >> L1C is at the same frequency as L1 but uses the code like Japan. >> > It looks similar to L5 actually, but coordination with Galileo, QRSS, > Glonass and Compass is underway. >> The new L2C signal is at 1227.60 MHz (120*10*F0). Allowing for path >> length corrections. >> >> The new L5 signal is at 1176.45 MHz (115*10*F0). This is intended for >> aircraft safety. It also has the largest frequency difference to L1 so >> should also be the best for determining the path length through the >> ionosphere/troposphere allowing for a more accurate time fix >> > Currently we have these signals: > L1 C/A (from all current sats) > L1 P(Y) (from all current sats) > L1 M(from GPS-IIR(M) sats) > L2C (from GPS-IIR(M) sats) > L2 P(Y) (from all current sats) > L2 M(from GPS-IIR(M) sats) > > In a couple of weeks we can also expect the first transmission of > > L5C(from GPS-IIR(M)20 sat) > > It will be years before we see L1C (from GPS-III sats). >> I'm hoping my Polaris Guide receiver will get upgraded firmware to get >> these signals as well as have WAAS added. See: >> http://www.prc68.com/I/DAGR.shtml#Pol >> >> Are there any new timing GPS receivers that take advantage of the new >> signals? >> > There is a few, but they are not in wide spread. You need to look into > the geodestic receiver market. Trimble amongst others have receivers > claiming support. > > Cheers, > Magnus > > ___ > 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 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.
Re: [time-nuts] New GPS Signals
bro...@pacific.net wrote: > Hi: > > There are three new civilian GPS signals, L1C, L2C and L5. > http://www.prc68.com/I/DAGR.shtml#GPSs > The original civilian signal, L1 is at 1575.42 MHz (154 * 10 * F0, > F0=1.023 MHz). > f0 should really be set to 10,23 MHz. > L1C is at the same frequency as L1 but uses the code like Japan. > It looks similar to L5 actually, but coordination with Galileo, QRSS, Glonass and Compass is underway. > The new L2C signal is at 1227.60 MHz (120*10*F0). Allowing for path > length corrections. > > The new L5 signal is at 1176.45 MHz (115*10*F0). This is intended for > aircraft safety. It also has the largest frequency difference to L1 so > should also be the best for determining the path length through the > ionosphere/troposphere allowing for a more accurate time fix > Currently we have these signals: L1 C/A (from all current sats) L1 P(Y) (from all current sats) L1 M(from GPS-IIR(M) sats) L2C (from GPS-IIR(M) sats) L2 P(Y) (from all current sats) L2 M(from GPS-IIR(M) sats) In a couple of weeks we can also expect the first transmission of L5C(from GPS-IIR(M)20 sat) It will be years before we see L1C (from GPS-III sats). > I'm hoping my Polaris Guide receiver will get upgraded firmware to get > these signals as well as have WAAS added. See: > http://www.prc68.com/I/DAGR.shtml#Pol > > Are there any new timing GPS receivers that take advantage of the new > signals? > There is a few, but they are not in wide spread. You need to look into the geodestic receiver market. Trimble amongst others have receivers claiming support. Cheers, Magnus ___ 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 Signals
Hi: There are three new civilian GPS signals, L1C, L2C and L5. http://www.prc68.com/I/DAGR.shtml#GPSs The original civilian signal, L1 is at 1575.42 MHz (154 * 10 * F0, F0=1.023 MHz). L1C is at the same frequency as L1 but uses the code like Japan. The new L2C signal is at 1227.60 MHz (120*10*F0). Allowing for path length corrections. The new L5 signal is at 1176.45 MHz (115*10*F0). This is intended for aircraft safety. It also has the largest frequency difference to L1 so should also be the best for determining the path length through the ionosphere/troposphere allowing for a more accurate time fix. I'm hoping my Polaris Guide receiver will get upgraded firmware to get these signals as well as have WAAS added. See: http://www.prc68.com/I/DAGR.shtml#Pol Are there any new timing GPS receivers that take advantage of the new signals? Have Fun, Brooke Clarke http://www.PRC68.com > Fellow time-nuts, > > GPS IIR-20 was succsessfully launched: > http://www.losangeles.af.mil/news/story.asp?id=123141115 > > Expect it to show up on the receivers eventually. Currently only PRN01 > is unused. > > Cheers, > Magnus > > ___ > 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 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.
Re: [time-nuts] New GPS backend comming
); SAEximRunCond expanded to false Errors-To: [EMAIL PROTECTED] RETRY On Wed, 22 Aug 2007 18:59:06 EDT, [EMAIL PROTECTED] wrote: >FYI: > >_http://rfdesign.com/military_defense_electronics/news/gps_acquire_architectur >e_0822/index.html_ >(http://rfdesign.com/military_defense_electronics/news/gps_acquire_architecture_0822/index.html) > > > >From that I read: [At a media roundtable on Aug. 16, Lt. Gen. Michael Hamel, commander of Air Force Space and Missile Command, said: "The Air Force is applying the same rigor for this transition as we do with our launch systems. If at any point there's a problem, we have the ability to transition back."] Ok, but how does one "transition back" with a launch system? Seems Challenger in 1986 could have used that feature. ___ 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.
Re: [time-nuts] New GPS backend comming
); SAEximRunCond expanded to false Errors-To: [EMAIL PROTECTED] RETRY FYI: _http://rfdesign.com/military_defense_electronics/news/gps_acquire_architectur e_0822/index.html_ (http://rfdesign.com/military_defense_electronics/news/gps_acquire_architecture_0822/index.html) ** Get a sneak peek of the all-new AOL at http://discover.aol.com/memed/aolcom30tour ___ 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.
