AmateurRadio.com

YPO - Peawanuck, ON - 401kHz (www.ve3gop.com)

It's CLE time! '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.

A 'challenge target' for listeners in North America is YPO - 401kHz in Peawanuck, ... in north - central Ontario just south of Hudson Bay. Listen for YPO's upper sideband on 401.399kHz. YPO has been heard in Europe, throughout North America and west to Hawaii. Its 125W and ~70' tower work well!

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, now decommissioned, '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. These databases have recently been re-vamped and are slicker than ever before!

From CLE organizers comes the following CLE info:

AP-378 Active Pass, Mayne Island

It's CLE time! '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.

Propagation on MF has been both hot and cold for the past few weeks, seemingly depending on where you live and the amount of geomagnetic activity affecting your region. Thankfully the Sun has ended, for now, its Coronal Hole Streams toward earth which had been causing so much disruption.

After being absent from 2m EME (moonbounce) for the past couple of years, I decided to spark-up again this spring to see if my simple system was still up to the task.

Pretty much every month, during the moon’s sweep through its northern declination, I get several days with moonrises right out in front of the house overlooking Georgia Strait. This is the large body of saltwater separating the British Columbian mainland (and the rest of North America) from Vancouver Island to my west.

Having an ‘over the ocean’ moonrise offers several advantages for me as it pretty well guarantees an extra 6db minimum of system gain (both on transmit and receive modes) and provides a noise-free environment for the antenna to look into.

Because of this advantage I’ve been able to get away with a very minimal system consisting of a single 9el Yagi and a small FM ‘brick’ amplifier which yields around 120W of output. The antenna is tower-mounted at 60’ and controlled in azimuth only. Without being able to track the moon as it rises, the Yagi is broad enough to give me about 2 hours of moon-time on each session before I start to lose signals. With most EME stations using four or more Yagis and high power, most of the heavy-lifting on my two-way work is being done by the other station. With the extra sea-gain here, my single 9el Yagi performs more like an array of four similar Yagis.
 

There always seems to be new stations to work whenever I get on the band and this spring was no exception. All told, I had 20 contacts, with 12 being new 'initials', bringing my total initials count to 130. The remaining 8 contacts were with stations I have worked previously. I was also able to add 2 new states, New Hampshire and Wisconsin, bringing my 2m WAS total to 30.

Conditions were poor to average, with one day in particular being excellent, when at one point I had a pileup of three callers!

Most of the stations contacted are always surprised to learn of my small system and comment that my station is the smallest one they have worked. I have worked a couple of two-Yagi stations over the years with one of them being worked several times.

Here are the cards that have arrived so far for this spring’s session:

If you haven’t given single-Yagi EME a try I would encourage you to test it out as you might be surprised at your results. Even without the added sea-gain, many of my contacts were loud enough to be easily workable with 6db less gain ... and there are dozens of big capable stations out there just waiting for new initials!

LF-336kHz courtesy: http://www.ve3gop.com/

It's CLE time! '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.

Propagation on MF has been both hot and cold for the past few weeks, seemingly depending on where you live and the amount of geomagnetic activity affecting your region. As well, the Sun has been throwing a lot of Coronal Hole Streams toward earth which may or may not affect this weekend's propagation ... but this is all part of the radio-magic fun.

A 'challenge target' for listeners in North America is LF - 336kHz in La Salle, Manitoba, in the southern central part of the province. Even though running just 50 watts, it's widely heard throughout North America and is a good target for listeners everywhere. Listen for LF's upper sideband on 336.390 kHz.

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. These databases have recently been re-vamped and are slicker than ever before!

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

 Hello all,

Our sixth special 'Channels Challenge' listening event is nearly here.
These are the full details.

    Days:      Friday 28 May - Monday 31 May
    Times:     Start and end at midday, your LOCAL time
    Range:     275 kHz - 425 kHz   (see below)
    Target:    Try to log ANY ONE NDB in each channel

The main challenge is to try and log ONE NDB in each of the
151 channels in the range from 275 kHz up to 425 kHz inclusive.
The last time we did this was in CLE248 in September 2019.

The 'channel' means the NDB's NOMINAL (published) frequency.
(It may not be quite where you hear the Morse ident of course). 
In parts of the World some NDBs are on intermediate frequencies,
such as 321.5 kHz.  Logging an NDB on a 'half frequency' would be OK.
  E.g. OK for channel 321 would be  EITHER  one on 321.0 kHz
                OR  one on 321.5 (shown as 321.5 in your log of course).

Each NDB must be a 'normal' one - no DGPS, NAVTEX or amateur.
(If you hear any UNIDs, please show them in a separate list).

So it means a highest possible total of 151 CLE loggings in all - and that
will surely be impossible for everyone!

If you have extra time and want to make the challenge more interesting you
could include NDBs which:

   Give you the greatest number of DIFFERENT RADIO COUNTRIES heard.
   (See our Countries list at
http://www.ndblist.info/beacons/countrylist.pdf

 
    Each State/Province in USA, CAN and AUS is a separate radio country)
   OR  give the greatest TOTAL DISTANCE from you to all of the NDBs.
   OR  include the greatest number of MIDDAY LOGGINGS
          i.e. heard within 2 hours of midday by your local clock time.

Send your 'Final' CLE log to the List, ideally as a plain text email (not in
an attachment) and, IMPORTANT, with CLE268 and FINAL at the start of its
title.
Please show on EVERY LINE of your log:

   #   The full date or day no.  e.g. '2021-05-29' or just '29', etc.
          and UTC (the day changes at 00:00 UTC).
   #   kHz  - the beacon's nominal published frequency.
   #   The Call Ident.

Show those main items FIRST on every line, before other optional details
such as Location, Distance, Offsets, Cycle times, etc.

Tell us your location of course and details of your receiver, aerial, etc.

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

Good hunting,
   Brian and Joachim
-------------------------------------------------------------------
From:      Brian Keyte G3SIA       [email protected]
Location:  Surrey,  SE England      (CLE coordinator)
-------------------------------------------------------------------

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

If you are interested in some remote listening - maybe due to local difficulties - you could use any one remote receiver for your loggings, stating its location and with the owner's permission if required.( e.g. see  kiwisdr.com ) A remote listener may NOT also use another receiver, local or remote, to make more loggings for the same CLE.

These listening events serve several purposes. They

(The following blog, originally published last summer, is as relevant as ever. Please pass the link to those that you think may benefit from reading it.)

 

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

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

If you are a new arrival, with a small or makeshift antenna for 6m, it's important to realize that you may not be hearing what others near you (with bigger antennas) are hearing and can easily mess things up when transmitting at the wrong time.

On HF, one can transmit or listen on whatever time sequence they wish. Chosing ‘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 neighbour 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 neighbours 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 it's 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 terrible 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 neighbours, 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-nine 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!

YUT - Replulse Bay, NU (courtesy: ve3gop.com)

Propagation on MF has been both hot and cold for the past few weeks, seemingly depending on where you live and the amount of geomagnetic activity affecting your region. As well, the Sun has been throwing a lot of Coronal Hole Streams toward earth which may or may not affect this weekend's propagation ... but this is all part of the radio-magic fun.

A 'challenge target' for listeners in North America is YUT - 335kHz in Repulse Bay, NU, at the north end of Hudson Bay. Even though running just 25 watts, it's widely heard throughout North America and Europe and is a good target for listeners everywhere. Listen for YUT's upper sideband on 335.406 kHz.

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. These databases have recently been re-vamped and are slicker than ever before!

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

Hello all

If you are interested in some remote listening - maybe due to local difficulties - you could use any one remote receiver for your loggings, stating its location and with the owner's permission if required.( e.g. see  kiwisdr.com ) A remote listener may NOT also use another receiver, local or remote, to make more loggings for the same CLE.

These listening events serve several purposes. They

I recently had the fluorescent bulb in one section of the under-cabinet kitchen counter lighting fixture go dark. This wasn’t too surprising as the 24” bulb had been in place since the house was built in 1990!

I purchased the replacement bulb only to find out that it was not the bulb but rather the ballast transformer that had failed.

A search for a suitable ballast replacement turned into a quick education when I learned that these things were quickly disappearing, with many models no longer even being manufactured. Another solution would have to be found and it appeared that fluorescents were bring replaced with, what else ... LED fixtures!

Offering similar brightness and colors as traditional fluorescent fixtures, the LED bulbs came in two basic styles.

One type lets you just pop-in a new LED ballast-compatible bulb and away you go. This is convenient but still wastes energy in the ballast and eventually would require an even harder to find ballast.

The second type is a directly-wired LED replacement, not relying on the ballast transformer at all. Having its own built-in switching power supply, these bulbs connect directly to the 120V AC line normally going to the ballast. It’s a very simple task to snip the 120V AC leads from the faulty ballast and connect them to one end of the bulb’s socket. Now totally disconnected, the original ballast can be left in place as is.

The entire fix took less than 30 minutes ... but how much noise or crud would the switching supply produce in the RF spectrum?

Crossing my fingers, I turned the light 'on' as well as my portable Sony ICF-2010 shortwave receiver. I could hear no noise coming from the radio. I could only detect some RF hash when I put the Sony (with its built-in ferrite bar antenna) right beside the fixture! This was good news and its quiet footprint was confirmed later, out in the shack, with radios connected to much larger antennas.

The bulb I used was a ‘toggled’ product, designed and engineered in Detroit , but I suspect is manufactured, like so many other LED devices, in China. The bulbs are sold in Canada and in the U.S. by Home Depot and possibly others.

If you’re looking for a radio-friendly fluorescent replacement or update, I have no hesitation in recommending these directly-wired LED bulbs from ‘toggled’.

And, if you’re also looking for a ham-friendly light-dimmer, see my previous blog on my own hunt for a noisy next-door neighbour.