The prettiest ham and the longest call

Fifteen metres was again in good shape today. The contacts I made included the prettiest ham I’ve yet worked, and the station with the longest call I’ve ever logged.

Natali, RV3ADL

Call me a male chauvinist if you like, but whenever I work a YL (young lady) on the bands I can’t resist looking to see if I can find a picture of her. I worked Natali from Moscow on PSK31 this afternoon and she must be the prettiest ham radio operator I’ve worked in my long career. She keeps a pretty neat shack, too.

The prize for the longest callsign ever logged goes to YO2013EYOWF which is the official call of the European Youth Olympic Winter Festival 2013 in Brasov, Romania. I pity anyone having to send that in CW! I don’t have any pictures of the YO2013EYOWF operators but they do have a very pretty logo which I expect will be on their QSL.

eQSL fraud?

In the last couple of weeks I have received two eQSLs for contacts that never happened. The QSLs were from made-up callsigns that are clearly SWLs, e.g. UA-123456. But the message with the card says simply: TNX For QSO TU 73! Curiously, both QSLs contained exactly the same wording.

Now I have nothing against SWLs. I started in this hobby as a broadcast SWL and I feel that all hams should have had experience as an SWL to get familiar with procedures, propagation and so on. But I am uncomfortable with receiving eQSLs from listeners as the eQSL system has no way to distinguish a listener report from an actual contact so their presence messes up my totals.

In practice it isn’t a big mess-up as I have never received an SWL card from a country I haven’t had a proper QSO with. So I do accept eQSLs that make it clear they are for reception of a contact I made. But TNX FOR QSO? Who do they think they are kidding, and what do they hope to gain from it?

Wide boys

What’s the point of PSK125? I just finished a session running PSK31 on 15m (which was really lively, by the way) when I thought I’d just check 10m to see if anything was going on up there. I soon found that there wasn’t much. The waterfall was devoid of traces, apart from a weak, wide, nebulous trace which proved to be PSK125.  PY2DN was calling CQ, but try as I might he couldn’t decode me.

It appeared that he was making some QSOs, presumably with people enjoying better 10m propagation than I had. PY2DN’s signal was far from perfect copy. Most times he transmitted I received mostly garbage. But I’m sure there was enough energy in the transmission to produce solid copy had he been using PSK31.

I guess the point of PSK125 is speed. PY2DN’s CQ and my reply both lasted about two seconds. But what’s the hurry? Not only can I not type that fast, I can’t even click macro buttons that fast. So the time saved is for nothing. I accept there is a role for PSK63 in contests, when speed matters, but only when signals are strong enough to provide good copy. PSK125 is a step too far. It spreads the energy too thinly.

I’ve tried loads of new digital modes but I keep on coming back to good old PSK31. I find it more satisfying in the long run. There’s tons of activity from heaps of different locations. You can often find a PSK31 signal when the CW and SSB band segments are dead. PSK31 is a real QSO mode where you can actually converse with somebody and exchange information with them. And you don’t need to run a kilowatt to a huge tribander to be successful. I was calling CQ on 15m with 40w to my attic dipole and I felt like a big gun: I was getting replies, including DX replies, to every other call.

I think PSK31 has earned its place alongside CW and SSB as one of the staple modes of amateur radio. Other modes are just for temporary amusement.

ARRL DX contest

There is still a few hours of the ARRL DX CW contest to go but I have worked all that I want to work this weekend. I only took part for fun, so no targets to beat. I did hope to work some of the rarer west coast states but conditions didn’t allow it. I only worked W/VE stations – in fact I only worked US stations, the VEs were conspicuous by their absence. I did hear one VE but I never managed to work him. So in comparison to other contests my haul of contacts was worse than normal.

I operated for a couple of hours late Saturday morning, and the same again after lunch. On Sunday morning I did another couple of hours but I almost gave up as I seemed to be hearing all the same stations I worked on Saturday. Then the jinx left and I managed to log another batch of new stations. But by Sunday afternoon I’d had enough, and it was a fine late winter day so I went for a walk by the river with Olga.

I think conditions this weekend were below average. Ten metres was all but dead; 15m was quite productive but the money band as usual was 20m. I didn’t try the lower bands as I think my attic antennas are too much of a compromise on those bands to work DX with them.

My total of 55 stations worked is nothing to write home about, but remember I was only working US stations – I ignored all the Europeans and Russians whom I would have worked in a normal contest. I worked 20 different states: CT, FL, GA, IL, MA, MD, MN, NC, NH, NJ, NY, OH, PA, RI, SC, TN, TX, VA, VT and WI. So my 100W was barely making it past the east coast. If anyone is interested in my full log the contest starts on this page.

Working in a contest is always fun. It’s not the winning, it’s the taking part that counts!

A JT65-HF update

Due to the health issues of the developer Joe Large W6CQZ it has been some time since there was a new version of the popular JT65-HF application. So I was interested to receive an email from Erwin, DK5EW, telling me about an enhanced version of JT65-HF made by Matthias DL3VCO called JT65-HF-Comfort.

JT65-HF as enhanced by  Matthias, DL3VCO

Matthias has not made an add-on to JT65-HF in the style of programs like JT-Alert. Instead he has made changes to the actual JT65-HF source code. I was particularly pleased to see that the enhanced version retains compatibility with the popular add-on JT-Alert by Laurie, VK5AMA. When I tried recompiling the JT65-HF source code myself the new version did not work with Laurie’s program, which I regard as an essential aid to JT65A operating. (In fact I have cheekily asked VK5AMA if he would consider making a version of JT-Alert that works with K1JT’s WSJT-X program!)

I have not spent much time with JT65-HF-Comfort as my interest at the moment is directed towards the new JT9 mode, but you can see from the screenshot that one of the improvements DL3VCO has made is to display the callsign above each trace on the waterfall. He has also added a new Statistics menu which displays the number of contacts you have made per DXCC entity per band. I couldn’t show you that as I use KComm for logging so my log is not in a format that JT65-HF-Comfort can read. You  can find a Google-translated version of the JT65-HF-Comfort information here.

If you are interested in trying JT65-HF-Comfort then you can download a setup program (a modified version of W6CQZ’s installer) to install the updated version. I shall certainly try using it the next time I do some JT65A operation.

My first JT9-1 QSO

PC4T Paul’s blog post about working Tasmania with 5 watts gave me the spur to try the new JT9-1 mode, so I installed the WSJT-X software. The user interface is quite a bit different to the older WSJT programs but most of the same controls are there. I never really figured out how to use WSJT, much preferring the simpler interface of Joe W6CQZ’s JT65-HF application.

Working SM5CS using JT9-1 mode
My experience with JT65-HF stood me in good stead as I was familiar with the sequence of exchanges, but I missed the JT65-HF user interface, its ability to decode all the signals in a swath of spectrum, and the alerts and built-in logging of it’s companion JT-Alert application.
My first QSO, also using 5 watts, was with SM5CS – not as impressive as Tasmania but sufficient to satisfy myself that I knew how to drive the program. I’m puzzled by the panoramic display though: the two peaks of the spectrum analyzer display don’t match up with the two traces shown on the waterfall.
I made the changes to KComm to allow me to log this new mode. I seem to have an increasing number of modes that I can log but not upload to eQSL.cc because the ADIF specification doesn’t yet include them, though JT9 is already there.

ARRL DX Contest questions

I see that the ARRL DX CW contest is next weekend. I haven’t decided yet whether I will come on and give away a few points, nor whether I will operate QRP or run 100 watts. I think it will depend on propagation.

One thing I am unsure about is what exchange to send. I believe DX stations – which means me in this context – are supposed to send RST and power.

If I’m running QRP (5 watts) do I send “5NN 5” or “5NN 005” or even “5NN TT5”?

If I’m running 100 watts would I send “5NN 100” or “5NN 1TT” or even “5NN ATT”? These short form numbers confuse me a bit. I’ve heard 1 being sent as A, and 0 (zero) being sent as the letter “O”. Or at least, I think I have.

If I change the power as I normally do and run 100W only when it is needed do I send the actual power I am using or stick to the same exchange (100W) throughout the contest?

Do I work only US stations or will all stations, even Europeans, benefit from working me with a point?


Subscribe FREE to AmateurRadio.com's
Amateur Radio Newsletter

 
We never share your e-mail address.


Do you like to write?
Interesting project to share?
Helpful tips and ideas for other hams?

Submit an article and we will review it for publication on AmateurRadio.com!

Have a ham radio product or service?
Consider advertising on our site.

Are you a reporter covering ham radio?
Find ham radio experts for your story.

How to Set Up a Ham Radio Blog
Get started in less than 15 minutes!


  • Matt W1MST, Managing Editor