After writing my article on how to build an AllStarLink node using a RaspberryPi 3b and SHARI radio device I was asked by a few people if I could possibly automate the process to make it easier for those who aren’t Linux command line junkies like me.

Over the last couple of days in-between doing other things I’ve been writing and testing a BASH shell script that will completely configure a fully working AllStarLink node.

To use the script you must already have your RaspberryPi (preferably a Pi 3b) connected to your LAN with full internet access using the Raspbian based version of the AllStarLink software downloadable from here.

The specific version I use is:

asl-2.0.0-beta.6-kc1kcc-20210324-rpi-armhf

I have tested the BASH script using this specific version of O/S only.

Once your RaspberryPi 3b is up and running, has full internet access and is accessible on your local LAN, using SSH login in as the user ‘repeater‘ using the password ‘allstarlink‘.

It’s important you only use this login to configure the node as this is the user the script is expecting to be run by. You must login via SSH as the SHARI device needs to be connected to the RaspberryPi 3b and you won’t be able to connect a keyboard and mouse at the same time. (If you are using two USB cables for the SHARI device then you can use a keyboard and mouse along with a monitor attached to your RaspberryPi instead of using SSH).

Once logged in as user repeater run the following wget command to download the zipped install script:

wget https://m0aws.co.uk/AllStarLink/AllStarLinkBuild.zip

Once downloaded you need to unzip the program from the zip file and make it executable using the following commands:

unzip ./AllStarLinkBuild.zip
chmod 755 ./install.sh

You are now ready to build your AllStarLink node. Before you run the script make sure you have your node number and node secret to hand. These are obtained from the AllStarLink portal.

Once you’ve got all your node information you can run the script using the following command:

./install.sh

The script will now take you through the full process of updating the operating system as necessary, installing all the required packages and software. It will then reboot the RaspberryPi and you will need to login and run the script a second time using the command above.

On the second run the script will install some python specific software, ask you to enter your callsign, node number and node secret and will then configure your node. The last thing it does is configure the Allmon2 and Supermon Web Admin websites. During this process it will ask you to enter a password twice for the Admin user for the two websites, make sure you make a note of this password as you will need it to login and control your node.

Once the node is configured it will be rebooted and you will then be able to connect to your node using your favourite web browser and the user admin and the password you set above.

To access the Allmon2 web-admin system use the following URL:

http://your-RaspberryPi-IP-Address/allmon2

For those of you who prefer Supermon you an use the following URL:

http://your-RaspberryPi-IP-Address/supermon

I have also pre-populated the Favorites button with a list of nodes that I use often. You can easily change these entries by editing the favorites.ini file in the /var/www/html/supermon directory as user root.

When you first login to your node via your web browser you’ll notice that it says your node isn’t in the database. You can update the database by using the following URL in your web browser:

http://your-RaspberryPi-IP-Address/allmon2/astdb.php

This will force an update of the database and your node information should now be displayed correctly.

Hopefully this will make it much easier for the non Linux people to build an AllStarLink node using a RaspberryPi 3b and a SHARI radio device.

More soon …

Meshtastic devices have really taken off in the UK over the last few months and there is now an established Mesh across a large portion of the UK mainland.

Looking to expand the device capability I stumbled across a really interesting little project that is still in the early stages of development but, is functional and worth trying out.

The TC²-BBS Meshtastic Version is a simple BBS system that runs on a RaspberryPi, Linux PC or virtual machine (VM) and can connect to a Meshtastic device via either serial, USB or TCP/IP. Having my M0AWS-1 Meshtastic node at home connected to Wifi I decided to use a TCP/IP connection to the device from a Linux VM running the Python based TC²-BBS Meshtastic BBS.

Following the instructions on how to deploy the BBS is pretty straight forward and it was up and running in no time at all. With a little editing of the code I soon had the Python based BBS software M0AWS branded and connected to my Meshtastic node-1.

The BBS system is very reminiscent of the old packet BBS systems of a bygone era but, it is ideal for the Meshtastic world as the simple menus and user interface are easily transmitted in seconds via the Mesh using minimal bandwidth.

The BBS is accessible by opening a Direct Message session with the M0AWS-1 node. Sending the letter H to the node will get you the initial help screen showing the menu above and then from there onwards it’s just a matter of selecting the menu item and following the BBS prompts to use the BBS.

The BBS also works across MQTT. I tested it with Dave, G4PPN and it worked perfectly via the Meshtastic MQTT server.

This simple but, effective BBS for the Meshtastic network will add a new message store/forward capability to the Mesh and could prove to be very important to the development of the Meshtastic mesh in the UK and the rest of the world.

More soon …

Ever since my QO-100 ground station has been operational I’ve been using my NodeRed QO-100 Dashboard to control my IC-705 and GQRX SDR software to drive my NooElec SmartSDR receiver. This gives me a full duplex ground station with both transmit and receive VFO’s synchronised.

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.

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.

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.

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.

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.

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.

More soon …

I’ve got a couple of old RaspberryPi computers on the shelf in the shack and so decided it was time for me to put one of them to good use. The first model on the shelf is the oldest and is one of the very first RaspberryPi 1 computers that was released. (It’s the one with the yellow analog video signal output on the board!). This particular model is extremely slow but, I hang onto it just as a reminder of the first SBC in the line.

The second one is a RaspberryPi 2, a quad core machine that is only slightly faster than the first model but, it’s powerful enough to run HAM Clock.

It didn’t take long to install a vanilla Raspbian Desktop O/S and get it configured on the local LAN. I installed a few packages that I like to have available on all my Linux machines and then started on the HAM Clock install.

The first thing I needed to do was install the X11 development library that is required to compile the HAM Clock binary. To do this, open a terminal and enter the command below to install the package.

sudo apt install libx11-dev

You will need to type in your password to obtain root privileges to complete the installation process and then wait for the package to be installed.

The HAM Clock source code is available from the HAM Clock Website under the Download tab in .zip format. Once downloaded unzip the file and change directory into the ESPHamClock folder ready to compile the code.

cd ~/Downloads/ESPHamClock

Once in the ESPHamClock directory you can run a command to get details on how to compile the source code.

make help

This will check your system to see what screen resolutions are available and then list out the options available to you for compiling the code as shown below.

The following targets are available (as appropriate for your system)

    hamclock-800x480          X11 GUI desktop version, AKA hamclock
    hamclock-1600x960         X11 GUI desktop version, larger, AKA hamclock-big
    hamclock-2400x1440        X11 GUI desktop version, larger yet
    hamclock-3200x1920        X11 GUI desktop version, huge

    hamclock-web-800x480      web server only (no display)
    hamclock-web-1600x960     web server only (no display), larger
    hamclock-web-2400x1440    web server only (no display), larger yet
    hamclock-web-3200x1920    web server only (no display), huge

    hamclock-fb0-800x480      RPi stand-alone /dev/fb0, AKA hamclock-fb0-small
    hamclock-fb0-1600x960     RPi stand-alone /dev/fb0, larger, AKA hamclock-fb0
    hamclock-fb0-2400x1440    RPi stand-alone /dev/fb0, larger yet
    hamclock-fb0-3200x1920    RPi stand-alone /dev/fb0, huge

For my system 1600×960 was the best option and so I compiled the code using the command as follows.

make hamclock-1600x960

It’s no surprise that it takes a while to compile the code on such a low powered device. I can’t tell you how long exactly as I went and made a brew and did a few other things whilst it was running but, it took a while!

Once the compilation was complete you then need to install the application to your desktop environment and move the binary to the correct directory.

make install

Once the install is complete there should be an icon on the GUI desktop to start the app. If like mine it didn’t create the icon then you can start the HAM Clock by using the following command in the terminal.

/usr/local/bin/hamclock &

The first time you start the app you’ll need to enter your station information, callsign, location etc and then select the settings you want to use. There are 4 pages of options for configuring the app all of which are described in the user documentation.

Once the configuration is complete the map will populate with the default panels and data. I tailored my panels to show the items of interest to me namely, POTA, SOTA, International Beacon Project and the ISS space station track. I was hoping to be able to display more than one satellite at a time on the map however, the interface only allows for one bird to be tracked at a time.

You can access the HAM Clock from another computer using a web browser pointed at your RaspberryPi on your local LAN using either the IP address or the hostname of the device.

http://<hostname>:8081/live.html

or

http://<ip-address>:8081/live.html

You can also control the HAM Clock remotely via web browser using a set of web commands that are detailed on port 8080 of the device.

http://<hostname or ip-address>:8080/

This is a great addition to any HAM shack especially if, like me you have an old HDTV on the wall of the shack that is crying out to display something useful.

More soon …

Since setting up the new HAM station here in the UK the one band I’ve not yet got back onto is 160m, one of my most favourite bands in the HF spectrum and one that I was addicted to when I live in France (F5VKM).

Having such a small garden here in the UK there is no way I can get any type of guyed vertical for 160m erected and so I needed to come up with some sort of compromise antenna for the band.

Only being interested in the FT4/8 and CW sections of the 160m band I calculated that I could get an inverted-L antenna up that would be reasonably close to resonant. It would require some additional inductance to get the electrical length required and some impedance matching to provide a 50 Ohm impedance to the transceiver.

Measuring the garden I found I could get a 28m horizontal section in place and a 10m vertical section using one of my 10m spiderpoles. This would give me a total of 38m of wire that would get me fairly close to the quarter wave length.

For impedance matching I decided to make a Pi-Network ATU. I’ve made these in the past and found them to be excellent at matching a very wide range of impedances to 50 Ohm.

Since I still had the components of the Pi-Network ATU that I built when I lived in France I decided to reuse them as it saved a lot of work. The inductor was made from some copper tubing I had left over after doing all the plumbing in the house in France and so it got repurposed and formed into a very large inductor. The 2 x capacitors I also built many years ago and fortunately I’d kept locked away as they are very expensive to purchase today and a lot of work to make.

Getting the Inverted-L antenna up was easy enough and I soon had it connected to the Pi-Network ATU. I ran a few radials out around the garden to give it something to tune against and wound a 1:1 choke balun at the end of the coax run to stop any common mode currents that may have appeared on the coax braid.

Connecting my JNCRadio VNA I found that the Inverted-L was naturally resonant at 2.53Mhz, not too far off the 1.84Mhz that I needed. Adding a little extra inductance and capacitance via the ATU I soon had the antenna resonant where I wanted it at the bottom of the 160m band.

With the SWR being <1.5:1 across the CW and FT8 section of the band I was ready to get on 160m for the first time in a long.

Since it’s still summer in the UK I wasn’t expecting to find the band in very good shape but, was pleasantly surprised. Switching the radio on before full sunset I was hearing stations all around Europe with ease. In no time at all I was working stations and getting good reports using just 22w of FT8. FT8 is such a good mode for testing new antennas.

As the sky got darker the distance achieved got greater and over time I was able to work into Russia with the longest distance recorded being 2445 Miles, R9LE in Tyumen Asiatic Russia.

In no time at all I’d worked 32 stations taking my total 160m QSOs from 16 to 48. I can’t wait for the long, dark winter nights to see how well this antenna really performs.

The map above shows the locations of the stations worked on the first evening using the 160m Inverted-L antenna. As the year moves on and we slowly progress into winter it will be fun to start chasing the DX again on the 160m band..

UPDATE 6th October 2023.
Been using the antenna for some time now with over 100 contacts on 160m. Best 160m DX so far is RV0AR in Sosnovoborsk Asiatic Russia, 3453 Miles using just 22w. Pretty impressive for such a low antenna on Top Band.

More soon …

Going through some old photos today I found a few great memories from the past of my old valve radio stations that I’d restored over the years.

These old radios gave me some wonderful moments over the years and a fair few hours of restoration to get them into operational condition. They sounded great on air and I often got comments from other amateur stations about how warm the audio sounded. Some did also mention the drift of the transmitter with temperature changes but, you just have to accept that when using vintage radio equipment.

Above is my old FT101 line up. It consisted of the great FT101E transceiver, a complete standalone solution that was extremely popular in its day. Below it is the FT101 line up made up of the FT101 transmitter, FR101B receiver and matching speaker.

Top right is the lovely Trio TS520S with the matching digital frequency display which is incredibly rare and very sought after today.

These radios gave me a lot of pleasure for many years and I wish I still had them today.

My second Yaesu valve line up took a lot more restoration than the 101 series and was quite challenging at times but, with a lot patience and time spent sourcing parts I got them back to as close to new operational condition as was possible.

The Yaesu 400 series line up consisted of the FLDX400 transmitter, FRDX400 receiver and was finished off with the FL2000B amplifier. These 3 pieces of radio equipment looked beautiful in the flesh and were wonderful to operate. Taking a good 15mins to warm up and become stable you couldn’t rush getting on air. This line up was my favourite by far even though they weren’t as good as the 101 line up.

Above the 400 series is the later FTDX501 transceiver with matching speaker. This was a great radio in its own right but, not as much fun to operate as the 400 line up. To the right of the FTDX501 is the matching Yaesu Microphone for the 400/500 series. This mic is incredibly rare and I had to visit many radio swap rallies to find it, worth the effort though.

Top right you can see my old SWL receiver, the great Drake SW4A. I never had a Drake line up as they are quite rare in the UK but, it certainly would had made a great addition to the station.

Finally this is a photo of two friends of mine, Steve Thomas M1ACB (Current General Manager of the RSGB) on the right and Andy, G6ALB with whom I spent many hours sending and receiving morse with to get our Class A licences. We had a fun day together operating the old radios and taking it in turns to handle the pile ups!

More 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.

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.

Getting back to antenna analysers, I purchased the JNCRadio VNA 3G from MLANDS at £199.96 + postage and have been trying it out on a couple of antennas here at the M0AWS QTH.

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.

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.

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).

I’ve yet to delve into the other functionality of the VNA but, I’m very happy with my initial experience with the device.

More soon …

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.

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.

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.

You can see all the details of my QO-100 contacts in my Online Satellite log.

More soon …

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.

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.

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.

More soon …

I’ve been making a few improvements to my QO-100 Node Red Dashboard whilst waiting for the 2.4Ghz hardware to arrive. I’ve added the ability to split the RX and TX VFOs so that I can tune away from the TX frequency for working split stations or for tuning to slightly off frequency stations. I also added a series of tuning buttons to the top of the GQRX side of the dashboard to enable easy tuning using the trackball connected to my Kubuntu PC. This worked well but, I really missed having a real VFO knob like a conventional radio.

As I had a Griffin Powewrmate USB VFO from a previous SDR radio I added it to the flow as well so that I had a physical VFO knob for the SDR receiver. Details on how I got it working using evtest and a simple BASH script are in the Griffin Powermate article.

The Node Red flow is looking a little busier with the addition of split mode and the Griffin Powermate USB VFO which has really enhanced the useability of the solution. It’s very impressive what can be achieved with Node Red with a little imagination. You really don’t need to be a heavy weight programmer to make things work.

I also put together some code to calculate the S Meter reading from the dBFS data the GQRX SDR software generates. It’s not 100% accurate but, it’s close enough to be useful.

On the IC-705 side of the Dashboard I also now display the 2.4Ghz uplink frequency so that it’s available for logging.

So with the QO-100 Dashboard ready to go live I have now started putting together the 2.4Ghz transmit path of the ground station. I have the 2.4Ghz transverter and matching 12w amplifier from DXPatrol, the IceCone Helix 2.4Ghz antenna from Nolle Engineering, some LMR-400-UF and connectors from Barenco and an appropriate water proof enclosure from Screwfix to fit all the kit into however, I’m now being held up by one simple little SMA male to SMA male connector that I need to connect the transverter and amp together.

The SMA connector has been ordered but, is taking a month of Sundays to arrive! Hopefully it’ll arrive soon and I’ll finally get on the QO-100 satellite and start enjoying the fun.

More soon …