Archive for the ‘dx’ Category

Yet in Quarantine, Life Blossoms!

About a month ago, I asked,

What is going on with you during this challenging situation?” and, “How do you use amateur radio, now that we are all stuck at home?  Are you using ham radio more, now?  Less?

I am moved to say, “Thank you, to each of you who commented and even those who made a video response. I sure appreciate it!

During that video blog (or, Vlog), back a month ago (link: Chat From a Quarantined Software Engineer – Welfare Check!), I mentioned my need for dental surgery. 

I did have to have the tooth removed.  It was completely split down the middle (top to bottom), down to the root.  There was no justifiable way to save the tooth. 

I now am missing two bottom back-most teeth, and one bottom, back-most tooth.  I can report that I have healed up nicely.  I am starting to enjoy a hamburger or two.

Through all of this, I’ve still been working. Also, I’ve been involved with a LOT more ham radio–especially with Morse code activities.

How has the last month treated you?  After watching this new video (below), please leave a comment or two, or three; let hear from you, okay?

More than anything, please leave a comment to let me know how you are doing.  I hope to hear from you.

Here’s the video:

73 de NW7US dit dit

 

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!


Contest Morse Code, Computers, and an Icom Rig

This past weekend (third full weekend in February, February 15-16, 2020) is the ARRL International CW Contest (ARRL DX CW link: http://www.arrl.org/arrl-dx ). This is interesting to my study of radio signal propagation as a columnist and as an amateur radio operator​ because of the contest objective: “To encourage W/VE stations to expand knowledge of DX propagation on the HF and MF bands…” This contest is a good way to get a feel for current propagation–though there are caveats.

Speaking of Morse code and the CW mode on our amateur bands: those of you using CW during contests, do you send by hand or by computer?  Do you copy the code by head, or do you use a computer for decoding?

Do you use a computer for Morse code operation?

Just curious about those of you who use CW. Do you send by hand or computer? Receive by head or computer?

In most contests like the ARRL DX CW contest, I copy by ear, and send mostly by rig keyer. If needed, I use a single paddle key with the Icom rig’s internal keyer to answer unique questions and so on.

Below is a quick demo of using the internal Morse code keyer in my Icom IC-7610 transceiver.

V47T, in the Saint Kitts and Nevis Island in the Caribbean, is calling CQ TEST in the ARRL DX CW contest.

Using the programmable virtual buttons, in which I programmed my callsign, NW7US, and other info, I answer and make a complete contest QSO.

In activity like the Straight Key Century Club (SKCC – https://SKCCGroup.com) K3Y special event, it is all manual. I send my Morse code using a WWII Navy Flameproof Signal Key, and decode with my ears.  It is contextual for me.

How do you do contesting Morse code?  Bonus question: How do you do logging while doing contest operation?

73 es best dx = de NW7US dit dit

 

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!

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.

How Did You Fare in CQ WW CW Contest Weekend?

Man, lots and lots of Morse code on the ham bands, this weekend. The CQ Worldwide CW Contest weekend was hopping with signals!

How did you do this weekend? How were conditions on the various contest bands?

Comment here and your report may make it into the propagation column in an upcoming edition of the Radio Propagation column in CQ Amateur Radio Magazine.

Here are a few moments as heard at the station of the CQ Amateur Radio Magazine propagation columnist, in Lincoln, Nebraska (yeah, that’s me, NW7US).

Here are the results of my dabbling with the Icom rig and this contest:

 NW7US's Contest Summary Report for CQ-WW
 Created by N3FJP's CQ WW DX Contest Log
 Version 5.7  www.n3fjp.com

 Total Contacts = 55
 Total Points = 8,979

 Operating Period: 2019/11/24 10:23 - 2019/11/24 22:51

 Total op time (breaks > 30 min deducted): 3:58:46
 Total op time (breaks > 60 min deducted): 4:45:17

 Avg Qs/Hr (breaks > 30 min deducted): 13.8


 Total Contacts by Band and Mode:

 Band       CW   Phone     Dig   Total       %
 ----       --   -----     ---   -----     ---
   80        8       0       0       8      15
   40        7       0       0       7      13
   20       25       0       0      25      45
   15       15       0       0      15      27
            --   -----     ---   -----     ---
 Total      55       0       0      55     100

 Total Contacts by State \ Prov:

 State       Total     %
 -----       -----   ---
                52    95
 HI              3     5

 Total = 1


 Total Contacts by Country:

 Country                      Total     %
 -------                      -----   ---
 Canada                           6    11
 Brazil                           5     9
 USA                              5     9
 Argentina                        3     5
 Costa Rica                       3     5
 Hawaii                           3     5
 Bonaire                          2     4
 Cayman Is.                       2     4
 Chile                            2     4
 Cuba                             2     4
 Japan                            2     4
 Mexico                           2     4
 Aruba                            1     2
 Bahamas                          1     2
 Barbados                         1     2
 Belize                           1     2
 Curacao                          1     2
 Dominican Republic               1     2
 French Guiana                    1     2
 Haiti                            1     2
 Honduras                         1     2
 Martinique                       1     2
 Montserrat                       1     2
 Nicaragua                        1     2
 Senegal                          1     2
 St. Kitts & Nevis                1     2
 St. Lucia                        1     2
 Suriname                         1     2
 US Virgin Is.                    1     2
 Venezuela                        1     2

 Total = 30


 Total DX Miles (QSOs in USA not counted) = 151,407
 Average miles per DX QSO = 3,028


 Average bearing to the entities worked in each continent.
 QSOs in USA not counted.

 AF =  83
 AS = 318
 NA = 124
 OC = 268
 SA = 137


 Total Contacts by Continent:

 Continent   Total     %
 ---------   -----   ---
 NA             32    58
 SA             17    31
 OC              3     5
 AS              2     4
 AF              1     2

 Total = 5


 Total Contacts by CQ Zone:

 CQ Zone   Total     %
 -------   -----   ---
 08           13    24
 03            7    13
 09            7    13
 07            6    11
 11            5     9
 13            3     5
 31            3     5
 04            2     4
 05            2     4
 06            2     4
 12            2     4
 25            2     4
 35            1     2

 Total = 13

From Lightning Comes a New Icom IC-7610 (First Transmission)

Wow. What a radio!

One of the most useful (and, to me, amazing) features of this Icom IC-7610, is the IP+ function, which, when turned on, improves the Intermodulation Distortion (IMD) quality by optimizing the direct sampling system performance. This function optimizes the Analog/Digital Converter(ADC) against distortion when you receive a strong input signal. It also improves the Third-order Intercept Point (IP3) while minimizing the reduction of the receiver sensitivity.

In short: I was listening to an s-0 (i.e., no strength-meter movement) weak signal of a DX station, when right adjacent to the frequency came an s-7 signal, wiping out my ability to copy that weak signal. I turned on the IP+ and the distortion of the adjacent signal disappeared, and once again, I heard the weak signal IN THE CLEAR! WOW!

This video is a quick capture of my running the Olivia Digital Mode on HF, on the 30-Meter band. The transmissions are of a two-way Olivia digital-mode radio conversation between station K8CJM and station NW7US on 12 November 2019 (UTC date). K8CJM is located in Dayton, Ohio, and I am located in Lincoln, Nebraska. I’m running the radio at full power. The radio is rated as being able to handle 100% duty cycle at full power. The radio ran cool, no significant heating.

A few months ago, a lightning strike took out my ham radio station. The antenna was NOT connected, but I did not unplug the power supply chain and my computer from the wall. The surge came in through the power mains, and fried my uninterruptable power supply, the interfaces between my PC and radio, and fried the radio. Thankfully, all of that was covered by my homeowner’s insurance policy, less the steep deductible. My insurance covered all of the blown items, and that provided me this chance to obtain a repack version of the Icom IC-7610. I bought an extended four-year warranty.

CAUTION: Check the documentation of your transceiver/transmitter. NEVER run your radio’s power out at a level that exceeds what it can handle in reference to the duty cycle of the mode you are using. Olivia, for instance, is a 100-percent duty cycle mode. Morse code is NOT quite 100% duty cycle. Nor is SSB, a mode that operates with a duty cycle much lower than 100%. Your radio’s manual should tell you the specifications regarding the duty cycle it can handle! If you run more power than your radio can handle with the given duty cycle of the mode in use, you will blow your radio’s finals or in some other way damage the radio! Beware! I’ve warned you!

Compression and ALC!?

Some have noted that it appears that I’ve left on the Compression of the transmitted audio. However, the truth is that compression was not being used (as is proof by carefully taking note of the zero meter movement of the Compression activity). I had the radio set for 20-Meter USB operation on the Sub VFO. Compression was set for standard USB operation. Note also that the radio was transmitting USB-D1, which means the first data/soundcard input to the radio.

Also, some people complain about my use of ALC, because, in their view, ALC (automatic level control) is a no-no for data modes.

The notion that one must NEVER use ALC when transmitting digital modes is not accurate.

Multi-frequency shift keyed (MFSK) modes with low symbol rate–such as the Olivia digital modes–use a single carrier of constant amplitude, which is stepped (between 4, 8, 16 or 32 tone frequencies respectively) in a constant phase manner. As a result, no unwanted sidebands are generated, and no special amplifier (including a transmitter’s final stage) linearity requirements are necessary.

Whether the use of ALC matters or not depends on the transmitted digital mode.

For example, FSK (Frequency-Shift Keying; i.e., RTTY) is a constant-amplitude mode (frequency shift only). In such a case, the use of ALC will NOT distort the signal waveform.

PSK31 does contain amplitude shifts, as an example, therefore you don’t want any ALC action that could result in distortion of the amplitude changes in the waveform.

On the other hand, the WSJT manual says that its output is a constant-amplitude signal, meaning that good linearity is not necessary. In that case, the use of ALC will NOT distort the transmitted signal-amplitude waveform. You can use ALC or not, as you choose when you run WSJT modes, or Olivia (MFSK).

Clarification

Nowhere in this am I advocating running your audio really high, thinking that the ALC will take care of it. I am not saying that. I am saying that some ALC is not going to be an issue. You MUST not overdrive any part of the audio chain going into the transmitter!

Transmit audio out of the sound card remains at a constant amplitude, so there will be no significant change in power output if you adjust your input into the radio so that the ALC just stops moving the meter, or, you can have some ALC meter movement. You can adjust your audio to the transmitter either way.

If the transmitter filters have a significant degree of ripple in the passband then you may find that RF power output changes with the selected frequency in the waterfall when there is no ALC action. Allowing some ALC action can permit the ALC to act as an automatic gain adjustment to keep the output power level as you change frequencies.

Linear and Non-Linear

Regarding linear and non-linear operation (amplifiers, final stages): While a Class-C amplifier circuit has far higher efficiency than a linear circuit, a Class-C amplifier is not linear and is only suitable for the amplification of constant-envelope signals. Such signals include FM, FSK, MFSK, and CW (Morse code).

If Joe Taylor’s various modes (in WSJT software) are constant-envelope signals, than class-C works, right? At least, in theory.

Some Additional Cool History

The digital mode, Thor, came out of DominoEX when FEC was added. Here is an interesting history of FSQ that seems to confirm that FSQ is like MFSK, so no problem with a bit of ALC.

The following is from https://www.qsl.net/zl1bpu/MFSK/FSQweb.htm

History – Let’s review the general history of Amateur MFSK modes. The first Amateur MFSK mode developed anywhere was MFSK16, specified by Murray Greenman ZL1BPU, then first developed and coded by Nino Porcino IZ8BLY in 1999. Before MFSK16 arrived, long-distance (DX) QSOs using digital modes were very unreliable: reliant, as they were, on RTTY and later PSK31. MFSK16 changed all that, using 16 tones and strong error correction. Great for long path DX, but nobody could ever say it was easy to use, never mind slick (quick and agile)!

Over the next few years, many MFSK modes appeared, in fact too many! Most of these were aimed at improving performance on bands with QRM. Most used very strong error correction, some types a poor match for MFSK, and these were very clumsy in QSO, because of long delays.

The next major development, aimed at easy QSOs with a slick turnaround, was DominoEX, designed by Murray Greenman ZL1BPU and coded by Con Wassilieff ZL2AFP, which was released in 2009. Rather than using error correction as a brute-force approach, DominoEX was based on sound research and achieved its performance through carefully crafted modulation techniques that required no error correction. The result was a simpler, easier to tune, easily identified mode with a fast turn-around.

DominoEX is widely used and available in many software packages. A later development by Patrick F6CTE and then Dave W1HKJ added FEC to this mode (THOR) but did not add greatly to performance, and at the same time eroded the fast turn-around. The final DominoEX- related development was EXChat, a version of DominoEX designed specifically for text-message style chatting. While completely compatible with DominoEx, it operates in ‘Sentence Mode’, sending each short over when the operator presses ENTER. EXChat was developed by Con ZL2AFP and released in 2014.

Back in 2013, Con ZL2AFP developed an MFSK mode for LF and MF which used an unusual decoding method pioneered by Alberto I2PHD: a ‘syncless’ decoder, which used a voting system to decide when one tone finished and another began. The first use of this idea was in JASON (2002), which proved to be very sensitive, but very slow, partly because it was based on the ASCII alphabet. The new mode, WSQ2 (Weak Signal QSO, 2 baud) combined the syncless decoder with more tones, 33 in total, and an alphabet specially developed by Murray ZL1BPU, which could send each lower case letter (and common punctuation) in just one symbol, resulting in a very sensitive (-30 dB SNR) mode with a 5 WPM typing speed.

In the subsequent discussion in late 2014, between the developers ZL2AFP and ZL1BPU, it was realized that if the computer had enough processing power to handle it, WSQ2 could be ‘sped up’ to become a useful HF chat mode. This required a large amount of development and retuning of the software to achieve adequate speed was involved, along with much ionospheric simulator and on-air testing used to select the most appropriate parameters.

Tests proved that the idea not only worked well, but it also had marked advantages over existing HF MFSK modes, even DominoEX. As expected, the new mode was found to have superior tolerance of signal timing variation, typically caused by multi-path reception, and would also receive with no change of settings over a wide range of signaling speeds.

So this is how FSQ came about. It uses the highly efficient WSQ character alphabet, IFK+ coding, the same number of tones as WSQ (33), but runs a whole lot faster, up to 60 WPM, and uses different tone spacing. The symbol rate (signaling speed) is modest (six tones per second or less), but each individual tone transmitted carries a surprising amount of information, resulting in a high text transmission speed. And it operates in ‘Chat’ (sentence) mode, which allows the user to type as fast as possible since they type only while receiving.

The ability to send messages and commands selectively has opened a huge array of communications possibilities.

What Makes FSQ Different

Incremental Keying – FSQ uses Offset Incremental Frequency Keying (IFK+), a type of differential Multi-Frequency Shift Keying (MFSK) with properties that make it moderately drift-proof and easy to tune. IFK+ also has excellent tolerance of multi-path reception.

IFK was developed by Steve Olney VK2XV. IFK+ (with code rotation) was proposed by Murray Greenman ZL1BPU and first used in DominoEX. IFK+ prevents repeated same tones without complex coding and provides improved rejection of propagation-related inter-symbol interference. In the context of sync-less decoding, the IFK+ code rotation also prevents repeated identical tones, which could not have been detected by this method.

Efficient Alphabet – In FSQ, a relatively high typing speed at a modest baud rate comes about because the alphabet coding is very efficient. All lower case letters and the most common punctuation can be sent in just one symbol and all other characters (the total alphabet contains 104 characters) in just two symbols. (The alphabet is listed below). This is a simple example of a Varicode, where it takes less time to send the more common characters. The character rate is close to six per second (60 WPM), the same as RTTY, but at only 1/8th of the baud rate. (RTTY has only one bit of information per symbol, 7.5 symbols per character, and wastes a third of its information on synchronization, and despite this, works poorly on HF).

No Sync – Another important factor in the design of FSQ is that no synchronizing process is required to locate and decode the received characters. Lack of sync means that reception is much less influenced by propagation timing changes that affect almost all other modes since timing is quite unimportant to FSQ; it almost completely eliminates impulse noise disruption, and it also contributes to very fast acquisition of the signal (decoding reliably within one symbol of the start of reception). Fast acquisition removes the need for the addition of extra idle characters at the start of transmission, and this leads to a very slick system. Add high resistance to QRM and QRN, thanks to the low baud rate, and you have a system so robust that it does not need error correction.

Cool.

See you on the bands!


Subscribe FREE to AmateurRadio.com's
Amateur Radio Newsletter

 
We never share your e-mail address.


Do you like to write?
Interesting project to share?
Helpful tips and ideas for other hams?

Submit an article and we will review it for publication on AmateurRadio.com!

Have a ham radio product or service?
Consider advertising on our site.

Are you a reporter covering ham radio?
Find ham radio experts for your story.

How to Set Up a Ham Radio Blog
Get started in less than 15 minutes!


  • Matt W1MST, Managing Editor




Sign up for our free
Amateur Radio Newsletter

Enter your e-mail address: