First WW-Digi contest

I expected a lot of people in this contest.  If one looks at the contacts made the last months in FT8 and FT4, I was even concerned of finding a place to call CQ.

NOT !

Some impressions

- Conditions were extremely bad, I never experienced such a bad propagation on 20m band.
   With only 2 JA stations worked, no ZL, no VK, no middle part of the USA, it was hard to make contact and to achieve a nice speed rate.  Highlight was the Sao Tome S9 station and a lot of Carribean guys. 

Also happy with the K1JT QSO.  Joe Taylor played in his own protocol contest.

- everyone was seeking how to play the contest.  I wasn't easy.  14.074 as the normal FT8 frequency,  then 14.090 and 14.092 as contesting FT8 freq and in between 14.080 14.082 and 14.084 as FT4 frequencies.
The band planning can be made better.   I did all combinations, sometimes calling cq contest, sometimes undercover as normal station calling CQ.

- another problem : how the config the software.  Normal QSO mode contest mode.  No 100% compatibility between the config modes.  IMO it is better to keep normal QSO flow to avoid conflicts and misunderstandings

- it seems that - my 24 bit Microham played very well -  with more activity there were big problems to decode (especially) FT4 signals and many QSO's were not corrected terminated. 

To be honest, it was a first time that high power was used, also on my side and I didn't notice more problems than before.  The new microham delivers cleaner sampling is my conclusion.

I didn't receive complaints about my (big) signal, continuously keeping an eye on my ALC.
This opens possibilities to use more power on 160M band in FT8.

- my ampli had big problems with 12s transmissions @1500W.  At a certain moment, smoke was detected, a few seconds later the ampli went into fault because of Pi tuning problems. 

I decided to continue with 1000W, without any problem.
In FT4 I could go to 1500 W.

- FT8/FT4 contest would be a robotic contest.  NOT !! 
Never had so many strategic choices to make.
What mode, which config, which segment, Run or S&P.   Frustrations because of the low run rate, etc...   This was not boring at all.

- I found a competitor with almost the same behaviour as myself.  Playing against W1RM was a contest in the contest, exciting till the last second.

Our ratings, points, multis and score were so close all the time that this was 100% fun.


- This contest is unique to measure station performance.  Because of the locator exchange, it is quite easy to see antenna behaviour.

The Steppir antenna was at about 18m height.

First and second lobe clearly visible, bad conditions (where are the missings QSOs in the 7000-7500 range ?) also visible.

This behaviour is predicted in Eznec, with two important lobes :

Next time I'll put the antenna some extra meters higher to change (lower angle) the DX lobe and add a third lobe in stead of 2.

To be continued.  Some work to do by organisors (band plan, qso stream) and operators...

In the mean time,  I prefer CW contesting.

Do not tolerate ON3 cheating

During the WW-DIGI contest I was connected to the contest-score-online website, to follow the exciting battle between W1RM and myself, putting each other to a higher level.

I also noticed a ON3 station, playing in the QRP categorie (5 W) and playing hard : first place, almost as twice the number of QSO versus the second place. 

In almost every category, a USA station was first, except for this QRP category.

ON3 stations can obtain a kind of rookie license by passing a ridiculous easy exam. 
As a consequence, they are limited to use lower power in order to experience the feeling of ham radio and to prepare for the normal hamradio exams.


This took my attention, so I went looking into detail.

He was playing with 5W, the limitation of the QRP category, I was playing with 1000W-1500W.
So a power difference of at least +23 dB.

This is the graph with the number of QSO's / hour :

And yes, I'm - big power with 3 element yagi- the green one. 

Conditions were extremely poor on all bands, so no propagation advantages possible. 
Everybody was complaining that only 20m band (my band) attracted participants.

This guy wasn't QRP, even not Low Power...  I should say rather around 500W.

Two objections :

If one gives rookies access to ham radio only to achieve more members (and so more member revenues) for a national club society, please think twice.  Quantity doesn't mean quality.

If the access is given, ie. a hamradio callsign to someone who had only to pass a very, very, very basic exam, please foresee enough control to retract the callsign in case of such false playing.

I am very disappointed, because FT8/FT4 contests (with better propagation) can give a lot of fun with real QRP equipment, as I noticed with my wire antenna and only 1W.   These false playing operators are putting high scores that aren't breakable with 5W.

And this here is not a question about running 10W in stead of 5W.

new Microham DXP installation with WSJT

Today my new Microham DXP interface arrived.  Serial number 14.

Easy installation is one of the main keypoints of this box.

However, after reading the manual, WSJT-X did not work.   For the guys who want a quick solution, just 2 tips : 

1. do not forget to change the Winkey setting on the DXP box to PTT (it has "none" as standard, so no PTT available). 

2. if you read the manual (I have version 1.0) it seems that you have to set the input tot DXP RX Left.

Not !!!  I had to set it RIGHT.  Now it functions.

First impression comparing to the USBIII interface : in FT4 I easily receive signal of -20dB.  I did not catch them with the usbIII.   

So I am ready for the first FT-contest this weekend.   It will be a try-out on 20m with high power. 1500W  If needed, I turn back to 1 KW or even 500 W.

Power problem FT4 solved

Fact : Power level of WSJT must be almost on maximum in order to have output to the TX ALC

Problem :  the WSJT-X v2.1.0 64bit windows version has a problem with controlling the sound mixer

Solution :

Step 1 : open the sound mixer in Windows (WSJT is not visible  in this mixer bar at this moment)
Step 2 : just perform 1 tranmission in WSJT.   The WSJT will appear in the Windows mixer
            There you will see the low level.

Step 3 : adjust the level to normal

Step 4 : don't forget to lower the power level in WSJT


Problem solved.

FT4 is a real winner !

First prediction :
FT4 will change the digital ham-world.  For sure !

Second prediction :
FT4 will make FT8 obsolete. 
FT8 will be remembered as the first very popular, easy accessible digital mode.  One year later, FT4 will take over.

Speed is superb.  This is going fast.  At least when there are people on the air.
I made 150 QSO's in FT4.  With 400 W versus 200 W in FT8. 

Duty cycle is only 30% (5 seconds on a 15 seconds send/receive stream), my system is running on lower temperature compared with FT8.

My first conclusion is that stronger signals are needed, as foreseen in the protocol, but that this mode will attract still more participants compared with FT8. 

to be continued... 

Thank you TR8CA for coming back to my FT4 CQ.

FT8 fox hound qso with OJ0C

Until now, I wasn't able to make Fox/Hound QSO's in FT8. 
Version 2.0.0 gave a (known) error and the program failed.

Today with v2.1.0 I decided to give it a new chance.  OJ0C was the fox, and there were only a few hounds from allover the world.  After some trial and error, the QSO was made.

F/H is not my favourite thing to work a pileup. 
Maybe I need more experience, maybe it will die with  the FT4 protolcol just launched.

Anyway, it works.

First FT4 qso ever

WSJT-X official v2.1.0 "FT4" release yesterday... today first test with FT4.

It works fine, but no one uses it yet.

I had to place it on the cluster and SP2GR was so friendly to come on frequency to make my first FT4 qso.
Some minutes later SM2OTU came also making a QSO.

I seems that we are the very first users, but the mode looks very, very fine.  Quick qso, nice reports, less bandwidth needed.

I detected one small problem with the new software version. No outgoing power  !
Fixed by clicking on the power tracking button on the right sight of the screen;


To be continued.