Hunting For NDBs In CLE281

YIV-300 Island Lake, MB (ve3gop.com)

It's CLE time once again. This is a challenge for all newcomers to NDB listening and the ultimate test of your medium frequency receiving capabilities. Can you meet the challenge?

'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.

 

It's a little different this time, with beacon hunters asked to report NDBs heard on any and all of the 10kHz markers only ... ie. 350, 360 ..

A central target for listeners in North America is YIV - 300 kHz in Island Lake, Manitoba. Listen for YIV's upper sideband on 300.401 kHz. YIV's 500 watts is widely heard throughout North America and has been logged in Europe. Can you find it?

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, transmitted on 365 kHz and its upper sideband CW identifier was tuned at 366.025 kHz while its lower sideband CW ident could be tuned at 363.946 kHz. Its USB tone was actually 1025 Hz while its LSB tone was 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 organizers comes the following CLE info:

Hello all,

Here are all the details for this weekend's co-ordinated listening event.

This one will be a bit different - we shall be trying out a new kind of ‘Special’. 

 Days:      Friday 24 June - Monday 27 June

 Times:    Start and End at midday, your LOCAL time

 Target:   NDBs with nominal (published) frequencies of:

                       200, 210, 220, 230, ………. . .  , 1630 kHz

                 i.e. the NDBs on any/all of the 10 kHz markers

                 but none on other frequencies (including nnn.5)

We hope this will provide a few more (mid-summer) NDBs than usual for Northern Hemisphere listeners - and for sure a (mid-winter) bonus for Southern Hemisphere listeners who always have relatively few NDBs within range. 

The usual ‘rules’ for log-making will apply.  First-time CLE logs, short or long, will also be very welcome, wherever you are listening from.

Please log the NDBs you can positively identify that are listed on the ‘ ---0.0 kHz’  frequencies, plus any UNIDs heard there too.

Send your CLE log to ndblist@groups.io with  CLE281  and  FINAL  at the start of its title.

Please show on EVERY LINE of your log:

 

   # The date and UTC (the day changes at 00:00 UTC).

   # kHz - the beacon's nominal published frequency, if you know it.

  # The Call Ident.

 

Show those main items FIRST on each line, before any optional details such as the NDB's Location, Distance, Offsets, Cycle time, etc.

As always, make your log meaningful to everyone by including your listening location and details of the receiver, aerial(s), etc.

It would be OK to use one remote receiver, with the owner's permission if necessary, provided that ALL your loggings for the CLE are made using it.

Joachim or I 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 at the very latest by 08:00 UTC on Wed. 29^th June.

We hope to complete making the combined results within a day or two.

You can find all CLE-related information from our CLE page ( http://www.ndblist.info/cle.htm ).

Good listening

 Brian & Joachim

These listening events serve several purposes. They

• determine, worldwide, which beacons are actually in service and on-the-air so the newly-re-vamped Rxx 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 DXers 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!

 

FT8 and the Magic Band

Now that 6m is in full swing once again, many of you will be operating FT8 on 6m for the first time! Things are a little different on 6m compared to operating FT8 on HF and here are a few things for newcomers that might help to keep you out of the naughty corner! (originally published in 2020 but still important today)

 

 

Today’s blog is directed to those that may be new to 6m or new to using FT8 on 6m. Some of the things discussed will make your experience on the magic band better for you and better for your neighbors.

Unlike using FT8 on the HF bands, 6m presents some different challenges, especially if you operate in a region where there may be a lot of other locals also using the band at the same time.


Although the weak-signal capability of FT8 has made it possible for many smaller stations or those with makeshift antennas to take advantage of the unique propagation 6m has to offer, it also can create problems for other users of the band when used inappropriately. In regions of dense population, even small stations can create very high local signal levels, often making it impossible for their neighbors to hear weak signals. This is not deliberately-caused QRM but arises when some operators operate 'against the flow’ and transmit on the opposite ‘sequence’ to everyone else in their local area.

On HF, one can transmit or listen on whatever time sequence they wish. Choosing ‘TX 1st’ or ‘TX 2nd’ is usually determined by who you hear calling CQ or who you wish to work. On 6m however, in a densely-populated region of local operators, chosing to transmit whenever you want to is a luxury that can create big problems for your neighbor who may be trying to hear that weak DX signal while you are transmitting!

These problem will not occur if everybody in the region uses and follows the same transmit-receive periods, so that everyone is listening or everyone is transmitting at the same time ... one or the other. Unfortunately, this ‘ideal’ system falls apart easily when one or more of your neighbors is not using the same sequence as everyone else.

For the past few years, a protocol that seeks to alleviate this problem has become popular and well accepted by those familiar with it. Those new to 6m may not know about it or understand the reasoning behind it.

Above all, I would urge new users of the band, or to the FT8 mode, to first listen carefully for a few minutes, before beginning operation, to determine what the majority of stations in their local region are using for sequencing. If they are using ‘TX 1st’, then your choice of ‘TX 2nd’ will likely cause hearing difficulty for many others, as well as for yourself.

Although there are no strict rules, there is a very successful and well-practiced protocol, and that is that the ‘easternmost’ station transmits on ‘1st’ while the ‘western end’ goes 2nd’. This is why you will hear most eastern stations in the morning hours transmitting ‘2nd’, as they are usually calling or looking for Europeans to their east, who are transmitting ‘1st’. By the same token, you will also hear western stations transmitting on '2nd', who are also looking for Europe to their east, transmitting on ‘1st’.

This sequencing protocol usually reverses later in the day when signals from Asia become a possibility, and all North Americans then become the ‘easternmost’ stations and will transmit on the ‘1st’ sequence ... unlike in the morning. I can easily see how newcomers to the band could become confused, when they hear both sequences being used! The best thing, once again, is to listen carefully first and then ‘go with the flow’.

You can read about the UK's Six Metre Group's initiatives regarding these protocols HERE.

OK... so you’re not interested in EU or Asia? Then it shouldn’t matter to you which sequence that you use and best operating practice would again be to ‘go with the flow’ in consideration of other users.

A few days ago I saw a prime example of exactly what not to do, in too many respects. I made a posting on the ON4KST 6m chat page that VE1SKY in NS (Nova Scotia) was being decoded here, mainly to alert others in my region that European signals might be coming next, as hearing the VE1s in BC is often an indicator that the European path is building.

In less than a minute, an S9+ local began calling ‘CQ NS’ on the exact opposite sequence of all others ... effectively blocking the waterfall and any possible hope of hearing weak EU signals. I’m sorry, but this is just terrible operating procedure, with almost zero chance of success, while showing no consideration for nearby users.

Just like working DX on CW or on phone, the best way, as it always has been, is to ‘listen, listen and then listen some more’. You will work FAR more DX by listening and calling at the right time, than you will by calling CQ.

I also see some local stations everyday, calling endless CQs, often for over 60 minutes straight and often with many replies that go unnoticed. With FT8, one can check ‘work 1st’, go away, and return later to see who they might have ‘worked’. Perhaps this is what these operators are doing, but they should understand that they are also creating non-stop QRM for other users ... those that choose to listen carefully to the band rather than to endlessly CQ. Once again, this is just poor practice.

You may argue that if nobody called CQ, then there would be no contacts made. There is nothing wrong with a few CQs but CQing for an hour? And don’t worry, there will always be other stations CQing endlessly for you to hear, even if it’s not a great way to operate.

With a little pre-planning for sequencing and consideration for your neighbors, everyone can and should be able to enjoy 6m FT8 with very few problems ... and that is my hope for all of us.

After forty-eight summers of CW and phone on 6m and two summers on FT8, these are some of my initial thoughts on how to best operate for maximum success and consideration for other band-users.

The latter is part of the basic framework upon which amateur radio was originally established, when back in 1914, the ARRL described in their 'Code of Conduct' for amateurs ... "The Amateur is Gentlemanly. He never knowingly uses the air for his own amusement in such a way as to lessen the pleasure of others." 

Now, let the magic, and the pleasure, continue!