WSJT-X Invalid ADIF header fix and seasonal change.

I tend to think that the harvest in the field behind GM4FVM marks the end of the Sporadic E season. Looking back, it is a week earlier this year, and two weeks earlier than the year before. Whether the Es follows the harvesting season or not is a matter of debate, but without any real evidence I imagine it is a fact, this is my blog, so there you go.

Harvesting beside GM4FVM on 16 August 2020.

As I write on 23 August 2020 there is plenty of Es activity to the East on 6m. Nothing on 4m where I suspect the Summer Es is mostly over.

I was a bit surprised to work SP1O on 2m on 22 August. He just rose up to +13dB, lasted for the full contact and then vanished. I was heard by many other SP and DL stations according to PSK Reporter, and other GMs heard SP1O. This did not seem to be Es as there was no sign of Es on 4m or 6m, so I thought it was very strong meteor scatter. Or, more likely, it may have been ionisation after a large meteor reached Earth. Anyway, the tone of FT8 was clear but there was the haunting ringing echo which suggested a meteoric cause. On the other hand there was no sign of anyone taking advantage on MSK on any band. So, who knows?

The latest version of WSJT-X, version 2.2.2 has brought various advantages. On FT8 the decoder has improved and is quicker, meaning that we now often see signals decoded before the 15 second rx period is complete. While this is a great advantage, it also opens the door to clicking on the message to initiate a reply and finding a period of silence before tx starts at the beginning of the next period. Great for heart-stopping mini-panics.

v2.2.2 also brought about an improvement to the logging side of WSJT-X. I always liked having "Prompt me to Log QSO" ticked, as this produces a QSO summary. As I use four instances of WSJT-X at once it can get a bit confusing and being reminded to log is a good thing. This also creates an ADIF log file, which I have not used (yet). Contesters use this log file as they tick the box "Log automatically (contesting only)".

Once I started using v2.2.2 it was immediately apparent that a glitch in earlier versions of WSJT had been fixed, and using the log prompt and logging each QSO no longer cleared the "Enable Tx command". Excellent.

Not so good was that another glitch has arisen. Once the ADIF file was created, every time I opened WSJT-X or changed configurations I got an error report: "Error Scanning ADIF Log - Invalid ADIF header".

If you do not use the logging, either prompted or automatic, then you will not experience this problem.

It was not a great hardship to cancel this error message each time I started WSJT-X. But then I have four instances of WSJT-X. More of a snag was having to cancel it every time I changed configuration, which I do every time I change from FT8 to MSK, or to JT65 or JT4 for beacons. More worrying, if the ADIF files created by WSJT-X were invalid I could not use them for logging if I ever need to. Contesters using the automatic logging facility would probably have problems exporting the files into their software.

I worked out that deleting the ADIF files would stop this happening, at least until I worked someone and logged it, in which case it came back again. Anyway, I did that for a while as I tried to work out a solution. The ADIF file can be read in a text editor, so I opened it in WordPad. The way to do this is to click "Open Log Directory", then right click on "wsjtx_log.adi" and select "open with" using whatever text editor you may have. WordPad is not great, but it comes bundled with Windows 10.

Here is an ADIF file I had (as usual click the images to enlarge if necessary)

The header is "WSJT-X ADIF Export<eh>". It needs to read "WSJT-X ADIF Export<eoh>. That is all you need to do, just add one character. Change <eh> to <eoh>.

Next click on "Save" in your text editor.

That's it. Problem solved. Close the text editor and the error message should be gone for good. Unless of course you delete the ADIF file, in which case after you work the next station and log it, a new ADIF file will be created with the same glitch in it. Then you would need to change it again. However, unless you delete the old file, you can probably just leave it as it is.

This is how it looks after it has been fixed, including that rather unexpected contact with SP1O.

I really appreciate what the WSJT-X team have done over the years. In a large software project there are bound to be glitches. In this case we might think that they fixed one issue and created another one. That would be to ignore the other improvements which v2.2.2 brings. The faster decoding will really benefit FT8. Contest working has been improved. I can understand that one letter in one line of code might go amiss. It is easy to fix anyway.

It is well worth updating to WSJT-X v2.2.2 and in general keeping it regularly in step with the latest version.

73

Jim

GM4FVM

An old man reflects on a tropo lift

It is, of course, a matter for each amateur to decide what to do in our hobby. I can hardly say otherwise when I pursue fairly narrow interests myself. I try, as far as possible, to avoid doing the same things over and over again.

I use my 2m/70cm radio, a Wouxun 950, to listen to what is going on in the general VHF spectrum. This is so that I can direct my listening to where the action is. If there is any action.

Wouxun 950 at GM4FVM

The Radio Society of Great Britain has changed the way amateur exams are conducted. As a response to the COVID-19 outbreak they have ended the monopoly of clubs and allowed remote invigilation of exams. Well, actually there never was a monopoly of clubs to carry out exams, that was just the way it worked out. That fact has not stopped some old duffers claiming that this has weakened the status of clubs in the community, even though our local club did more to prevent anyone sitting exams than help them.

So some new amateurs have arrived into the 2m FM madhouse. Well done. Freed from the need to find a club willing to help, they are now licensed. Well done. Proof indeed that the club system was actually holding things back, or it did that around here anyway.

Listening, as I do, to 2m FM I heard one of this new breed of amateur remarking "If I could get this antenna up a couple of feet I think maybe I could work up the coast as far as Montrose". I pondered over this for a few days before it dawned on me that he meant to work the GB3GN repeater near Montrose (it is actually nearer Banchory). Anyway, I also listen to that repeater, but I use it as a pointer to conditions. It sends the location "Banchory" in morse on a regular basis, which is a bit of a giveaway that it isn't in Montrose.

What he does is a matter for him. However, I did think that measuring your success by working a repeater on a superb site just 131km away is not exactly challenging. Sure I use repeaters myself, perhaps once a month or less. However, working any repeater is not exactly the pinnacle of my radio desires.

GM4FVM to GB3GN, not a difficult path.

No doubt when I was first licensed I had similar modest aims. People learn their trade in this hobby and move on from their initial fascination with just being able to "get on the radio".

Or do they?

Well some do. Others are content with the dream of working a (not very) distant repeater. The fact is that when they do eventually work some proper DX "through" the repeater, they are just working the repeater in the same way they always do.

I suppose it is the lack of ambition about all this which depresses me.

As I listened to GB3GN recently I heard people rather grumpily complain that "DX" is occupying their repeater which is surely for local use. I suppose they have a point. If the station local to me does indeed put his antenna up to reach GB3GN then at his spectacular 131km range he may not be welcome.

It is, of course, a matter for them. Did I say that before?

My FM radio scans away to itself. It is not really GB3GN that interests me but it's sister GB3NG near Fraserburgh. When I can hear that with no noise I know things are on the up, to the North anyway. At 197km I can guess that I might get across the North Sea to Norway or Denmark using a more efficient mode than FM.

For me, hearing a distant repeater is just a signpost of improved conditions. The local ones are a way of having very local contacts. They are not a DX aim for me in themselves, more like beacons you can easily scan for. And as the Wouxun scans I also listen to the coastguard:-
Aberdeen coastguard - conditions normal,
Humber coastguard - strong means slight lift,
Belfast or Stornoway coastguard - things are on the way up,
Coastguard from across the Heligoland Bight - wow!

Hearing local stations in the Baltic nattering on 2m FM during the 13 July 2020 opening was another sign that I needed to be ready for Sporadic E (see last posting). Of course they did not leave any gaps for anyone to break in, and maybe they didn't want to work any DX anyway. But it shows it is always worth scanning.

Plus during lulls I can listen to the doings of the Craster lifeboat. And there is drama like the endless procession of people and bodies being fished out of the sea at the bottom of the cliffs at nearby St Abbs and even occasionally divers being airlifted to Aberdeen hospital for treatment for "the bends". It amazes me how many people fall into Eyemouth harbour. Oh, it is exciting stuff you hear when you scan.

I had an interesting 2m FM QSO with Dave, GM4PKJ, who really is near Montrose. We discussed the Hepburn chart for the week ahead, and hoped for some tropo ducting. We were not disappointed. I am not "anti-FM" any more than I am "anti-repeater" (or "anti-contest" for that matter). I do all those things, but I try to keep my interests wider than just one of them.

It was great to have a long blether with Dave and get away from digital modes for a while - Warning - risk of getting narrow views if I stick with too many digital mode contacts.

And he sent me a QSL card which arrived next day!

So what did happen? There was a "tropospheric enhancement event", mostly on 9 August but also affecting the day on either side. This was caused by a small high pressure system in the North Sea which did not look very exciting when Kawser Quamer showed it on the BBC Scotland weather forecast. Luckily Hepburn warned me, Dave PJK, and lots of other people.

On 8 August I worked Jaap, PA0O, plus OZ1FDH and OZ7UV. This marked the start of the event.

By 9 August the "above 70cms" map was looking more like 2m usually does:

DX Maps on 9 August 2020. Coloured by band. Red 23cm, blue 9cm, green 6cm

I have some sympathy for the view that DX is not the only thing to be measured. After all, if my world stopped at the Montrose repeater (which, by the way, is in Banchory) I would still get a lot of satisfaction from the contacts I might have with locals. So I must rate the voice contacts as more worthy than data. The other standard I might apply is the frequency band. I have said before that a contact on a higher band counts for double points. And what do points make? Prizes of course. Also, multiple bands mean multiple prizes.

So during this opening I worked the following stations on multiple bands:-

2m and 70cm:
OZ1AXL, OZ5AGJ, OV3T, PE0DNY and OZ1JMN. Probably OZ1IEP too but the 2m contact was a bit scratchy.

Then on 70cm and 23cm (for more points):
SM6CEN. The contact on 23cms was a rather scratchy SSB affair.

And finally on 2m, 70cms and 23cms (for maximum points)
OZ2ND and OZ7MHZ. Almost made it to OZ1AXL as well.

Bonus points too for OZ2ND for SSB on both 70cms and 23cms which included a long blether on 23cms about 1970s VHF valve transmitters.

Plus the "merit award" which was won by SM6VTZ for working me on 23cms CW. This was awarded both for a new country on that band and raising my 23cms ODX from  689km to 880km. Even getting me on to CW deserves a medal at least.

Now let me just think about this. A ragchew with OZ2ND on 1296MHz. One part of the rather long discussion was about how we never expected this to happen when we were first licensed. Back then it was 6 or 8 watts of AM on 2m. Indeed, back then working Montrose on 2m would have been amazing.

Maybe I have been a bit hard on the current crop of FM-ers. Maybe they too will be chatting with an OZ at 689km on 23cms in 40 years time. Or having an easy CW contact at 880km into a new country (Sweden).

I suppose I think they should be doing it now while they can, but I guess they have to make all the mistakes along the way before it dawns on them to challenge themselves a bit more.

Somehow I never expected to have a long chat on microwaves using an antenna that hardly ranks much above the TV aerial most people have on their gable end.

The lower antenna (just 1.5m long) just worked 880km

This was not moon bounce or anything very technical, not high powered (just 50 watts each way) and not some funny mode (it was SSB and CW).

For years I have not been not much better than those who settle for an easy life on FM. The simple fact was that the 1296MHz band has for years been beyond where I was comfortable. In fact, for a long time 432MHz was my "Montrose". If only I put an antenna up I could work something, but why bother? I mean, why not stick on FM? I am quite pleased I was not dreaming of working Montrose and made the leap into something rather more rewarding. Not just rewarding but surprising too really.

As for the usual analysis of DX rather than chatting potential, here it comes (click to enlarge if you need to) ...

144MHz contacts at GM4FVM on 9 to 11 August 2020

35 QSOs, 21 squares, 9 DXCC, Best DX DL1RWN (JO46) 973km.
=========================================

432MHz contacts at GM4FVM on 9 to 11 August 2020

20 QSOs, 10 squares, 5 DXCC, Best DX SM6CEN (JO67) 882km
===========================

1296MHz contacts at GM4FVM on 9 to 11 August 2020

4 QSOs, 3 squares, 2 countries. Best DX SM6VTZ (JO58) 880km.
===============================
I really should be pleased with the 2m results, including as they do a new country (OY), new squares (such as my first contact with G7RAU in IN79), more QSOs than any other band, more squares, greater distance. And it certainly is great. But so is 70cms. As for 23cms, well not many contacts, but all of them great.

OK, I know working greater distance is not everything. I know a good old ragchew is often what is needed. It was doing both at the same time that surprised me.

At this stage in the year I am often on 4m or 6m doing some meteor scatter. This year I seem to be distracted.

Are other amateurs being too easily pleased with simple FM contacts?

Or am I getting old?

73

Jim
GM4FVM