First QSO(s) using FT8

I recently downloaded the Release Candidate for WSJT-X v1.8.0-rc1 as I was curious to try out the new FT8 mode.

After ticking the boxes Auto Seq and Call 1st I tuned to 20 metre band and set the program to call CQ.
There was a bit of waiting before a station replied to my call but then the program did everything itself. The whole QSO went like this

    CQ G8YPH IO83

    G8YPH SP6ECQ JO71

    SP6ECQ G8YPH -14

    G8YPH SP6ECQ R-14

    SP6ECQ G8YPH RRR - at which point the log QSO dialog box popped up. I just clicked OK

   G8YPH SP6ECQ 73
    SP6ECQ G8YPH 73 - this was transmitted automatically as a courtesy

Then the program went back to transmitting CQ again. It all worked seamlessly and the logging was intercepted by JTAlert and passed via QSO Relay to Ham Radio Deluxe logging module. I didn't have to add FT8 to HRD as some people have queried on the HRD peer support Facebook group as it was done automatically.

An initial auto controlled QSO

FT8 Waveform in the waterfall. Considerably different
than other JT Modes

Overs are 15 seconds long so FT8 can cope with fading QSOs. I believe you need a fast PC though to cope with decodes. These tend to take around 1 second at around the 13th second of the receive cycle.

I also noticed it coped well with hiccups in reception where nothing was received or decoded from the answering station in the middle of a QSO. When a successful packet was received the program went onto the next step in the transmission sequence - transmitting two or three RRR's until a 73 was received for instance.

Software versions used at G8YPH

• WSJT-X Version 1.8.0 Release Candidate 1
• JTALert-X 2.9.10
• QSO Relay 1.6.6371.29224
• Ham Radio Deluxe 6.4.0.661

Radio Yaesu FT-450D

So far I am impressed but the extra 73 transmission means you don't go back to calling CQ after you have sent a successful RRR and received a 73 from the receiving station.

WSJT-X 1.8 Release Candidate

I've just downloaded the release candidate for WSJT-X from https://physics.princeton.edu/pulsar/k1jt/wsjtx.html and installed it.
This version has the new FT8 mode and I was eager to try it out.

It seems to be able to automatically establish communications after calling CQ and initiate a full QSO. I have yet to make my first contact with it despite being on 20m for a couple of hours.

There isn't much information available about FT8 (that I have found) but from what I have seen so far it looks like a useful mode for quick QSO's normally associated with fading signals.

JTAlert once again supports Ham Radio Deluxe - but read on

I just noticed this on hamapps.com

"New JTAlert 2.10.0 is available for download.

This version has full support for FT8 and the 15sec T/R period.
HRD v6 logging is again supported. HRD v5 and V6 users need to upgrade their JTAlert version to 2.10.0 to avoid logging and spotting the wrong mode (FT8 spotted/logged as T10 or JT9).

Visit HamApps.com for the download link and upgrade instructions.

Please review these release notes for 2.10.0
  **** HRD V6 logging is again supported by JTAlert.
  **** The HRD V6 logging support in this release is a one-time event.
  **** Releases after 2.10.0 will again no longer have HRD V6 support.

  New Features:
    - Full FT8 mode support and its 15 sec T/R period.
    - All the Wanted alert types support FT8 mode tracking.
    - Scan Log supports FT8 mode for all Alert types.
    - Additional Alert tracking option, "Any WSJT-X Mode (JT65 or JT9 or FT8)".
    - FT8 mode statistics from HamSpots included in Band Activity displays.
    - Call History popup & standalone window support FT8 data from Log lookup.
    - WSJT-X mode character included in JTAlert titlebar (before the Band).
       Character matches that used in WSJT-X, "#" = JT65, "@" = JT9, "~" = FT8.

  Changes:
    - Macros window single instance setting removed. Each JTAlert instance must
       open its own Macro window for each WSJT-X/JTDX instance.
    - End TX/RX Period alert disabled for FT8 mode.
    - Auto-Halt after current TX is disabled for FT8 mode.
    - Confirmed Bands Display (below log fields) right area will display Bands
       worked/confirmed matching WSJT-X TX mode JT9 or FT8
    - Many internal code changes to support FT8 mode and 15s T/R period and to
       correctly distinguish between WSJT-X and JTDX running processes.
       (** The JTDX program calls itself wsjtx.exe which it isn't **)
    - The multi-instance support has also been changed. Running multiple copies
       of JTAlert against both WSJT-X and JTDX simultaneously is not supported.
       You can run multiple instances of JTAlert against either WSJT-X OR JTDX
       only. Both types of applications can be running simultaneously on the PC,
       but only one JTAlert operating mode (against WSJT-X or JTDX) is allowed.

  Fixes:
    - WSJT-X docking stops when a WSJT-X Configuration switch is made.
    - DXKeeper Capture window inadvertently populated when DXKeeper is instructed
       to filter its display on a new DX Call change.

de Laurie VK3AMA"

One time event? I'm not sure what is going on there and I actually don't care. I now use the excellent QSO Relay as a go between to allow JTAlert and HRD logging to function

HRD 6.4.0.659 Issue

I thought this was a temporary fault with HRD 6.4.0.646 as reported in a previous post. The latest version 659 still has the same problem.
This is when upgrading from an older version to the current version then the installation routine uninstalls the Microsoft Access Runtime.

Not a major issue as long as you manually reinstall the runtime before you fire up the logbook module.

Making QSO Relay auto start in Windows 10

QSO Relay, if you haven't already tried it out, is a superb piece of software written by VK2BYI. Essentially it bridges the gap between JTAlertX and Ham Radio Deluxe since the author of JTAlert discontinued support for HRD 6.x (the paid for version of HRD).
QSO Relay sits in between the two pieces of software and relays QSOs to HRD.

QSO Relay normally runs in the task bar
near the clock. After a reboot it was found
not to be automatically running.

I found that occasionally it wasn't logging until I found out why. It wasn't running in the task bar after a reboot. On Windows 7 you can just drag the shortcut for any software you want to run on Windows startup into the StartUp folder on the start menu.

Not so on Windows 10 and you have to do a little fiddling to get it to do the same.

Press the Windows key and R simultaneously to bring up the Run dialog.

In the box that appears type shell:startup and press OK

Windows explorer opens in your own AppData location

Next drag the shortcut of the program you wish to auto start into the explorer box, in this case the shortcut of QSORelay.

Close explorer and that is it. Next time you reboot Windows and login QSORelay will be automatically running.

QSO Relay 1.3 - An update

Chris Fredericks VK2BYI responded to a support email about an issue I was seeing with QSO Relay.
I was seeing a popup message saying that QSO Relay could not verify if a QSO had been written into the HRD Database.
I switched on "Enable Tracing" as per the troubleshooting guide.

This Created a Session log and also should the Exception logs. After turning off the enable tracing tick box it wrote all the issues to the session log.

I then sent Chris the contents of my c:\users\<my user name>\AppData\Roaming\VK3BYI\QSORelay folder to the email stated in the guide

He replied back the very next day with the solution to my problem.  When I looked at his advice I indeed hadn't created a connection string to the HRD Access DB. I had not configured QSO Relay correctly - DOH. I'm not sure how I missed that but a few clicks and I was done.

Next right clicking the QSO Relay icon in the task bar brought up the "Synchronise Databases.." option.

This synchronises the JTAlertX and HRD databases. I clicked it and got a message back saying that I had a duplicate record in my HRD database. It wrote the actual error into an exception log which is human readable. There it was in plain sight. I had a dupe in the log from back in 1980 that I hadn't noticed!
I deleted the dupe from HRD logbook and ran the synchronise process again. It ran without error.

Next, while still having the "Enable tracing" option checked I made a WSJT-X JT65 QSO.
QSO Relay intercepted the ADIF log and parsed it through to HRD without any error. I disabled the "Enable tracing" option and the session log was written to and closed. Examination of this log found that communication had worked and all was good.

I can't emphasise just how useful this small program is in your radio arsenal. When using WSJT-X and Ham Radio Deluxe Version 6.x in conjunction with the latest JTAlertX it is an essential addition.

Great thanks go to Chris VK2BYI for adding this superb program to the ham radio community and his fantastic support.

QSO Relay Version 1.3 review

I have been using JTAlertX 2.8.7 with Ham Radio Deluxe and decided to stick with that configuration due to the author of JTAlertX withdrawing support for HRD V6 (the paid for version).
This has been to the disappointment of many radio hams worldwide as the community thought that the two packages integrated well together. For whatever reasons the olive branch to make up was offered to the author from HRD LLC and was ignored.

Anyway new on the scene is a small program written by VK2BYI that enables usage of the later versions of JTAlertX to function again with Ham Radio Deluxe. Hurrah I hear you say.

I installed version 1.3 of the software this morning along with the latest version of JTAlert. QSO Relay comes with quick installation instructions and an in depth manual. It makes use of MicroSoft .Net Framework 4.6 which is pre-installed on Windows 10. Older versions of operating system may require you to install .Net Framework 4.6 if it hasn't been installed by other programs on your system.

JTAlertX needs to be changed to log to a standard ADIF file. The Quick Install pdf file shows you how to configure this.When firing up the QSO Relay software the first time after installation you need to configure it.
The pdf file shows you how to do it and then synchronize your HRD database with QSO Relays own SQLlite database.

Operation

In use the QSO Relay acts as a proxy between JTAlertX and Ham Radio Deluxe logbook.  It runs as a system tray application that listens for contacts being forwarded from WSJT-X/JTALertX via a UDP port. As datagrams are received they are logged locally in a SQLLite database and then relayed using TCP to the Ham Radio Deluxe Logbook (Version 6.x) database.
I found this worked well but there was a popup message saying that the QSO had not been entered into the log. When I looked at the HRD logbook it was there. I was unable to capture the popup box as it was partially obscured by another window. Another QSO brought the same popup box but again disappeared before I had time to look which program was generating it.

If you want to try out the software yourself I can recommend it and it is available from www.vk2byi.com.au/qsorelay

Ham Radio Deluxe LLC offers olive branch to JTAlert developer.

Dr Mike Carper, WA9PIE, the co owner of Ham Radio Deluxe LLC has offered an olive branch to Laurie VK3AMA the developer of JTAlert. Essentially Mike has offered to meet up with Laurie, maybe over a meal, to repair a relationship issue.
There are a lot of radio hams worldwide hoping for a good outcome for this. At the time of writing Laurie has not accepted Mike's dinner invitation. Mike is in Melbourne, Australia until May 12th 2017.
Good luck Mike I hope it all goes well.

Terry G8YPH

"I sent Laurie (VK3AMA) an email inviting him to dinner with me in  Melbourne.  He basically replied saying he wasn't interested in a dinner reservation.  For the record - I've never had any interactions with Laurie - positive or negative.  I've certainly not done anything to cause ill will.  Nonetheless, I'll keep trying.  I think HRD and JT Alert have users who need our mutual and cooperative support.  I hope he'll reconsider.  I'll be in Melbourne until Thursday.

Mike, WA9PIE"

HRD 6.4.0.646 minor issue

Ham Radio Deluxe 6.4.0.646 was released earlier today (18th April 2017) and immediately I found an issue with it. I noticed during installation a message saying "Microsoft Access 2007 is being uninstalled". There were no questions asked it just did it.
The end result was that no databases (logbooks) could be opened nor new ones created. The simple solution to this is to reinstall the Microsoft Access 2007 Runtime. You did keep that copy you had didn't you? If you can't find it don't worry as there is a link in the FAQs section of the Ham Radio Deluxe LLC website.
Here it is
https://tickets.hrdsoftwarellc.com/kb/faq.php?id=114

or go straight to Microsoft Website to download it yourself.
https://www.microsoft.com/en-gb/download/details.aspx?id=4438

After installation the logbooks return.

Migrating Ham Radio Deluxe to a new computer

This is easy to do and is outlined in the HRD manual. Just follow the instructions and all will work ok.

I had reason to re-format my computer. A Windows 10 upgrade to the Windows 10 Anniversary update edition didn't go too well. I think originally upgrading the computer from Windows 7 to Windows 10 with an inplace upgrade wasn't the correct way to go. I had all sorts of issues with soundcards not working 100% afterwards and crackling sounds. When I let it do the anniversary update things went from bad to worse. I let it run for a few months and persevered with its idiosyncrasies.

Then a couple of weeks back (late February 2017) I had had enough. I bought a new 1TB HDD to replace the 2TB HDD I had been using for the C: drive. I kept that so I could retrieve any files off it should it be necessary.

The boot into Windows 10 Anniversary edition was quick and uneventful. When I had it attached to my domain I uninstalled any of the crapware that gets installed by default and installed Avast AV.
The next thing I installed was Ham Radio Deluxe. I restored the backup I had made including the registry files (If you want to backup a working version of HRD in RIg Control go to Tools>Archive and follow the instructions).

I started up the rig and fired up HRD and everything was there, logbook, DM780 settings, Rig control with all the customizations I had made, the lot. I can't see why people make such a big deal out of it. If you follow the instructions in the manual it works first time. Admittedly I tried it on a virtual machine that I had built on another computer to test the process before I tried it for real.

I then reinstalled only the essential software I need on that PC which is:

• Microsoft Office 2016
• Google Chrome
• WSJT-X
• JTAlert
• Sketchup 2017
• Adobe Reader
• VNC Reader 

and a few other minor pieces of software.

All data files are stored remotely on a server so I had no data to restore.

I made a list of what had been installed and on what date to ensure that if I install anything else and it breaks something I can narrow it down.

Snow, 40 metres and JT65 with XSJT-X v 1.7.0

It is snowing this dull last day of February morning in 2017.
I have been using WSJT-X for quite some time now and find that it is the only software I use these days due to the modes it brings to datamodes. I was a volunteer for the release candidate of 1.7.0 reporting back any issues (I didn't find any) and have been using the production version since day one.

It is used at G8YPH in conjunction with Ham Radio Deluxe as the rig controller and logger. Although JTAlert (at least with my setup) is now stuck at version 2.8.7 due to the ongoing spat between HRD LLC and the developer of JTAlert.

Anyway it is snowing and DX is flowing in on 40 metres this morning. I am making the most of it until conditions change. I can even see snow/ice sticking to the antenna so it must be cold out there!

JT9 DX on 40 metres mid morning

The HF bands are up and down, communication if you believe the propagation forecasts are not very good (early February 2017). A case in point was today with inter UK working being not very good. Close continental Europe of course is fine. I worked a station in Luxembourg, Netherlands and Switzerland.
Then on JT9 I saw Paul KA1MDQ over in Mashpee, MA, USA on the screen calling CQ. I went straight back to him and we exchanged RST signal reports of -22db and -25db respectively. As people know my antenna isn't complicated (just a long wire with 5 watts fed from a remote ATU into a 9:1 UNUN). This was a distance of 3152 miles - not bad for 40 metres during the day. I was encouraged that the bands are still open during the mid morning which is my normal time of working.

Propagation forecast 7th February 2017
K of 1 is good and it does say conditions on 80-40m is fair during the day.

I had a look around 40m over the previous weekend on JT9 and JT65 at about 1AM and found that it was crowded with stations from all over the world. It's a pity I like my bed more than I like radio so did not work anybody.

News from Ham Radio Deluxe and JTAlert

It seems that controversial co owner of Ham Radio Deluxe LLC Rick Ruhl W4PC has now retired from HRD LLC his last day was 30/12/2016. I wish the company all the best in their future endeavours.
A few days earlier the author of the fantastic JTAlert program Laurie VK3AMA has stated that version 2.9 will no longer support Ham Radio Deluxe integration. This is a shame but entirely understandable given the way he was treated.
To all JTAlert / HRD V6 users. 

I will no longer be providing support for HRD V6 logging within JTAlert.
This comes into effect with the next public release of JTAlert (2.9.0).

Affected HRD users can continue to use the current version of JTAlert (2.8.7) for as long as they want.
I will not be able to provide any support for that version, however, if a future HRD release breaks the JTAlert/HRD integration.

The free V5 of HRD will continue to be supported.

Moving forward, all future JTAlert versions will not support HRD V6 logging.

I will not be participating in any public or private discussions regarding the reasons for this decision".

I sincerely apologise to the affected HRD users.

de Laurie VK3AMA

And later he gave a brief expanation of his decision

Laurie, VK3AMA

After some "soul-searching", I now feel I owe the community an explanation, even if brief, regarding my decision to abandon HRD V6 logging support in JTAlert, especially to those users directly affected by this decision.

"Bottom-Line", I don't want myself or my software to have any sort of association with HRDLLC the company, their policies or their products.

This decision was a long time coming. The draft for the announcement had been sitting in my email draft folder for over 12 months. I came close to making the announcement on two other occasions in that time, but chose to "back-off", primarily because I knew this would affect a large number of JTAlert users and I felt uncomfortable with that.

The "die was cast" when HRDLLC released HRD ver 6.3.0.435 in October 2015. That release contained malicious code that deliberately shutdown JTAlert on a users PC without warning or message to the user that HRD had performed this unauthorised act. Details of this are publicly available within this groups message archives.

There have been several other events and interactions with HRDLLC over that time that are not publicly known, contributing to this decision, and I will not be discussing them here or privately.

While the association with HRDLLC was simply that my software had a feature that extended the functionality of HRD in providing a JT65/JT9 logging bridge, I am no longer comfortable supporting (by association) HRDLLC the Company, their policies or their products.

Again, I sincerely apologise to the affected HRD users.


de Laurie VK3AMA

I currently am running the following to control the rig for JT modes:

• Version 6.3.0.612 of Ham Radio Deluxe
• Version 2.8.7 of JTAlertX
• Version 1.7.0 r7405 of WSJT-X

It looks like this may be my setup for the foreseeable future until something else comes about - I might have a look at DXLab again for instance. I do wish with the change in management of HRDLLC that they can make amends with Laurie but I do entirely understand and support Laurie's decision.