Radio, railways, stuff...

M0RVB

MeshCom

(updated / edited 16/Feb/2025) Having played with Meshtastic a little while ago I came across an amateur radio specific mesh, MeshCom (https://icssw.org/en/meshcom/). Aimed at 70cm operations and with callsigns required I thought this was a better way forward than Meshtastic which, in our area at least is (or was at the time anyway) entirely used for people asking if they can be heard. MeshCom will work on a variety of hardware similar to Meshtastic. I opted for a RAK setup because it has an Ethernet module and I personally prefer this over wifi connectivity. It also gives the possibility of powering the device using PoE which in turn makes it easy to remotely power cycle it. So, the RAK hardware duly arrived via Aliexpress and is easy to assemble, literally plug and play. I got the RAK 4631 RF module, 19007 base board, 13800 Ethernet interface and 19018 PoE module. Firmware is loaded by simply downloading the file from the MeshCom website, althogh it can be quite hard to find. Once that is done, the RAK module is set to appear as a USB disk by quickly clicking the reset button twice. The firmware is dragged across and the RAK resets and loads the firmware up. Nice and easy. It can be configured via the console (e.g.PuTTY, or 'screen' on the Mac) and also via an iPhone app via Bluetooth (BLE). I set it all up with my callsign etc and got a welcome message from a German amateur almost immediately. Nodes can be found via https://meshcom.oevsv.at However, there is an issue with PoE. It doesn't work, although it important to note that this is not a fault of MeshCom. Looking at my Netgear switch it looks like the RAK is trying to negotiate but continually fails. A search on the web found that there is an issue whereby the RAK PoE module is simply not sinking sufficient power and one option is to wire a resistor across its output - I have yet to try this, because there is a further issue... The main issue is that the RAK would freeze at random, sometimes in as little as 5 seconds from boot. This has improved a lot since I installed Meshtastic to ensure the RAK device was ok - it was, that was stable for hours - and reinstalled the firmware after again erasing it all. It managed an hour this way, then froze, but after a reboot it has been running for many hours. I would report this but as yet after 8 months of being a member of the relevant groups.io group I am moderated as a new member and so cannot send messages. Anyway, I also installed the software on a T-Beam and after finding the latest firware (4.34o), which was a struggle in itself, I can send messages from it to the mesh via the RAK device as gateway. There is currently very little MeshCom activity in the UK - 4 nodes I think -…

Continue reading...
M0RVB

Airspy HF+ and RSPdx compared

I now have a second YouLoop (supplied by Moonraker) set up in the loft, this time connected to the RSPdx which itself is connected to the Linux PC. I use SDR++ on the Mac and am getting used to the excellent software (see https://www.sdrpp.org). There are versions specifically for Ubuntu, Windows, MacOS (Intel and Apple silicon) and the Raspberry Pi, plus the source code is available to compile yourself. So I wanted to compare the Airspy HF+ Discovery and the RSPdx. When installed on the Linux PC SDR++ does not see the RSPdx. However, once the relevant API is installed and running it duly appears in the devices list as SDRplay and displays the necesary antenna selection menu. So here they both are, looking from 0 to around 85kHz. First the Mac and Airspy: And the Linux PC and RSPdx: This is about as clean as I managed to get the various settings and it is particularly useful having the same software on each machine. Of course this is a rather arbitrary comparison given the multitude of settings and the fact that they are on two different platforms, plus the two YouLoops are facing in different directions. But it does at least show that, while the Airspy is as good as everyone says the RSPdx is still a useful SDR, plus it has the three software selectable inputs. For me this is handy as I intend to connect the PA0RDT antenna and a Cross Country Wireless loop which I have yet to set up.

Continue reading...
M0RVB

Airspy and MacOS

Just recently I realised that amongst my kit I do not have a scanner other than the baby IC-R2. So I had a look to see what there is and they range from cheap but limited range ones that do not have a continuous coverage to expensive types that are just way over the top for my needs. My interest is limited to having something I can quickly switch on and listen to a few spot frequencies, including amateur radio ones and the local airport ATIS. I also have a bunch of various SDRs but none met the 'quickly switch on' requirement. Time to fiddle then. Other than the various Raspberry Pi systems the only always-on system I have is a Mac Mini. The other two desktops - Linux and Windows - only get turned on when I want to use the FT450D or TS2000X on digimodes or I need more screen real estate for something. So what can I do with the Mac? I already had CubicSDR loaded and I downloaded the Mac version of gqrx. As I use SDR# on Windows and after reading some blog posts I found and downloaded sdrpp. I already have the Airspy HF+ Discovery connected to the Windows box and a RTL-SDR V3 dongle. At this time my thoughts expanded to consider if I use an SDR then I want one with a very good range - so, the Airspy. Anyway, I mixed and matched the software and SDRs to see what fits the best. For CubicSDR and the RTL-SDR dongle I could not find a way to switch it to direct sampling mode so there was nothing below 24MHz. I probably missed a setting. This setup worked fine for VHF FM and airband. I could not get CubicSDR to see the Airspy. For GQRX and the RTL-SDR dongle again I could not find a way to switch to direct sampling. With the Airspy all went well except it was rather difficult to control down at VLF. That's probably just me. For SDRpp the RTL-SDR could be switched to direct sampling but at the end of the day it only works down to 500kHz. With the Airspy it is very like the Windows version which I find easy to use. I did note that when changing frequency a lot it can get confused - for example, I went from airband down to VLF and could not get to 60kHz time signal but it worked fine after restarting the software. A like for like comparison between the Airspy and SDR# on Windows and SDRpp on the Mac showed very similar results, the differences being to do with she speed of the waterfall and there are numerous settings to explore yet. So the Airspy is now connected full time to the Mac and the YouLoop. The real acid test will be to see if it holds up during the next SAQ broadcast later this year but it looks like it will. Above: Windows 10 +…

Continue reading...