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.
M0AWS Meshtastic BBS Main Menu accessible on M0AWS-1 node.
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.
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.
M0AWS – HAM Clock running on RaspberryPi Computer
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/
M0AWS – HAM Clock remote command set
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.
I’ve been active on QO-100 for a few days now and I have to admit that I’m really pleased with the way the ground station is performing. I’m getting a good strong, quality signal into the satellite along with excellent audio reports from my Icom IC-705 and the standard fist mic.
I’m very pleased with the performance of the NooElec v5 SDR receiver that I’m now using in place of the Funcube Dongle Pro+ SDR receiver. Being able to see the entire bandwidth of the satellite transponder on the waterfall in the GQRX SDR software is a huge plus too.
M0AWS QO-100 Satellite Log map showing contacts as of 23/06/23
As can be seen on the map of contacts above, I’ve worked some interesting stations on some of the small islands in the Atlantic and Indian Oceans. The signals from these stations are incredibly strong on the satellite and an easy armchair copy.
DX of note are ZD7GWM on St. Helena Island in the South Atlantic Ocean, PP2RON and PY2WDX in Brazil, 8Q7QC on Naifaru Island in the Maldives, VU2DPN in Chennai India, 5H3SE/P in Tanzania Africa and 3B8BBI/P in Mauritius.
There are many EU stations on the satellite too and quite a few regular nets of German and French stations. I’ve not plucked up the courage to call into the nets yet, perhaps in the future.
There are a lot of very experienced satellite operators on QO-100 with a wealth of information to share. I’ve learnt a lot just from chatting with people with some conversations lasting well over 30mins, a rarity on the HAM bands today.
We also had our first Matrix QO-100 Net this week, an enjoyable hour of chat about all things radio and more. We have a growing community of Amateur Radio enthusiasts from around the world on the Matrix Chat Network with a broad spectrum of interests. If you fancy joining a dynamic community of radio enthusiasts then just click the link to download a chat client and join group.
Over the years I’ve built many multi band vertical HF antennas including multi-element quarter wave verticals like the DXCommander configuration, multiple end fed vertical dipoles all on the same pole and a host of other configurations. As with all multi band antennas there’s always a compromise, on some bands it performs well and on others it doesn’t, it’s the nature of the beast.
For some time now I’ve been using a multi band vertical antenna that has over the last year performed incredibly well on all bands from 80m to 10m. Don’t get me wrong, it’s not perfect however, it has out performed every other multi band HF vertical I’ve tried to date even though it’s by far the simplest antenna design and according to the antenna modelling software I have it shouldn’t be as good as it is.
So what is this magical multi band HF vertical I speak of? Well it’s nothing more than a piece of wire 13.4m long taped up a 12.4m vertical Spiderpole with 1m of wire tucked down into the top of the Spiderpole.
Obviously this is not going to be resonant on any band without some sort of impedance matching circuit at the bottom of the wire. Originally this antenna was my end fed half wave vertical antenna for the 30m band that was fed via a 49:1 Unun. This antenna worked incredibly well on the 30m band allowing me to work DX globally with ease but, it was a single band antenna and I wanted a multi band solution.
I decided to remove the 49:1 Unun and replace it with a home brew LC circuit made up of a coil made from 5mm copper tubing and a large air spaced variable capacitor I had laying around from an old ATU project I built many moons ago.
This simple LC arrangement at the bottom of the wire worked incredibly well and tuned the wire from 80m to 10m with a perfect SWR on each band using nothing more than a ground rod and 4 x 12m radials. Performance was surprisingly good on all bands 80-10m giving me the ability to get some DX stations that I’ve never been able to hit before. The only drawback to this solution was the fact that I had to go out and manually tune the antenna every time I wanted to change band. Not so much of a problem in the summer but, in the winter in the pouring rain and howling wind it’s no fun at all. (I resolve this issue further down in the article!)
Multi Band Vertical HF Antenna using a 12.4m Heavy duty Spiderpole at the end of the garden
Performance on the HF bands is incredibly impressive with this antenna. Modelling it on EzNEC software it shouldn’t be that great on bands above 20m however, it seems to defy the modelling software as it performs amazingly well on 17m, 15m and 12m, better than any other vertical antenna I’ve made for those bands. How this can be I do not know, normally my antenna builds match closely what the modelling software shows but, in this instance it doesn’t and I’ve really no idea why.
Multi Band Vertical HF Antenna showing loop at top and wire tucked down into pole
Always wanting to put things into perspective here’s some details of the contacts I’ve made on each band showing how well this antenna has performed over the last year or so.
Firstly the 80m band, I’ve not used this band much over the winter months as I’ve got into the higher bands however, the map below shows all the stations worked on 80m using this antenna.
Stations worked on the 80m band from the M0AWS QTH
There are 51 contacts in total, not a big number by any means however, there are some good distances made with contacts into North America, South America and Indonesia. I’m sure I could had done better if I’d spent more time on this band, something to aim for next winter perhaps.
Next is the 60m band, a band I really like and have enjoyed over the winter months. The antenna performs incredibly well on this band even though we have very limited access to 60m here in the UK. With 288 contacts in the log with a good spread of distances I’m really pleased with how this antenna performs on this band.
Stations worked on the 60m band from the M0AWS QTH
Moving up in frequency the 40m band is the next one on the list, this is a great band and one that I’ve loved for many years. I’ve spent countless hours on CW on this band in the past and worked some great DX. The performance of this antenna on the 40m band is excellent, if I can hear the DX normally I can work them regardless of where in the world they are located. With 226 contacts in the log spread globally over the winter here in the northern hemisphere I have no complaints about performance of this antenna on the 40m band.
Stations worked on the 40m band from the M0AWS QTH
Moving up onto the 30m band I have to admit this is probably my favourite band of all. I’ve spent so many hours on CW working some of the best fists I have ever heard on the air I’ve grown to love this band not just for the DX available but, for the quality of operator found on this narrow piece of the RF spectrum. Needless to say since the antenna is a half wave on the 30m band performance is stunning, out performing any other 30m band antenna I have ever made. It’s even better than the 30m Delta Loop antenna that I built and used when I lived in France.
With 467 contacts in the log on the 30m band you can tell this is my goto band and one that offers access to some of the best DX in the world.
Stations worked on the 30m band from the M0AWS QTH
The 20m band is a band that I never really used until I moved back to the UK from France. Living in France I had acres of land and so I was very much into the low bands, 160m to 30m and never ventured above this part of the spectrum. Now living back in the U.K. with a typical U.K. sized garden the low bands are much more difficult to get onto and so my interests have moved up in frequency somewhat.
Getting onto the 20m band I was amazed at how easy it is to work DX stations compared to the low bands, it’s simply a case of if you can hear them you can work them, there’s no real challenge to be honest. Because of this the band is always super busy with people shouting over the top of each other to get the DX. Not to be put off, I’ve made a surprising 412 contacts on 20m covering the globe. This antenna works incredibly well on this band and you really don’t need anything else to work DX on 20m.
Stations worked on the 20m band from the M0AWS QTH
Next is the 17m band, one of the WARC bands that I’ve never really ventured onto until now. I have to admit I really like this band, when it’s open it’s normally open to the world all at the same time. With an almost undetectable background noise level you can hear the faintest of signal on this band. This is one of the bands that according to the EzNEC modelling software this antenna shouldn’t be any good on but, I have to say that it’s performance is beyond anything I ever imagined. I’ve worked my longest distance yet on this band and with this antenna, ZL4AS at 11776 miles, a distance I haven’t achieved yet on any other band. The 17m band really is a great band, I’d actually say it’s better than the 20m band even though there is considerably less spectrum available. With 220 contacts in the log it’s been a fun band to use.
Stations worked on the 17m band from the M0AWS QTH
Continuing the theme of the WARC bands, the 15m band is another one that I’ve only discovered in the last 12 months. It’s only now that I realise what I’ve missed out on due to my addiction to the low bands for so many years.
I’ve only made 76 contacts on the 15m band, not a lot at all really. This is mainly due to the fact that I get easily side tracked by the 17m and 30m bands most of the time and the radio VFO never gets as far as 21Mhz. Performance of the antenna is good on 15m, I would say not as good as on the 17m band but, it’s no slouch by any means.
As you can see on the map below, I may of only made 76 contacts on the 15m band but, they are spread right across the world proving that this antenna’s DX-ability on 21Mhz really is rather good.
Stations worked on the 15m band from the M0AWS QTH
Finally we arrive at the top of the WARC bands, the little 12m band. Once again this band is very much like the 17m band, super low background noise level, when it’s open you can work huge distances with very little power but, often there is quite deep QSB that can make getting that elusive DX a bit more challenging.
With only 66 contacts in the log once again I’ve not spent a huge amount of time on this band but, it hasn’t disappointed. With global coverage from this antenna on 12m once again I am astounded at how well it works. With software modelling saying it should be terrible on 24.9Mhz with nothing but super high angle radiation, it really shouldn’t be a good antenna for DXing on this upper WARC band but, it is and I have no idea as to why!
Stations worked on the 12m band from the M0AWS QTH
Finally we arrive at the 10m band, another band that I have never got into even though many refer to it as the magic band. This is the band that I’ve made the fewest contacts on, not because the antenna doesn’t work at the dizzy heights of 28Mhz but, because I hardly ever get the VFO dial past the lower bands due to the level of DX available. I really should make more effort to get the best out of the 10m band, especially now the summer is coming.
With a measly 19 contacts in the log I should be ashamed of myself for not doing more on this band as it is very often open and busy with traffic. Since I’ve not really used the antenna that much on the 10m band it’s hard to say how well it performs however, I have had contacts into North and South America and so it shows potential.
Stations worked on the 10m band from the M0AWS QTH
As you can see, the performance of this antenna is self evident from the log entries, it works superbly even though the modelling software says it shouldn’t above 14Mhz. This is now my main antenna here in the U.K. and I’ve only made one change to the initial setup and that is to add a CG3000 remote auto ATU to replace the home-brew LC tuning circuit.
CG3000 Remote Auto ATU housed in a plastic box
With the CG3000 auto ATU in place I no longer have to venture out into the cold, wet garden in the winter months to change band, it’s just a case of sending a continuous 10w signal into it and leaving it to tune in less than 2 seconds. The CG3000 is a Pi Network ATU so it handles both high and low impedance loads with ease. A Pi Network ATU is one of the best you can have, I’ve made my own in the past and had excellent results.
So in summary, 13.4m of wire vertically up a 12.4m pole with 4 x 12m radials, a ground rod and a CG3000 Auto ATU will give any HAM station the ability to work DX on all bands from 80m to 10m without ever having to leave the shack to tune it.
Since I got the CG3000 off of Ebay for a bargain £170 and the 12m heavy duty Spiderpole for under £100 the total cost of the antenna is considerably less than many commercial offerings available and yet performs as well if not better.
If you want to get this antenna onto the 160m band then you just need to add a small coil into the mix at the bottom of the wire to increase the inductance in circuit. The CG3000 will then happily tune the entire 160m band. It’s best to remove this coil though for all the other bands otherwise performance is reduced.
Please be aware that the performance of this antenna will not be anywhere near as good if you use the ATU in your radio at the end of a coax run. This is because the coax becomes part of the antenna and the radiation pattern is all but destroyed. You will be extremely disappointed if you use the antenna in this fashion. The ATU must be at the end of the wire and connected directly to ground and the radials to get the performance that I have experienced.
Finally, if you have an Icom IC-705 and AH-705 remote auto ATU you can use the AH-705 ATU in place of the CG3000, you will get the same results as I have with the CG3000.
I have used my AH-705/IC-705 combo quite a few times with this antenna with excellent results although, the big antenna can sometimes result in the receiver of the IC-705 getting overloaded especially on the lower bands. This is easily resolved by reducing the RF Gain on the radio.
Following on from my initial article on plotting realtime WSJT-X decodes on a Node Red map I’ve made a few enhancements to the flow so that it includes even more data then before.
The additions to the flow now enables collection of status information from WSJT-X so that the flow is able to capture the frequency that the radio is tuned to and also the mode that WSJT-X set to. Neither of these two bits of data are in the decode message payload and so a separate mini-flow has to be created to collect the data from the status payload along side the other main flow.
Node Red flow showing additional sub flow in the top left corner of the flow editor screen
Since the status information needs to be available to all other flows I used flow variables to store the status information in so that it can be addressed directly from any of the other flows in the Node Red app.
If you’d like to use the flow in your radio room then I have put a download link below for a file that you can import into Node Red and build the flow in an instant.
Following on from my previous article on Enhancing Digital modes with Node Red I’ve now got to a point where I have realtime decode information from the WSJT-X digital application being plotted on a Node Redworld map not just for CQ calls but, for stations in conversation too.
The flow has become somewhat more complex than it was originally as more and more functionality has been added. I have deliberately split out the flow process into more nodes than are really necessary so that the flow is easier to understand. Anyone from a programming background like myself will soon realise that a lot of the nodes could actually be combined into one big node however, the overall flow process wouldn’t be so easy to understand for the Node Red newcomer and would possibly put people off from trying it out.
Current WSJT-X Node Red flow
Above is a screenshot of the flow as it currently stands. It’s pretty easy to understand what is happening in the flow due to the fact that the processes are broken out into small, easy to digest blocks.
From the top down we connect to WSJT-X via UDP port 2237 and listen for the data stream. As the data is received it’s passed directly into the WSJT-X-Decode node that converts the information into a Node Red compatible format. The data is then filtered with only the information required being passed onto the next node. There are two outputs from the filter node as we require two different streams of information, namely “CQ” and “TX1” data. All the rest of the data from WSJT-X is ignored as it’s not required at this time.
The “Get freq & SNR + Others” node builds a decode message payload with all the correct data, in the right format ready to be passed on along the flow. This node also sets a number of parameters required by the map node to be able to control the display of the data.
The next node along is “Set msg.payload”, this brings together all the necessary data into a single message payload that is then worked on by all the nodes further along the flow.
The next 3 nodes perform the simple task of moving some of the data into the objects defined by the world map node, if the data isn’t moved into these specific objects the map will not plot anything.
Now we get onto the slightly more difficult bit that might put off those who aren’t from a programming background. The next 7 nodes are all javascript functions which I have created to perform tasks that cannot be done via the standard Node Red pallet.
At this point it’s worth noting that I’m not a javascript programmer, I’ve used Python, Rust, Go, C and many other languages during my 40 plus year career but, javascript has never been one of them. I’m sure any seasoned javascript programmer will most likely raise an eyebrow at my attempt at javascript programming but, you need to remember that I’m doing this in my retirement and my enthusiasm for learning yet another programming language has wained somewhat!
So, getting back to the flow, each javascript function does just one task each of which is as follows:
Set rx_time – Sets the time the data was received/processed
Remove RR73 in tx1 – Remove decodes where RR73 is in TX1 instead of a valid callsign
Set Dynamic Icon Colour – Sets the icon colour depending on what type of call is decoded
Maidenhead to LON/LAT – Converts Maidenhead locator codes into LAT/LON Coordinates
Calc Distance – Calculates the distance between “My QTH” and the DX station
Calc Bearing – Calculates the bearing/beam heading to the DX Station from “My QTH”
Generate Search URLs – Generates the URLs for QRZ and my own online log lookups
Editing the Calc Distance function with debug info in the far right panel
Once all the functions have run the resultant data set is forwarded on to the WSJT-X Stations Map node where it is plotted real time on a world map.
To view the map point your web browser at your PC running Node Red as follows:
http://radiopc.your.domain:1880/worldmap/
Or if you haven’t got a DNS setup at home then just use the IP Address of the PC instead:
http://192.168.100.10:1880/worldmap/
Don’t forget that for all of this to work you must configure WSJT-X to send data via UDP on port 2237 otherwise the flow won’t be able to connect and listen for the decode data.
You may have noticed that there are 3 other nodes that I haven’t mentioned yet. The two green greyed out nodes are Debug nodes that can be enabled when required to help see what is going on in the flow. These debug nodes will display data in the debug panel on the right of the flow editor screen when they are enabled, they are extremely useful for debugging!
The third is the blue My QTH node, this contains data pertaining to my QTH that is plotted on the map using an orange icon. You can easily edit this node to point to your QTH instead.
WSJT-X Node Red map showing orange icon denoting my QTH
Once the flow is deployed you’ll be surprised how quickly the data starts to be plotted on the map. Stations calling “CQ” are shown by Green icons and stations that are in a QSO with another station are denoted by the Red icons.
Each icon is clickable and will present all the information collected by WSJT-X for each station viewed.
WSJT-X Node Red World Map showing FT8 stations realtime on the 12m Band
The popup also has two clickable entries, one will take you to the qrz.com page for the station being viewed and the other will search my logs to see if I have worked that station already and if so it will open a new tab showing the information.
Node Red Function Editor showing the Generate Search URLs function
You can edit the “Generate Search URLs” node so that it points to your online logs search engine so that you can view your own log data instead of mine.
Below is a close up of the popups that are displayed when each icon on the map is clicked. The popups show the information collected from WSJT-X for each station plotted on the map.
Left – Green “CQ” Popup and Right – Red “TX1” in QSO popup
If you fancy trying this out for yourself but, don’t fancy creating all the nodes in the flow manually then I have made an export of the flow available for download. All you have to do is download the file, unzip it and then import it to Node Red and you’ll have everything built ready to play with.
For a couple of weeks now I’ve been playing with Node Red to add functionality to my digital mode applications.
To get to know how it all works I initially used Node Red to create a series of dash boards for my servers and virtual machines to show realtime information on CPU temperature, CPU load, memory usage and storage etc.
Node Red Flow to collect information from a virtual machine (VM)
This worked very well and I was soon able to generate the information I needed in a palatable format. This was a great way to get to know Node Red flow building and introduced me to using gauge and graph nodes in flows.
The resultant Node Red Dashboard for one of my Virtual Machines
Once I had mastered creating dashboards for servers/virtual machines (VMs) I then started to investigate using Node Red to plot data from WSJT-X on a map.
I currently use the PSKReporter website to see stations that I hear on a map as WSJT-X sends the data to the site automatically however, this information is always 5mins or more old. For some time I’ve been wanting to see the information realtime as it is received and so I was hoping to be able to achieve this via Node Red.
Node Red has nodes available for a multitude of applications all easily installed via the Manage Palette menu in the flow editor.
I installed the WSJT-X Decode and World-Map nodes and set about building a flow to capture the data and plot it on a world map.
Building a Node Red Flow to decode WSJT-X data and plot it on a World Map
Putting the building blocks of the flow together is fairly straight forward and easily achieved using the excellent flow editor built into Node Red.
I configured WSJT-X to make the decode data available via UDP on port 2237 and then started the flow by creating a UDP node that connects to WSJT-X using the same port. The data immediately started flowing and I could see the information via a debug node.
I can’t stress enough how useful debug nodes are in Node Red. You can add debug nodes onto any output on any other node to capture the data as it flows. This gives you the ability to check what you’re getting is what you expected and also to see the format the data is in. The debug data is displayed in the debug panel on the right of the flow editor in realtime and gives you a great view of what is going on in your flow.
I decided to start with capturing the data for stations calling CQ as this was easily identifiable in the JSON object coming out from WSJT-X.
Passing the output from the WSJT-X-Decode node into a switch node I added a rule that filtered out data containing “type: “cq” and passed it onto the next switch node that created a payload consisting of the station callsign, maidenhead grid square and type so that it could be passed onto the next node for processing.
The next node in the flow is a function, this is where it gets a bit tricky. To be able to plot data on the map we need the Lat/Lon coordinates of the station making the CQ call. Since WSJT-X uses maidenhead locator data I needed to convert this to Lat/Lon coordinates before passing the data to the map node to be plotted.
Since Node Red is written in Java all the functions have to be written in javascript. The problem here is that I am not a javascript programmer and so this meant I’d need to learn yet another programming language. Unfortunately Node Red doesn’t allow functions to be written in C, Rust, Go or Python, all languages that I know well and after retiring from over 40 years in the UNIX/Linux/IT world my enthusiasm for learning yet another programming language has wained somewhat.
Being so close to having a working solution I pressed on and after much head scratching I finally put together some javascript that converts the maidenhead locator information in to good old fashioned Lat/Lon coordinates. I’m sure a seasoned Javascript developer wouldn’t be impressed with my code but, it works and does what I need and so I’m happy with it for the time being.
WSJT-X FT8 stations calling CQ on the 60m Band plotted on a Node Red World Map
Once I had the location information converted it was just a matter of passing the data to the world map node in the correct format for it to be plotted realtime.
As you can see on the screenshot of the map above, it worked extremely well with stations popping up as they were decoded by WSJT-X.
I now need to refine the data sent to the map so that it shows the frequency the station is calling on, the time they made the CQ call and the mode (FT8/FT4 etc) being used.. I would also like to add the distance from my QTH to the station calling CQ to round the information off however, this will mean writing another javascript function which, I’m not sure I want to dive into just yet.
I also need to add into the mix stations that aren’t calling CQ but, who’s callsign and grid square are passed on from WSJT-X. This will mean I will then be able to add to the map those stations that are actively working other stations and maybe I might even be able to show a line between the two stations that are in QSO.
This has been a fun but, steep learning curve however, it will certainly add some great functionality into my radio room and enhance my radio HAM addiction even further.
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
