Author Topic: E07a Transmission issues?  (Read 730 times)

Cherrypie

  • Newbie
  • *
  • Posts: 4
    • View Profile
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
When you can't figure out why your SWR is so high. Then you realize your antenna isn't plugged in.

MDK2

  • DX Legend
  • ******
  • Posts: 1892
    • View Profile
    • My radio reception videos
Re: E07a Transmission issues?
« Reply #1 on: March 10, 2017, 1411 UTC »
According to priyom.org's schedule, that 4577 kHz transmission is scheduled "in case of traffic." I'm not sure what they mean by traffic exactly, but the implication seems to be that it won't necessarily transmit. I guess that there was no "traffic" during the 2100 and 2120 transmissions.
Denver, CO.
Grundig Satellit 750, Tecsun PL-600, SDRPlay RSP2 Pro.
two homebrewed mag loops (10' and 15' circumference).
Soon to include RA0SMS mini-whip, but need mounting before that goes online.
eQSL's appreciated, wickerjennie (at) gmail

Token

  • Global Moderator
  • DX Legend
  • *****
  • Posts: 1521
    • View Profile
Re: E07a Transmission issues?
« Reply #2 on: March 11, 2017, 0128 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!
« Last Edit: March 11, 2017, 0132 UTC by Token »
T!
Mojave Desert, California USA

Cherrypie

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: E07a Transmission issues?
« Reply #3 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.
When you can't figure out why your SWR is so high. Then you realize your antenna isn't plugged in.

Token

  • Global Moderator
  • DX Legend
  • *****
  • Posts: 1521
    • View Profile
Re: E07a Transmission issues?
« Reply #4 on: March 11, 2017, 0305 UTC »
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.

The fact the first TX at 2100 had a message and that the second at 2120 was a null is the odd part, that would be an error.  And since the 2140 TX did not happen, that would seem to indicate the first slot should have been a null also.

You wouldn't happen to have a recording of the 2100 TX would you?

By the way, the callup of this family of stations gives you a clue to the frequencies that will be used.

All three of these time slots, 2100 UTC on 5877 kHz, 2120 UTC on 5277 kHz, and 2140 UTC on 4577 kHz, in March will have the callup of "825".  Notice anything with that callup and and those freqs?  All the freqs end in 77, and the 100's kHz digit is the same as the callup digits in that order.

I mean, look at the callup, 825, eight, two, and five.  And the first time slot freq is 5_8_77 kHz.  The second time slot freq is 5_2_77 kHz.  The third time slot freq is 4_5_77 kHz.  This family of stations does this commonly.

T!
« Last Edit: March 11, 2017, 0312 UTC by Token »
T!
Mojave Desert, California USA

Cherrypie

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: E07a Transmission issues?
« Reply #5 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.
When you can't figure out why your SWR is so high. Then you realize your antenna isn't plugged in.

Token

  • Global Moderator
  • DX Legend
  • *****
  • Posts: 1521
    • View Profile
Re: E07a Transmission issues?
« Reply #6 on: March 12, 2017, 2213 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.

OK, unfortunately I am a little confused then.

Looking at the two threads, your first post in this thread said that E07a missed a sched on 4577 kHz.  You said it missed the 2240 UTC TX, but apparently you mean the 2140 UTC TX, that is the time it should have been on 4577 kHz if there was a message, an easy time conversion mistake and no biggy.   By the way, those kinds of time noting errors are part of the reason every clock I can see at the radio desk, including the PC clocks, are on UTC time.

Then you quote 2220 UTC on 5277 kHz with a null.  Again this should be 2120 UTC, but once the time gets hosed in the notes it tends to stay that way ;)  The transcript you posted fits well for what should have been in the 2120 UTC, 5277 kHz transmission, assuming a null.

When I asked about a recording of the 2100 TX you said no, but the transcript in the other thread was what was sent.  Quoted below:

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

Looking at that post, with the transcript, it says 4577 kHz at 2140 UTC.  So that post says that the 2140 UTC TX on 4577 kHz did happen.

However the message posted, the transcript, is the one that should have been sent at 2040 UTC on 7651 kHz.  The callup 616 is used on the set of 2000 UTC / 10651 kHz, 2020 UTC / 9151 kHz, and 2040 UTC / 7651 kHz.

Could there be some errors in your notes?

T!
T!
Mojave Desert, California USA