AmateurRadio.com

Recently I attempted a SOTA activation of Skiddaw G/LD-004. It is an easily accessible summit and a really good MTB route (called Back ‘o’ Skiddaw – although I’m not sure there is a link between the lake district and pirates but we’ll run with it). I’ve ridden it before but it has been a few years and the 17.5m route is straightforward and involves 2 out of the 4 lakeland MTB activities, these are of course:

1. Riding – Sounds trivial but read on
2. Pushing – Right its too steep / rocky / muddy. Get off and push the thing (generally up).
3. Humping – Stage 3 is extreme. You have to carry your bike. It is very heavy after a few meters
4.  Throwing – This is the last resort and usually used in the summer when vegetation is everywhere. Pick up your bike and throw it on the bracken. Step into the flattened area. Pick up and repeat.

As I said the route is straightforward. The kit is standard….

1. FT817nd
2. LiPo – 3S 11.1v 2200mAh
3. SOTAbeams SB270 (no longer available but a great antenna)
4. VX-8GR APRS handheld
5. Fishing pole
6. End fed half wave antenna and ilertuner
7. Palm paddle key
8. 7m fishing pole

So imagine the scene. Dropped son off at cub camp and parked up. the sun is shining and the breeze is gentle. A good spring day. No need to check the high level weather forecast as you can see the summit. Assume its a bit colder and windier up top so pack a lightweight fleece.

Ride off. Enjoy the view. Here are a few photo’s

Nobody this way

Or that way…excellent

Windy, cold and rocky. makes riding fun (ish)

I kept my helmet on to keep the heat in

Whilst on stage 2 (pushing) up seat how (a lower summit and not a SOTA one) a fell runner was coming down with full kit on. To the untrained eye this might sound reasonable but as this is Cumbria it is rare to see a fell runner (because they are very quick generally, blink and they’ve gone…into the mist) and its even rarer to see one wearing a jacket. I was concerned. Sure enough the wind got stronger and stronger. Even though I was on the windward face I was shielded or in some kind of wind flow niceness. It didn’t last. Over the top of the ridge and it was howling and cold. Quick up the top and find a windless spot on the leeward side of the summit.

Skiddaw is a loose rocky summit that is old, as are all the lakeland summits and valleys for that matter but thats a whole new post. The summit might have been in a wind tunnel. 40+mph and around 3c. Not good when you’re in shorts. So on with the spare clothes and set up. No chance of HF today and VHF was going to be a quick one. I tried 2m USB but couldn’t keep the antenna straight so switched to FM and added more rocks to the support. No joy. I had to drop it to ground level and made do with the few contacts I made. Not what I planned at all.

There will be many morals to take from this experience. I like to focus on the positives and ignore the negatives, it helps block out the cold in this instance. So the main points…..

2 hours up……..10 minutes down…….great down hill section weaving around the many walkers who on the whole were much better behaved than they have been in the past. Just don’t touch the brake rotors for a while and keep them spinning.

Next summit will be…….TBC

My main project for at least the last 12 months has been building a solid magnetic loop antenna and its companion automatic loop controller. I’ve been roughly tracking its progress at my magnetic loop antenna project page on this blog.

As usual, life has got in the way, but I want to get back on track and complete the project. To start pumping some RF current through it again, over the weekend I spent a short time playing with the loop on WSPR on 40, 30 & 20m. The tests were too brief but they certainly confirm that the loop is capable of transmitting a signal in spite of the fact the loop is only half a metre above ground and surrounded by metal garden furniture, a steel framed awning and gutters.

I used the WSPR Beacon android app to control my transmitter. There was some discrepancy (tens of Hz) between the actual output frequencies on the app and those shown on WSPRnet. I also found that tuning the loop to each WSPR frequency using the iP30 antenna analyzer was easy and the KX2 gave lower SWR figures.

The brief test became an exercise in understanding theWSPRnet results taking into account propagation and loop orientation which was aligned north-south.

This map view combines all 20 spots of the 1W VK2RH transmissions from grid square QF56oc. The first test was logged at 2017-05-07 01:36 UTC. (I’ve trimmed repeated info from the chart below to improve its fit on the page.)

40 metres favoured north-south, while 30 metres was literally an all-rounder and 20 metres was too brief. These results probably say more about propagation than the loop, not to mention the heavy lifting done by all the reporter stations extracting my down to -26 or -27 dB signals from the noise! Impressive all round!

I wonder how many people are using the Sotabeams WSPRlite antenna tester device. Certainly looks tempting, especially for longer term antenna evaluation.

In any case, the main purpose of today’s exercise was to re-start the loop project. The To Do list includes

• building & installing the SWR bridge into the loop controller,
• deciding on the best way to couple the stepper motor shaft to the tuning capacitor shaft,
• and wiring it all together with appropriate coax and control cables.

Results from a study published by University of California Berkeley in The Journal of Psychology found that amateur radio operators are 45% more likely than the general public to believe fake news articles or material with misleading or outright wrong claims.  Researchers weren’t specifically studying amateur radio operators, but discovered the correlation by accident.  The report noted:

“We tested over 15,000 adult subjects and recorded profiles of each person… the common attributes like age, race, ethnicity, etc. and also their likes, dislikes, hobbies, diets, habits, etc.  We discovered a strong and unexpected correlation with those claiming to be amateur or “ham” radio operators after running all of the data through an analysis using a recently developed Reverse Polish Bayesian algorithm.  The unexpected data correlation continues to have the research team puzzled and further study is warranted.”

There is currently no proven explanation for the correlation, however one plausible hypothesis has emerged, that exposure to high levels of radio frequency energy combined with very fatty diets and long periods of television viewing, with political and news programming exposure, causing the frontal cortex of the brain to rapidly atrophy.  Researchers are struggling to reproduce the characteristics as lab mice either die or become very disinterested when exposed to the combination of factors, especially when frequencies in the 3.5 Mhz range are used in experiments.

This article originally appeared in Radio Artisan.

I am sitting here watching the NFL playoffs and remembered that I never posted my final post about my portable station build. I completed the build last year. I say completed, but of course that does not rule out future modifications. I am a ham after all right? 

The major change from the last post to this one is the addition of a front panel on the lower portion that allowed me to add connectors for power and antennas easily in the front of the box. 

There are two antenna connectors on the left for the FT-857D, one for HF and the other for VHF/UHF. The HF jumper actually is connected to the antenna tuner and there is another jumper goes to the radio. There is also a VHF/UHF connection on the right for the FT-8800R. The power connector I salvaged from a computer power supply and made a power cable that plugs into the Powerwerx power supply. 

The last picture is the setup in action at Field Day. I was running PSK31 with my club on 20m and had a good time. You can see that the radio on the left is running and there is no power connector in the front. In this picture, I have a 35 amp/hour battery under the table feeding power into the RigRunner mounted in the back of the rack. I was able to run low power digital modes all day and into the night. I still had power left over when I went home.  



I have been happy with the rack that I built. Lately I have thought about splitting the radios apart into their own rack as I have found that I don’t use both at once usually. There are also events where I need just the FT-8800R and don’t need the HF gear. Having the FT-857D along for the ride does give me a spare radio if something were to malfunction with the FT-8800 during an event I suppose. So for now, this is the result. 

K5UNX

Last year I decided that I wanted to learn and use CW. To that end, I enrolled and completed the CW Academy Level 1 class with the CW Ops group (http://www.cwops.org/cwacademy.html). I have 2 CW QSO’s under my belt and I need to get on the air and make some more. Ion preparation for that, I decided to get the 500Hz CW Filter to add to my FT-857D. The radio has two slots for optional filters. Looking online, it seems the filters for the FT-857D are getting harder to find. I found one on INRAD’s web site and ordered one. It came a few days later and sat on my desk for a couple days. being Saturday and getting some things done, I decided to install it. I found it’s really very easy to install this filter.

To start with, there are 7 screws that hold on the top cover of the radio. 2 on each side and 3 on the top. The labels are simply my way of remember where things go in the back of the radio while it’s in my portable rack.

After removing the cover the locations for the filters are in the back left corner, as shown in the lower left portion of the photo below.

An up close look.

The filter is pretty easy to orient. There are 3 pins on one and and 4 on the other so it’s hard to get it backwards. There was also a reminder from INRAD that the circuit board went down and the label faces up. Here is after the installation which is simply pressed in.

After the installation, I wanted to make sure it was recognized by the radio so I powered it in and looked at the filter menu option and the 500Hz filter showed up as option B.

Now all I have to do is get on the air! When I do that, I will try to remember to make a video demonstrating how the filter affects reception of CW signals.

If you have a FT-857(D) and would like a CW filter for it, you might put this project on your list. I can imagine a day when these filters are really hard to find!

73!
K5UNX

My last post, I talked about getting Linux setup for my new ham laptop. This is a short post to cover another small step in that process.

Tonight I was working on getting Rig Control working for my FT-857D and CQRLog on Linux. A lot of times, when I read posts like this, or watch youtube videos, people ignore the hardware side and just focus on the software side of things. I am going to try and cover both.

The hardware setup is simple. I am using the programing cable (CT-62B cable) that came with my RT Systems software to connect the CAT port of the FT-857D to a USB port on the laptop.  Windows will see this cable a COM port, in my case, COM3 when I booted to Windows.

I found I had to install a couple things in Linux in order to get this working properly. When I intalled CQRLog, hamlib was installed along with it. I also had to install a package called libftdi1. When I look at the output of “dmesg” I see that the CT-62B cable shows up as ttyUSB0 which is the name of the serial port in Linux that I am going to use to communicate with the radio.

In CQRLog I set the following:

• RIG Model = 122 FT-857
• Device = /dev/ttyUSB0
• Serial Speed = 4800 (This is what the radio is set to)
• Check the box for “Run rigctld when program starts”

Everything else on the TRX control setup in CQRLog is set as default and not changed from the installed values.

One last Linux setting, in the /etc/group file, I had to add my user name to the “dialout” group. This can be done with the command usermod from a terminal. In openSUSE which is what I am running, I ran the command “usermod -G dialout k5unx”. I then logged out and back in and started up CRLog. When I opened the TRX control window the frequency matched what was one the radio and when I spun the radio dial, CQRLog changed with it.

More to come as I get up and running with Linux on my ham radio laptop. 

The last few years, I have been using an old hand me down laptop for my ham radio activities. The old one had little memory, the battery that didn’t last very long, was starting to boot unreliably, even after a Windows reinstall, and a few other issues. So I bought an open box Dell laptop at a discount from a local retailer. It has 8GB of RAM and a 1 TB disk drive and i5 processor. While it’s not a top of the line laptop, it’ll work for what I have intended. Also the screen isn’t the highest resolution but since it’s dedicated to ham radio usage only it won’t be a problem.

My main goal with this project is to use Linux more for my ham radio activities. I now work professionally in the Linux world so I would like to carry that experience into my ham radio hobby. I am setting this up as a dual boot system, keeping Windows 10 that came on it, and then installing OpenSUSE Leap 42.2 as my Linux distribution. I know Ubuntu seems to be the most popular distribution, but I am most familiar with SUSE Enterprise Linux, so OpenSUSE draws on that experience. I run openSUSE 42.2 on my work laptop on a daily basis so I am very familiar with it.

I thought I would post about the steps I am taking to achieve this so if anyone else decides to do something similar, I will have shared what I went through. I will try to follow this up later with posts about using various Linux applications for ham radio like CQRLog, WSJT-X and other things I find useful.

I will use the Windows install for a few things. My old ham radio laptop was running Windows so I can duplicate it’s capabilities if needed. One of those jobs is some Windows software that I bought from RT Systems for programming my radios. I’ll eventually investigate Linux alternatives such as Chirp but that will be low on the priority list.

The first steps I took in the process are:

• Boot into BIOS/uefi and disable Secure Boot. I don’t need this.
• Boot up Windows, create user account, and fully make sure all updates are installed, and any initial setup.
• Make a Windows 10 recovery USB thumb drive. This is built into Windows 10.
• Download the restore image from Dell to restore the laptop if needed.
• Run the Windows Disk Cleanup utility to remove all unneeded files including any previous version of Windows left behind after the updates, and all update related files. I check all the boxes in the cleanup utility including system files.
• Defragment the C: drive. This is needed so I can shrink the C: partition
• Use diskmgmt.msc to shrink the main Windows 10 partition to about 450GB. That will leave about 430GB of free space to use for Linux installation. I had to disable system protection, pagefile and hibernation in order to get the drive to shrink to where I wanted it. These are unmovable files and might hamper the  ability to shrink the disk. After shrinking, I reenabled all of those.
• VERY IMPORTANT STEP: Use Clonezilla to make a complete cloned backup of the entire disk drive so I can put Humpty back together if something bad happens or I make a mistake. This will backup all the partitions to a set of files on a USB drive, and allow me to completely restore the drive and partitions.  I now have 3 ways to restore the system. Clonezilla backup, restore image I downloaded, and the Windows Recovery thumb drive I created.
• Install Dropbox as I’ll use that to transfer some things from the old laptop to the new one.

BACKUPS are very IMPORTANT as is the ability to UNDO something even if it means a full restore. NOTE: Clonezilla doesn’t backup empty space to the resulting backup is smaller that the drive that’s being cloned.

Now it’s time to install Linux. I made a bootable thumb drive from the openSUSE Leap 42.2 iso. This was done using dd on my work Linux laptop. The website to download openSUSE from is: http://www.opensuse.org.  There are two openSUSE distributions. Leap is a point release and Tumbleweed is a rolling release and always at the bleeding edge. If you want something stable then Leap is the way to go. It’s also what I run on my work laptop as my primary OS.

I booted from the Leap thumb drive, and went through a normal install. From the free space I created by shrinking the Windows partition, I made a 4GB swap partition, a 50GB / (root) partition and assigned the rest of the space to /home which is where all my data will reside.

When Linux is installed, it installs the Grub2 bootloader which is able to detect Windows 10 and make it a selection at boot time. When you boot the system, a Grub2 menu will display allowing the choice of which operating system to boot. You can also choose which one boots as default when the grub2 timer expires.

One thing I found . . . When I booted back into Windows, it assigned drive letters to the Linux partitions which is something I did not want. I started up diskmgmt.msc in Windows and removed the drive letter associations from the 3 Linux partitions. That way Windows won’t mount the Linux partitions and possibly cause an issue.

At this point, I have a dual boot system and am ready to go. So far on the Linux side I have installed the following:

• Terminator – A nice terminal program
• cqrlog & mysql – Popular Linux Ham Radio Logging program. I exported my log from HRD (ver 5.24) on the old computer and imported it into cqrlog.
• tqsl – I made a backup of my certificate using tqsl on the old Windows computer and was able to restore it using tqsl on the new Linux installation.

One last thing before moving on. I took another Clonezilla backup of the entire laptop drive. Now I have two Clonezilla backups and could restore either one if I desired. 

Just a note on Virtual Machine vs Dual boot. I use VM’s daily on my work laptop and my other personal laptop so I am very accustomed to their use. On my work laptop I run Linux full time with Windows 10 in a virtual machine along with about 10 other Linux VM’s (not all running at once). For the ham laptop I wanted two things. To run Linux as full time as possible for my ham radio hobby, and for the operating system to have direct access to the hardware without the virtualization layer in the middle.

More to come!