This solution has worked incredibly well from the outset and over time I’ve added extra functionality that I’ve found to be useful to enhance the overall setup.
The latest addition to the ground station solution is a Sennheiser Headset that I picked up for just £56 on Amazon (Much cheaper than the Heil equivalents at the HAM stores!) and have found it to be excellent. The audio quality from both the mic and the headphones is extremely good whilst being light and comfortable to wear for extended periods.
M0AWS – Sennheiser SC 165 Headset
To incorporate this into the ground station the headset is connected to my Kubuntu PC and the audio chain to the IC-705 is sent wirelessly using the latest version of WFView. This works extremely well. The receive audio comes directly from the GQRX SDR software to the headphones so that I have a full duplex headset combination.
Audio routing is done via pulse audio on the Kubuntu PC and is very easy to setup.
Since I no longer have a mic connected to the IC-705 directly I found that I needed a way to operate the PTT wirelessly and this is where the latest addition to my NodeRed QO-100 Dashboard comes in.
Adding a little functionality to the NodeRed flow I was able to create a button that toggles the IC-705 PTT state on and off giving me the ability to easily switch between receive and transmit using a simple XMLRPC node without the need for a physical PTT button.
M0AWS – Additional NodeRed PTT Flow
The PTT state and PTT button colour change is handled by the Toggle PTT function node shown in the above flow. The code to do this is relatively simple as shown below.
M0AWS – NodeRed Toggle PTT Function to change button colour
The entire QO-100 Dashboard flow has grown somewhat from it’s initial conception but, it provides all the functionality that I require to operate a full duplex station on the QO-100 satellite.
M0AWS – NodeRed QO-100 Dashboard complete flow
This simple but, effective PTT solution works great and leaves me hands free whilst talking on the satellite or the HF bands when using the IC-705. This also means that when using my IC-705 it only requires the coax to be connected, everything else is done via Wifi keeping things nice and tidy in the radio shack.
M0AWS – Updated NodeRed QO-100 Dashboard with PTT button
The image above shows the QO-100 ground station in receive cycle with the RX/TX VFO’s in split mode as the DX station was slightly off frequency to me. The PTT button goes red when in TX mode just like the split button shown above for visual reference.
As you can probably tell, I’m a huge fan of NodeRed and have put together quite a few projects using it, including my HF Bands Live Monitoring web page.
Since I’ve been using my Icom IC-705 on the QO-100 satellite I’ve been getting no end of unsolicited great audio reports with one Op even saying I have the best audio he’s ever heard on the satellite.
Most people are surprised when I tell them that I am using the stock fist mic that comes with the radio. It’s nothing special, in fact it’s rather cheap and plastic, not particularly good quality however, it does seem to have a good sounding mic insert.
The other great thing about the IC-705 is that it has a two channel parametric equaliser built into the radio. Many people don’t realise this and miss out on the massive improvement they can make to their transmitted audio with just a few simple adjustments.
The stock fist mic has a very flat response across the audio frequency range out of the box and doesn’t sound particularly inspiring. Many see this as a negative and often just replace the mic with either a headset (probably from Heil), a boom mic (again probably from Heil) or another, better quality fist mic. All of these options cost varying amounts of money when in reality none of them are necessary.
Starting from a flat audio response is actually a good thing as it makes the equaliser adjustments more pronounced, making it easier to adjust the settings to suit your voice.
We all have different voices but, there is one thing that is pretty much the same for everyone and that’s the frequency range in which the articulation of the words and sounds we make can be found. It’s this part of the voice that is often lacking when we struggle to understand what the DX station is saying.
It’s become common place on the HAM bands these days for stations to boost the bass frequencies and reduce the mid and high frequencies with the net result of a horrible bass ringing sound and muddy mid range often making it very difficult to understand what is being said.
Having spent some considerable time watching the great videos on audio from the late Bob Heil, K9EID it’s clear that the most important frequencies to enhance are those around 2.5khz as this is where all the articulation is in the human voice.
To this end I set about setting up the audio on my IC-705 QRP radio so that my voice sounded such that it is easy to comprehend even in the most difficult of situations on air. This doesn’t mean that it has to be very harsh and overly bright, quite the opposite in that to be heard clearly in all conditions on air one’s audio needs to be balanced across the frequency range with an enhancement in the 2.5Khz frequency range.
M0AWS IC-705 Transmit audio settings – part 1
To reduce the unwanted, muddy bass the first thing to do is change the transmit bandwidth for the “Wide” setting to 200-2900Hz. This will cut off the bottom 100Hz from the voice reducing the overall bass output from the standard fist mic that comes with the radio. This will ensure a 2700Hz wide SSB signal, the recommended max for QO-100 operations and the preferred bandwidth on the HF bands.
On top of this I made a further reduction of 2dB on the TX Bass setting to help balance out the overall audio response of the mic insert.
Next I set about enhancing the higher frequency response of the mic insert and found that it required an increase of 4dB to bring out the articulation of my voice. This enhanced my audio considerably compared to the standard output from the fist mic and improved the intelligibility of my voice considerably, especially in difficult band conditions.
To complete the setup I set the compression to 3 and mic gain to 35 so that the overall drive level is increased slightly giving a greater average output from the radio.
M0AWS IC-705 Audio Settings – part 2
Once I’d got the audio setup correctly I enabled the configuration by setting the Transmit Bandwidth (TBW) to the “Wide” config in the IC-705 Function menu so that the correct settings were made active.
Ever since making these relatively easy changes I have had no end of unsolicited great audio reports from stations asking me what mic I am using and how I’ve managed to get such good audio from the IC-705. Many are surprised that I am using the OEM fist mic that comes with the radio and I’m sure there are those who don’t believe me!
Of course all voices are slightly different and these settings may not be perfect for your voice but, all those that have tried these settings have told me that their audio sounds better than ever and that DX stations often comment on how good their audio is.
I also went through the same exercise with my Yaesu FTDX10 with it’s standard fist mic and again achieved excellent results with it’s 3 channel parametric equaliser. I’ll go through the somewhat more complicated setup for the FTDX10 in another article soon.
Many years ago I had an MFJ-259B antenna analyser that I used for all my HF antenna projects. It was a simple device with a couple of knobs, an LCD display and a meter but, it provided a great insight into the resonance of an antenna.
MFJ-259B Antenna Analyser
Today things have progressed somewhat and we now live in a world of Vector Network Analysers that not only display SWR but, can display a whole host of other information too.
Being an avid antenna builder I’ve wanted to buy an antenna analyser for some time but, now that I’m into the world of QO-100 satellite operations using frequencies at the dizzy heights of 2.4GHz I needed something more modern.
If you search online there are a multitude of Vector Network Analysers (VNAs) available from around the £50.00 mark right up to £1500 or more. Many of the VNAs you see on the likes of Amazon and Ebay come out of China and reading the reviews they aren’t particularly reliable or accurate.
After much research I settled on the JNCRadio VNA 3G, it gets really good reviews and is very sensibly priced. Putting a call into Gary at Martin Lynch and Sons (MLANDS) we had a long chat about various VNAs, the pros and cons of each model and the pricing structure. It was tempting to spend much more on a far more capable device however, my sensible head kicked in and decided many of the additional features on the more expensive models would never get used and so I went back to my original choice.
Gary and I also had a long chat about building a QO-100 ground station, using NodeRed to control it and how to align the dish antenna. The guys at MLANDS will soon have a satellite ground station on air and I look forward to talking to them on the QO-100 transponder.
M0AWS – JNCRadio VNA 3G PackagingM0AWS – JNCRadio VNA 3G in box with connectors and cables
Initially I wanted to check the SWR of my QO-100 2.4GHz IceCone Helix antenna on my satellite ground station to ensure it was resonant at the right frequency. Hooking the VNA up to the antenna feed was simple enough using one of the cables provided with the unit and I set about configuring the start and stop stimulus frequencies (2.4GHz to 2.450GHz) for the sweep to plot the curve.
The resulting SWR curve showed that the antenna was indeed resonant at 2.4GHz with an SWR of 1.16:1. The only issue I had was that in the bright sunshine it was hard to see the display and impossible to get a photo. Setting the screen on the brightest setting didn’t improve things much either so this is something to keep in mind if you plan on using the device outside in sunny climates.
(My understanding is that the Rig Expert AA-3000 Zoom is much easier to see outside on a sunny day however, it will cost you almost £1200 for the privilege.)
A couple of days later I decided to check the SWR of my 20m band EFHW vertical antenna. I’ve known for some time that this antenna has a point of resonance below 14MHz but, the SWR was still low enough at the bottom of the 20m band to make it useable.
Hooking up the VNA I could see immediately that the point of resonance was at 13.650Mhz, well low of the 20m band and so I set about shortening the wire until the point of resonance moved up into the band.
JNCRadio VNA3G showing 20m Band EFHW Resonance
With a little folding back of wire I soon had the point of resonance nicely into the 20m band with a 1.35:1 SWR at 14.208Mhz. This provides a very useable SWR across the whole band but, I decided I’d prefer the point of resonance to be slightly lower as I tend to use the antenna mainly on the CW & FT4/8 part of the band with my Icom IC-705 QRP rig.
Popping out into the garden once more I lengthened the wire easily enough by reducing the fold back and brought the point of resonance down to 14.095Mhz.
JNCRadio VNA3G showing 20m Band EFHW Resonance 14Mhz to 14.35Mhz Sweep
The VNA automatically updated the display realtime to show the new point of resonance on the 4.3in colour screen. I also altered the granularity of the SWR reading on the Y axis to show a more detailed view of the curve and reduced the frequency range on the X axis so that it showed a 14Mhz to 14.35Mhz sweep. With an SWR of 1.34:1 at 14.095Mhz and a 50 Ohm impedance, the antenna is perfectly resonant where I want it.
It’s interesting to note that the antenna is actually useable between 13.5Mhz and 14.5Mhz with a reasonable SWR across the entire frequency spread. Setting 3 markers on the SWR curve I could see at a glance the SWR reading at 14Mhz (Marker 2) , 14.350Mhz (Marker 3) and the minimum SWR reading at 14.095Mhz (Marker 1).
The male to male SMA connector that Neil, G7UFO kindly posted to me arrived late this afternoon and I wasted no time getting it connected between the 2.4Ghz up-converter and the 12w amplifier.
Male to Male SMA connector for QO-100 Ground Station
Initially when I powered up the 12v to 28v converter board the output voltage was only showing 22v and so I had to adjust the onboard variable resistor to get the voltage closer to the recommended 28v for the amplifier. I decided to run the amplifier at 27v so that it wasn’t being pushed to it’s full and so readjusted the voltage converter back down to 27v. This seems to work very well with the amplifier not getting very warm at all during use.
M0AWS QO-100 2.4Ghz Uplink Hardware.
Getting on air I was really impressed at how strong my signal was on the 10Ghz downlink. With my own signal peaking 5/9+10dB I was very happy with the performance of the ground station.
I made a few contacts very quickly with the first being OH5LK, Jussi from Helsinki Finland. Jussi was actually the first station I worked on CW too when I was running just 200mW, it was great to have him for both of my first contacts on QO-100.
I then went on to work a few stations from Wales, Germany, Poland and Belgium but, the one that I was totally shocked to get on my first real day of QO-100 operations was ZD7GWM, Garry (HuggyBear) on St. Helena Island, South Atlantic Ocean. This is an Island that I have never had a contact with before on any band and so I was extremely happy to get a new first especially on my first QO-100 day.
Garry and I chatted for some 25 minutes covering many topics, it was great to have an armchair copy over such a distance, something that would be impossible on the HF bands. What a great way to start my QO-100 satellite career!
One of the things I really like about the operators on QO-100 is that they have time to stop and chat, this is so refreshing and a rarity today. I’m really going to enjoy this satellite.
I’ve been waiting for over a week so far for a male to male SMA connector to arrive from Amazon so that I can connect the 2.4Ghz up-converter to the 2.4Ghz amplifier. Since it still hasn’t arrived I decided to connect the up-converter directly to the IceCone Helix antenna to see if I could get a signal into the QO-100 satellite.
To my surprise I could easily hear my CW signal on QO-100 even though the total output from the up-converter is only 200mW.
I didn’t expect to be able to hear my signal since it’s a tiny amount of power that has to travel some 22500 miles to the satellite but, I could hear it and was amazed that it was peaking S8 on my SDR receiver.
2.4Ghz Up-Converter connected directly to the antenna bypassing the 2.4Ghz Amplifier
Being excited I put out a CQ call that was soon answered by OH5LK, Jussi in Finland. Jussi gave me a 579 report which I was extremely pleased with. He was of course much stronger at a 599+ at my end. We had a quick QSO and exchanged details without any problems at all. Its really nice to get a QRPp contact without any QSB or QRM.
M0AWS QO-100 1.1m off-set Dish and IceCone Helix antenna ground station
Neil, G7UFO who I chat with regularly in the Matrix Amateur Radio Satellites room has posted a connector out to me so I’m hoping it will arrive on Monday and then I’ll be able to connect the amplifier and hopefully get a few SSB contacts.
UPDATE: I’ve since had 2 SSB contacts via QO-100 using just the 200mW O/P from the up-converter. Both times I got a 3/3 report not brilliant but, perfectly acceptable for the amount of power I’m putting out.
The Weak Signal Propagation Reporting Network (WSPR) known as “Whisper” in the HAM community is a QRP/QRPp beacon mode that is used by many HAMs around the world to see pretty much realtime propagation on the HF bands.
I first started using WSPR when I lived in France some years ago and it proved invaluable for assessing antenna performance and directivity. It’s not a new mode by any means and nowhere near as popular as it used to be as it’s really been superseded by FT4/8 these days that provides the same functionality but, with QSO capability too.
Having an old RaspberryPi hanging around and reading about the WSPR software that’s available for it now I decided to put the Raspi to good use and build a WSPR beacon for the 20m band that I could leave on 24/7.
Having the EFHW Vertical at the end of the garden means that I can connect it directly to the Raspi without the need for an ATU as it’s fully resonant. (It’s actually resonant on 20m and 10m)
I normally run both my RaspberryPi mini computers completely headless and then SSH in to them from my MacBook Pro and decided this was the best way to go with the WSPR beacon too since the WSPR software is command line based and doesn’t require a GUI.
First thing to do was to upgrade the OS from Debian Buster to Bullseye. It’s been a while since I used the Raspi but, it fired up perfectly and connected to the LAN without issue.
After a little time I had the O/S updated to Bullseye and the Raspi was ready for the software build.
The WSPR program comes in source code only so, this means you have to compile it yourself. This isn’t a big job as it comes complete with a makefile.
Using a terminal run the following commands to download and compile the WSPR source code.
So first thing to do is install git.
sudo apt-get install git
Once git is installed I downloaded the software from the git repository.
It only takes a few seconds to download the software which is stored in a new directory called “WsprryPi”.
Before the code can be compiled there’s a small issue with the includes in one of the source code files that needs to be resolved so that the code compiles without error.
cd WsprryPi
vi mailbox.c
Using your favourite command line editor, ‘vi‘ in my case I added the following line into the include statement at the top of the code.
#include <sys/sysmacros.h>
Once added the full include statement looked like this:
Once done, I saved the file ready for compilation.
Compiling the code is easy, just run the make command and sit back and watch all the compiler messages scroll across the screen.
make
Compiling the WSPR source code
Once compiled without errors, I just needed to install the binary.
make install
At this point the software is ready to go.
I quickly soldered up a lead to go from the RaspberryPi GPIO pins to the Coax cable that is connected to the EFHW vertical antenna in the garden and connected it all up ready to test.
RaspberryPi 2 WSPR Beacon connected to EFHW vertical for 20m/10m bands
Pins 7 and 9 on the Raspberry Pi’s GPIO pins are where the signal is output. Pin 9 is the Ground pin, and pin 7 is the Signal pin. Pin 7 goes to the inner of the coax and pin 9 to the ground side of the coax.
The purple cable is the ethernet cable connecting the Raspi to my local LAN so that I can access it remotely via SSH. I’ve powered the Raspi off of the USB port on the wifi access point in the radio shack which is always on.
Once it’s all connected it’s just a case of starting the WSPR program from the command line as user root.
wspr -s -r M0AWS JO02 10 20m > ./wspr.log &
I run the WSPR program as root user so that it has the correct privileges to access the devices to communicate with the GPIO headers, if you want too start it as your normal user then you’d need to use sudo to gain the root privileges.
The command line options I’ve used are as follows:
-s
Check NTP before every transmission to obtain the PPM error of the crystal
-r
Repeatedly, and in order, transmit on all the specified command line freqs.
M0AWS
My Callsign
JO02
My Locator Square
10
The power being used in dBm
> ./wspr.log &
Redirects all output to wspr.log in the current directory and then puts the program into the background so that it is left running when I log out.
Once the program is started you can monitor progress by using tail on the log file.
tail -f ./wspr.log
The output you will see will be something like this.
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:06:01.015
TX ended at: UTC 2022-07-17 16:07:51.638 (110.623 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:08:01.015
TX ended at: UTC 2022-07-17 16:09:51.639 (110.624 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:10:01.015
TX ended at: UTC 2022-07-17 16:11:51.642 (110.627 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:12:01.015
TX ended at: UTC 2022-07-17 16:13:51.639 (110.624 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:14:01.015
TX ended at: UTC 2022-07-17 16:15:51.639 (110.624 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:16:01.014
TX ended at: UTC 2022-07-17 16:17:51.639 (110.624 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
Obtained new ppm value: 4.09996
TX started at: UTC 2022-07-17 16:18:01.015
TX ended at: UTC 2022-07-17 16:19:51.640 (110.624 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:20:01.014
TX ended at: UTC 2022-07-17 16:21:51.638 (110.624 s)
Desired center frequency for WSPR transmission: 14.097100 MHz
Waiting for next WSPR transmission window...
TX started at: UTC 2022-07-17 16:22:01.004
TX ended at: UTC 2022-07-17 16:23:51.628 (110.624 s)
You can pass multiple bands on the command line if you want to hop around bands.
It’s also recommended that you add a low pass filter between the Raspi and coax connection to help suppress any harmonics that may be generated. You can make one easily enough using just a capacitor or there are a number of prebuilt low pass filters specifically made for the GPIO hat on the Raspi online.
With only 10dBm (10mW) output from the RaspberryPi it’s surprising the distances that the signal travels. In no time at all I had reports from all over Europe and as the day progressed reports started coming in from Iceland, the USA and Russia.
Map showing stations that heard M0AWS on WSPR
I used http://wspr.aprsinfo.com WSPR monitoring website to watch progress as the day went on and after 24hrs had been heard by a number of stations over 3000 miles away.
You can also get a more detailed view of reports from the WSPRnet website where you can query the database and create a detailed list of all decodes over a set period of time.
Detailed list of WSPR decodes
Since my EFHW Vertical is resonant on both 20m and 10m I’ll now run it for the next 24hrs on both bands to see what results I get.
Now that I’ve got my new radio shack up and running I decided to give my Icom IC-705 QRP rig an outing and see if I could work a distance of 2000 miles with 1w output.
This is something I’ve been wanting to do for a while but, only being able to sit at the picnic table in the garden or in the summer wasn’t particularly conducive to a long stint on the radio.
Icom IC-705 wirelessly connected to my MacBook Pro
For this challenge I decided to use FT4 or FT8, whichever was active on the bands. This is a great mode for QRP operations and can get a tiny signal through when other more traditional modes fail.
I used both my EFHW vertical for 20m/10m and my EFHW vertical for 30m that can also be tuned on most of the other HF bands too. This gave me most of the HF bands for the challenge.
Initially I worked a lot of stations in the 600-700 mile range, conditions weren’t brilliant and there was a lot of deep QSB.
My first notable distance QSO was with YO4DG near Mangalia Romania at 1383 miles, this equates to 0.72mW/Mile, my lowest mW/Mile achievement up until this point.
Not long afterwards I saw SV8DCY on the WSJTX waterfall, I wasn’t sure if he’d hear me or not but, I gave a call. To my surprise he came back and became the longest distance QSO for a short time. At 1485 Miles to Kalloni Lesvos Island, Greece this equates to a new low of 0.67mW/Mile.
I then went on to work a bunch of stations in the 1000 miles or less range for a while as conditions on the bands were up and down. It’s amazing how many times I got an answer from a station only for them to disappear completely before the QSO was completed.
The next contact of note was with CU3HN in the Azores, 1713 Miles at 0.58mW/Mile, a new lowest mW/Mile record set. it’s amazing how far you can get a signal with such a tiny amount of power.
RV6F in the Stavropol region of Russia was the next big mile marker, 1932 miles at 0.51mW/Mile. It took a number of attempts to get the QSO to complete as we kept losing each other due to the deep QSB that was between us on the 20m band but, with a little patience and persaverance we eventually got the QSO to complete and it was in the log.
At this point I decided to switch over to the 10m band to see if it had opened up to more than just Europe. When I checked earlier there were only European stations being heard, most being well under 1000 miles. Sure enough the band had indeed opened up and I was hearing stations out to the east that were in excess of 2000 miles.
PSKReporter map showing signals heard on the 10m band
After tuning up and listening for a bit my first call was to RL9F in Perm Russia. This was the one that I’d been looking for, 2084 miles at 0.47mW/Mile this was the one that could complete the challenge.
After a few failed attempts due to deep QSB we eventually got a complete QSO in the log finishing the challenge.
2000 miles using 1w is a lot of fun, frustrating at times when you’re being heard by stations on the east coast USA but, none are answering your reply to their CQ calls.
PSKReporter has proven invaluable, being able to see who can hear you makes a big difference when trying to eek out the last mile when using next to no power.
In total 31 stations were worked over a 9 hour period, not huge numbers but, for many an M0AWS call sign isn’t exotic enough to answer and so many of my calls to stations were ignored. Sad really.
You can view all the log entries for the 2000 Mile 1 Watt challenge on my WSJTX Log.
So, what next? Well I guess it has to be 3000 miles or more using just 1w from my trusty Icom IC-705.
Operating a QRP station can often make you feel like you’re not getting out when no one responds to your multiple CQ calls. This was the case the other day when I was trying out my new to me Begali Traveler Light morse key.
I was on the 20m band calling and calling to no avail, the band was open as I could hear other stations just fine so I knew there was traffic on the band. The SWR on my EFHW Vertical was perfect as it always is and so I knew there wasn’t a problem with the coax/antenna combination.
Wanting to know if my signal was indeed going anywhere I decided to make use of the SeeMe facility on the DXCluster that I use. The SeeMe facility effectively allows you to enable spots for your own callsign from the Reverse Beacon Network (RBN).
The SeeMe facility is easily switched on by issuing the set/seeme command on the DXCluster of your choice. Once enabled you will start to see spots for your own callsign from the RBN every time you call CQ using CW.
RBN Spots for M0AWS calling CQ on the 20m Band
As you can see above, I was clearly getting out very well with some great signal reports from a good spread of stations even though I was only using 5w of CW.
You can of course use the RBN website to view the spots if you prefer, it’s not quite as realtime as the DXCluster but, it provides the same information eventually.
M0AWS spots on the RBN Website
The view on the RBN Website is almost the same as that from the DXCluster however, it also shows your CW speed in WPM. I was also surprised to get a spot from the USA at 8dB, that’s a good signal (Just over S2) considering I was only using 5w of power.
I came to the conclusion that no one needed an exotic M0 call for their log and so I went on to my normal search and pounce approach and worked a bunch of stations spread around Europe and Asiatic Russia. My little 5w signal did well and I was able to get through the pileups by using my slide off to the side technique so that my little signal stood out on it’s own. This technique works well when trying to get a QRP signal into a pileup and is used often.
Needless to say, my Begali Traveler Light twin paddle morse key once setup how I like it was superb to use, light to the touch, quick and responsive. Begali make such beautiful morse keys!
Since purchasing my Begali Pearl twin paddle morse key I’ve been looking to get another Begali for my IC-705 portable setup. Going portable means I need a key that isn’t super shiny like the Pearl, something a little more hardy would be ideal.
I was looking to buy the Begali Simplex Basic directly from Begali as it would be ideal for portable operations however, my lovely wife spotted another Begali key for sale on Ebay and pinged the details over to me to take a look at.
Begali Traveler Light
To my surprise the key for sale on Ebay was a Begali Traveler Light, the perfect key for portable use and at a much lower price than new.
I contacted the seller immediately asking a couple of questions about the key and got an immediate response, always a good sign!
It turned out that the key was being sold by Wallace, MM0AMV up in Scotland. Looking at his QRZ page it’s clear he’s an avid CW fan as he has two Begali keys. This was backed up by the conversation we had via Ebay messaging.
In no time at all I had paid the £170.00 including postage and was the owner of my second Begali morse key.
My Begali Traveler Light Morse Key #904
The key was in as new condition as described by Wallace, clearly it had been looked after well.
It didn’t take long for me to get it hooked up to my IC-705 and on air. After a little adjustment of the gap and return tension I had the key setup comfortably for my weird left-handed use.
The key isn’t anywhere as near as heavy as my Begali Pearl key but, it’s plenty heavy enough to stop it moving around when in use. This is of course is helped by the two fold out legs that stabilise the key firmly during use but, protect the paddles solidly when in transit. It’s a great design and a very unique approach to making a fairly light but, solid twin paddle for portable usage.
In the garden with my Begali Traveler Light and IC-705 connected to my EFHW Vertical for 20m
Once folded the key takes very little space in the IC-705 portable case and completes the setup nicely. IC-705 radio, AH-705 remote auto ATU, Begali Traveler Light, tripod and a few interconnect cables, the perfect portable station.
IC-705 Portable station case with plenty of space for future additions
Since purchasing the IC-705 I’ve found that I’ve hardly used my Yaesu FTDX10, which is strange considering the receiver, filtering, DSP and APF combination is considerably better on the FTDX10 than it is on the IC-705. The IC-705 has a much nicer, easier to use user interface and it’s just a lot of fun to use even though it’s only a QRP rig. I can see me having many happy hours on air with this QRP station.
More soon …
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok
