Topics

196

HF Beacons / Single letter beacons, March 13, 2015

« on: March 13, 2015, 1818 UTC »

Some of the single letter beacons seen here this morning:

- 7039.2 kHz, F beacon
- 7039.3 kHz, K beacon
- 7039.4 kHz, M beacon
- 8495.0 kHz, C beacon
- 8495.2 kHz, F beacon
- 8495.4 kHz, M beacon, bad audio harmonics about every 100 Hz
- 10872.0 kHz, C beacon
- 10872.4 kHz, M beacon
- 13528.0 kHz, C beacon
- 13528.1 kHz, A beacon

T!

197

HF Beacons / Post dawn, tune around the beacons, March 13, 2015

« on: March 13, 2015, 1808 UTC »

To go along with my "pre dawn" tune around the beacons, here is a quick look at an hour or so later, post dawn.

- 4097.1 kHz, 1443 UTC, Inyo Whooper.
- 4095.73 kHz, 1503 UTC, dasher, unknown dasher, dash is about 5.78 seconds long and every 10.48 seconds.  Later it shortened up to about 5.3 seconds long every 10.3 seconds.  Pronounced frequency sag on dash start.  Similar to old Coxie, but not sure it is the same beacon.
- 6626.17 kHz, 1531 UTC, ditter, dits are about 0.075 seconds long and about 0.69 seconds apart.  I have seen this beacon a few times, but not sure if it has been reported here.  Almost lost in Rocky/Rainy, but clearly separate on close inspection.
- 6626.33 kHz, 1531 UTC, ditter, Rocky.
- 6626.48 kHz, 1531 UTC, ditter, Rainy.
- 6700.43 kHz, 1613 UTC, Hexy2k dasher, about 0.48 sec dash every 0.91 sec.
- 8193.72 kHz, 1620 UTC, Marin Dit.
- 8194.2 kHz, Inyo Whooper second harmonic.

T!

198

HF Beacons / Pre dawn, a tune around the beacons, March 13, 2015

« on: March 13, 2015, 1750 UTC »

I have not been paying much attention to the beacons recently.  Sure I see them as I tune around, but not really taking note.  A few of the old friends are gone, and one or two new ones appear to be there.  So this morning I took a little look.

These are the ones noted pre local dawn, I will do a separate post on the post dawn beacons seen.

- 2016.73 kHz, 1352 UTC, ditter, dit is about 0.16 sec long and occurs about every 0.88 seconds.  I have been seeing this one for a while, but I am not sure it has ever been reported here.
- 2018.26 kHz, 1352 UTC, ditter, dit is about 0.22 sec long and occurs about every 1.25 seconds.  Cycles on and off, about 2 mins on for 5 mins off, but this may vary.
- 2097.3 kHz, 1359 UTC, A beacon.  Sends letter A in CW about every 10 seconds.
- 4094.5 kHz, 1403 UTC, X beacon.  Sends letter X in CW about every 7 seconds.
- 4096.27 kHz, 1405 UTC, dasher, Hexie, dash is about 1.13 seconds long and sent about every 2.19 seconds.
- 7998.2 kHz, 1346 UTC, dasher, dash is about 0.65 sec long and occurs about every 3.1 seconds.
- 13559.95 kHz, 1407 UTC, ditter, dit is about 0.050 seconds and sent about every 1.09 seconds.  Dit has rough ending that might be 2 shorter dits, so this could be sending the letter D in fast CW.  Has been active for some time, but not sure if reported here.

T!

199

HF Mystery Signals / MOVED: Pips 13559 kHz

« on: March 01, 2015, 1757 UTC »

This topic has been moved to HF Beacons.

http://www.hfunderground.com/board/index.php?topic=20854.0

200

HF Mystery Signals / MOVED: 6605 usb cw

« on: February 27, 2015, 0126 UTC »

This topic has been moved to Spy Numbers.  Since this is obviously CW, even if it was unidentified, it is not a mystery.

http://www.hfunderground.com/board/index.php?topic=20809.0

201

HF Beacons / Possible new beacon, 4096.8 kHz, 1420 UTC, January 30, 2015

« on: January 30, 2015, 1436 UTC »

While cruising the bands this morning I ran across what might be a new beacon around 4096 kHz, at least it does not quite match what I have noticed there before.

A dasher, sending an aproximate 0.15 second long dash about every 0.95 seconds.  Center freq about 4096.8 kHz.  Measurements are rough as the signal was very weak.

I might be wrong, but I don't recall a beacon matching these parameters being here before.

T!

202

Spy Numbers / New Asiatic M12 Thursday schedule with log, January 22 2015

« on: January 22, 2015, 1936 UTC »

While at the listening gear last night (0030z, January 22, 2015) I noticed a short duration carrier come up on 14492.3 kHz in AM with somewhat muddy broadcast station audio followed by some quick dashes.  This is the same habit sometimes seen when the Sunday V07 and Wednesday / Saturday Asiatic M12 transmitters are warmed up prior to transmission.  So I parked a receiver on that freq for a while.

At 0100z a new (to me) M12 transmission started.  The signal levels and bearing of reception (towards Asiatic Russia or Kamchatka from my location) match the V07 and Wednesday / Saturday M12 signals, and the choice of frequencies also closely matches.  I think it is probable that this is from the same source as those two schedules.

I tried multiple European remotes at the same time to see if it could be heard there.  As most often with the Sunday V07 and the Wednesday / Saturday M12 I could not receive these transmissions using the European remotes.

Since this was the first night of reception for me I have no idea yet what other days this schedule might be active.  But the schedule has been added to my automated recordings to find out.

Schedule chart here (short though it is yet):
http://www.tokenradio.net/Radio/SharedFiles/NumbersTfer/M12_T_Pacific_latest_sched.JPG

T!
Mojave Desert, California, USA

Thursday schedule Asiatic M12 Logs
M12  15826kHz  0100z  22/01/2015  [435  435  435  1  1  1 (R9),  791  127 (R2)]  0111z  Strong  T!  THU
M12  14576kHz  0120z  22/01/2015  [435  435  435  1  1  1 (R9),  791  127 (R2)]  0131z  Strong  T!  THU
M12  13416kHz  0140z  22/01/2015  [435  435  435  1  1  1 (R9),  791  127 (R2)]  0151z  Strong  T!  THU

Although the group count and transmission time for this message matches what was sent the day before, on January 21, 2015 during the 0020 / 0040 / 0100 schedule, the message was not the same.

203

Spy Numbers / Asiatic M12 Wednesday / Saturday schedule logs, Dec 20 2014 to January 21 2015

« on: January 22, 2015, 1935 UTC »

The somewhat new Asiatic M12 station on Wednesday and Saturday continues.  The frequencies for January are now known.  The station still occasionally tunes up the transmitter using audio that might be from a broadcast station, as does V07 and the newly found Thursday Asiatic M12 schedule.  I have had no luck hearing this station on European remotes, only on Asian and Western US receivers.

Schedule chart here:
http://www.tokenradio.net/Radio/SharedFiles/NumbersTfer/M12_WS_Pacific_latest_sched.JPG

T!
Mojave Desert, California, USA

(edit)  For those of you wondering "what is an Asiatic M12?"  The numbers station M12 has historically been largely reported by European listeners, and the source has been in or near Europe.  The transmissions I am reporting here seem to be (not proven, but good indications) sourced from far eastern Russia or Kamchatka.  I carry these transmissions in my logs as "Asiatic M12" only to make searching my logs and tracking station activity easier.  Other than probable source location there are no real differences between this M12 and the ones normally reported in Europe.

Wednesday / Saturday schedule Asiatic M12 Logs
M12  18576kHz  0020z  20/12/2014  [548  548  548  T T T (R9)]  0022z  Strong  T!  SAT
M12  17436kHz  0040z  20/12/2014  [548  548  548  T T T (R9)]  0042z  Strong  T!  SAT

M12  18576kHz  0020z  24/12/2014  [548  548  548  1 (R9),  564  1t1 (R2)]  0029z  Strong  T!  WED
M12  17436kHz  0040z  24/12/2014  [548  548  548  1 (R9),  564  1t1 (R2)]  0049z  Strong  T!  WED
M12  15826kHz  0100z  24/12/2014  [548  548  548  1 (R9),  564  1t1 (R2)]  0109z  Strong  T!  WED

M12  18576kHz  0020z  27/12/2014  [548  548  548  1 (R9),  564  1t1 (R2)]  0029z  Strong  T!  SAT
M12  17436kHz  0040z  27/12/2014  [548  548  548  1 (R9),  564  1t1 (R2)]  0049z  Strong  T!  SAT
M12  15826kHz  0100z  27/12/2014  [548  548  548  1 (R9),  564  1t1 (R2)]  0109z  Strong  T!  SAT

M12  18576kHz  0020z  31/12/2014  [548  548  548  T T T (R9)]  0022z  Strong  T!  WED
M12  17436kHz  0040z  31/12/2014  [548  548  548  T T T (R9)]  0042z  Strong  T!  WED

M12  15826kHz  0020z  03/01/2015  [854  854  854  T T T (R9)]  0022z  Strong  T!  SAT
M12  14576kHz  0040z  03/01/2015  [854  854  854  T T T (R9)]  0042z  Strong  T!  SAT

M12  15826kHz  0020z  10/01/2015  [854  854  854  T T T (R9)]  0022z  Strong  T!  SAT
M12  14576kHz  0040z  10/01/2015  [854  854  854  T T T (R9)]  0042z  Strong  T!  SAT

M12  15826kHz  0020z  14/01/2015  [854  854  854  T T T (R9)]  0022z  Strong  T!  WED
M12  14576kHz  0040z  14/01/2015  [854  854  854  T T T (R9)]  0042z  Strong  T!  WED

M12  15826kHz  0020z  21/01/2015  [854  854  854  1  1  1 (R9),  843  127 (R2)]  0031z  Strong  T!  WED
M12  14576kHz  0040z  21/01/2015  [854  854  854  1  1  1 (R9),  843  127 (R2)]  0051z  Strong  T!  WED
M12  13416kHz  0100z  21/01/2015  [854  854  854  1  1  1 (R9),  843  127 (R2)]  0111z  Strong but QRM from S4285  T!  WED

204

10/11 meters / MOVED: Mystery signal question

« on: January 05, 2015, 1924 UTC »

This topic has been moved to HF Mystery Signals.

http://www.hfunderground.com/board/index.php?topic=12565.0

205

European Pirates and Private Stations / MiniRadio11155 kHz LSB January 4 2015, 1438 UTC

« on: January 04, 2015, 1444 UTC »

Music and ID announcement on 11155 kHz LSB, 1438 UTC, January 4, 2015.  I did not understand the announcement at first but playing back the recording it is MiniRadio.  Heard on European remotes, not locally in California.

(edit 2) Off with no announcement 1449 UTC

(edit 3) Appears to have moved to 9010kHz USB at 1454 UTC

T!

206

North American Shortwave Pirate / UNIDed CW 6925.1 kHz AM 0015 UTC 21 December 2014

« on: December 21, 2014, 1857 UTC »

UNIDed CW and music transmission in AM, I first noticed it at about 0015 UTC, December 21, 2014, on 6925.1 kHz.  

I noticed an MCW transmission that started at roughly 0015 UTC, it sent CW in AM mode saying "attention west coast 5 watt pirate radio show 22 Dec 0200 UTC sstv and physical qsl card awaits k" and then into some kind of music (too weak to make out).  It then repeated the cycle, CW and same music (might have been an announcement jingle), and off 0041 UTC.  It came back on air at 0045 UTC and repeated the message one time, CW and then jingle/music, off at 0052.

I could hear Channel Z under this transmission.

Unless the operator missed a date this is an announcement for a show the next night, Dec 22.

T!

207

Spy Numbers / Asiatic M12 Logs, Dec 6 to Dec 17, 2014

« on: December 19, 2014, 1620 UTC »

A newly reported M12 schedule that is probably sourced from Asiatic Russia or Kamchatka region continues, and we now have all three 0020/0040/0100 frequencies for December.  For internal note keeping purposes this one is temporarily called Asiatic M12 in my electronic log, only to make it easily searchable and distinguishable from European M12 logs. 

If you are on the US west coast, Canada, or South America your chances are very good on hearing this station.

Chart here:
http://www.tokenradio.net/Radio/SharedFiles/NumbersTfer/M12_Pacific_latest_sched.JPG

Recording of 10/12/2014 113 group message here:
http://www.tokenradio.net/Radio/SharedFiles/AudTfer/M12_18576_CW_12102014_0020z.mp3



Asiatic M12 Logs

M12  18576kHz  0020z  6/12/2014  [548  548  548  T T T (R9)]  0022z  Strong  T!  SAT
M12  17436kHz  0040z  6/12/2014  [548  548  548  T T T (R9)]  0042z  Strong  T!  SAT

M12  18576kHz  0020z  10/12/2014  [548  548  548  1 (R9),  567  113 (R2)]  0030z  Strong  T!  WED
M12  17436kHz  0040z  10/12/2014  [548  548  548  1 (R9),  567  113 (R2)]  0050z  Strong  T!  WED
M12  15826kHz  0100z  10/12/2014  [548  548  548  1 (R9),  567  113 (R2)]  0110z  Strong  T!  WED

M12  18576kHz  0020z  17/12/2014  [548  548  548  T T T (R9)]  0022z  Strong  T!  WED
M12  17436kHz  0040z  17/12/2014  [548  548  548  T T T (R9)]  0042z  Strong  T!  WED


T!

208

Other / Intruder dashes on 29679.9 kHz, Dec 17, 2014

« on: December 17, 2014, 1634 UTC »

For the last couple days I have been hearing dashes on about 29679.9 kHz, the frequency does appear to move around a little.  I first noticed them about 2300z on Dec 16, and they are still up right now, 1530z Dec 17.

The dashes appear to be spaced about every 2.35 seconds, and they are roughly seconds 0.46 seconds long.  There is either some kind of modulation on the first 0.06 seconds of the pulse, or it takes the transmitter that long to settle.  About 0.06 seconds further into the pulse (roughly 0.12 sec from start) there is a further glitch.  The pulse is stable for the remaining time it is on, about 0.32 sec.

T!

209

Other / MOVED: UNID CW station 8009 khz 23:23 - 23:31 utc 12-6-14

« on: December 17, 2014, 1611 UTC »

This topic has been moved to Spy Numbers.

http://www.hfunderground.com/board/index.php?topic=19755.0

210

HF Mystery Signals / READ THIS BEFORE POSTING, what this board is, and getting the most out of it

« on: December 01, 2014, 1623 UTC »

This board is about identifying mystery or unknown modes heard in the HF spectrum.  If you don’t know what a signal is there is a good chance that others might know, or at least be able to take a good guess.  As signals are identified here they will be added to the HF Signals Identification Wiki here (  http://www.hfunderground.com/wiki/Signal_Identification  ) on HFU (if they are not already on it).

The purpose of this board is not to ID unknown transmission, but rather the mode of a transmission.  That means those odd noises you always wondered about as you tuned across the bands.  If you hear an unknown SSB net or unknown ALE net and want to know who it is or where it is from it should not be addressed here, the mode of those transmissions are already known, and there are other boards on HFU to ask such questions.  However, if you hear a signal that you cannot identify the mode of, and it turns out to be ALE, this is the perfect place for that.  There will be some overlap here, but let’s try to stay with unknown modes as much as possible.

Not everyone has the same level of exposure in a hobby such as this, so it is understandable, in fact inevitable, that occasionally someone will ask about a mode that has already been covered or seems very basic.  So what?  As long as the person asking the question goes away with more information than they started with, it is all good.

Keep in mind that the folks answering here typically are not professionals and might not know either, so if you get no answer that does not mean you are being ignored.  Sometimes unknown stays unknown, but that does not mean a discussion about it does not shed at least a little light on it.  And a lot of people only check these boards every once in a while, so your question might not be answered right away.

What should be in a post?

Without certain basic data a mode cannot be identified.  The more data you can include in your post the more likely the mode is to be correctly identified.  For example, asking a vague question like “I heard a clicking noise in the 8 MHz band, what is it?” will probably not result in a meaningful answer.

The minimum information presented with a question should be:

1.  Frequency (kHz)
2.  Time (UTC)
3.  Duration
4.  Receiver Mode
5.  Receiver Location
6.  Description.

1.  Frequency of the signal, preferably in kHz.  Be as precise as you can be here, sometimes one or two kHz can be the difference between a proper ID and a false ID.

2.  Time of the reception, in UTC.  Radio reports are almost universally done in UTC or GMT anyway, it avoids confusion.  If you post it in your local time then whoever wants to answer has to convert to UTC to get an idea of when it was, and they may not know your location or the proper time offset for your location.

3.  Duration of the transmission.  Was this a signal that stayed on constantly?  Or did it come and go in short bursts?

4.  Receiver mode you were using when you heard the signal.  Sometimes when people do not know what a signal is they use an incorrect mode to try and listen to it.  A signal will often sound different depending on what mode you use to listen to it.

5.  Location of receiver.  This does not have to be exact information, but signals that might be heard on 8000 kHz at 2300 UTC on the west coast of the US are a little different than the ones that might be heard at the same time in Jalalabad.  If you are using a remote receiver than your location is not the one that counts, but rather the location of the receiver is what needs to be known.

6.  Your description of what you heard.  What did it sound like?  What do you think it might be?  Even if you don’t know what it is it can’t hurt for you to say what it sounded like.



In addition to the above minimums there is additional information that can increase the likelihood of a correct identification.

If using a local radio, what is your receiver and antenna?

It is very desirable for you to include a link to a video or audio recording of the signal in question.  Including a recording increases the chances of a correct identification significantly, I cannot stress enough how helpful to ID this is.  If you are unsure what receiver mode to record the audio in, try a couple of them.  Unfortunately it is not always possible to make such a recording.

A picture of the transmission goes a long way.  If you are using an SDR a screen shot of the waterfall display is a big help.  If you are using a traditional receiver a screen shot of the audio fed into some kind of spectral display software, like Argo, fldigi, SpectroGram16, etc, is a good thing.