DGPS Logs Jun 21, 2017 UTC 2307 - Jun 22, 2017 UTC 2312 (AFE822x)

[skeezix]

Koblenz... yes?!? 0.5 kHz channel, time is right. Can't confirm with only one decode, but not going to cross it off the list either.

Koblenz
Thursday, June 22, 2017 02:19:42

Fort Stevens
Thursday, June 22, 2017 05:33:04
Thursday, June 22, 2017 05:55:56
Thursday, June 22, 2017 06:10:51
Thursday, June 22, 2017 06:18:54
Thursday, June 22, 2017 06:19:10
Thursday, June 22, 2017 06:55:38
Thursday, June 22, 2017 06:55:41

Point Escuminac
Thursday, June 22, 2017 01:09:22

Lauzon
Thursday, June 22, 2017 06:00:48
Thursday, June 22, 2017 06:01:14
Thursday, June 22, 2017 06:26:49
Thursday, June 22, 2017 06:28:48
Thursday, June 22, 2017 07:24:54

Cardinal
Thursday, June 22, 2017 06:20:42
Thursday, June 22, 2017 06:21:42
Thursday, June 22, 2017 06:27:17
Thursday, June 22, 2017 06:39:58
Thursday, June 22, 2017 06:43:12
Thursday, June 22, 2017 07:17:06


Count    ID   ref1 ref2 kHz   Baud City                           Country              Lat      Lon      km     Deg
1        105  410  411  288.0 100  Aguada Lt                      India                15.496   73.778   13,165 14 
1        493  824  825  302.5 100  Koblenz [Test Station]         Germany              50.367   7.583    6,974  45 
7        886  272  273  287.0 100  Fort Stevens, OR               United States        46.208   -123.96  2,363  284
16       907  304  305  320.0 200  Richmond, BC                   Canada               49.114   -123.183 2,283  292
1        936  332  333  319.0 200  Point Escuminac, NB            Canada               47.075   -64.8    2,210  74 
607      871  172  173  300.0 100  Appleton, WA                   United States        45.792   -121.332 2,168  282
10       827  244  245  312.0 200  Tampa, FL                      United States        27.85    -82.543  2,138  149
39       799  044  045  290.0 200  Penobscot, ME                  United States        44.453   -68.776  1,942  83 
232      772  198  199  306.0 200  Acushnet, MA                   United States        41.749   -70.889  1,852  93 
662      771  196  197  294.0 100  New Bern, NC                   United States        35.181   -77.059  1,765  123
95       778  192  193  292.0 100  Kensington, SC                 United States        33.491   -79.349  1,759  132
143      803  006  007  293.0 100  Moriches, NY                   United States        40.794   -72.756  1,743  98 
5        927  316  317  309.0 200  Lauzon, QC                     Canada               46.821   -71.165  1,729  75 
1286     806  012  013  289.0 100  Driver, VA                     United States        36.963   -76.562  1,670  116
148      804  008  009  286.0 200  Sandy Hook, NJ                 United States        40.475   -74.02   1,659  101
1516     844  094  095  324.0 200  Hudson Falls, NY               United States        43.272   -73.542  1,595  90 
46       870  170  171  309.0 200  Reedy Point, DE                United States        39.569   -75.572  1,585  106
959      847  058  059  301.0 200  Annapolis, MD                  United States        39.018   -76.61   1,538  110
6        919  308  309  306.0 200  Cardinal, ON                   Canada               44.783   -75.417  1,417  85 
1828     792  136  137  297.0 200  Bobo, MS                       United States        34.125   -90.696  1,233  168
1142     839  118  119  322.0 100  Youngstown, NY                 United States        43.239   -78.972  1,170  95 
73       918  310  311  286.0 200  Wiarton, ON                    Canada               44.75    -81.117  971    87 
2289     838  116  117  319.0 200  Detroit, MI                    United States        42.306   -83.103  883    106
642      836  112  113  292.0 200  Cheboygan, MI                  United States        45.656   -84.475  704    81 
48518    777  218  219  304.0 200  Mequon, WI                     United States        43.202   -88.066  474    113
19773    831  102  103  298.0 100  Upper Keweenaw, MI             United States        47.233   -88.628  446    55 
42384    863  156  157  311.0 200  Rock Island IL                 United States        42.02    -90.231  421    141
35127    830  100  101  296.0 100  Wisconsin, Point WI            United States        46.708   -92.025  219    30 
105106   864  158  159  317.0 200  St Paul [Alma], MN             United States        44.306   -91.906  144    122




CURRENT DGPS ADVISORIES FOR 22 Jun 2017

Site Name    Site Id    BNM #    OUTAGE MESSAGE

SCHEDULED / UNSCHEDULED OUTAGES

Kodiak   897   0239-17   
BROADCAST SITE WILL BE UNUSABLE FROM 06/27/2017 17:30 Z TO 06/27/2017 22:30 Z.

Lincoln   764   0242-17   
BROADCAST SITE IS UNUSABLE AS OF 06/22/2017 18:44 Z UNTIL FURTHER NOTICE.

Lincoln   764   0234-17   
BROADCAST SITE WILL BE UNUSABLE FROM 07/13/2017 16:00 Z TO 07/13/2017 18:00 Z.

Upolu Point   879   0238-17   
BROADCAST SITE WILL BE UNUSABLE FROM 07/05/2017 18:00 Z TO 07/06/2017 00:00 Z.

Bobo   792   0211-17   
BROADCAST SITE WILL BE UNUSABLE FROM 06/27/2017 14:00 Z TO 06/27/2017 16:00 Z.

Youngstown   839   0223-17   
BROADCAST SITE WILL BE UNUSABLE FROM 06/27/2017 13:00 Z TO 06/27/2017 17:00 Z.

Whidbey Island   888   0212-17   
BROADCAST SITE WILL BE UNUSABLE FROM 06/27/2017 17:00 Z TO 06/27/2017 21:00 Z.

Tampa (Macdill)   827   0227-17   
BROADCAST SITE STATUS IS UNCONFIRMED DUE TO NETWORK OUTAGE AS OF 06/13/2017 08:20 Z UNTIL FURTHER NOTICE.


GENERAL INFORMATION

Millers Ferry   865   0157-17   
DGPS BROADCAST SITE WILL PERMANENTLY CEASE BROADCASTING CORRECTIONS ON 30 JUNE 2017 AT 1400Z

Reedy Point   870   0204-17   
DGPS BROADCAST SITE WILL PERMANENTLY CEASE BROADCASTING CORRECTIONS ON 31 JULY 2017 AT 1400Z

Rock Island   863   0158-17   
DGPS BROADCAST SITE WILL PERMANENTLY CEASE BROADCASTING CORRECTIONS ON 30 JUNE 2017 AT 1400Z

St. Paul (Alma)   864   0159-17   
DGPS BROADCAST SITE WILL PERMANENTLY CEASE BROADCASTING CORRECTIONS ON 30 JUNE 2017 AT 1400Z



_{AFE822x v2.0 SDR with 43' Wellbrook ALA100LN loop oriented E-W}

[ChrisSmolinski]

Interesting maybe-catch: Koblenz

Maybe try re-running just the one SDR recording file containing the 0219z time period back through ADGPS with more aggressive settings, and see if any additional decodes pop up?

[skeezix]

What would be good settings for that?

[ChrisSmolinski]

You could make the step limits -25 and 25 (or even larger), and maybe make the step size small, even down to 1 Hz?

[skeezix]

With a step size that small, wouldn't that cause duplicate decodes? Sure, I can get a bunch more, but it would be the same one.

[ChrisSmolinski]

In theory it should not, if the timestamps are the same ADGPS will ignore duplicates (or should). You can always manually delete/ignore any duplicate timestamps you see.

Sometimes this extracts additional decodes out of the noise. Of course it could also be manufacturing them 

[skeezix]

Does it normally ignore dupes too? I frequently get 2-4 decodes without the intense decode. Doing math, I can see how there can be up to three decodes per second at 200 bps (using 1 second resolution). Unsure how I've had 4 or even very rarely 5.

[ChrisSmolinski]

It should ignore them, but there could always be a bug and/or some weird edge condition I am not taking into account (which I guess is also a bug).

[skeezix]

I put in -25, 25, and 1.

Ran it for 10 seconds and St Paul had 663 decodes, Wisconsin Pt 162, Rock Island 285, and Mequon with 271.

[ChrisSmolinski]

OK, so there's a bug. Maybe I can find and fix it before winter 

[skeezix]

Which then brings up the number of decodes per second.

The timestamp has a resolution of 1 second, but there can be multiple messages per second. In the decode output, can you have it additionally log the Z-count with the timestamp? That would make every decode unique and would be able to find dupes easier.

[ChrisSmolinski]

Not easily, it would require lots of changes to the code, both the main app and the DLLs that do the actual DSP, and how data is passed between them.

Are you seeing the duplicates on Mac or Windows? Or both?

[skeezix]

At 0,0,1, I've always seen multiple per second (1-5 (albeit 4 is rare and 5 is extremely rare) on both Mac & Windows. That behavior is consistent¹ between the two platforms.

While changing it would be a lot of work, but I think having a unique identifier (timestamp+zCount) would be very useful to make sure the data is accurate.


¹ While they both exhibit this behavior, multiple runs, even on the same machine, produce slightly different results. This really does not make sense.