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
To practise my morse at the radioclub I looked for a simple morse practise oscillator and found Morse practise oscillator kit - Kent and ordered it at the beginning of Februari. It took a while for it to arrive, but it arrived and I built it in one evening. It's a quite simple kit. Which means the power for the whole circuit runs via the morse key, in theory about 120 mA. And that is more than the octocoupler on the CW output of the nanokeyer I built is willing to deliver (50 mA). So I can't use the practise oscillator straight away, there will need to be a small amplifier in between. Some searching suggests I can use a transistor as 'power amplifier'. Time to look at what I may have (which is not a lot) or find a transistor somewhere. Solution: order a bunch of transistors in a collection so I have some in the junkbox. Oh and: The dashes and dots in the title are the word 'MORSE' in morse.
The Kent morse practise oscillator built
Last weekend was the EAPSK63 contest and I participated on Saturday. Lots of stations from Spain active and I managed to work 29 unique Spanish provinces. A total of 82 contacts. I could only participate Saturday afternoon and evening so that limited my time in the contest.
I did some more testing with the HP power supply I bought last November. In previous tests the output voltage seemed to be limited at 13 volts and it seems limited to 13.10 volt at the moment. The RM Italy HLA300V plus amplifier I have will only output about 55 watts maximum in digital modes so that's less than I expect. A higher input voltage may fix this, but I'm not sure how to get the power supply to deliver this and keep running. The previous power supply gave up in a busy weekend but before that the HF linear amplifier delivered more power. I have seen it go over a 100 watt on digital modes. The difference in output from the linear amplifier with 13.10 or 13.27 volt power is quite large, which surprises me.
During our wintersport holiday in Austria I also brought my Arrow antenna and handheld radios along to try a satellite contact. Before the holiday I read on twitter that Peter Goodhall 2M0SQL has unconfirmed gridsquares which included the place I was going on holiday. So I prepared for trying to make the contact during the holiday. In the preparation I got a theory why I had problems with the satellites with a 2 meter downlink frequency. During the holiday I soon figured out there wasn't a lot of time for contacts, during the day we were on the pistes and we went to bed early because we had a lot of physical activity. And the place we stayed was between the mountains so for satellite passes I was limited to high passes. In the end I did listen to one Fox-1D pass which was high and long enough. In a serious amount of falling snow so that was a new experience in amateur radio: trying to make contacts in the snow. Reception of Fox-1D was quite good on the Baofeng UV-5R radio, but transmitting back up didn't work out, I never made a contact. I did not hear Peter on that pass, so that did not work out at all. But I learned several things, including the fact that the theory about the 2 meter downlink frequencies and the Wouxun KG-UVD1P was correct so the result is positive anyway.
I was preparing for trying some satellite contacts and noticed the Fox-1B and Fox-1D had nicer opportunities for a contact. But I always have problems receiving any signal from those satellites on the handheld radio that I use for satellite contacts, which is the Wouxun KG-UVD1P I got for Christmas in 2012. Not the ideal radio for amateur satellites, but easy to bring along and to program with split frequencies. A while ago I noticed that radio was constantly receiving noise on the 2 meter band and I had to set the squelch level quite high to stop it. I thought it was some local overload or local noise in the 2 meter band. But today while working on the preparations for some satellite contact possibilities I figured the problem is with the radio and something is actually wrong on the 2 meter receive side. I have two other handheld radios. One is a Kenwood TH-D7 where I can't change the squelch level so it's not really usable for satellite contacts and the other is a Baofeng UV-5R which can't be programmed via the computer. So I spent a lot of time entering all the possible doppler-shifted frequencies of both satellites on the keypad of the Baofeng UV-5R. I hope that gives me a working radio for Fox-1B/Fox-1D and I can get a few new contacts in the log. Update 2020-02-27: I was correct! I tried a Fox-1D pass with the Baofeng UV-5R radio and I had easy reception of the satellite. Trying to get my signal over the satellite didn't work, but at least I know what the reception problem was.
I had one whole contact on the 60 meter band a few years ago with a German station. This band is supposed to be outside of the reach of my longwire, but with a lot of tuning it can work. This weekend the longwire and the tuner absolutely did not want to get to a workable state on the 80 meter band so I tried the 60 meter band again. In FT8 mode, as that is what gets me the most result from home outside of contests. This got me a number of contacts. Also one new country already confirmed: Tajikistan. And a new country with a questionable contact, so I'm waiting to see whether the other side will confirm or not. Formally 60 meter doesn't count for ARRL DXCC, but to me every contact counts in some way. I even got stations responding to me before I called CQ, I guess some amateurs are keen on getting a new callsign in the log. I took down the wire antenna Saturday early in the evening because the winds were picking up for another storm.
I'm still working on learning morse code. Sending morse code with the paddle is going ok at about 10-12 words per minute. Receiving is also somewhere around that rate, but I make more errors receiving. I practise receiving morse with G4FON (Windows), xcwcp (Linux) and IZ2UUF morse trainer (Android). G4FON offers Farnsworth timing, where the letters are transmitted at a higher rate but there is extra spacing between letters to lower the rate of transmission. In xcwcp I can add extra dots between letters and in IZ2UUF morse trainer I can set extra length as a factor of the letter length. Three somewhat different methods to help learn morse at a reasonable speed. To practise sending morse I use either the FT-857 radio or the control unit of the remote radio as expensive morse sounders. For the morse training at the radio club this is somewhat bulky and the internal buzzer of the nanokeyer is not loud enough so I ordered a practise oscillator kit from Kent morse equipment in the UK. I also joined The Less Involved Data Society where I hope to meet newcomers to morse on the air. So I am now LIDS member number 414. And for the rest: practice, practice, practice. Changing between modes of practice such as whole words in English or Dutch or back to random characters or groups of 5 letters helps improving speed and accuracy.
This weekend I had some random radio time so I made a number of contacts. By numbers mainly in FT4 and FT8 but also some SSB and CW via the remote radio. I activated HamAlert triggers and used that to get a few countries in the log that I wanted confirmed via LoTW. This worked for Corsica and San Marino. I got an alert for a San Marino call on Saturday and worked it reasonably fast after an FT8 CQ from that station. On Sunday I saw a notification for a Corsican call on FT8. When I saw the activity I noticed the station was just calling other stations. So I just started answering the callsign in the hope of getting the contact and after a few tries the hint came across and I got the contact in the log. This is an area where an alerting system that uses more sources than just the DX cluster network works better: the station from Corsica never showed up on the DX cluster, but the activity was seen by PSKreporter and filtered by HamAlert into a notification to me. The contact with Corsica is already confirmed on LoTW.
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.