Thursday, 14 September 2017

Did I miss an aurora?

I have been in Blankenberge which, as is well known, is in Belgium. It is customary in this blog to show the means of transport I used at the end of my trip (how did that come about?). Anyway here is a tram at De Panne, which was as far as we got before heading back to Blankenberge...
Tram at De Panne 09 September 2017
We did use trains which were more comfortable and rather faster to reach Belgium in the first instance.

The journey back from De Panne was, at 115 minutes, the longest time I have ever travelled in one tram. We broke the journey on the way out, but as we were tired on the return we decided to do the whole thing in one trip. Result - seriously numb bums. Almost as bad as the plastic seats on Euskotren from Bilbao to Irun via Donostia.

Anyway, it was clear to me that all my recent talk of the "end of season wind-down", and me decamping to Belgium, doesn't stop auroras happening. If I learned anything in statistics class (did I learn anything in statistics class?) it was that anything with a distinct probability, however small the probability, will happen sometime if you wait long enough. Like motorcycle accidents and unexpected pregnancies, if the basic requirements keep being met, then eventually even an unlikely outcome will occur, given enough time. So we shouldn't be surprised, and that also explains the scars on my leg, my broken upper jaw, and other things like me being here in the first place.

I have gone on about this before. The "Carrington Event", the most violent solar storm seen and recorded (so far), occurred in 1859. When I was at school we were told it was a "once in a hundred years" event, so we have better expect it soon. Now we are told that it was a "once in 400 years" event. We shall see. "Once in a hundred years" floods seem fairly common these days.

The aurora on 8 September was a good one. Not in the Carrington Event category, as one of those would threaten power systems and satellite communications, but good all the same. As we have not had a good aurora for some time, and as I missed it (boooh-hoooh), I am lucky to be able to draw on the reports of others to describe what it was like. Mike, GM3PPE is about 30km South West of me in IO85, David GM4JJJ is about 90km North-West of me in IO86, and both gave me accounts of the event. Thank you to both of them for allowing me to quote from their reports.

The basic plan for aurora is to be on alert for anything untoward happening. Mike was able to send me this email on 6 September which was very accurate in predicting the events of the 8th.
"I was on 15 meters this morning working stations on FT8 when suddenly at 0910Z all signals disappeared.  The same on the other HF bands.  I thought my rig had broken, or the antenna fallen down!  Then 30 minutes later all signals back.  A massive event on the sun.  Middle of the day another total radio blackout.  Apparently the biggest solar X class solar flare for several years.  It looks like there was an accompanying CME in our direction, which augurs well for a big Au event over the next 24 to 36 hours."

After the aurora Mike sent this report "6 meters started buzzing at lunchtime and closed to Au contacts mid evening. Kp went up to 7 and the geomagnetic records went purple.  I have never seen that happen with previous events.

I worked about 40 stations all over the UK and Europe, with some even on SSB.  Signals were very strong with some peaking 59A on my K3.  Towards the end of the event some signals start going Es, with hardly any Au buzz at all.  LA8HGA was particularly noticeable for this effect."
" ... the Au opening ended quite abruptly for me at about 1830Z - as you say, quite early.  In terms of DXCC countries, I worked G, GM, GW, EI, ON, LY, SM, F, DJ, PA and LA, making a total of 21 squares.  Not a bad haul for one day on 6 meters!"
Quite right Mike, and well done on that. 21 squares on 6m is remarkable and once again it proves what can be done on VHF.

SSB can be useful during auroras, even if the distortion makes it difficult to use voice. There is a large band of amateurs who never use CW, and during an aurora they can only be reached on phone. If I need the square I can use almost any mode I need to, however difficult that might be.

Mike sent me a link to the British Geological Survey site:-

This certainly shows the 8 August event in context (and shows the purple bar graph which was a new one on me too) ...
BGS "Current Geomagnetic Activity" chart for Lerwick taken on 14 September 2017
Click to enlarge if necessary (as always).

Note too that geomagnetic activity had another smaller peak later in the week and there may be some more action to come. The fact that you often see possible warnings of auroral events when nothing actually appears is part of the joy and the frustration of the hobby. This time who knows?

David, GM4JJJ sent me these useful illustrations of his operations:- 

2m Aurora Map showing worked squares with 500km intervals in red

4m Aurora showing worked squares with 500 km intervals in red

OH SLICE meteor Radar showing the solar flare attenuation at 36.9 MHz on the day before Aurora at around Noon. 

Thanks and congratulations David, well done.

It takes a fair amount of determination to work stations on 2m during an aurora. The Doppler shift is greater as the frequency increases. This makes life harder.

Clearly 8 August 2017 was a "big" aurora in every way. 

I am sorry I missed it. I used to work in Belgium and I always enjoy practising my rusty Vlaams (and indeed Dutch and French, if I can admit to that too). 

En waarom niet? Een fles Kwak voor GM4FVM!

Thanks for all the information and let us see if there is another aurora round the corner.



Friday, 1 September 2017

31 August Es and the end of the season wind down

Here, as I gaze over my estates from the lofty heights of the old stone tower at the end of the West Wing, I see the workers toiling in the fields to save the wheat crop ...
Harvesting the wheat as seen from GM4FVM's QTH on 27 August 2017
Actually, there does not seem to be too much toil involved sitting up there in the cab of the harvester watching the machinery doing its work.

If I really did have a West Wing with a stone tower on it, I would have attached another antenna to it long before now. Especially if it had lofty heights.

No, this week I have been watching the field behind the house being sucked clean of all its produce, then straw baling being completed. The straw bales have already been removed and no doubt ploughing and drilling will be complete within days. Who knows what crop will be pushing up next year?

When it comes to harvest time I start thinking of Autumn, and the end of the Es season. Time for me to review the Summer and then batten down the hatches for Winter.

This year I feel that I have overdone things over the Summer. I think that it is time for a break from operating and use the opportunity to spend a bit more time with my other projects.

Most of my amateur radio life has been marked by upsurges and downswings in activity. I am not an operator with just a rig and a bit of wire, but nor am I someone who invests all his time and money in this hobby. I move around the middle ground, sometimes getting too much involved and having to step back a bit. So this is time for a step back.

The Es season is over, the Christmas VHF Contests are over the horizon. Time for a measured reaction. The Autumn promises more Es, more aurora, more meteor scatter, and more tropo. So bring it on, as I am not going hunting for it.
 31 August produced a nice Es opening.

I knew it was coming towards the end of the week because the RSGB VHF propagation report said there wasn't going to be one then, but "at the head of the week" and it would "struggle" due to "weak Jet Streams".

So, of course with this promise I reckoned that if they say it will happen weakly at the beginning of the week I should start looking for a strong one at the end of the week. I find that is the best way of treating these reports, and it has always worked for me.

I am not saying that Jet Streams have nothing to do with Es (though that is what I think, but it is hard to prove a negative), but what I can say with fair certainty is that using them for prediction does not work. Relying on the predicted Jet Stream to base an Es prediction is always wrong here.

Jet Streams might be implicated in Es (I doubt it) but if this is the track record of making predictions based on them, what I have seen over the last year or so makes the predictions look laughable.
Es as reported by DXMaps at 21:18 on 31 August 2017.
I had a number of nice contacts, including I6FLD, IK4ISR, IZ8IBC, SP7QJF and SP8NR on 50MHz, and returning regulars DD3SP and OK2BRD on 70MHz.

Actually Sandro, DD3SP was an interesting one on 4m as I worked him first with meteor scatter on MSK144 at 13:16. I guessed that would be my last German station on 4m for this year, as their temporary authorisation ended on 31 August. But then I worked him again on SSB on Es at 20:32. I also worked Jiri, OK2BRD twice, both on Es. First by FT8 at  20:37, then again on SSB at 20:45.

It is notable that the last QSO was at 22:55 and I only stopped because I needed some sleep. This bout of Es was generated by a geomagnetic storm caused by a coronal hole. There was no widespread aurora, though I did hear the usual Northern Ireland beacons over the previous day or so. I often see this Es pattern repeat itself during positive polarity coronal hole disturbances. Perhaps today we will get some negative polarity material from the Sun too, and maybe an aurora.

10m Es was pretty good as well...
10m Es on WSPR, 31/8/17. Presumably Mauritius was F layer, but you never know!

A great day of Es to round off the season, so to speak. I will miss the German stations on 70MHz even though, due to conditions, they have not been as prevalent as previous years. I already miss Italian stations who we have not heard on 4m for several years.
It definitely has been a busy Summer and I am in need of a bit of a break. Never mind the radio, a brilliant Tour de France (Rigobero Uran was brilliant) was star of the season. Now the battling of Contador, Nibali and Aru are keeping me welded to the television and La Vuelta Ciclista a Espana. Not just cycling, but cricket has been superb too, plus of course Masterchef Australia. What a Summer.

I am not going QRT, just taking a bit easier. There is plenty more for this blog, or so I hope anyway.




Sunday, 27 August 2017

2017 Es season - not that bad? Aurora springs to the rescue.

I wrote this over the past few days. It started off being a piece complaining about poor Sporadic E conditions. As the piece developed, it turned out that things were not as bad as they had seemed.

What was bugging me was that on the 70MHz band (4 metre band), I had only had one Es QSO so far in August. Normally I would have had many more, and I can often work up to 8 DXCC in August, whereas of course in 2017 it was just one. I moaned about this in my last posting, and I went off and got the figures out of the logs to prove it.

Of course, it was probably just random variation (and not the weather and definitely not the jet stream). As I was finishing off my blog there was a small opening on 4m. I worked two stations in 4m, both in EA. One was on SSB and the other on FT8. That was followed the next day by a short opening into OH with two stations worked. For a while, the OIRT interference made it look like the "good old days" of Radio Gdansk...
OIRT broadcast stations at GM4FVM on 27 August 2017

So I have decided to re-write my downbeat piece as a review of the good things that have happened recently. And why not?

I can hardly complain about the 2017 Es season as a whole, even if August has been relatively poor. Six trans-Atlantic contacts on six metres on six different days so far this year. These cross Atlantic paths are (we believe) multiple hop Sporadic E. Ron, WB3LHD, went so far as to send a very striking QSL card direct ...
QSL Card received direct from Ron for 6m FT8 QSO on 29 July 2017
We do have sea eagles not far from here, plus kites and buzzards overhead, but that is quite a bird. Even the slightest squeak from any large bird sends Katy out of the garden and into the shack for shelter, so I have kept Ron's card out of her very sharp cat vision.

However, none of those NA QSOs were in August.

I suppose in this respect I am "old school". I really like receiving an unexpected QSL card through the post. After I sent the card back (direct) Ron sent me a screenshot of what the QSO looked like from his end. Unfortunately I did not take a screenshot at my end.

Nor can I complain about working 7K2KF in Algeria recently. I view this as a new continent. Sure, I have worked Madeira and the Canary Islands on 6m, which count as Africa, and had many 2-way spots with CN8LI on WSPR, but I have never before had an actual QSO with a station on the African continental mainland itself.
7K2KF on 6m at GM4FVM on 25 August 2017
I am not sure why this has taken me so long as the CN8LI spots prove that the path is open quite often. 2162km to 7X2KF is not far in 6m terms. It seems that the "FVM equations" are the problem, with Egypt, Tunisia, Libya, Algeria and Morocco all within easy range but not very active. The issue here is not about the level of Es, but more about the level of activity. Or so I suspect.

It also depends how the weekends fall in the month. Conditions are always better at the weekend. Of course, this is not true, but it seems to be. There are more stations around, they make more noise when the bands open, and that gets others involved.

I have also had a few QSOs into France - which is a great place for me to find new squares on 6m. France was late to release the 6m band, and then at first only part was opened up. Now it is easy to work French stations but they are still few and far between. Given the size of France, just about everybody starting up is in a new square for me.

However good things have been on 6m, 4m has not been good for weeks. I have to conclude that it is probably just normal statistical variation. Up here at 56 degrees North I am towards the edge of the strong Es. Stations in the Mediterranean get much more, and the further North you go the less we benefit from it. So it might reach us here on 6m, but the ionisation might just be too weak to work at 4m from here. A few days like that and it makes all the difference.
If Es levels may be down (and reading the above, they probably are not down), auroral activity is definitely down.

I wrote a long piece about auroras to illustrate them, but I still have not posted it.

There were more auroras over the last couple of years, and fewer recently. ("Please, no more figures Jim", they cry). That is probably due to the well established pattern the auroras peak in the two years after a sunspot maximum.

Like meteors, auroras do not go away just because it is not a maximum period for them. The various sites suggested that a coronal hole might have been active for the previous two days, but nothing exciting was predicted for 23 August. Suddenly my 10m WSPR monitor showed a blast of noise which filled the waterfall right across the screen. It must have been fairly wideband but I did not see it on the higher bands...
Wideband noise burst on 10m before the aurora on 23 August 2017
This was followed by me hearing the beacons on 2m in Northern Ireland, plus the 4m beacons on  Syke and in Northern Ireland. Interestingly the 4m NI beacon is now running PI-RX mode and I could compare the signal direct and via aurora, depending on which way I turned my beam antenna.
GB3CFG beacon near Carrickfergus while beaming directly at it (tropo)
GB3CFG beacon while beaming North (aurora). PI-RX is decoding despite the Doppler distortion
I must say something more soon on this blog about PI-RX beacons. Let us say now that unlike almost every other data mode, PI-RX works during an aurora. Looking at the comparison above, between direct and via aurora, it is amazing that PI-RX can make anything out of it at all.

Beacons were all very well, but what actual stations could I hear. As usual, not many.

I managed to work one station each on 4m and 6m. They were both LA9BM. Leif and I seem to find ourselves in this position quite often - the band is open but there is nobody else to work. Not quite though, he worked a few more, including OH0CO. I had heard OH0CO over the past few days via meteor scatter but he did not hear me, and I did not hear him on aurora. Aland Island would have been a new DXCC on 4m and 6m, but not a new square.

Anyway, I worked LA9BM on 4m and 6m using CW, and not even using my pre-programmed QSOs using the keyer memory. All done old style with a keyer and brain power. I did hear a couple of other stations but their CW was far too fast for me to try to work. Why does anyone use fast CW during an aurora when signals can be distorted and hard to copy?

I like a good aurora. Even if I only got to work one station on two bands, this one was better than nothing.



Monday, 21 August 2017

MSK144 and The Perseids

Well, the Perseid meteor shower has been and gone for this year.

After I wrote the eleven points about MSK144 and the Perseids David, GM4JJJ added another. I will re-post it here:-

Might I add a number 12 bulletin point?

In MSK144 there is a checkbox marked 'sh'. This allows a short-format message format to be used.

The user guide explains:
For operation at 144 MHz or above you may find it helpful to use short-format Sh messages for Tx3, Tx4, and Tx5. These messages are 20 ms long, compared with 72 ms for full-length MSK144 messages.

It also makes plain that on 50 and 70 MHz sh is not useful as the pings are of much longer duration anyway.

What is important to remember is that on 144MHz, you need to know if the other station is using sh or not, failure to use the sh setting if he is using sh will result in no decode even when a strong burst is received.

Another point is that if sh is used, there is a greater chance of false decides, so once you have detected the other station it is best to use RIT to get your RX frequency as close to his transmitter frequency as you can and then narrow FTol.

Thanks for that David.
"Sh" is accessible by clicking a box. SWL mode is for listening to the Sh messages of others

I might even add point number 13.

13) Think about AGC?
On the face of it, AGC should be turned off, especially on 2m metres. Meteor scatter pings are short events and they tend to be shorter the higher you go in frequency. AGC will cut your receiver gain as soon as a ping is detected, and therefore seems like a bad idea for a mode which depends on momentary signals. You receiver gain may remain lowered as the ping trails off, and thus you might miss the weakest part of a vital ping.

In practise I find that this is not an easy decision to make. Using my IC-7100 and IC-7300 the initial AGC action is very deep. However, the recovery time is adjustable and you can make it very fast indeed. At the fastest setting the response is good and it seems to help in some cases.

I would therefore suggest that it might be a good idea to try the AGC on and off for trial periods. To some extent it will depend on your rig. Slow acting AGC is almost certain to be detrimental, but fast AGC might work depending on the equipment. If in doubt, I would suggest turning it off.
I am a bit worried that listing 13 points makes meteor scatter with MSK144 look very difficult. It is not difficult. Why not try it and see?
Just because the Perseids are over, there is no need to wait for another shower to try meteor scatter propagation.

About 40,000,000 kg of material collides with the Earth every year. Whilst during a shower the particles may be bigger and there may be more of them, this is still only about 4 times the average for a normal day. When I say bigger, maybe golf ball sized, rather than the size of your thumb nail or smaller. But even a speck of dust can produce an ion trail as it falls to Earth and compresses the atmosphere in front of it, producing heat, light and ionisation as it progresses. Either the "burned up" particle is reduced to a speck of material which falls gently through the lower atmosphere, or, more likey for the ones that interest us, they are vapourised entirely by the intense heat.

Any object large enough to remain a significant size and reach the Earth's surface is called a meteorite. If we are ever going to be on the receiving end of a large meteorite then, believe me, the effects it might have on radio propagation will the be the last thing we are interested in. So the small ones are our main interest, and they fall all year round.

Is random meteor scatter a reliable method of communication? Take my QSOs with Henning, OZ1JXY. Since 2014 I have worked Henning by meteor scatter 61 times, at all times of the year and at all times of the day. That is reliable meteor scatter communication over a fairly short distance - 732km. During the same period I have worked Henning only two times on Es and once each on aurora and tropo. Anyone who suggests that meteor scatter is confined to a few days of the year needs to look at the performance of that link (not even a sked, all of it random answers to CQ calls).
OZ1JXY blasting in on FSK441 on 1 October 2016, outside a recognised meteor shower

There is enough "stuff" falling into the atmosphere, be it space dust from far-off stars, emanations from the Sun, space debris, or whatever, to keep a good QSO going all year round (though in February the going gets tough).

The Perseids shower is formed by the Earth crossing the dust trail left behind by a previous pass of the Swift-Tuttle comet. As we pass through the path of the comet we cross the material it left behind. Thus we have a predictable event to take into account. Random meteor trails are not as dense, but they are capable of producing surprising results for the amateur. And they occur almost all the time if you have the patience to wait.
Given the many advantages of MSK144 over previous formats, I am surprised to see so many stations on 2m still using FSK441. I will not go into the reasons for this, but they are just plain stupid. The justification used by one or two of these people is keeping MSK144 off the table for the rest of us.

For many operators, all they do is follow the pack, which in this case means sticking with FSK441. Nevertheless, for the few operators who drive this piece of numb-skullery, the basic object of resisting the spread of MSK441 is their belief that changing mode will damage their success. It won't.

There is a sort of meteor scatter neurosis which develops amongst operators. I know, I have had it too. The other station seems never to have heard you, though you can hear them (or vice versa, it doesn't really matter which). Therefore, the fault is clearly your antenna, their antenna, the software, your sound card, the phase of the Moon, ..., perhaps this new mode will reduce my QSO potency. This is human nature, given the characteristics of a mode that depends on tiny wisps of signal. But, meteor scatter communication depends on probability. You are waiting for a randomly timed event to happen. The gaps between hearing the other station are --- random. Who'd have guessed it? There is no need to blame your rig, or MSK144 for it, nor anything else. Mind you, when you are sitting there waiting for a signal, you might think of everything under the Sun.
Here the Perseids produced a few interesting contacts here.

6m MSK144 - LX1JX, S59A, SM6A, and SO3Z
4m MSK144 - DF1AN, DF3XZ, DF5VAE, DJ9YE, DK5YA, DK6AO, DL4KUG, DL9YEB, GD0TEP, OH7TE, ON4FI, OK1DIG, OZ1JXY (of course - twice), OZ1MFP, OZ6GH, PA3ECU and YL2CP,
2m FSK144 - SM2CEW and SM7THS

With 6m squares now being less sought after by me (I already have quite a lot), I have been looking for new ones and not calling ones I have. On the other hand, most of the 4m contacts were from stations hunting out my square, IO85. I do not think that I live in a rare square on 6m, especially as it has Edinburgh City in it. However, on 4m there are not many active operators, hence it is more in demand.

With 2m I stood out for a while by sticking to MSK and working no-one as a result. I had a few QSOs on FSK but that was it.

Two new countries for me were provided by LX1JX on 6m and YL2CP on 4m. Many years ago Jack, LX1JX (JO30, 843km) was my first LX station on 4m (on FM!) but it has taken a while to track him down on 6m. YL2CP (KO27, 1674km) had to have a lot of patience to work me as we had a number of attempts over two days. Because YL have only recently gained 4m he was much in demand and had to keep switching to other stations who kept calling him. We did it in the end though.
All this talk of meteor scatter has made me think about how reliable it is, and how unreliable Es has been for me this year. I must look all that up and see if I am imagining it.




Wednesday, 9 August 2017

After Es, why not try meteor scatter with MSK144?

As the Es season starts to wind down, my mind turns to meteor scatter.

Anybody on the VHF bands who uses modes like JT65, PSK, JT9 or FT8 already has all of the basic system to use the MSK144 mode.
2 metre band MSK144 activity seen on PSK reporter on 9 August 2017
When I was first licensed meteor scatter seemed exotic and very difficult. So it was in the 1970s. Only the kings of the hobby tried meteor scatter. I also became aware that these stations tended to use pretty high power. The text books suggested that commercial meteor scatter stations used hundreds of kilowatts and huge high gain antennas. So it looked to be out of my league.

The real game changer for me was the arrival of personal computers running data modes via audio tones. We now have the WSJT-X suite which offers MSK144, the latest solution to the meteor scatter mode battery. MSK144 can also be found on MSHV, and both these suites can be downloaded via the links on the right of this page.

Now anyone who is used to the other WSJT-X modes can try meteor scatter. My long held view that lots of power and large antennas were needed has been proved wrong. Whilst a simple dipole or loop is not going to work, I found that using about 100 Watts and an HB9CV got me round Europe reasonably well. A few simple improvements - going to 200W and a three element yagi certainly helped a bit more - but not too much.

As it says in the WSJT-X User Guide:-

Meteor-scatter QSOs can be made any time on the VHF bands at distances up to about 2100 km (1300 miles). Completing a QSO takes longer in the evening than in the morning, longer at higher frequencies, and longer at distances close to the upper limit. But with patience, 100 Watts or more, and a single yagi it can usually be done.

Not just the modes have changed over the years, so have the radios. These days most rigs are rated at full power output for FM use. They often have several multi-speed fans. MSK144 has 15 second tx segments which makes appreciable difference compared with the longer tx periods we used to use. This gives two rx cooling segments in each minute, which the rigs seem much happier with. Frequency stability has improved out of all recognition, though I have added the optional TXCOs to my Yaesu and Kenwood rigs.

You can listen to the VHF bands and hear meteor "pings" - short bursts of scattered radio signals. They are not all weak. At their peak periods pings can be remarkably long, up to a  minute or two and come in sustained bursts. However, the more common individual ones are not so strong and last for fraction of a second. In this situation, adding more power or pre-amplification does very little for communication during the peak moment but might lengthen the time you can hear the signal as it fades away. What MSK144 does is to further improve the ability of data modes to cram the necessary information into a short enough time to be decoded at the other end. 

There is a lot of variation in meteor activity between times of the year and also between times of the day. The meteors strike the Earth every day, but there are periods when large groups arrive over a period of a day or so, and these are called "meteor showers". Despite what you hear, you can work meteor scatter at any time of the year, not just on the few days of the meteor showers. It gets harder between mid January and April, but it can still be done. And generally the period between 06:00 and 12:00 local time is probably best.

So all this means that anybody who can work other data modes can probably try meteor scatter. However, meteor scatter requires a different operating technique. Whilst there is a lot of complexity about the mechanics of communicating via meteors, and a lot to do with the meteors themselves, the purpose of this posting surrounds getting started. I am going assume that you know or can read up about the concept of meteors and scatter, so I am not going to cover that.

What I am saying is based on the IARU Region 1 meteor scatter rules - other parts of the world will have their own systems which may be different.

Here are my 11 key suggestions for converting to meteor scatter:-

1) Be patient

There is huge variability in the numbers of particles hitting the Earth. Breaking this down annually, the number is so low between mid-January and the end of March that I often work almost nobody. By comparison the peaks during the "showers" can provide contacts almost continuously

It takes patience to get the right conditions to pass the necessary information back and forth to constitute a QSO. MSK144 is a masterpiece of software design in which the data stream is carefully honed to convey the information quickly enough to get through a very short opportunity while the ion trail caused by the meteor is in the right place. MSK144 is very good at it, but you still need the meteors to be in the right place, so often you have to wait.

During a shower burst you can have a quick QSO. At more normal times you might send CQ for ten minutes and hear nothing. Then you hear a reply during a short ping on the 10th minute. You send your report for ten more minutes and hear nothing until the end of another (say) seven minutes when you get your report back.

So you have to be ready to just keep sending your message and waiting to receive the other one. It can be a bit frustrating and when you are neurotic (like some we could mention) you begin to think that it is all your fault; perhaps your antenna has collapsed, or you have drifted off frequency, or gone into a trance.

It stands to reason that QSOs tend to be longer at times when there are fewer meteor pings. So during showers it is much easier to get replies. The daily cycle runs so that meteor strikes are at their peak around 06:00 local times and least around 18:00. But it is still possible to work stations at all times if you have the time to devote to it.

2) Stick to the correct segment.
By convention, in Region 1 those beaming East or South transmit "second". This means that they listen for the first 15 period between 0 and 15 seconds), transmit in the second (15-30), then of course listen in the next (30-45) and transmit in the next (45-60). This is indicated in that they listen in the red quadrants and transmit in the green below:-
The IARU Region 1 meteor scatter minute
Obviously the station they are working to the East of them is beaming West and therefore doing the opposite. Doing so avoids interference to nearby stations. This is why dipoles, verticals and omni-directional antennas of all sorts are not very popular on meteor scatter.

The minute is divided into four quadrants of 15 seconds each. From the start of the minute these are 00 to 15 seconds (first), 15 to 30 (second), 30 to 45 (first again) and 45 to 60 seconds (second again). Then the next minute starts. So, you alternate between transmitting and receiving segments. If I was beaming East or South I would listen 00 to 15 and again 30 to 45 seconds, and transmit 15 to 30 and 45 to 60.
Note the "Tx even/1st" box ticked - I must have been beaming West
The reason for this arrangement is simple. It means that any stations in your area who are beaming in the same direction as you will all be listening at the same time. Otherwise, if stations transmitted during random segments you could find a local station transmitting while you were trying to listen.As the signal fills your receiver passband that would bring everything to a halt.

This system is not perfect. For example, at what point does "East and South" become "West and North"? Things get a bit blurred round the edges but in general it all works well. It would be impossible to use meteor scatter if everyone just transmitted at will. We will see the consequences of all this later.

It seems simple to transmit in the right segment relating to your beam direction, but it is very easy to get it wrong as I know only too well.

3) Don't waste time calling on the wrong segment
Not only will you annoy everybody around you if you call on the wrong segment, it does not really work either.

This is very easy to do by mistake. Whilst you may have ticked the box correctly, WSJT-X invites you to be quick and double click on the other station's callsign to enter their details and reply. Doing this will also set your tx period to the opposite of the station calling, which could well be the "wrong" one for you. I have been guilty of this by mistake.

Just clicking the callsigns and replying indiscriminately will get you into hot water with other local operators. Random calling works on Es with FT8 and JT65, but not on meteor scatter - regardless of mode.

4) Keep your PC clock accurate
Obviously this whole system falls down if stations fail to keep their station clock accurate. There are two commonly used systems for PCs, Dimension4 and Meinberg. No doubt similar software is available for Macs and other operating systems.

As a default Windows only checks the time when it is started up. This is not frequent enough as computer clocks are not very accurate and the errors over a long operating session would be too great for our purposes. There are various arguments for and against either Dimension4 and Meinberg. But still, either of them is vastly better than no clock synchronisation at all.
Meinberg working away - these are supposedly UK time sites but they are anything but.
 If your clock goes out of synchronisation you will probably drift gently out of the correct segment. This is not good because if you are trying to work someone part of your signal will be impossible for them to hear as they will be transmitting then. Also, this misplaced snatch will turn up in the receivers of those stations around you who are straining to hear weak signals. Not good.

5) Get on the right frequency
Just because your VFO says that you are on, say, 50.280, that does not mean that it is accurate.

Both WSJT-X and MSHV software suites provide variable settings for "FTol", or frequency tolerance. If your frequency is not accurate you have to hope that the other station (1) is on the correct frequency, and (2) has their FTol setting wide enough to decode you. Better still, get on the right frequency yourself, reducing the risk of falling outside the other station's FTol range.

The reason why FTol is variable is to allow for different computers in use by each station. The advice is to run the widest FTol which you can. Widening FTol increases the demands placed on your computer's processor.  WSJT-X comes with MSK144 set for narrow FTol (+- 20Hz) and the notes advise operators to increase this as far as possible providing their computer processor has the capacity to cope. You cannot rely on the abilities of the computer at the other end so get on the right frequency to start with.

If your rig does not have one, add a higher stability TCXO oscillator. To find out if you need one, a simple thing you can do is to look at the frequency recorded by the software from received stations. Good local stations should be a guide. Doppler shift tends to vary the dx stations by 10 or 20Hz each time, but it is still interesting to see if you are roughly right ...
OH7TE is close to 1500 so he might decode me if he could hear me (he couldn't hear me anyway)
 If most of the frequencies you see are spread evenly on either side of 1500 you can be pretty sure that you are more or less right. If all of them are above, or all of them below, or the differences are more than about 50Hz in many cases, it might be worth calibrating your frequency.

The other (not recommended) way to find out that your frequency is not accurate is to go on anyway and find that nobody is replying to your CQs.

6) Get off the right frequency
That sounds odd given the last suggestion (5). This time I am assuming that your VFO is correctly calibrated and stable, but the frequencies you want to use are very busy.

It is best to get off the "centres of activity" frequencies as soon as possible. You can do this easily by using that frequency as a "calling frequency". The standard approach is to call CQ and give the working frequency you want to use in kHz. For example here I am calling on 70.170 and listening on 70.712.
In WSJT-X, the rig VFO is set to 70.172, the TX CQ to 170 and settings to "Fake it"
In the example above the message sent is "CQ 172 GM4FVM IO85" and WSJT-X changes the VFO on every over to send that message on 70.170 but revert to 70.172 for reception. So if any station wants to call me they only have to turn their VFO to 70.172 and carry out a normal QSO. As soon as I hear a call on 70.172 I uncheck the box beside "Tx CQ 170" and a normal simplex QSO results. This keeps 70.170 clear of long drawn out QSOs.

MSHV does it differently, using the split VFO arrangement in most rigs, but the effect is the same in terms of the message and the outcome.

The frequencies in common use for MSK144, as far as I can see, are 50.280, 70.280 and 144.370. I cannot comment on the "rightness" of these centres of activity. I know that 50.280, for example, is not in accordance with the Region 1 band plan. I am just reporting on what I see.

People seem to be more likely to use a different working frequency if there is a lot of activity, and it is more common on 2 metres where contacts often take longer.

70.170 is an interesting case. During the periods when German stations have access to the 70MHz band it becomes a sort of multi-purpose calling frequency. I have heard CW, SSB, JT65 and FT8 on it. However, when there is no Es or tropo propagation it becomes a sort of meteor scatter calling (and working) frequency.

7) Consider the Hot Bearing
No, not your big ends knocking, Hot Bearings in this case are alternative beam headings. Strictly speaking the direct beam heading between your station and a dx one will not work well for meteor scatter due to the scattering pattern. The ideal heading varies during the day and with the distance between the two stations.

Luckily both WSJT-X and MSHV calculate the "Hot" angle once you enter the locator square of the other station. This can be either a "Hot A" or "Hot B" angle, but the distinction does not matter for our current purpose.
MSHV suggesting a Hot A bearing of 134 rather than the direct angle of 118 degrees
It is worth considering the Hot angle and trying it. Personally I follow the advice given to me by Bryn, G4DEZ (SK), who suggested aiming "somewhere in between" direct angle and Hot Bearing. In my case, with modest gain antennas, the beamwidth is not narrow anyway and my telescopic tube masts introduce some slack, so my antenna angles are not very precise.

WSJT-X marks these Hot Angles simply as A and B and there is little in the guide to explain what they mean. I suspect that not knowing about the Hot Angles is the cause of many missed contacts.

8) Don't assume that MSK144 only works during the mornings of meteor showers.
As I write this the Perseids shower is due to peak in three days time. Already the bands are busy. The Perseids is a long lasting shower so it is not sensible to limit yourself to the peak couple of days.

These showers can be great fun but meteor scatter propagation is possible every day of the year. It is also possible at any time of the day. It is just that sometimes it gets harder. We like harder. Harder is character forming. Easy is fun but you don't learn much.

The major showers are listed on sites like this:-

Whilst the average shooting star observer needs to pick a shower period listed on these sites to see anything interesting, we in the radio world can find meteor trails at any time of the year (and in daylight too!).

Associations like the RSGB and ARRL list major showers in their propagation predictions.

Be aware that the Southern Hemisphere is affected by different shower patterns. If you happen to live in the Southern Hemisphere expect everybody to just assume that you live in the Northern Hemisphere. It is like your national radio society assuming that you live within 25 miles of their office. It comes with the territory of living where nobody expects you to. An unusual place like "Somewhere in the World". Golly gosh.

Anyway, 06:00 outside a shower period is likely to be as productive as 18:00 during a shower. And 18:00 at any time is better than not getting on the bands at all.

9) Use the most up to date software.
For some reason I cannot understand, several 2m meteor scatter operators still use the technically inferior FSK441 modes. Personally, I prefer a mode that works better, and MSK144 is that mode.

MSK144 uses 15 second transmit periods, which is remarkable to see in operation during a strong meteor shower. QSOs are over in a minute. Also, there is none of the panic with FT8 over getting the right macro running at the start of the over - you can change the macro at will during a segment. So if you are sending CQ on  MSK144 and you see that someone has called you, you just change your tx message mid-transmission and if the conditions permit it will be decoded at the other end.

I have an old copy of "the Amateur Radio Operating Manual", dating from 1991. The meteor scatter procedures in there are mind boggling. They are complex way beyond the rather fiddly methods described above. We do not know how lucky we are. I had forgotten most of it, and luckily now you can forget all of it.

10) Try the different bands
The days when "VHF" was simply assumed to mean 2 metres have gone. 4m if you have it is great for meteor scatter. 6m is good too. The bands have different feels to them. On 2m the pings are shorter and a lot of QSOs are pre-arranged. On 4m and 6m the signals tend to last longer and everything is much more relaxed.

11) Have fun
You don't need a kilowatt linear. You don't need a big antenna. If you already have a beam and WSJT-X you already have the setup. If you can do JT65 or PSK you can do MSK144.

Even if you just turn on and start you are not likely to fail completely. Keeping to the suggestions above will improve your strike rate. But if all you do is tune in and listen I bet you will find it fascinating.

See you during the Perseids.




Thursday, 27 July 2017

More on FT8, WSJT-X1.8.0-rc1 and imaginary band conditions

Well, I have had a lot more chance to work with FT8.

1) When FT8 does work

Included in my activity has been more time on 40m which was good fun as it included a QSO into VK and then I missed this ZP9 because I had to go out and quell a cat fight in the garden (don't ask, it involves a "Squeezy" bottle full of water - not to wet the cat but to cause it to find a close shave enough to leave the premises). ZP9 on 40 would have been a new one...

ZP9CTS missed on 40m at GM4FVM on 23 July 2017
Still, VK will do nicely.

In operation it is fairly easy to cut out an entire 30 seconds of otherwise missed DX opportunity by being quick to reply to calls.

I leave the PC pointer over the second line above the bottom (once the "Rx Frequency" box has filled - before then you have to pick the lowest blank line). It takes a bit of care to put it over where the other station's callsign will appear. Then I resist the temptation to click as soon as their callsign is decoded (on the line below). This is because my reaction time is not quick enough to click on that before the callsign moves to the line above.

 It certainly works if you click it within 2 or 3 seconds. Here is what the result looks like, showing that the next CQ was interrupted by the reply within two seconds and the other station received it fine ...

I have decided not to get steamed up about the superfluous 73 which often happens. Yes, I could hang over the spot with my pointer ready to click if I failed to get a 73. This might save 30 seconds. So far I cannot see the need to do it. It is worth doing it when getting replies to CQ calls as otherwise people can get fed up and stop calling.

2) When FT8 does not work

I have had a series of mysterious failed contacts where my reply was not decoded at the other end even though we were strong signals in both directions.
LA7DFA not decoding me on 6m for 20 minutes. Click to enlarge if necessary.
I was calling LA7DFA all this time and he only copied me once. After I got his report I sent mine but he did not decode that at all. This went on for twenty minutes. You can see that I missed his messages quite a few times too, even though I could see a big signal on the waterfall. Signals were strong enough and Per sent me several emails about it as things went on. There was little that we could do about it. Eventually Per suggested that we move to meteor scatter and once we had sorted out an "FTol" settings issue with MSK144, the QSO was instant. Hardly surprising as I could hear Per clearly.

This failure and a few others like it are rather mysterious. It does not seem to be a timing issue and I have switched back and forth between Meinberg and Dimension 4 several times which makes no difference. Signal strength is not an issue. Usually the other station has decoded my CQ and perhaps my reply. Drift does not seem to be involved. Sometimes I have decoded their message once, but not again. Sometimes it passes, other times it goes on for ages (though the example above is extreme).

A bit of a mystery that situation. I see others seem to be affected too. I still feel that I must be doing something wrong.

3. When nothing works (or so I imagine)

Between 1 July and 27 July 2017 I worked only 4 stations outside the UK on the 70MHz band.

This seemed so bad I decided to compare it with 2016, when the figure for the same period was 5.

Then I checked 2015, and then it was 7.

So four is not so bad. I do not recall July being quite so bad on 4m.

On 6m, by comparison, in 2016 I worked 18 stations and in 2017 I worked 55. So July is not so bad on 6m, and certainly not when I can rattle through the contacts on FT8.

Ah, the good old days. When July was full of 4m DX and the world was well ordered.

What went wrong?



Wednesday, 19 July 2017

WSJT-X and FT8 - you have to be quick

This is not a criticism. I like FT8. This is just what I found by trying to use it on the busy bands.

After a night using FT8 on 40 metres, I have to say that it is very efficient. It proves, however, that I am not as efficient as I might like to be.

It all comes down to managing the 15 second time segments.

In a nutshell, the transmitted signals have to start right at the beginning of the tx segment (of course), but this is very difficult to achieve if you are waiting to see a decoded signal from the other end. So human intervention, which may not be well timed, was tending to slow everything down.

Lets us suppose that I decide to call CQ, just like the 40m calls last night.

EDIT I have corrected typos in the timing, but the point remains the same.

I might do this during segment 1, at 0 minutes and 15 seconds.

1. 0m 15s CQ GM4FVM

Unless I was fairly careful or had set this on the earlier receiving segment, it is very unlikely to start at exactly the right point. Much more likely it will start after the beginning of the segment and therefore not be a signal which can be decoded by anyone else. Thus the next segment, my receive one, will be silent.

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence

Set up as it is to auto repeat, it will call CQ again next time.

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM

Anyone likely to reply to me will have to wait to see the decode of my signal (duh!). From what I have seen, not many people with normal reactions can click on my callsign in their software before the next tx segment has begun. With only 2 seconds available for decode, reaction and processing that is hardly surprising. The rapidly ageing demographic of amateurs (including me) only makes this less likely to happen.

So at some point during the next segment I get to see a reply, but it is never going to decode.

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM
4. 1m 00s Trace seen but no decode

There is no time for me to put up "QRZ?" either, as I have to wait to see whether that trace decoded or not. So I just send CQ again. There is nothing for the other station to do either, other than transmit again, but this time I will decode it as it started automatically at the correct time. It turns out that it is A1DX, a (non-existent but) very desirable station to work.

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM
4. 1m 00s Trace seen but no decode of call from A1DX
5. 1m 15s CQ GM4FVM
6. 1m 30s GM4FVM A1DX KM33

Great, A1DX, a rare station in a fairly unusual square! I have to wait to see the decode, by which time even though I click on A1DX's callsign it is too late to get the full message transmitted and she only gets two fragments which she cannot decode. However, it shows at my end as having gone (along with the record of another CQ which it interrupted, showing up as two tx lines on the panel).

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM
4. 1m 00s Trace seen but no decode of call from A1DX
5. 1m 15s CQ GM4FVM
6. 1m 30s GM4FVM A1DX KM33
7. 1m 45s CQ GM4FVM/A1DX GM4FVM +03

At this stage A1DX will see that I have replied but get no decode, so she just sends her call again. We all need to be patient here.

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM
4. 1m 00s Trace seen but no decode of call from A1DX
5. 1m 15s CQ GM4FVM
6. 1m 30s GM4FVM A1DX KM33
7. 1m 45s CQ GM4FVM/A1DX GM4FVM +03
8. 2m 00s GM4FVM A1DX KM33

At this point automation takes over and the rest of the QSO proceeds very quickly without further intervention by either of us (just as well given the speed of our reactions). The path shown next will be followed providing that A1DX has the "Auto Seq" box ticked, but it turns out that she has. Otherwise it will take forever to do this.

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM
4. 1m 00s Trace seen but no decode of call from A1DX
5. 1m 15s CQ GM4FVM
6. 1m 30s GM4FVM A1DX KM33
7. 1m 45s CQ GM4FVM/A1DX GM4FVM +03
8. 2m 00s GM4FVM A1DX KM33
9. 2m 15s A1DX GM4FVM +03
10. 2m 30s GM4FVM A1DX R-16
11. 2m 45s A1DX GM4FVM RRR
12. 3m 00s GM4FVM A1DX 73

OK she might send 88s, as we do go back a long way.

But anyway, now a further issue arises. If I have by now altered my WSJT-X panel to send the next CQ, I will not know if A1DX sent 73 until it is decoded. She might have not received my RRR and then she would send R-16 again, which would mean me changing everything again and wasting time. So I am almost obliged to leave everything in auto until I see the decode of 73, by which time it is too late to stop me sending 73 myself. If I do intervene by changing this to CQ it gets me nowhere because the resultant changed message is not able to be decoded by anyone. So I end up with this ...

1. 0m 15s CQ GM4FVM
2. 0m 30s Silence
3. 0m 45s CQ GM4FVM
4. 1m 00s Trace seen but no decode of call from A1DX
5. 1m 15s CQ GM4FVM
6. 1m 30s GM4FVM A1DX KM33
7. 1m 45s CQ GM4FVM/A1DX GM4FVM +03
8. 2m 00s GM4FVM A1DX KM33
9. 2m15s A1DX GM4FVM +03
10. 2m 30s GM4FVM A1DX R-16
11. 2m 45s A1DX GM4FVM RRR
12. 3m 00s GM4FVM A1DX 73
13. 3m 15s A1DX GM4FVM 73
14. 3m 30s Silence
15. 3m 45s CQ GM4FVM

Thus, in theory a 6 segment cycle (as it often is on JT65) becomes a 14 segment cycle. The FT8 segments are only a quarter of the length of the JT65 ones of course.

If it goes round again, the correct start time of segment 15 reduces subsequent iterations to 13 segments. Instead of calling CQ after 6 cycles on JT65, I ended up calling CQ after 12 cycles on FT8. This produces twice as many QSOs on FT8 compared with the same time on JT65, not four times as I might have expected before actually trying it.

It is quicker if you are the one answering the CQ of course. It takes longer if you are the one calling CQ as you have the dead rx periods.

I recognise that there might be some failings on my part due to my slow reaction times. The other stations seemed to be doing the same. I tried to sharpen up at my end, for instance by being ready to double click on the other station's callsign as soon as it appeared on my panel (you have to do it on the "RxFrequency" side as it moves up the screen on the other side, plus it will move up a line as soon as you start to tx, so I aimed for the second line up). This usually saved two segments, but I had to be lightening quick.

Nobody at the other end seemed to be moving any more quickly than I was, and all the QSOs were like the one above. I had to call CQ twice before I got a decode of the other end's callsign, even though after the first CQ I could see something on the waterfall. It was never decoded the first time. They were not getting as quick as I was.

With careful timing it is possible to reduce this process, but nobody was doing it last night. My lack of ability to avoid sending a second redundant 73 at the end of the cycle really annoyed me, but I just did not have the time to get it right and change over to CQ as soon as I had received 73. That is my standard procedure on JT65. Maybe I just need to loosen up and accept that as the whole process is better then the odd missed segment is OK.

This all seems simpler on MSK144. The modes are not technically comparable, but MSK144 also has 15 second segments. There is enough time to work out what to do next on MSK because timing is not important on meteor scatter - and on 60 second JT65 there is plenty of time even though you still need to concentrate. I pondered a bit on whether the same FT8 protocol with 30 second segments (with the extra 15 seconds devoted simply to deciding what to do next) would actually take the same time to complete a QSO. The answer with some of the real-life contacts was "yes".

Of course the built-in automation takes a lot of the problems out of all this. It works 100% fine. It is only when cranky old humans get involved that it all goes awry. Well not "awry" as it still works, but it diverges from the ideal. Put simply, my desire to complete "a QSO", meaning all the stuff done right, is part of the delay. I am the one deciding not to go straight on to CQ without seeing 73, but then that seems pretty logical to me. Let me put it this way - I do it on all the other modes.

Further automation, like automatically replying to the next signal or the weakest signal, is on the way for FT8. The snag with this, despite the attraction for others, is that I don't want to do it. I really want to know who I am replying to to before I reply. The UK does not have a "banned list" but some DXCCs do. In general I just do not want to be able to work everyone who might just call me.

Automatically going to CQ once 73 is received would be a good option for me though.

This is a fine balance to strike. At what point does speeding up the QSO get too fast for the operator to keep up with?

In the early 1980s I was taking a post graduate course at Queen's University of Belfast. I took an option in Ergonomics, which examined what was then called "man/machine interface". You know, aircraft cockpit dials all reading the same way, and how to design a control panel for a nuclear reactor. Great stuff and very useful in later life. Well ...

At one point we were trooped (!) into the university "Drill Hall" where a line of personal computers was arranged. I had never used a personal computer before, as the only computers I had used were the size of small buildings. We had to compare the interfaces on Microsoft and Macintosh machines. Microsoft was DOS, the Macs had ... windows. I wrote a long essay (my essays are still long) to say that windows were a much more accessible human/machine interface than obscure keystrokes. Speeding up the process using windows still left the operator with enough time to decide what to do next at their own pace, having been provided with timely visual clues. Did Microsoft read that? I don't know, but that is my qualification to blether on this topic now. I studied ergonomics you know.

I might have just got a bad night on 40m, with everybody new to the mode. However, it looked a bit like we might have got near to the limit as to how far we can shorten the reaction time available to operators and still expect them to sort things out in time. We can react more easily to messages that can be decoded as they arrive - like CW - where the message is gradually building up during the QSO. With data modes however, you get nothing until you are presented with a fully decoded message or still just nothing. What you do then is limited in all sort of ways. Further automation is possible but do we really want it?

Here is an FT8 QSO today on 6m ...
50MHz FT8 at GM4FVM on 19 July 2017. Click image to enlarge if necessary
This is better than the 40m ones last night. There is the same jittery start. Did he not hear me the first times I called, or did he click to reply during a segment and I did not decode the partial message? There was QSB. Once we got into automatic mode everything went well until two 73s and even an extra one from me which I cancelled part way through. It is not really comparable with last night, as on 6m DX everybody is keyed up and concentrating, while on 40m around Europe it is ... different.

Let us get this straight. Most of the QSOs I had would never have taken place on JT65, and no other mode either. Whilst FT8 might not be working for me at four times the speed of JT65, it is certainly getting through the QSOs at twice the rate, which means half of the 40m ones would never have happened in any other mode. As for the 6m contact, well -17dB is a pretty weak signal, so FT8 won the day technically. Once he actually heard me and started his reply the QSO was complete in another 45 seconds. With JT65 the QSB would have got him before the end anyway. I am a fan of FT8.

FT8 works. The high pace makes me feel fraught and unlike JT65 there is not much time for logging and feeding the cat between overs. I can cope with that (can Katy?). However, it is a bit ... wearing ... keeping up with it. Worth the effort though.

The protocol works very well, the operator is in need of a software upgrade.

If you ever need your nuclear reactor control suite updated, you know the person to call. I will put in some delay time to allow for second thoughts before pressing "go" - you cannot get people to react fast enough and still see the consequences of their actions. Other people! Eh? Who needs them?

I wonder did windows ever catch on in computing?




Friday, 14 July 2017

VHF data frequencies plus WSJT-X 1.8.0-rc1

Thanks to David, GM4JJJ, for pointing out me that the long awaited sharpening of the blades of WSJT-X, version v1.8.0-rc1 r7847, is now available at the WSJT Home Page link on the right. Follow the link  to WSJT-X and select the "candidate release" of WSJT-X 1.8.0.

Our attention was immediately drawn to a new "mode" (or protocol as some people put it). FT8 offers many advantages over JT65 on VHF. In particular it should suit weak long distance signals affected by QSB and Doppler.

At first glance there are several features in FT8 which I can certainly see will help. Immediately noticeable is a 15 second segment time which is just what we need for DX. This means that a QSO can be completed in a minute. If you want to know why that is important ask a CW operator. On JT65, a mode otherwise well suited to VHF DX work, you can sit and hear a station for a minute, reply, and at the end of 2 minutes get nothing back, never knowing whether you were heard or not.

I used to work with a guy who said "try to see the bigger picture - what does this mean for me?". Tee hee. The bigger picture here is that I might have worked Japan in the time I sat and watched many JA stations calling CQ. Quite possibly they were also watching me and other Europeans calling CQ, and the path just was not open for two minutes. Yes, overall it was open for a hour or more, but between any two stations it was only open for a minute or two.

I can get a whole QSO done on FT8 in a minute ....
A full QSO on FT8 in one minute, with 15 seconds thrown in for the 73s
At this speed you have barely enough time to respond so there is auto sequencing to reply automatically. Anyone who has used 30 second segments on MSK144 will feel very comfortable with FT8.

Not only are the segments shorter, but the synchronisation is at the start, middle and end. A readable signal in a 15 second segment should be 100% decoded, whereas the same length of strong signal would be less likely to decode in a 1 minute JT65 segment and even less so in 2 minute WSPR one, depending on the fading. If I understand it correctly, the chance of decoding is better as the segment gets shorter, thanks too to more frequent synchronisation. That is another plus for FT8 but not at the level of the "fast" JT modes like MSK144 or fast JT9, which can decode tiny fragments of signal. However, it does represent a huge step forward for the terribly weak and fading VHF stations we now hear.

What FT8 seems to represent is a very clever blend of tweaking the protocol with tailoring to the WSJT-X wrapper. So while a better decoding process will bring benefits (-20dB is promised), cutting the segment time and auto sequencing will bring much more chance of working those fleeting Japanese, Chinese and ... well, who knows where? ... stations.

I tested it by working a few stations and some I could not decode due to their clearly late timing. Every well timed station was copied easily.

Apparently it is possible to set it to automatically reply to the first station which comes back to your CQ, and further developments will see it able to reply, not to the first reply, but the weakest reply out of several. Now that is a DX-ers dream.

I worked a couple of stations using FT8 on what I am pretty sure was iono-scatter. It was neither as steady nor as strong as Es, and it certainly looked like that mode. FT8 looks like a great mode for iono-scatter, and once Es has faded it will be very interesting to see how we get on with the even more esoteric propagation methods. I will be particularly interested to try mixed iono/tropo/meteor scatter - type melanges.

EDIT - by melange I mean mixture - not the drug in the film, which was fictional by the way. Nor the "Melange" two stroke oil/petrol mixture machine I used for my Puch motorbike in the 1970s.

MSK144 seems to have totally replaced JT6 on 4m and 6m meteor scatter. I would really like to see FT8 replace JT65 on VHF Es. What chance of that happening? Not much I suspect. Human nature being what it is (the rest of this has been deleted so as not to offend the dozy old duffers in the hobby who think we should be running a museum).
I am not even going to start on the great 6m "operators versus the band planners" debate. What frequency should we use - the one the Region 1 band planners think we should use, or the one that works?

I did raise this before, and I will explain it at some stage for anyone who is understandably confused. But for now, I just do not want to get involved.

I was involved at some stage in the past with the 4m equivalent. I had some discussions with the then RSGB VHF Manager. It was easy to agree with this gentleman that 70.091 was good frequency for WSPR on 4m. Much later a row developed between me and some others versus a self-appointed rule maker about this. We won the argument as 70.091 remained, but I was hurt, bruised and annoyed by the whole episode - enough to put me off 4m WSPR for years.

Lately, several of us have been putting forward 70.176 for JT65. This seems to have stuck. I have worked a number of DXCC on that frequency and I see others doing it too. I have no particular qualification to decide these things, just 40 years of using the band and an interest in using data. That self-appointed rule maker seemed to be more interested in STOPPING me using data.

Thank you to several VHF supporters for occupying 70.176 and making it unofficially ours.

So with the arrival of FT8 a pattern of allocations emerges which would put, in ascending order, FT8 on 70.174, JT65 on 70.176 and by analogy, JT9 on 70.178. MSK144 is already on 70.280. WSPR is already on 70.091.

None of these frequencies is "right". The contesters will complain about infiltrating their precious bands, but then data modes are in use during openings, whereas contests never happen during openings (erm, or so it seems). I do not want to start a whole debate about 70.176 as it is now in use. The other modes as suggested by me fit around this as they do on other bands - leaving the 6m shambles out of it for the moment. So does anyone object?

Total data users on 4m - about 20 maybe. Total bandwidth used = very little, during periods of vanishing brevity. Surely this is not too much to ask? Just somewhere to go to find similar minded folk. A sort of "data cottage" - no maybe we should not suggest data cottaging on a family-oriented blog. A data village pump. That is a better idea. A centre of activity. And anyone who wants to transmit any other mode over it can do so. After all, it is in the "all modes" region.

Actually, it doesn't matter all that much. I have discovered that 4m operators can actually turn their VFOs and find other people. There you are, on 5MHz they transmit outside the band because they do not have the wit to change frequency, but on VHF we can actually listen in different places at different times. Amazing. Chapeau. Speaking of which, isn't Fabio Aru amazing?

This area around 70.176 is pretty good for the various international frequency allocations we have at the moment. It is not perfect, but it might be OK. There might be an argument for moving WSPR to 70.172 to fit in, as 70.091 is not so widely available, but I do not want to start that row up again.

Well, I have said it now. I bet there is an argument about this idea.