Amateur radio ⁽²⁴⁹⁾

I've been doing the '12 days of QRZ' again this year and managed to get the award yesterday - I started two day late as I forgot about the award. So far I had endorsements for 80m, 40m, 30m and 20m, and today I added 17m and 10m. A couple of log entries were the same stations over two or three days, I'm not actually stalking you! It's fun and frustrating at the same time, logging, sending to QRZ and LoTW and hoping for a match. A few 60m QSOs from yesterday were from stations that had previously logged to LoTW and now are not... but never mind. Just one more day for 60m and 15m to get 12 days in each and the associated endorsements. The award updates automatically once you get sufficient days and go to the awards page again, Now then, 12m. I did not realise last year, nor this year that it is included, as are all bands. You need to go to the bottom of the awards check page and click on 'all bands'. So this year I added 3 days (so far) of 12m, 9 to go. I've never heard anything on 160m, the…

Well. Further to my previous post where all hope seemed to have gone out of the window I finally made progress today, but not the way I set out to. First off, I pulled a Raspberry Pi 4 from another project and sat the CaribouLite HAT on it. Next was a fresh installation of DragonOS. But this time it did open the ssh port - I've no idea why it did not before and note I am being unscientific here as I changed the Pi, but I am not going backwards. Then, time for install.sh... All seemed to go well but the software failed to compile completely. Searching on the errors I added #include to two source files, cariboulite/software/libcariboulite/src/CaribouLiteCpp.cpp and cariboulite/software/libcariboulite/src/CaribouLite.hpp. Stripping out all the 'apt's and 'depmod' from install.sh and running it again and the software compilation completed! I had already added and commented out the necessary lines in /boot/firmware/config.txt so a reboot was all that was needed to kick it into life. The driver was loaded - lsmod|smi showed this and also /proc/device-tree/hat now exists, both precursors to success according to the notes and YouTube videos. Running sudo SoapySDRUtils --find showed the card, and, finally (!), running SoapySDRServer…

I came across this via a post someone made somewhere - actually it might have been an email on a group. Anyway, with a tx/rx range top to 6GHz I thought, why not? It arrived quite quickly from Crowd Supply via Mouser with Crowd Supply charging the VAT but no other taxes on arrival. I duly mounted it on a spare Raspberry Pi 3B with a fresh Bookworm 64 bit OS and followed the installation instructions at https://github.com/cariboulabs/cariboulite but I always got various errors and never got to a working system. The errors were mainly surrounding the SMI driver and the kernel headers. There seemed no way round this one, and thus no working system. Following on from another complaint I downloaded and installed DragonOS, a 64 bit variant with lots of SDR utilities built in. Once installed, although the developer stated that ssh is available from first boot and does not need the usual empty ssh file it is not - the system does not open port 22 but does open the vnc port so I then had to find out which of my desktop systems has a vnc viewer as I never use it. When I found one…

My second NinoTNC is built. The parts came today from Mouser in a huge box. I need to adjust the case a little to make it fit nicely but now I have this one I can go mobile and see how access to GB7RVB is. So far, no-one has connected (and yes, the antenna is still in the loft!) I did find a TNC program for the Mac called KISSet which works fine once I remembered to put my callsign in! I wondered why it was sending data and GB7RVB's TNC was receiving - no callsign. Twit. It worked fine after that.

Here is the setup for GB7RVB, not much to see really. The radio is a Tait TM8110 which has been configured according to information on the OARC wiki. The NinoTNC is next to it, both currently sitting on top of my Portsdown. Above, and annoyingly not square because I need to move some cables, is the Pi 4 which is PoE powered from a Netgear switch.