WSJT-X Users MUST Upgrade to Version 2.0.0

I had noticed that my waterfall was showing 20 or more signals that should be decoding, but only a few were.  Nevertheless I continued to work stations for this final month of the International Grid Chase.  I became concerned that the internal sound card in my K3s had been damaged.  So today I hooked up a different external sound card and had the same small number of decodes.  That was a good thing, it meant that my radio was fine.  Must be something wrong with configuration of WSJT-X.

Before tearing into things, I went to the WSJT-X website and immediately noticed a fairly stern warning that said the FT8 protocol had been changed in a way that was no longer compatible with older version like mine (1.9.1).  Users were urged to upgrade to 2.0.0 quickly and no longer use the older version starting Jan 1 2019.

Well, that’s the explanation.  In the past few days the standard changed.  My out of date program wasn’t decoding the calls from newer 2.0.0 users.  I updated, and life is back to how I remember it.

Be sure to update your WSJT-X

Posted in FT8, WSJT-X | Leave a comment

Clearing the air on FT8

I follow a fairly large number of groups that are associated with various aspects of Amateur Radio or Electronics. I’ve seen a lot of discussing pro and con about FT8.  My personal view is that Amateur Radio should be as big a tent as possible.  If someone finds something about the hobby that excites them and gets them on the air making contacts that is a good thing.  So all the FT8 folks are doing good things for the hobby, and those that chose to complain would better serve the hobby by simply moving on. 

That said, three things REALLY disturb me about the FT8 discussion, because they are based on misinformation and/or a poor understanding of what is going on.

First misconception is that FT8 is automatic.  You turn on your radio, start the program running, and come back a few days later to see what you have worked.  That is absolutely false.  Yes the timing requirements are such that having a contact proceed without automatic sequencing would be difficult (and would waste time slots).  But the user must initiate the contact.  I did a bunch of RTTY work and shifted to other modes like PSK31 with the times.  I don’t see anything more evil about FT8 than the folks that used to send “Brag Tapes” that would endlessly drone on about their gear.  Honestly anyone who has ever used a program like HRD will find that a PSK31 contact isn’t much less automatic than a FT8 contact.  Click a mouse, punch a function key twice and you have your contact complete and in the log.

Second misconception is the a whopper — FT8 somehow magically decodes signals below the noise floor.  That simply isn’t true.  The MSFK FT8 signals are VERY narrow (6.25 Hertz per tone), and the computer is using VERY narrow filters to detect those signals.  But the individual bits, when looked at at the appropriate bandwidth, are about 9 dB ABOVE the noise floor at a  minimum.  Some might wonder why WSJT-X displays numbers like -18 or -24.  Isn’t that 24 dB below the noise floor?  Well that figure is referenced to a 2500 Hz wide bandwidth (a standard SSB signal), which is why the numbers seem so small.  But take a look at the waterfall and you will see there is no magic going on.  A fellow named Claude Shannon, way back around 1948, proved mathematically that no signal can be decoded lower than 1.6 dB below the true noise floor despite any amount of filtering or processing.  In real life most systems require 5 dB above the noise floor or more.

Last misconception has to do with time keeping, with many folks opining that the clock must be accurate to milliseconds to decode.  While it is true that having your PC clock within a second of accurate time is good, it is not uncommon to work people whose clock is 2.5 seconds off.  The other thing is that the only thing that does matter is that the seconds are accurate.  This is so everyone starts decoding bits at the same time.

It is pretty easy to set your clock based on WWV and get it more than close enough.

OK, off soapbox.  Happy Holidays from the big tent.

Posted in Digital Mode, From the OM, FT8 | Leave a comment

Sad Day for AMSAT – AO-95 RX Malfunction

AMSAT has reported that “during the next steps of commissioning we discovered an anomaly with her receive capability. After a few days of tests, analysis, and discussion, it appears that Fox-1Cliff/AO-95 will not be commissioned as our fourth Fox-1 amateur radio satellite.”

They continue to explore the possibility of recovery, but the bird is not currently receiving commands from the ground, and cannot be removed from “Safe Mode”.  They are requesting telemetry uploads to help diagnose the issue.  AMSAT engineers have been directed to focus their efforts on other projects.

My thanks go out to all the AMSAT volunteers involved with this and other satellite projects, and especially to the engineers that worked so hard getting Fox1-Cliff ready to go. So many good things ahead!

Posted in AMSAT, AO-95 | Leave a comment

One Billion LotW Closing in

On Dec 1, LotW was sitting at 993,013,173 QSOs in the database.  Today, 8 days later, it is now at 996,282,776 Qs.  So in 8 days it has gone up a bit more than 3 million.  If that trend holds, we will be at 999 million on Dec 18, and can expect that final million to happen sometime between Dec 20 and 21.

Posted in LotW | Leave a comment

Congrats to AMSAT for Fox-1Cliff (AO-95)

AMSAT launched another Fox FM Cubesat, Fox-1Cliff, on December 3.  It’s downlink is 145.920 MHz (Uplink 435.300 with a 67.0 Hz tone).  The satellite is still being tested and is not available for use yet, but you can easily hear the voice beacon every 2 minutes when it is overhead saying “Fox1-Cliff Safe Mode”.

I noticed that it was due over my area around from 15:37 to 15:49 UTC.  I had no problem picking up 4 beacon transmissions from 15:41 to 15:47 UTC.  Here is audio from one of them:

Congratulations to AMSAT and the entire Fox Team!

I understand the best-guess object # is 43770, and it is showing up in various tracking programs as Fox1Cliff, AO-95, or object 43770.

Posted in AMSAT, AO-95, Satellite | Leave a comment

LotW Rapidly Approaching a BILLION QSOs

As of today, LotW is sitting at 993,013,173 QSOs in the database.  A bit more than two days ago it was at 991,853,472 QSO.  In other words, adding about a million QSOs every 2-3 days.  At that rate, we might hit 1,000,000,000 QSOs before year end.

Go, go LotW!

LotW Stats as of 16:40 UTC on Dec 1, 2018

Many thanks to the ARRL for a wonderful electronic confirmation system.  It has been fun to see it grow over the past 7 years (my experience with it).

Posted in LotW, Operating | Leave a comment

Has Solar Cycle 25 begun?

From SpaceWeather.com

Over the weekend, a magnetically reversed sunspot appeared in the sun’s northern hemisphere. Its high latitude and “backwards” magnetic polarity mark it as a member of the next solar cycle. Is Solar Minimum over? Not even close, but this development does suggest that Solar Cycle 25 is stirring.

From earthobservatory.nasa.gov:

Sunspot forecasters can distinguish old and new cycles by looking at two features of sunspots. The first feature is latitude. The first sunspots of a new cycle initially appear at high latitudes. As the cycle progresses, they begin appearing progressively closer to the solar equator. The second feature is polarity. Like the Earth, the Sun has a magnetic field, but the Sun’s field flips much more frequently than the Earth’s—usually at the peak of each sunspot cycle. The rapid flipping of the Sun’s magnetic pole affects the polarity of sunspots, helping scientists distinguish between sunspots belonging to different solar cycles.

Posted in Solar Cycles | Leave a comment

Mobile ZumSpot

I’ve been using my ZumSpot on my home WiFi network for a few months.  I’ve heard several folks use their’s with their cell phone internet connection (Hotspot), and started to mess with that a couple of weeks ago.  It didn’t work the first time, it connected to my iPhone WiFi, but didn’t seem to be working.

Today I did a firmware upgrade and update cycle before trying it again, and it seemed to work perfectly.

To add your phone Hotspot to your ZumSpot, go to your pi-star address on your browser and select the “Configuration” tab.  Scroll down the page until you find the “Wireless Configuration” section and select the “Configure WiFi” button.  Turn your cell phone Hotspot on, and wait for its SSID to show up, then select it and enter the Hotspot password.  Once this is done your ZumSpot should be configured to connect to whichever network it finds (home WiFi or phone Hotspot).

Posted in DMR, YSF, ZumSpot | 6 Comments

6-meters: The Magic Band

I usually do a bit of 6-meters operation during the spring and early summer for chance openings, but I’m not a 6-meter OP by any stretch of the imagination.

I was checking my LotW account this morning to see where things stand (goal wise) and I noticed a confirmation had come in from XE2JS in Mexico on the 6-meter band.  Just shows how magical that band can be (even in July).  Funny that I have only the US and Mexico now (only have 23 states confirmed).  I know I’ve worked a number of stations in the Caribbean.

Posted in 6-Meters, DX | Leave a comment

First JS8Call QSO

I’ve been reading the email about the new JS8Call keyboard QSO mode.  If you think FT8 but allowing free-text messaging, you’ve got the basic idea.  The exchange rate isn’t very fast, equivalent to 10-15 WPM CW, but it has similar heavy forward error correction as does FT8.

What you type is broken up into small chunks and sent out, then reassembled by the software.  See the middle of the screen where you can see W8VYM’s final transmission, which took about 5 blocks of 15 second.

I found the software very easy to install, and the setup and use quite intuitive.  I was on the air within a couple of minutes of downloading the program.

My condolences go out to John, WBVYM, in Eastman, GA for putting up with my fumbling during my first on-air QSO.

To obtain the software you must sign-up for the JS8Call group on groups.io (https://groups.io/g/js8call).

Because the software is in beta release, versions automatically expire.  The current version, 0.8.3, expires this Thursday, so a newer release will be out before then.

Thanks to Jordan, KN4CRD, for this fascinating new mode!

Posted in Digital Mode, JS8Call | Leave a comment