PE4KH Amateur radio - Koos van den Hout

Most recent QSO's for PE4KH

Callsign Band Mode Locator RST(R) RST(S) Satellite

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

I am usually located around maidenhead locator: JO22NC

The 'hamradio' items from my homepage

2020-01-06 Security tools can help practise morse
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 oucho
And 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 16078
Use better parameters with pwgen to generate actual passwords.

2020-01-01 Closing 2019 in amateur radio, time to plot the number of contacts and look back
QSO count plot up to December 2019 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.

2019-12-29 New countries.. on the 70 centimeter band
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.

2019-12-27 First radio contacts with the radio and antenna setup at a remote location
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.

2019-12-06 Received ISS SSTV again
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. ISS SSTV image ISS SSTV image ISS SSTV image

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.

2019-12-01 Better audio for learning morse
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 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-dev:amd64: /usr/lib/x86_64-linux-gnu/
while the files linked to a part of the runtime package:
$ dpkg -S /usr/lib/x86_64-linux-gnu/
libpulse0:amd64: /usr/lib/x86_64-linux-gnu/
$ dpkg -S /usr/lib/x86_64-linux-gnu/
libpulse0:amd64: /usr/lib/x86_64-linux-gnu/
But 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
And 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!

2019-11-24 Morse with the Kenwood TS-480 and remoterig
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.

2019-11-23 PC control of the TS-480 radio working again, including for remoterig
I dug into the "why isn't remote CAT control not working" on the Kenwood TS-480SAT with the remoterig setup and as the debugging session progressed I found out it wasn't even working locally. The Kenwood TS-480 radios have a male db9 connector just like the PC had, and the non-intuitive part is that it needs a straight-through cable with data lines and hardware flow control.

I had a bunch of serial cables and adapters cobbled together to get from DB9 female to DB9 female with wires 2 and 3 coming out uncrossed, but it did not have hardware flow control and that had worked one evening before but now it decided to go on strike.

Thanks to the visit to the "Dag van de radio amateur" (DvdRA) ham convention and the extra parts ordered on-line from Conrad I had enough parts to make my own serial cable with the right wiring, including covers for the connectors with the cable coming out on the side.

So my skills in building right serial cables using a soldering iron, flexible wire and an amount of patience were recalled. I am very sure I haven't done that yet this century. Old CAT-5E cables are a good source of flexible cable with 8 wires.

When I had a finished cable with hardware flow control I first did a local test before I started putting the covers on the connectors and when that did work fine I put the covers on, redid the test and switched to testing over the remoterig connection. That also worked.

Update: And for the laptop which doesn't have serial ports I activated the COM port to USB translation on the control side. It took a bit of searching before I found that /dev/ttyACM0 was the active port, so now I can run CQRLOG on the laptop with full control of the radio.

2019-11-22 Finished the remoterig setup and made the first contact
I finished the setup of the remoterig system. The second part is with lots of wires, first setting jumper wires in the radio box and the control box and after that connecting lots of wires to radio, frontpanel, microphone and other parts.

It took a bit of browsing the manual, checking my jumper wires under good light and redoing the checks but eventually it got all connected.

After that it was setting the software parameters for the specific radio and the connection to the control panel. And the next step: pressing the power button on the frontpanel on the control box and seeing it become active and hearing audio from the radio.

So it's now working. The bit that doesn't work yet is CAT control of the radio (Computer Assisted Tuning, where I can read the status and give commands over the serial port). The forwarding of the CAT port to a USB serial port on the other side did not give me any communication on the connected computer. I'm sure I'll get that fixed.

Next step was to spin the dial and find someone searching for a contact. Not a lot of activity on the 40 meter band, but I heard a greek station calling, answered it and got into the log.

2019-11-21 First setup of the remoterig interfaces
The remoterig set I ordered arrived.

At first I found the box somewhat empty: no manuals. But the entire manual can be found on-line: User manuals - RemoteRig. The manual is about 200 pages so printing it would be a bad idea. The remoterig site is somewhat slow so I downloaded the PDF manual to my computer.

Most of the setup is done via a webinterface, but the initial network setup needs either the right IP addresses hardcoded or a USB connection and the Microbit setup software which is only available for Windows. I did try to see whether one of the four com-ports via USB that showed up would allow me to do a minimal setup via a terminal program but that wasn't true. So I booted Windows to change the units to DHCP. For the radio-side I made an address allocation in the DHCP server, for the client side it is fine to have any usable address.

And for my next minor issue: they only use IPv4. So my inner linux and networking geek is a bit dissapointed, but my inner radio geek will do just fine.

After that bit I went back to Linux, the rest of the software setup is via a webbrowser. For the hardware setup, which is how it connects to the radio (which pin has audio, which pin has power) it needs a number of internal jumpers and jumper wires connected.

Items before 2019-11-21
This page is created by Koos van den Hout, reachable via e-mail as my callsign @
Other webprojects: Weatherstation Utrecht Overvecht, Camp Wireless, wireless Internet access at campsites The Virtual Bookcase book reviews
--... ...--
This page generated by $Id$ in 0.005251 seconds.