PE4KH Amateur radio - Koos van den Hout

Most recent QSO's for PE4KH

Callsign Band Mode Locator RST(R) RST(S)
RA3MBG20MFT8KO96-15-02
IU8FRE20MFT8JN70+06+08
UA3AGY20MFT8KO85-12-13
EA5LH20MFT8IM99-13-24
A92AA20MFT8LL56-17-09
R8AEF20MFT8LO94-18-23
UX8ZA20MFT8-13-16
UA6HBJ20MFT8LN04-12-03
RC6AA20MFT8KN96-05-13
UT0IL20MFT8KN88-08-03
EA5RA20MFT8IM99-12+00
2E0EGS40MFT8IO93-14-16
UT2MA20MFT8KN98-05-18
RA9LL20MFT8MO27-20-24
9A6T20MFT8JN75-08-11

I passed my novice radio amateur exam in March 2013 and I registered the callsign PD4KH (pappa delta four kilo hotel!). I passed my full radio amateur exam in March 2016 and I registered the callsign PE4KH (pappa echo four kilo hotel!).
PE4KH on qrz.com
PE4KH on hamqth.com

I am usually located around maidenhead locator: JO22NC

The 'hamradio' items from my homepage

2017-08-28 I participated in the SCC RTTY 2017 contest from the radioclub location
Again this year had the SCC RTTY contest in the same weekend as the barbeque of the radio club so the solution was to work in the contest from the location of the radio club. I set up with the endfed antenna in the available field.

That field is close to some houses so I had some interference. And the main problem was that the computer control between the laptop running fldigi (the contest logging software) and the radio regularly gave problems, usually leaving the radio in transmit mode. The laptop and the computer interface aren't shielded very well which is probably a reason, combined with the use of the endfed antenna which is known for causing interference since it's an asymmetric antenna.

In the end I made 53 contacts. Less than the number of contacts in previous SCC RTTY contest but I had limited time and local noise was higher than I expected. For a next time I am working on a common mode choke to limit interference to the computer and maybe some noise. And probably next time I contest at the radio club I will try to use a different antenna location.

2017-08-24 Operated outdoor portable at the location near Maartensdijk again
This morning I had some time and a good reason to leave the house. So I packed the radio, batteries and headphones and loaded all of it in the trailer of the recumbent and cycled to the bend in the road with a table and some trees where I operated portable before.

The local noise was very low again, about S1 on the 20 meter amateur band and about S4 on the 40 meter band. But conditions made the 20 meter band very quiet so I tried answering some calls on the 40 meter band first. In total I had 5 contacts, three of which were activations in the world wide flora and fauna program. Some of the contacts later in the morning were on the 20 meter band after it opened up.

All in all a nice way to spend the morning. Things noticed:

2017-08-24 Uploading FT8 contacts to LoTW from CQRLOG
Other people from my radioclub were reporting they uploaded FT8 contacts to LoTW so I wanted to try this too. I uploaded earlier contacts as 'DATA' (and got some confirmations) but FT8 is the correct mode so I wanted to re-upload them.

After my earlier experiences uploading FT8 contacts to eQSL I expected some database work to be able to upload those contacts again. Finding the right field to set to the right value was a bit of work since I expected the approach to be similar but it wasn't. In the end:
$ mysql -S /home/koos/.config/cqrlog/database/sock cqrlog002
mysql> update cqrlog_main set lotw_qsls = '' where mode='FT8';
Query OK, 77 rows affected (0.01 sec)
Rows matched: 78  Changed: 77  Warnings: 0
That's after trying most lotw related fields and values.

2017-08-22 New QSL cards ordered, again from LZ3HI
Almost two years after I ordered QSL cards for PD4KH they ran out. I had to print stickers with the PE4KH call sign for a while to update the cards.

PE4KH qsl card front PE4KH qsl card back Now I had time to make new cards and see what the options where. I promised myself nicer cards with not just the standard data but nice colour pictures on the front side so I looked at ideas, drew some things on paper and worked a few evenings in the Gimp to get the ideas into something that would survive being printed. I created files for printing at 600 dots per inch so there should be no strange printing artefacts.

Image credits:

2017-07-24 Last night receiving ISS SSTV images
And a third night. I used the timed recording option of audacity, which in the current linux version does not offer the option to set in advance how to save the project. This time I 'only' recorded for 7 hours, and was able to save the project afterwards without needing a recover. But on reloading the saved project audacity complained about some internal error in it, and it still had the problem of assuming 44.1 kHz sampling while showing the project sample rate as 48 kHz. Anyway, images decoded from the audio and I even recieved a few new ones.

2017-07-23 Another night of receiving ISS SSTV images
On the night from Friday to Saturday I had the whole setup ready to receive more ISS SSTV images. And nothing was received since I had the antenna unplugged during Friday because of thunderstorms and forgot to plug it back in.

So when I found that out I put a note on my desk with 'Antenna unplugged?' which can be a reminder to unplug it when I'm done or plug it in when I want to receive something.

ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image ISS SSTV image On the night from Saturday to Sunday I plugged the antenna in and let the whole setup run again like on the earlier run on Friday Received slow scan TV images from ISS while I was sleeping. To make sure I had the antenna plugged in I tuned to 145.750 MHz where I can hear a distant repeater faintly.

Again audacity hung after the recording, and this time on recovery it had some issues with the saved project. At first I could see and hear audio of SSTV passes but qsstv could not decode anything. In the waterfall display of qsstv it looked like the frequencies were too low. I had a thought that maybe something decided the samplerate was back to 44.1 kHz so I simply speeded the audio of an image pass up by 8.8435% and suddenly it decoded fine.

In the end I decoded 11 images from the ISS SSTV project. Numbers seen 8, 10, 9, 6, 7, 8, 6, 4, 5, 6.

And 2 images from nearby radio amateurs who weren't operating according to the bandplan... but at least did not interfere with the ISS SSTV transmissions.

2017-07-21 Received slow scan TV images from ISS while I was sleeping
I read about the current ARISS Celebrates it’s 20th Anniversary through SSTV Event and noticed the planned times weren't really compatible with my day/night cyclus. I know, as a hardcore radio amateur I should be up at the weirdest hours for rare events but I also like my sleep a lot and my wife really dislikes alarms at weird hours.

Automation to the rescue: I decided to record all of a night of ISS signals on the computer with audacity and decode images from it later. The computer adjusted the radio for doppler using gpredict. Since I don't have an automatic rotor for satellite antennas I used the VHF/UHF vertical. This may seem strange but the weakest signals from ISS are when it is right above the horizon (which is when the vertical has the best reception). And as noticed on earlier SSTV events that compared to other amateur satellites the ISS has a strong signal.

So I left it running for a night and checked the results afterwards. The result was a 9 hour recording and audacity decided to hang after stopping the recording. I made a backup copy of the audio data just to be safe and restarted audacity. Luckily it recovered the project fine after restarting.

With a recent version of qsstv I decoded the recorded audio and searched for ISS passes in the recording.

The result is 13 decodes in one night. It turns out it received audio from a number of low passes that I did not see in gpredict because I have gpredict set up to skip low passes (those that don't come above a 20 degree angle above the horizon). But the strong signals from ISS make those show up in my radio anyway.

Decoded and seen the numbers sofar: 11 (partially), 12, 9, 10, 9, 10, 9 (partially), 9, 7, 8.

2017-07-16 Uploading FT8 contacts to eQSL
This evening I noticed incoming FT8 QSO's in eQSL, so the mode is now recognized there. But I needed to retry uploading all FT8 contacts to get them to upload. It took a bit of experimenting, but finally the right SQL command to mark the contacts as not uploaded was:
$ mysql -S /home/koos/.config/cqrlog/database/sock cqrlog002
mysql> update cqrlog_main set eqsl_qslsdate = NULL where mode='FT8';
Query OK, 24 rows affected (0.02 sec)
Rows matched: 26  Changed: 24  Warnings: 0
And now they are all uploaded.

That is about a week between first seeing mentions of FT8 in radio amateur news and the first confirmed contacts.

2017-07-16 I participated in the DMC RTTY 2017 contest
Or maybe I should use the word 'played' again: 6 contacts. It was a weekend with not much time for radio and when that time did happen propagation wasn't cooperating very well. The advantage of contests is that there are a lot of stations who want to hear every other station, so I used the last 20 minutes of this contest just to answer a few calls and get in the log.

2017-07-12 New digital mode for amateur radio FT8
This week there was a sudden 'buzz' about a new digital mode for amateur radio from Joe Taylor, K1JT. It's like JT65, with a very minimal exchange (callsign, locator, signal report) but with a lot faster timing: each turn is 15 seconds and from what I can see somewhat more than 13 seconds transmitting. I made the first few contacts today after downloading wsjtx from WSJTX-Development : Greg Beam as Ubuntu package.

Screenshot waterfall display WSJT-X with FT8 mode They are now in my log, but uploading to eQSL / Logbook of The World is not possible yet as 'FT8' is not seen as a valid mode yet. The solution for LoTW seems to be to change to 'DATA' but this solution does not work for eQSL. I'll have to upload those contacts later when the mode is recognized.

First contact was with IZ8GNR and I also had contacts with club members PA2RG and PD3RFR.

With JT65/JT9 I sometimes get distracted waiting 50 seconds before it's my turn to react again, with FT8 it's more high-speed work (somewhat less than 2 seconds to react to a CQ or an answer). WSJT-X now has an auto-sequence feature which will step through the exchange automatically.

Items before 2017-07-12
This page is created by Koos van den Hout, contact information at the end of my homepage.
Other webprojects: Weatherstation Utrecht Overvecht, Weather maps, Camp Wireless, wireless Internet access at campsites The Virtual Bookcase book reviews, webcam.idefix.net
This page generated by $Id$ in 0.037077 seconds.