Showing posts with label DX. Show all posts
Showing posts with label DX. Show all posts

Saturday, 20 July 2024

Finding Your Best Crystal Radio 'DX Diode' (Part 1)


Over the past few weeks I’ve had time to examine many dozens of diodes, mostly germanium, in my crystal radio diode collection. Many of them were removed from equipment built in the '50s and '60s (old diode matrix boards), some are vintage NIB 1N34As while others are modern SMD Schottky style diodes.

 
There are numerous excellent websites such as this one by Dick Kleijer or  SV3ORA's site  ... all describing elaborate ways to determine which diode is ‘the best one’ (the holy grail diode!) for crystal radio work. Most methods use a vigorous, somewhat complex test procedure plus a lot of math, most of which is well beyond my old brain, in attempts to flesh out each diode’s inherent characteristics ... as the sites referenced above illustrate, the simple appearance of a crystal diode belies its complexity and determining  diode behaviours can be more challenging than one might suspect.

My testing procedures were much more basic, and in the end, may hopefully reveal the best diode in my collection. I think one needs to undertake this with the understanding that there really is no overall ‘best' crystal radio diode but rather, only a diode that is best for your particular system and what works best in my system may not necessarily be the best one in yours.
 
My plan was to measure a few diode behaviors, shrink the list of candidates and then compare them against each other in my system's high-Q tank circuit.
 



My first step was to measure Vf or the forward voltage needed to ‘turn the diode on’. This can usually be determined to reasonable accuracy by using the diode test function on most digital multimeters. I’ve always supposed that the diode with the lowest Vf  turn-on threshold would probably be the most sensitive, but is it the only factor? Hopefully my tests would indicate if anything else is in play.
 
The next task was to determine the minimum signal level of a 1000 Hz modulated carrier on 1400 kHz that could be detected by each candidate diode. An RF probe was used to measure the level of signal capacitively coupled into my crystal radio’s antenna tuning stage which was then lightly coupled  into the detector stage, using the diode under test. No importance was given to the actual base level of this signal other than to note the level at which it could first be detected by ear (using sound powered phones) and making sure the coupling distance between stages remained the same for all diodes under test. This allowed me to compare weak-signal diode ‘sensitivity’ to the diode’s previously measured turn-on point or Vf value. Would the diode with the lowest Vf also be the most sensitive when used in a detector circuit composed of complex impedance, resistance, reactance and capacitance values that the test diode would be looking into?
 
The RF signal coupling was adjusted so the injected carrier could be varied between 0 and 10mV as measured on the RF probe. For each diode, the signal level was slowly increased from ‘0’ until the 1400kHz tone-modulated AM signal could first be detected.
 
The lowest 'first detected' signal level was .6mV while the highest level required 3.4mV, representing a pretty good range of diode behaviours. There were 49 different diodes in the test pool.
 
Four of the 49 diodes detected the .6mV signal, six detected the signal at .7mV, and nine first detected the signal at .8mV. The remainder required a still higher level of injected signal. The average level of first detection was 1.2 mV.
 
Of the four .6mV ‘best detectors’, their turn-on Vf values ranged from .15V to .38V while the .7mV and .8mV detectors had a Vf between .181V and .40V!
 
It seemed, not surprisingly, that generally the higher the Vf turn-on threshold, the greater was the level of signal injection needed for first detection … but evidently using the Vf value alone to determine the ‘best diode’ was not the hard axiom I had always assumed it to be!
 
Since a low Vf was not necessarily needed for good sensitivity, would there by any other tests that might indicate best performance?
 
The next trial was to measure actual diode currents in my hi-Q detector while receiving a lightly-coupled constant level input signal (1400kHz) to see how this value related to Vf. Measured diode currents (Id) varied from 9uA to 14uA for the same level of input signal, with the diode having the lowest Vf also producing the lowest current level ... hhhm! There was more to this than I expected, but generally, the lower valued Vf diodes tended to produce the most current and consequently the louder headphone signal … but not always! Some diodes with a Vf as high as .46V yielded high currents!
 
This now begged the question, “Does the higher current diode with a higher turn on (Vf) prove to be a better overall performer than the diode that turns-on early but produces a weaker signal?” What is the relationship between diode current and weak signal detection?
 
The next step was to express the relationship mathematically by calculating the ratio between the diode’s Vf and the level of diode current  (Id) measured in the previous test (Id / Vf). Each diode could then be assigned a number (Vdx) that might possibly indicate it’s true performance potential in my own system.

The diodes with the highest Vdx values would then be A-B tested under real receive conditions to see if any (or just one!) particular winner(s) might emerge … and if Vf was as critical as initially believed.
 

The Vdx values proved most interesting and seemed to account for some of the anomalies noted in earlier measurements with some of the higher Vdx values coming from diodes not necessarily with a low Vf. I’m hoping that this sorting concept properly takes into account both turn-on level (Vf) and current level (Id), since a higher level in either number will compensate for a lower level in the other. Vdx values ranged from 23 to 66, with seven diodes in the higher 53-66 range.



Click Image For Larger View


All of the 49 diode's test parameters were put onto a spreadsheet and listed in order of their Vdx value.


Click Image For Diode Spreadsheet Data


The highest Vdx assignment of 66 went to my 40-year junkbox resident, a JHS Sylvania 1N3655A microwave mixer diode. It will be interesting to see if it really is the best of the lot! Although it did not produce the loudest signal (Id) compared with others, its Vf turn-on was an impressive .181V and its weak-signal detection level was good although not the lowest. A couple of the UHF diodes exhibited the interesting behaviour of picking up the UHF data stream 'clicks' from my nearby wifi booster. The 1N3655A was one of them.
 
1N3655A Vf = .181V Id = 12uA Vdx = 66
   

Diode #2, with a Vdx of 62, is a mystery diode with a very low Vf of .197V. It was slightly louder and oddly enough, dug down slightly further than the 1N3655A, which had a slightly lower Vf. Although I don’t recall specifically, I suspect the diode may have been removed from a VCR front end many years ago.
 

Mystery diode  Vf =.197V  Id = 12.2uA Vdx = 62
 

Diode #3 with a Vdx of 61 is a modern SMS7630 Schottky microwave detector diode in an SMD package. Although it did not produce a competitive level of loudness (Id) in the diode current test, its shockingly low Vf turn-on of .147V and weak-signal detection threshold were the best of all diodes tested. Before testing, all SMD diodes were mounted on small PC boards in order to attach leads.
 

SMS7630 Schottky  Vf = .147V  Id = 9uA Vdx = 61


Diode #4 (Vdx of 60) is an ISS98, another modern Schottky microwave detector. I recall seeing this diode recommended for good performance in an FM crystal radio detector. Its sensitivity level was excellent.
 

ISS98 Schottky Vf = .211V  Id = 12.5uA Vdx = 60


Diode #5 (also with a Vdx of 60) appears to be a normal germanium of unknown type. I suspect it was used as an RF mixer since it was found on a small printed circuit board with three others, connected in a diode ring configuration typically seen in balanced RF mixers. It produced high current as well as good weak signal capability. 
 

Mystery diode Vf = .22  Id = 13.2uA Vdx = 60


Diode #6 (Vdx of 55) also looks like a germanium of unknown type with a body striping of gray-white-green-gray. If the last band is ignored, this could be a 1N895, a UHF germanium diode. It shows the typical internal cat-whisker type of junction often seen on the 1N34 germaniums.
 

Mystery diode Vf = .238V  Id = 13uA Vdx = 55


Diode #7 with a Vdx of 53 is marked as a ‘95481’ on a green body. It had excellent sensitivity and produced a strong signal (Id), elevating it to the top tier to be looked at more closely.


'95481'  Vf = .246V  Id = 13uA Vdx = 53


Diode #8, another germanium mystery, earned a Vdx of 49 due to its fairly high Id level.



Black 'T'. Vf = .258V  Id = 12.5uA  Vdx = 49


The rather beat-up looking Diode #9 is marked with what appear to be house numbers, '1846' and '6628'. I believe this was pulled from an old portable radio's FM section many years ago. Interestingly, like some of the UHF mixer diodes, '1846 / 6628' detects my high speed modem data stream clicks. Additionally, this tortured specimen produced the highest level of signal among all 49 diodes, with an Id of 14uA.


Vf = .294V  Vdx = 48 Vdx = 14 (Schottky?)


Diode #10 appears to be the brother of Diode #8 with a Vdx of 48. Although it has a lower turn-on point and was a better weak signal detector, it did not produce as much Id as its sibling, dropping it one notch lower on the list. Like its brother, it also has the mystery 'T' marking. Both are most likely unmarked 1N34As.

Vf = .252V  Id = 12 Vdx = 48


As well, three other diodes garnered my interest. Although they ranked lower than I expected, all had previously been found to be good detectors in my system. Their lower ranking may be a hint that my system of grading is not a valid method of determining best performance. All three will be given a harder look in the upcoming elimination tests.

The first is the germanium FO-215. Often touted as 'the holy grail' crystal radio diode but I have never found it to be particularly outstanding. Maybe my system has a lower Q than it really needs in order to show its stuff. This diode is shown on the bar graph above as #11. During testing, it appeared much less capable of weak signal detection than most others but its low Vf and high Id elevated its overall ranking.

Vf = .272V  Id = 13uA  Vdx = 48


The second diode is the Soviet-era D18, a military-grade germanium in a glass '50s-style package. I have previously found it to be a very good detector but its high turn-on level lowered its ranking. The D18 appears on the bar graph as #12.



Vf = .366V  Id = 12.2uA Vdx = 33


The third diode is a vintage Sylvania 1N34 from the 50s and likely one of the first 1N34s to be manufactured. Although it produces a loud signal, its Vf was higher than expected. As I recall, it was salvaged from an old parted-out Heathkit.  It appears on the bar graph as #13.


Vf = .335V  Id = 13uA  Vdx = 39


As mentioned earlier, one can measure and calculate a large amount of data for crystal diodes while they sit passively on the bench but they really need to be mounted, tested and compared in the actual system in which they will be used. Comparing diodes 'A-B' style in real time with weak signals may be better than any measurements made on a diode being bench-tested. 

Will a new ‘holy-grail’ emerge from the pile? This type of testing requires a lot of careful listening so time will tell. 

Testing will be ongoing over the summer / fall months ... stay tuned for the final results, hopefully in time for the fall DX season!

Thursday, 13 August 2020

Some 6m Summer Excitement






With three seasons of FT8 under its belt, there’s no doubt that it's taken over as the number-one mode for the 6m band ... there are very few traces of CW or SSB to be found.

What it hasn’t taken away, is the magic!




For the most part, this summer’s conditions from the west coast were pretty normal, except for when they weren’t ... and when they weren’t, they were pretty spectacular!

The spectacular parts were highlighted by one particularly unique contact that can only be attributed to some heads-up operating skills, a little help from FT8 ... and the unpredictability of Sporadic-E.

On June 20, at 0056Z, K7CW (Paul), south-west of Seattle, nudged his signal all the way to Hong Kong, more specifically, to VR2ZXP’s crowded apartment building. But that’s not the incredible part. That happened when Paul heard and exchanged signal reports with Alfred’s tiny station!

Paul, K7CW

VR2ZXP is located in one of the most densely populated cities on the planet.


Not the best location for weak signal 50MHz DX!

"As I told to Paul, it’s a hard job to be a ham in VR2 Hong Kong especially for the DX. Hong Kong is a high density population city. 99% people are living in apartment only. The housing price here is crazy around US$1800 per sq. feet. Neighborhoods always complain why we setup antennas out of our windows and produce radiation to affect their health. So, what we just can do is to use a small whip with QRO for the QSO. Besides, interference is also serious. Thousands of air conditioner is surrounding me and a power station 132kV to 11kV is just faced to me in 1km away. Here the noise level on low HF band at night is S9."


As indicated above, Alfred’s station is located in a typical high-rise apartment, surrounded by numerous others, with no room for antennas. His solution is to clip a short (60”) whip antenna, horizontally mounted on his balcony railing, similar to this one from 20 years ago ... before being surrounded by noisy high-rise apartment buildings!




I’m not sure which is the most spectacular part of this contact ... that Alfred could detect Paul’s signal in such a noisy environment using such a small makeshift antenna or that Paul was able to copy the tiny signal coming from uptown Hong Kong.





K7CW's 9el - 50' Yagi at 80'
"Anyway, our QSO with Paul is really special. However, I am just a small potato on this story. Without below reason, our QSO may not be success.
1) Paul’s big gun antenna and his station perfect setup.
2) The JT operation mode which introduced by K1JT Mr. Joseph Hooton Taylor. Let me have a chance to say thank you to Joseph."
However, the summertime fun did not stop here. Early on the morning of May 31st, westerners were treated to what some 6m diehards called the best European opening they've ever experienced!
Up on Vancouver Island, John, VE7DAY, was surely glad that he checked the band early, as what followed was a European opening that bounced from one country to another for over 3-1/2 hours! By the time it was over, John had bagged 66 contacts on FT8 and 19 new DXCC entities, including the difficult to work 9H1 in Malta! John's list looks more like 20m CW rather than 50MHz in mid-summer: GM, PA, G, I, DK, 4O, 9H, OM, HG, LA, HB, OE, SM, 9A, MW, YT, OK, LZ, SV!
Long openings like this occur very rarely, making them even more thrilling and can cause even the most experienced 6m DXer’s mouse-hand to tremble with excitement!

Some of VE7DAY's wallpaper from the May 31st opening.

Others up and down the west coast also filled their log pages with ‘new ones’ ... unfortunately my exciter was on the workbench while replacing the screen so I never knew what I had missed until some time later ... probably just as well. I guess I must have been pretty naughty at some point, as the 6m gods definitely singled me out for special punishment that morning.

Once the exciter was back together I was able to catch a few good openings myself, the best of which was early on the morning of June 23 when I was able to work SV9CVY (Crete), SV1DH (Greece) and IS0AWZ (Sardinia).




Crete and Sardinia gave me DXCC #89 and #90. Three days later, during a nice opening to the southern states, J68HZ in St. Lucia snuck through the QRM for #91. After a further three days, on June 29, another very early opening put 8 more Europeans in the log including HA8CE (Hungary) and YU7EF (Yugoslavia) for #92 and #93 respectively.







The band also produced several long openings to Asia, usually in the late afternoon hours. Several contacts were made with South Korean stations, China and dozens with Japan.

All told, the band produced some exciting activity this summer. Countries worked here were:
JA, JW, TG, V31, J68, LA, SM, SV9, SV, IS0, EA, HA, YU, F, 9A5, BG, HL, EA8. Certainly FT8 had much to do with a good portion of the action but it is difficult to say just how much. Many of the Europeans were very strong and could have easily been worked on CW in a matter of a few seconds, rather than the 60 - 75 seconds required for a valid FT8 exchange, assuming there are no repeats. But it's contacts like Paul and Alfred's that continue to validate the special name given to the band ... you just never know what tricks might be next.

Saturday, 11 July 2020

NEOPHYTE Adventures








I've just added a new page to my website, The VE7SL Radio Notebook, that describes my NEOPHYTE 1 regenerative receiver spring construction project. The new page can be found here.







Like most simple regens, its performance far exceeds its simple circuit expectations. My listening adventures with it continue during The Radio Board's annual Homebrew DX Contest which runs from July 11 - 24th. You may want to give it a try, after of course, you've checked-out my new web page!

Wednesday, 25 March 2020

Hunting For NDBs In CLE254




Once again it's a CLE weekend.

During these stressful times, the CLE might hopefully provide some peaceful relief for you.






'CLE's are 'Co-ordinated Listening Events, and NDB DXers around the world focus their listening time on one small slice of the NDB spectrum.

This time the hunting ground is the 20 slice from 400.0 - 419.9 kHz. kHz

A good target for this one is MOG (404kHz) in Montague, California, up near the border with Oregon. It gets out very well and has been logged from Finland to Hawaii. Its been on-and-off of late so maybe you can catch it while it's on again!

Listen for MOG's upper sideband on 405.027kHz with your receiver in the CW mode.

From CLE coordinator Brian Keyte (G3SIA), comes the following CLE info:

Hello all,

Our 254th Coordinated Listening Event starts on Friday.
This frequency range is not packed with signals for any of us, but if conditions are OK there should be some nice surprises.

Do join in, whether you have days to spare, or only an hour or so over the weekend.  Staying at home seems to be essential advice for most of us at present - this could be a great way of spending time there!

    Days:    Friday 27 March - Monday 30 March 2020
    Times:   Start and end at midday your LOCAL time
             (Many of us will be changing our home clocks this weekend -
               however UTC time continues unaffected)
    Range:   400 - 419.9 kHz

Please log all the NDBs that you can identify with nominal (listed) frequencies in the range - it includes 400 kHz, but not 420 kHz - plus any UNIDs that you come across there.

Send your final log to the List (no attachments please and ideally in a plain text email) with ‘FINAL CLE254’ in its title.

Show on each line:
    #   The Date (e.g.  '2020-03-27', etc.,  or just '27' )
    #   The Time in UTC (the day changes at 00:00 UTC).
    #   kHz  - the nominal published frequency, if known.
    #   The Call Ident.

Please show those main items FIRST.  Other optional details such as Location and Distance go LATER in the same line.
As always, of course, tell us your own location and brief details of the equipment that you were using during the Event.

We will send the usual 'Any More Logs?' email at about 19:00 UTC on Tuesday so that you can check that your log has been found OK.
Do make sure that your log has arrived on the List by 08:00 UTC on Wednesday 1 April at the very latest.
We hope to complete making the combined results within a day or two.

You can find full details about current and past CLEs from the CLE page http://www.ndblist.info/cle.htm   It includes access to CLE254 seeklists for your part of the World, prepared from the previous loggings in Rxx.  (Thanks, Martin and Alan, for your help with that)

Good listening
 - enjoy the CLE and do take care of yourself and your family.
      Brian and Joachim
-----------------------------------------------------------------
From:      Brian Keyte G3SIA      ndbcle'at'gmail.com
Location:  Surrey,  SE England     (CLE coordinator)
-----------------------------------------------------------------

  (If you would like to listen remotely  you could use any one remote
  receiver for your loggings, stating its location and owner and with their
  permission if required.  A remote listener may NOT also use another
  receiver, local or remote, to make further loggings for the same CLE)

These listening events serve several purposes. They:
  • determine, worldwide, which beacons are actually in service and on-the-air so the online database can be kept up-to-date
  • determine, worldwide, which beacons are out-of-service or have gone silent since the last CLE covering this range
  • will indicate the state of propagation conditions at the various participant locations
  • will give you an indication of how well your LF/MF receiving system is working
  • give participants a fun yet challenging activity to keep their listening skills honed
Final details can be found at the NDB List website, and worldwide results, for every participant, will be posted there a few days after the event.


The NDB List Group is a great place to learn more about the 'Art of NDB DXing' or to meet other listeners in your region. There is a lot of good information available there and new members are always very welcome. As well, you can follow the results of other CLE participants from night to night as propagation is always an active topic of discussion.

You need not be an NDB List member to participate in the CLEs and all reports, no matter how small, are of much value to the organizers. 

Remember - 'First-time' logs are always VERY welcome!

Reports may be sent to the NDB List Group or e-mailed to CLE co-ordinator, Brian Keyte (G3SIA), whose address appears above. If you are a member of the group, all final results will also be e-mailed and posted there.

Please ... give the CLE a try ... then let us know what NDB's can be heard from your location! Your report can then be added to the worldwide database to help keep it up-to-date.

Have fun and good hunting!


Sunday, 22 December 2019

Hunting For NDB Pairs In CLE251


A fairly popular CLE event held around this time of the year is the "Noah's Ark" Holiday CLE!

It calls for listeners to hunt down and log pairs of NDBs from as many 'radio countries' as possible.


As explained below, in NA and Australia, states and provinces count as separate 'radio countries' thankfully.

For those unfamiliar with this monthly activity, a 'CLE' is a 'Co-ordinated Listening Event', as NDB DXers around the world focus their listening time on one small slice of the NDB spectrum.

If you've been meaning to participate in  CLE, then maybe this weekend is a fine time to try! We continue to have  a lot of first time submissions so you won't be alone!

As well, if you're trying to learn CW, copying NDBs is perfect practice as the identifier speed is generally slow and the letters are repeated again every few seconds!

This past week has seen a long period of great propagation quickly get worse with the arrival of another coronal hole stream. This is quickly abating and the ionosphere may well have fully recovered for the nine-day event.
When tuning for NDBs, put your receiver in the CW mode and listen for the NDB's CW identifier, repeated every few seconds. Listen for U.S. NDB identifiers approximately 1 kHz higher or lower than the published transmitted frequency since these beacons are modulated with a 1020 Hz tone approximately.


For example, 'AA' near Fargo, ND, transmits on 365 kHz and its upper sideband CW identifier is tuned at 366.025 kHz while its lower sideband CW ident can be tuned at 363.946 kHz. Its USB tone is actually 1025 Hz while its LSB tone is 1054 Hz.


Often, one sideband will be much stronger than the other so if you don't hear the first one, try listening on the other sideband.


Canadian NDBs normally have an USB tone only, usually very close to 400 Hz. They also have a long dash (keydown) following the CW identifier.


All NDBs heard in North America will be listed in the RNA database (updated daily) while those heard in Europe may be found in the REU database. Beacons heard outside of these regions will be found in the RWW database.

From CLE organizer Brian Keyte, G3SIA, comes the details:


Hello all

We hope you are looking forward to our "Noah's Ark" Holiday CLE – it
starts at midday on Christmas Day and you can listen at any times
from then right through to midday on Thursday 2nd January.
It's very straightforward. Just as the animals went into the Ark two by two,
so the Radio Countries' NDBs will go into our logs two by two.

    Days:     Wednesday 25th December to Thursday 2nd January
    Times:    Start and End at midday, your LOCAL TIME
    Target:   A maximum of TWO NDBs from each Radio Country
    Range:   190-1740 kHz

So during the course of the event we shall try to log TWO NDBs from each
of as many Radio Countries as we can - e.g. 2 from France, 2 from Spain,
2 from the Florida, 2 from Quebec, 2 from Brazil, 2 from New Zealand, etc.
Each Australian and USA State and each Canadian Province is a separate
Country.  For our full list see: www.ndblist.info/beacons/countrylist.pdf
Each NDB making the pairs can be logged at any times during the event.
UNIDs, Amateur, DGPS and Navtex beacons are not included, but any
UNIDs can be shown in a separate 'non-CLE' list or in a separate email.

Noah didn't have single animals in the Ark, but if you can only log ONE
NDB from a Country, it will still be welcome in your log without a mate!

Everyone is asked to please listen for YOUR OWN NEAREST active NDB
and include it with the one other logging for that Country (if any).

For details of a country’s active NDBs go to www.classaxe.com/dx/ndb/rww/
If you are listening from Europe or North America replace the rww by
reu or rna respectively.    Next to 'Locations' enter the State or Country
abbreviation(s), then select 'Only Active’ at the bottom.

Post your final, complete log to the List (please not in an attachment)
with CLE251 and FINAL in the Subject heading, to arrive at the very latest
by 09:00 UTC on Saturday 4th January.

As usual, please include on every line of your log:
    #  Date** and UTC (the day changes at 00:00 UTC)
    #  kHz (the nominal, published, frequency if possible)
    #  Call Ident

Those main log items must be shown FIRST with the country shown
LATER in the same line, together with any other (optional) details
such as location, offset and distance.


**IMPORTANT -  IF YOU USE THE SIMPLE 'dd' DATE FORMAT.
  The input program for REU/RNA/RWW does not allocate the month and year.
  The good people who enter the information for us then have to tell the
  program what month and year to use.  That is not a problem IF ALL
  LOGGINGS FOR THE SAME MONTH ARE GROUPED TOGETHER.
  So please help us by making sure you separate your December and
  January loggings, even if it breaks up some Noah pairs.


Where possible, we suggest that logs are in Radio Country order, instead
of in the usual kHz order, so that the country pairs appear together.

We'll send an ANY MORE LOGS? email at about 20:00 UTC on Friday 3rd
January showing whose logs we have found. Try to post your log to the
List before that  so you will get confirmation that it has arrived OK.

Good listening, everyone.  Enjoy the CLE.
And finally, radio or not, Joachim and I wish you a very HAPPY CHRISTMAS.

  Brian
(CLE Coordinator)


Reminder 1:
This is an ideal event to help you qualify for one or more of Joe Miller's
attractive Award Certificates - they make great "wallpaper" for any
listening shack.  Joe, our Awards Coordinator, invites us to submit
requests.  http://www.ndblist.info/awards.htm will take you to the
different web pages containing the advice you will need.
Certificates can be ordered direct from the REU-RNA-RWW database.
Now is a good time to apply with so many NDBs going off air.


Reminder 2:
You could use any ONE remote receiver for your loggings, stating its
location and owner - with their permission if required.
( e.g. see https://sdr.hu/ )
A remote listener may NOT also use another receiver, whether local
or remote, to obtain further loggings for the same CLE.


These monthly listening events serve several purposes. They:
  • determine, worldwide, which beacons are actually in service and on-the-air so the online database can be kept up-to-date
  • determine, worldwide, which beacons are out-of-service or have gone silent since the last CLE covering this range
  • will indicate the state of propagation conditions at the various participant locations
  • will give you an indication of how well your LF/MF receiving system is working
  • give participants a fun yet challenging activity to keep their listening skills honed

The NDB List Group is a great place to learn more about the 'Art of NDB DXing' or to meet other listeners in your region. There is a lot of good information available there and new members are always very welcome. As well, you can follow the results of other CLE participants from night to night as propagation is always an active topic of discussion.


You need not be an NDB List member to participate in the CLEs and all reports, no matter how small, are of much value to the organizers. 

Remember - 'First-time' logs are always VERY welcome!

Reports may be sent to the NDB List Group or e-mailed to CLE co-ordinator, Brian Keyte (G3SIA), whose address appears above. If you are a member of the group, all final results will also be e-mailed and posted there.


Please ... give the CLE a try ... then let us know what NDB's can be heard from your location! Your report can then be added to the worldwide database to help keep it up-to-date.

Have fun good hunting and have a great Christmas!

Monday, 16 December 2019

FT8 ... Such A Tease

Looking towards EU over Georgia Strait, last winter



With the continued tsunami of FT8 activity on the HF bands, I decided to have a look at what was happening in the FT8 segment of 160m.




On Saturday afternoon, about ninety minutes before my local sunset here in south west British Columbia, I set my receiver and 160m half-sloper to work, along with WSJT-X, on 1840kHz USB mode.

Although still in broad daylight, the waterfall was immediately flooded with signals! As I started to pay closer attention, I realized that many of the signals were from Europe! Many were audible while the rest were fast-approaching that level, being stronger than -20db. I let the receiver run for another few hours and took a screen capture of my PSK Reporter screen, illustrating what had been decoded over that time span:

courtesy: https://www.pskreporter.info/pskmap.html

Checking other NW or VE7 monitors during the same time span showed no EU decodes at all, which I found surprising ... perhaps I missed someone. My location here on the eastern shoreline of Mayne Island looks towards EU and many other directions directly over a large body of saltwater ocean, Georgia Strait. The photo above was taken last winter, through the living room window. It is also very quiet, electrically, with little or no noise most of the time.

It appears that the lack of man-made noise combined with the theoretical 6db saltwater horizon gain (being realized), is enough to allow these signals to be heard. Signals continued to be decoded as darkness approached but at around 1800 local time, began to drop off ... evidently this appears to be a sunset enhancement, similar to what I often see to the east coast on the 630m band.

Now here’s where it gets even more interesting, as my decodes for the ninety minutes before and after local sunrise indicated a similar pattern!

The most probable path for these signals, around sunrise, would be via the long path in darkness. Although there is no saltwater directly behind me, it seems that the 'quietness' may be enough to do the job. Here’s the slightly post-sunrise screen cap from PSK Reporter:

courtesy: https://www.pskreporter.info/pskmap.html

FT8 is surely a tempting seductress. So far I have resisted the fast-growing urge to spark-up in this mode on 160m ... but I may be growing weaker. This all looks so very interesting.

Sunday, 7 July 2019

Magic Band Mid-Season Observations

courtesy: KC8RP FT8 Info

We are now half-way through this summer’s Sporadic-E season, normally the magic band’s best time of the year. The only exception to this being the winter months of those solar cycles that are robust enough to raise the F2 MUF up as far as 50MHz ... something that occurred for only two or three days during the peak of Solar Cycle 24.

Unfortunately, it really looks as if the old reliable bread and butter modes on 6m, CW and SSB, are fast going the way of the dodo bird, as very few signals on either of these modes have been heard here this summer. As speculated last year at this time, it seems as though the weak signal (WSJT) FT8 mode now reigns supreme on the band, which has come as a great disappointment to myself and many other diehard CW ops.

At the start of this year’s season I reluctantly decided to pay more attention to this mode and see if it could put any  new DXCC entities into my 6m log ... if so, it would be time well-spent.

For the past several years, my main 6m interest has focused on European or South / Central American openings, which are usually unpredictable and short-lived. As usual, most of the season’s openings have been domestic, with signals from the central and south-eastern states being the ones most often heard. Usually, signals during these openings are strong and fairly reliable and lend themselves to easy two-way work on either CW or SSB. For the vast majority of summer time openings, FT8 is not needed, as signals are not weak.

For some reason, the popularity of this weak-signal mode on 6m continues to grow in popularity even though signals are so strong! Where this mode really shines is on the short-lived long haul openings to EU or on similar long paths from the PNW, of which there have been very few this season.

With everyone crowded into a narrow passband of ~ 2kHz, it doesn’t take much to mess things up for your neighbours if you don’t think carefully about how your operating can affect other users of that small sliver of space.

One of the most common examples of poor operating skills that I see is the seemingly endless CQ. This is much easier to do on FT8 than with conventional modes, as the software used can do this automatically for you, every 15 seconds ... while you fiddle with something else in the shack. I’ve seen some nearby stations call CQ continuously for over 60 minutes at a time, with no replies. What this does is make it difficult for other nearby users to actually hear / decode any weak signals on the band that are being covered by the loud CQing station(s) during this entire span of time. Strong local signals can wreak considerable havoc with weak-signal mode software as it's just not designed to happily handle strong signals and do a good job of decoding weak ones at the same time! Please think about this if you are one of those long CQers ... you are not the only one trying to use the band.

Another observation has to do with 'sequencing'. FT8 users must decide if they will transmit on the ‘even’ or on the ‘odd’ 15-second sequence. If you, and all of your neighbours are loud with each other, then it makes sense that everyone is better off operating on the same sequence. This way, all locals are transmitting at the same time which means they are all listening at the same time as well ... nobody causes QRM for one another if everyone uses the same sequence.

This comes off the rails very easily when just one or two strong neighbours choose to transmit during the receive sequence being used by everyone else.

There has been a long-standing precedent for sequencing, established and utilized by meteor-scatter operators for several decades. It calls for stations on the eastern-most end of a path (Europeans for example) to transmit on ‘evens’ ... the ‘0-15’ and ‘30-45’ second segment of each minute. Stations on the western-end of the path (NA) transmit on the ‘odds’ ... ‘15-30’ and ‘45-60’ second portion of each minute. When looking towards JA later in the day, everything reverses for NA stations, as they now become the eastern-end of the path.

Some operators seem to get totally confused by this or don’t check to see what sequence is being used locally before starting to operate ... while some don’t really seem to care.

I’m not complaining about what a given amateur chooses to do but simply describing some of the roadblocks to better use of FT8 and why it is not necessarily very well-suited for 90% of the typical propagation seen on 6m Es.

Many of the newer stations often seem to be using poor or makeshift antenna systems on 6m and are often not able to hear stations responding to their CQs, which may be strong enough locally to disrupt reception for those that are able to hear weaker signals.

I have deliberately made a point of never calling CQ on FT8. From decades of CW DXing I have come to understand that it’s much easier to work DX, on any band, by spending your time listening ... and then calling when the time is right. It’s no different with FT8, yet I see CQs that go on forever. Some will argue that if nobody called CQ, then there would be nobody to hear, which is of course valid ... the reality is, most amateurs cannot resist calling CQ, especially DX stations who enjoy working a pileup. There seems to be no shortage of CQers and those seeking DX should take advantage of that fact.

One loud station was seen yesterday calling another for over 90 minutes-straight. Perhaps he had wandered away from his shack and had forgotten to ‘Halt Tx’ before leaving! FT8 users need to understand how to use their software efficiently.

As for PNW to EU propagation this summer, it has been almost non-existent although I have worked CT1HZE in Portugal and JW7QIA in Svalbard ... by listening ... listening ... and calling briefly, both on FT8. In both cases, signals were brief but strong enough for CW! During the short-lived appearance of the JW7, two NA stations were noted calling ‘CQ JW’ the entire time. Perhaps if they had spent this wasted time more wisely by listening, they would have worked JW.

I’m happy to report that Svalbard was a new DXCC entity for me on 6m, #88, and the first 'new one' in a few years.

It seems that when used sensibly, FT8 is a useful application to have in your DX toolbox ... but for most daily summer Es operation, it’s just not needed. CW or SSB is well up to the task most of the time, even for small stations. Where FT8 shines is on the very brief, often unstable, long haul (EU-NA or JA-NA) paths and then, only if your neighbours don’t do things that will get them into the naughty-corner!

Now, let’s see what the second half of the season has in store for the magic band .... maybe the best is yet to come.