Pips 6920 kHz 1428 UTC 7Dec15

[jFarley]

Noting pips on 6920.  Period seems to be 3 seconds.  Either props are sucky, or there are gaps in the timing.

No time to chase //s as I have to head out to work.

Seems to have gone off  around 1448 as I write this.
And back on at 1454.

[ChrisSmolinski]

Noted starting around 1519:

5970
6060
6240
6320
6420
6720
6820
6920
7020
7460
7570
7680
7800
7920
8040
8160
8280
8400
8530
8660
9050
9190
9330
9610
9900
10510
10200
10350
10670
10830
10990
11490

5970 seems to be the lowest, I checked and nothing lower. They were getting quite weak above 8 MHz, so I could have missed some.

[Token]

Noting pips on 6920.  Period seems to be 3 seconds.  Either props are sucky, or there are gaps in the timing.

No time to chase //s as I have to head out to work.

Seems to have gone off  around 1448 as I write this.
And back on at 1454.

They have used 3 second timing before, but typically that is with a shorter pulse, about 0.063 sec.  the other possibility is that you were on a frequency that was part of both networks, and you heard both of them.  Typically there are one or two frequencies in a set that have both networks active on them, so you hear an odd spacing.  If youa re hearing about a 3 sec spacing with the 0.125 sec pulse I would bet this is the case, particularly if you hear the shorter spacing on one freq, and longer spacing on another.

I was not at home this morning, so could not grab anything on these today.

T!

[ChrisSmolinski]

Noted again, at least on 6820 and 6920, at 1755z.