AmateurRadio.com

YUT - 335 kHz (courtesy: VE3GOP)

It's CLE time once again! This coming weekend the CLE  hunting grounds will be 335.0 - 349.9 kHz.







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! Lately, we've had 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!

A nice challenge in this one is to hear YUT - 335 kHz. 'YUT' is located at Repulse Bay, Nunavut, way up on Baffin Island.

'YUT' runs just 25W into a massive vertical and is well-heard throughout North America and parts of northern Europe. Listen for its upper-sideband CW identifier repeated every 10 seconds (with your receiver in the CW mode) on 335.406 kHz.

At this time of the season, summer lightning storms should be drawing down significantly and with some decent propagation there will be many stations to be logged.

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

Our 249th Co-ordinated Listening Event is less than a week away.
Just a normal CLE using a busy range of frequencies.
First-timers' CLE logs will also be very welcome, as always. 

    Days:      Friday 25 October - Monday 28 October
    Times:     Start and end at midday, your LOCAL time
    Range:     335.0 - 349.9 kHz

Please join us wherever you are - just log the NDBs you can identify
having their nominal frequencies in the range (it includes 335 kHz
but not 350 kHz) and any UNIDs that you come across there too.

We last concentrated on these frequencies in CLE233 (June 2018).

Please read the 'Final Details' which will follow on Wednesday.

73   Brian

 (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).

The following blogspot was originally published in July, 2016. Hopefully some will find this of interest as the topic is still very relevant.

***************


A recent posting on Yahoo's Perseus SDR Group inquired about the use of external or PC-based DSP manipulation of signals partially masked by noise to improve readability. The most interesting part of this short discussion was the result of one response indicating:


"BTW one of the best and most simple noise reductions is to lower the volume."

to which the original inquirer responded:

"BTW, lower the volume to reduce noise ... ?? That was a joke, right ??"

Other comments soon followed, including my own, initially:

"Actually, for whatever reason, this works...at least when copying very very weak CW signals. I think it is more of an ear-brain thing where the noise
gets more focus than the signal when listening at moderate levels but
cranking everything down to a very low level has always improved copy for
me....not sure why this works as well as it does."

From Roelof Bakker, PAØRDT:

"The ear brain system works much better at low volume as it is easily
overloaded by strong signals. Similar like too much direct light in 
your eyes will degrade contrast. I guess this is getting worse with
age, but I am not sure about that.

I have been watching many videos on YouTube which demonstrate ham
radio gear and most if not all use far to high volume settings,
which degrades readability. I believe it is a normal habit to raise
the volume for weak signals, but this is often contra productive.

When listening for weak signals at low volume settings, a quiet room
is mandatory. I have taken considerable effort in building a quiet
PC, that is aurally quiet.

What does wonders for copying weak signals with the PERSEUS is to
switch off the AGC."


"No it's not a joke and it's not the RF Gain. It's one of the capabilities of the human ear.

Of course qrm can be limited and reduced but noise is difficult. What you often see is that with all those noise reduction things is that the volume drops. Make an audio recording of a part with and without a (white) noise limiter switched on. Open it into an audio editor and you will see that the amplitude of the part where the noise reduction is on is lower. Now amplify that part to the same level as where the limiter is not active and play it back. You will be astonished how little the difference is.

It's probably also a thing that can differ from person to person but I've never seen tools that can make an unreadable signal readable. Most of the time they sound just different, not better."

Likely there is a ton of data showing how our ear / brain link deals with noise or tones buried in noise. With audio levels set to anything above bare minimum, I think it's very easy for your brain to react mainly to the noise and not to the tone. Reducing this level possibly puts the two back on even levels ... even though there really has been no change in signal-to-noise ratio.

When trying to copy very weak, difficult signals, I've always found that turning audio levels down to bare minimums helps me personally. As Roelof mentioned, the entire environment must be dead quiet as well so that there are no outside distractions. Even the sounds of the headphone cord, brushing against clothing or the table top, can make the difference between copy and no copy. Decades of copying very weak ndb CW idents buried in the noise as well as spending several years on 2m CW moonbounce, has taught me that my ear-brain connection works best when audio inputs are very, very low.

courtesy: http://justagwailo.com/

As an interesting aside, my years of copying weak CW tones, has shown itself in other ways as well. Before retirement as a high school tech ed teacher, staff were required to have their hearing checked annually, as part of the medical plan's requirement. Each year the mobile audio lab would roll-up for the tests. I would always make sure to sit perfectly still, with no headphone cord wires brushing against my clothing. The tones varied in frequency and intensity and were often extremely weak, not unlike the weak echoes I was used to copying from the lunar surface. The reaction from the examiner was always the same, every year ... complete astonishment when checking the results and usually a comment that I had the hearing of a teenager! Thankfully my hearing, which I've always been careful to protect, remains exceptionally good, for which I am truly grateful ... so often this is a genetic thing and there is little one can do about controlling hearing-loss as one ages.

I shudder anytime I see a young person with headphones or earbuds firmly in place and with the music volume cranked up to unbelievably high levels. Sadly, many of them will likely pay the price for this later in life as such hammering-away at the delicate auditory mechanism has a cumulative rather than a short-term effect.

So ... the next time you find yourself trying to copy that ultra-weak signal just riding along in the noise, try turning the audio way, way down. Take a deep breath and listen to the tone, not the noise. If you ask me, the best signal filter is still the one between our ears.

ZSJ - 258 kHz Sandy Lake, ON : source

This coming weekend will see another monthly CLE challenge. This time the hunting grounds will be split:    240.0 - 259.9 kHz and 420.0 - 439.9 kHz.

 

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! Lately, we've had 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!

A nice challenge in this one is to hear ZSJ - 258 kHz. 'ZSJ' is located at Sandy Lake, in northwest Ontario.

'ZSJ' runs 500W into a 150' vertical and is well-heard throughout North America. It has been reported in Hawaii and in Europe. Listen for its upper-sideband CW identifier (with your receiver in the CW mode) on 258.404 kHz.

At this time of the season, summer lightning storms may provide additional listening challenges but maybe we will get lucky. Propagation can often be as good as mid-winter if the lightning cooperates.

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,

These are the final details for our 246th co-ordinated listening event
this weekend.  We'll be listening in two contrasting frequency ranges.
First timer logs too?  Yes, please!

    Days:      Friday 26 July  to  Monday 29 July
    Times:    Start and end at midday, your LOCAL TIME
    Range:    240.0 - 259.9 kHz  plus  420.0 - 439.9 kHz
                     (BOTH ranges are for ALL listeners)

Please log NDBs that you can positively identify in the ranges, plus
any UNIDs that you come across there.
The lower frequency range will be really hard for most listeners in
Europe, the higher range not at all easy for most others.

Send your final CLE log to [email protected]  if possible as a plain text
email and not in an attachment.
Show  CLE246  and  FINAL at the start of its title to help us find your log.
Show on EVERY LINE of your log:

   # The Date (e.g. 2019-07-26, etc.)  or  day (e.g. 26)
   # UTC  (the day changes at 00:00 UTC).
   # kHz  - the beacon's nominal published frequency (if you know it).
   # The Call Ident.

Please show those main items first on each line, BEFORE any optional
details (Location, Offsets, Cycle time, Distance, etc.)
If you send interim logs, do make sure that you also send a 'FINAL' log
containing all your loggings.  As always, do make your log useful and
interesting to everyone by including your own location and brief details
of the receiver, aerial(s) and any recording equipment that you used.

We will send the usual 'Any More Logs?' email at about 19:00 UTC on
Tuesday so that you can check that your Final 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 Wednesday 31 July.  Joachim and I hope to complete
making the combined results within a day or two.

To help you with your search you can find lists and maps showing the
target NDBs for your part of the World at http://www.ndblist.info/cle.htm
Select the  CLE SEEKLIST  link there.

Good listening
      Brian
--------------------------------------------------------------------
From:      Brian Keyte G3SIA       ndbcle'at'gmail.com
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).

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.

When I completed my ‘Jones 6L6 Push-Pull Oscillator’ project in the spring, I made a start on a new ‘spring-summer radio project’ which was to be based on some 1937 RK-39 tubes that had been gathering dust here for many years.

With an unusually sunny and warm spring, I soon found that my radio-bench time was being hi-jacked with a lot of outside yard work and getting all of next winter’s firewood split and stacked away before the really hot weather arrived.

I found myself working on the project in tiny bites, sometimes not making any progress at all during the passage of a week. Headway was also tempered by the fact that I’ll often deliberate for several days over the placement of a single component or the selection of one component over another. I find this slow pace and decision ‘pondering’ during the design phase of any project to be most enjoyable as it gets my old brain working more than normal, on things that really interest me.

I’m happy to report that my latest project is now complete and fully operational and ready for operation!

As usual, I have written and published a web page fully describing the project and some of the background details of the building process.

My ‘Building A ‘37-Style ‘RK-39’ Crystal Power-Oscillator' page can be found here.

Hopefully we can have a CW QSO with it in the near future!

About a month ago I received a new morse code key, the 9A5N solid state CW paddle. I chose the all black twin lever model and from the get go Neno 9A5N was in contact with me. The paddle arrived from Croatia within 3 weeks of me ordering it. Most of the 3 weeks was the key being slowly moved through Canadian customs or it would had been here sooner. It was very well packaged and Neno advises that you keep the shipping box if ever you need to store the key for a move. The uniqueness of the solid state paddle are:
 
- No moving parts to ware or make a clicking noise.
- You just turn it off when not in use so no accidental dit's or dahs sent when inadvertently touching    the paddle.
- There is not maintenance (other than changing the batteries) no periodic mechanical adjustments.
- If you have owned a iambic key there really is no learning curve just turn in on and away you go.

The only adjustment that you may want to do is adjust the touch sensitivity with the key factory set at 10 grams and adjustable to 50 grams in 5 gram steps. Seeing this is a touch paddle depending on your "touch" you may want to increase or decrease the sensitivity. I seemed to be happy with were it was factory set to at 10 grams.
The nice thing about this paddle is it's not bang your head on the wall menu driven. What I mean by this is I have owned ham radio electronic devices that can drive you crazy with long and short holds of buttons and or combination button holds. Then there was the count the short and long beeps and so on. With the 9A5N paddle to adjust the sensitivity you simply turn the paddle on, then hold the on/off button in the on position until you are greeted with 3 LED blinks now release the button and your ready to adjust.Then simply touch the left paddle to increase and right to decrease. If you hit the top end (50 grams) or bottom end (10 grams) the LED will blink 3 times to let you know. To save and try a new stetting either wait 15 seconds or push the power button once.
The only other menu change you can do is place the keyer in contest mode and what this means is the keyer will not time out and turn off on you. Normally If you forget to turn the paddle off it will do so after 40 minutes of non operation.
To enter contest mode make sure the key is off then push and hold the on button until the LED flashes then release the button. So in a nut shell to adjust the key paddle touch sensitivity start with the key turned on and hold the power button. To put the key in contest mode (meaning it will not turn off on it's own) start with the key off and hold the power button. 
The key is very well made and the base is 1.8 kilo's so it's not going anywhere on your desk as you use it.
The last item I wanted to mention was yes it does take batteries (2 AAA) according to Neno's instructions the battery life should be up to 800 operating hours. The blue LED which is on during operation will indicate low battery life when it gets dim. So you do have an indication when its time to change out the batteries. Finally the paddle is warrantied for 24 months from date of purchase.

YPM - 274 courtesy: VE3GOP

This coming weekend will see another monthly CLE challenge. This time the hunting grounds will be 270.0 - 319.9 kHz.

 





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!

A nice challenge in this one is to hear YPM - 274, located in northwest Ontario near Pikangikum.

'YPM' runs just 25W into a 100' vertical but is well-heard throughout North America. Listen for its upper-sideband CW identifier (with your receiver in the CW mode) on 274.368 kHz.

Summer lightning storms may provide additional listening challenges but maybe we will get lucky.

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

Our 243rd co-ordinated listening event is this weekend, covering a 50 kHz
frequency range - about three times wider than usual. 

    Days:     Friday 26 April - Monday 29 April
    Times:   Start and end at midday, your LOCAL time
    Range:   270.0 - 319.9 kHz  (NDB signals only)

In part of the frequency range it might be quite a challenge to tease out
the NDB signals from among the DGPS ones.
Any first-time CLE logs will be very welcome, as always.

Please log the normal NDBs you can identify that are listed in the range
(it includes 270 kHz but not 320 kHz).

Please send your CLE log to NDB List, if possible as a plain text email
and not in an attachment, with 'CLE243 FINAL' at the start of its title.

Show on EVERY line of your log:
  #   The Date  e.g. '2019-04-26', etc.  (or just '26')
  #   UTC  (the day changes at 00:00 UTC).
  #   kHz  - the beacon's nominal published frequency if you know it.
  #   The Call Ident.

Those main items can be in any order within themselves, but BEFORE any
other optional details (Location, Distance, etc.) later in the same line.

As always, give details in your log of your own location and the receiver,
aerial(s), etc. that you were using.
If you send any interim logs, be sure to send a FINAL (complete) one.

You can find anything else to help you, including CLE seeklists for your
part of the World, from the CLE page, http://www.ndblist.info/cle.htm

Please look out for our 'Any More Logs?' email at about 17:00 UTC on
Tuesday so that you can check that your CLE log has been found OK.

Do make sure that your log has arrived at the very latest by 08:00 UTC
next Wednesday, 1st May.
We are hoping to make all the combined results within a day or two.

Enjoy your listening
Brian and Joachim

-----------------------------------------------------------------
From:      Brian Keyte G3SIA      ndbcle'at'gmail.com
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).