Radio and rails...

I now have a Raspberry Pi set up on one of the four monitors in the shack. The original layout was two screens at the top on Linux, then bottom left on Windows and bottom right - central to where I sit on the Mac as the main screen. But that layout had two major issues... I use a program called Barrier to basically act as a KVM switch for the three systems with the Mac as server. That way the Mac mouse and keyboard controls any of the systems, although it can be awkward sometimes where Windows expects keys which Apple doesn't have. But Barrier does not understand dual monitors and so moving the mouse up from the Mac got to the Linux box fine, but moving it down from the left hand screen would not get to Windows as the program does not see it being physically there. I could live with that, except for issue two... The main issue was with the Linux screens being at the top and thus making me sit back or crank my neck upwards, not a good position. So... I got to realising that although I use both screens on the Linux…

Another new toy, a Quansheng UK-K5(8). Size-wise it's taller and heavier than the Baofeng UV5R and has a nicer display. The reason I got this, apart from the price is there is firmware available to enable a spectrum display among other things. I've loaded this version: https://github.com/egzumer/uv-k5-firmware-custom/wiki. Loading was simple enough. There have been mentions that one needs to insert the programming cable very firmly but I found that my aftermarket Baofeng USB cable went in quite easily with a click. Once I had remembered you need to turn the radio on in program mode the firmware went in via the Edge browser in just a few seconds. Other than that I have yet to use it on air and it has not yet been near a spectrum analyser so no idea how good or bad it is RF wise. There's plenty of information out there already anyway. For me, like the UV5R it's a handy little radio that won't hurt too much if lost or damaged, but it is the available firmware that seals the deal.

After having ditched Meshtastic, for now at least, I had a fiddle with two of the LoRa modules with a view to repurposing them. And there they are. The first is a LoRa APRS r/o iGate, listening on 439.9125MHz, and the second is a receiver for radiosondes listening around 400MHz. Nestled under a 70cm ground plane in the shack is, of course a good way to ensure nothing is ever received unless it is very close! However, it is destined for greater things... although at the end of the day it's just me fiddling. The LoRa APRS map is at https://lora.ham-radio-op.net/ The radiosonde one stands a better chance of actually receiving something, especially as it is currently connected to the 70cm big wheel antenna in the loft. See https://sondehub.org/ The plan is to connect these two along with the module running TinyGS to a common antenna currently in the loft. They will be connected using a Crosscountry Wireless multicoupler which is due to arrive in a day or so.

For me, and this is in no way intended to persuade people not to dabble, Meshtastic was the usual 'new shiny' that I like to fiddle with, but it was just that. A bit of radio fun for little outlay using devices I can redeploy. In our wider area it seems to have snowballed and become rather congested. While I can see the point, I have many other radio bits and bobs to play with and having yet two more antennas in the loft was rather overdoing things. I had to seriously think exactly what I had used it for and it came down to occasionally saying 'good morning', answering when people ask if anyone is receiving them, and... well, I am struggling to find anything else. Of course I stress that is what I had used it for, not taking away from what others are doing. It is a neat idea. So both nodes have been switched off.

Both my 868MHz and 433MHz nodes are being odd today. I had been looking into the data that arrives when '--noproto' is sent to the node and, typically there is a fairly constant stream of data. But today, despite both being power cycled there is no data at all. Odd, because when I ask the 868Mhz node for its nodelist it is being updated. Maybe it's something in the new firmware but for now I've been fiddling enough and it's time to take a step back. I have not had any successful traceroutes today, I responded to a couple of requests and got no reply. It's made worse by the fact that, having moved the nodes in the loft they are now out of BLE range. Both are connected to a Raspberry Pi via USB so I can access the nodes that way but for client use I use my mobile node assuming that the node in the loft will relay everything - maybe not. And for 433MHz I only have the one node anyway. Mind you, it is raining and I suspect that is making a fairly decent shield for 868MHz, and I have yet to see any activity…