We seek to understand and document all radio transmissions, legal and otherwise, as part of the radio listening hobby. We do not encourage any radio operations contrary to regulations. Always consult with the appropriate authorities if you have questions concerning what is permissible in your locale.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Cherrypie

Pages: [1]
1
Spy Numbers / Re: E07a Transmission issues?
« on: March 12, 2017, 1833 UTC »
Unfortunately, no. I did not capture a recording of the 2100 transmission. I did however take a good transcript that can be found in my previous post.

2
Spy Numbers / Re: E07a Transmission issues?
« on: March 11, 2017, 0155 UTC »
3/8/17

Notes:
E07a missed scheduled transmission on 4577 kHz. It is scheduled at 2240 UTC. I can verify the transmitter was operational, I received traffic from it 60 minutes prior.
This could possibly suggest multiple transmitters aimed at Europe and at North America.
 
-----------------------------
3/8/17
E07a
Start: 2220 UTC
End: 2224 UTC
5277 kHz USB

Null with 9 groups of:

825 825 825 000


-Cherrypie

E07a did not miss the transmission in the time period pointed out.  By the way Cherrypie, I think you have done a time conversion wrong, it should have been 2120 UTC, Wednesday, March 8, 2017, on 5277 kHz, not 2220 UTC as you posted.  In the 2200 period that day, at 2200, 2220, and 2240 UTC, would be M12 (E07a's Morse code sister station), not E07a.

In March, on Wed / Thu the 2100 time schedule is 2100 UTC on 5877 kHz, 2120 UTC on 5277 kHz, and 2140 UTC on 4577 kHz.  The same message, if any, will be sent in each time slot.

However this station, like all of the stations in its related family, will NOT transmit the third transmission if the message is a null.  The third time spot, 2140 UTC, will only be used when there is a message.

As noted, the 2100 UTC, 5877 kHz, and the 2120 UTC, 5277 kHz, transmissions were a null, "825  825  825  000".  Since there was no message, it was a null, the 2140 UTC TX did not happen.

And that is what the "in case of traffic" means, if there is a message to send, and not a null, the third time period will also be included.

So, no schedule missed, just normal operations for the station.

T!

I now realize my mistake on the time conversion. However the format is intriguing. The first message had traffic, the second was null. Therefore I assumed the traffic would have been re-transmitted on the third transmission. Thanks for correcting me Token, I appreciate it.

3
Spy Numbers / E07a Transmission issues?
« on: March 10, 2017, 0542 UTC »
3/8/17

Notes:
E07a missed scheduled transmission on 4577 kHz. It is scheduled at 2240 UTC. I can verify the transmitter was operational, I received traffic from it 60 minutes prior.
This could possibly suggest multiple transmitters aimed at Europe and at North America.
 
-----------------------------
3/8/17
E07a
Start: 2220 UTC
End: 2224 UTC
5277 kHz USB

Null with 9 groups of:

825 825 825 000


-Cherrypie

4
Spy Numbers / E07a 4577 USB 2140 UTC 3/8/17
« on: March 10, 2017, 0519 UTC »
3/8/17
4577 USB
Start:2140 UTC
End: 2146 UTC
616 1 616 1 616

42814 90048
40005 36295
02253 91468
85697 65098
89724 68557
50304 67909
68147 06572
34433
000 000

Notes:
Header had minor technical issues. Short .25-.5 second pauses occurred.

Pages: [1]
HFUnderground Mug
HFUnderground Mug
by MitchellTimeDesigns