I passed my novice radio amateur exam in March 2013 and I registered the
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
I am usually located around maidenhead locator: JO22NC
I upload logs to eQSL.cc and ARRL Logbook of the World, during and after being active on the radio. I upload logs to www.qrz.com and clublog on a regular basis. I like paper cards via the QSL bureau so I send those out when requested or when I think the other party will appriciate one and I will respond when I receive a card. You can also request a card via the Log Search on clublog for PE4KH using the OQRS service. Notifying me via e-mail that you would like a card is also possible.
I appreciate SWL reports for QSOs and will respond.
gallery of eQSL cards received by PD4KH, PE4KH, PE4KH/P, DL/PE4KH.
Antenna rotor project
D-Star digitale amateur radio (Nederlands)
Recent contact (QSO) map for PE4KH embedded using google maps
gcmwin for linux maps with gridsquares contacted (red) and confirmed (blue) :
Mapped HF contacts by PE4KH
Mapped 10M contacts by PE4KH
Mapped 15M contacts by PE4KH
Mapped 17M contacts by PE4KH
Mapped 20M contacts by PE4KH
Mapped 30M contacts by PE4KH
Mapped 40M contacts by PE4KH
Mapped 60M contacts by PE4KH
Mapped 80M contacts by PE4KH
Mapped 2M contacts by PE4KH
Mapped 70CM contacts by PE4KH
Mapped satellite contacts by PE4KH
Like in previous years I participated in the UBA PSK63 Prefix Contest in the weekend. Overall it was a nice contest, with 111 contacts in total which makes this a good contest score. I started in the 20 meter band on Saturday, moved to the 40 meter band after propagation died down due to the sun going down. On Sunday morning I started on the 40 meter band but soon gave up, there was a lot of interference on that band. I switched to 20 meters and made some more contacts. In the end: 38 contacts in the 20 meter band and 73 in the 40 meter band.
I turned on the remote radio today and saw in the DX cluster that the ZC4UW dxpedition was still active although 7 January was the last day. The signals were never good enough to make the contact, but this made me rethink the DX alerting options I have. I used 'DX Alert' on Android before, but this program had some difficulties and I can't find it anymore on the google play store which suggests it's really going out of support. The new suggestion is HamAlert which processes data from the DX Cluster network, PSKreporter, Reverse Beacon network and Sotawatch, allows the user to set triggers and report via push notification to a Android/Iphone when the HamAlert android app or equivalent iPhone app is installed. I created an account, installed the app and set up my first triggers: countries in and around Europe I don't yet have confirmed in bands/modes that I can use. It's a lot easier in HamAlert to set these up compared to DX Alert because it can all be done on the HamAlert website and can be customized more easily. Update 2020-01-12: First score: I activated the alerts today because I had some time to get on the radio between other things. I saw alerts for E44RU which is in Palestine on a non-standard FT8 frequency. I spun the dial, adjusted a bit and made the contact. And that's a new country for me.
This weekend was the ARRL RTTY Roundup edition 2020 and I participated. Late Saturday evening I saw a few US stations come up on 40 meters. Sunday afternoon I made a lot of contacts to mostly European stations on 20 meters. In the evening after dark the contacts from Europe seemed to stop after the first 24 hours were over but when I checked again late in the evening more US and some Canadian stations were decoded on my end and I worked them. In the end 110 contacts, a nice score for this contest. Claimed score: 110 qso points * 33 multipliers = 3630. The one that got away: I saw a station from California calling and giving state 'CA' in contacts, but he never heard me. That's the first time I heard or saw anything from one of the western US states.
Today I needed blocks of random letters to practise sending morse. What better tool to create those blocks than good old pwgen with the right settings:$ pwgen -0 -A 5 12 ahhud eizaa kuoku ahyoo aequi epiis eiwei eimap sohsh papai ikeit ouchoAnd the trick for generating groups of five digits is a bit longer:$ pwgen -r abcdefghijklmnopqrstuvwxyz -A 5 12 97228 85996 98876 38451 06091 98556 53369 73632 29509 29032 89601 16078Use better parameters with pwgen to generate actual passwords.
Time for a new plot of the number of radio contacts. Months with contests are quite visible. After the peak in number of contacts in July there was first a holday and after that no big peaks in number of contacts. December 2019 jumps out a bit again due to the FT8 roundup on 8/9 December in which I made 66 contacts and later in the month the troposperic ducting allowing contacts over interesting distances in the 70 centimeter and 2 meter band added to a sprint at the end. In 2019 I made a few more contacts than in the previous record year 2017. Looking back at my amateur radio resolutions for 2019 I think most came true. If I look at them one by one:
Now I have to think about 2020, but the year is still young.
- Keep learning morse! - I'm still working on my morse, but there is measurable improvement. I have learned the full set for the Belgian CW exam and I'm working on accuracy and speed.
- Get more countries on more HF bands in the log - More countries and more slots on HF are in the log. I also use the club station to achieve that goal. The ARRL DXCC Award shows that I'm getting somewhere.
- Moonbounce on 2 meter - I've listened on the right frequencies to the moon on 2 meter. Nothing heard.
- Those digimode contests, and maybe a few phone contests - I participated in two phone contests and a number of digimode contests. No serious improvement in scores.
- Operate HF outside - I operated HF outside. Not as much as I would like.
- At least one satellite contact - Multiple satellite contacts have been made!
I saw reports of special propagation on the 2 meter band and even on 70 centimeters today. Normally I can get something further than line of sight on 2 meter and line of sight is the hard limit on 70 centimeter. But with some propagation types it's different and signals can get further. So I tried FT8 on both bands and got Belgium, France, Germany and England in the log on 70cm and new callsigns on both bands. Denmark still got away, I had an almost-contact with a Danish station on 70 centimeters but it stopped after the initial exchange. This is all with the vertical antenna on the roof. I wonder what a beam or big wheel antenna for 70cm or 2meter could do. At the same time I spun the dial on the remote HF radio so I also got some calls in the log on 20 meters. Update: Current distance record on the 70 cm band is 803 kilometers to F8DBF in France and the first contact with Denmark has been made.
The main unit of the Kenwood TS-480SAT radio is now at a different location and the frontpanel is at home. With an OpenVPN connection between them so it's not exposed to the big bad internet. And it's working! I currently have access to a 10/15/17/20 meter antenna and I have already heard stations I wouldn't dream of receiving at home. And the first country in SSB in the log that I only had in digital modes before: Ceuta and Melilla, the Spain enclaves in Africa. Lag is minimal, audio is less delayed than listening to the utwente websdr to the same signal. Control works fine, so I can control the radio like I'm sitting behind it, including menu settings. Comparing received signals on the local radio with the attic dipole and the remote radio is hell and heaven: local noise is S9+ and the remote location has almost no local noise (while still being in an urban environment) so I can hear even weak stations fine. I leave the noise blanker off most of the time because it's not needed to hear signals fine. Not making loads and loads of contacts yet, propagation isn't cooperating very well and there aren't many people calling CQ. But when a somewhat special station calls CQ there are a lot of answers so there are numerous amateurs active. Or I guess they go to their set when they see an interesting callsign on the DX-cluster. I also got morse keying by paddle working beforehand. Hearing the sidetone from the radio with just a bit of lag got annoying fast when doing morse at a bit of speed so the sidetone is now from the control unit and the sidetone in the radio is silent. It's still set to the same audio frequency as the sidetone in the control unit to allow for finding the zero beat frequency.
This week had an opportunity to receive ISS SSTV pictures. The Russian on the ISS were transmitting SSTV images as part of the Inter-MAI-75 project. The pass had a partial first image, a nice decode of one full image and the start of a third image. Even the good receives are a bit noisy/unsharp, I'm not sure whether that's an artifact of the PD120 mode or some local noise ending up in the image. This is one of the rare occasions where living close to Russia is a good thing: the Russians time the passes to optimize reception in Russia.
I installed xcwcp from the unixcw packages on a different system and noticed it did not use PulseAudio. It said it could not find PulseAudio and skipped to ALSA. The downside of ALSA in xcwcp is that it pushes audio 10 characters ahead, with PulseAudio the buffer is smaller. Some searching using strace found that xcwcp tries to open libpulse-simple.so which wasn't found on that system. It is available on my laptop, as part of:$ dpkg -S /usr/lib/x86_64-linux-gnu/libpulse-simple.so libpulse-dev:amd64: /usr/lib/x86_64-linux-gnu/libpulse-simple.sowhile the files linked to a part of the runtime package:$ dpkg -S /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 libpulse0:amd64: /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 $ dpkg -S /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0.1.1 libpulse0:amd64: /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0.1.1But I don't have package libpulse-dev on that other system. Solution: make the symlink by hand in /usr/lib/x86_64-linux-gnu with:user@system:/usr/lib/x86_64-linux-gnu$ sudo ln -sf libpulse-simple.so.0 libpulse-simple.soAnd I reported it as a bug for ubuntu: Bug #1854630: xcwcp doesn't use pulseaudio but given the list of bugs in Ubuntu I reported or commented on before with a lot of 'undecided' and not a lot of progress I'm not sure anything will happen. Back to practising morse after this diversion!
The next thing I want to get working is morse with the remoterig and the Kenwood TS-480. The good thing is that the remoterig has a built-in morse keyer to overcome jitter problems. And that keyer has the option to make a winkeyer usb interface available. I did some minor testing with the winkeydaemon driver together with the paddle and it works. So I can use both the keyer from the computer and the paddle at the same time, just like with the nanokeyer and the FT-857 radio. There is one strange thing though: this keyer responds somewhat different from the nanokeyer when I do a fast dah-dit. I expect the dit to follow after the dah even when I already stopped touching the left paddle (dit) before the dah ends.