N3BKV’s Ham Radio Hacks

  Have you ever wondered where the plane or helicopter overhead is coming from, where it is going or who operates it? I found myself logging into my SkyAware monitor several times a week to look up that information. The problem was that it only showed what was overhead at that moment and logging in took a minute or two each time. I knew there had to be a better way to see this information quickly and to keep a historical record of all the aircraft traffic I had observed. One of the fun side effects of running a local ADS-B receiver with dump1090-fa on a Pi with an RTL-SDR dongle, is that you end up with a constant stream of aircraft telemetry sitting on your Pi. aircraft.json updates every second or two with hex codes, positions, altitudes, speeds and it's all there waiting to be analyzed and not just sent to Flightaware. Recently, I learned about JetClock which is a slick, commercial desk clock that shows you the aircraft passing overhead with airline, route, photos and all kinds ...

  There is a special kind of magic in a blinking cursor. Before social networks, web forums, Slack, Discord and group chats, there were bulletin board systems. You dialed in, waited for CONNECT, logged in with a handle, read the bulletins, checked your private mail, posted a message and logged off with the unmistakable finality of: NO CARRIER For radio amateurs, that world never really disappeared. Packet BBS systems, club bulletin boards, mailbox nodes, Winlink-style messaging, APRS bulletins, repeater status pages and remote station dashboards all come from the same basic idea: low-bandwidth, text-first, asynchronous communication. That is the spirit behind CBBS_PI — a vintage CBBS-style BBS emulator built in Python for a modern Raspberry Pi, Mac, Linux box or Docker host. It is part nostalgia project and part platform for experimentation. What It Is CBBS_PI is a text-mode bulletin board system that recreates the feel of early BBS systems. It supports local terminal access, Telne...

  Bridging WaveNode Power Meter Data into Thetis One of the fun things about modern ham radio is that so much of the station is now software-defined it's not just the radio, but the amplifiers, power meters, rotators, dashboards, remote control systems and logging tools around it. That also creates a familiar problem: all the pieces know useful things, but they do not always speak the same language. This project started from a simple question: Can Thetis display WaveNode RF power and SWR data the same way some stations use TelePost LP-100A meter data? The short answer is: maybe and this project is an experimental bridge to help test exactly that. The Problem Thetis already has a Multi Meter I/O feature that can accept external meter data. Many hams have used this with the TelePost LP-100A, where meter information is sent into Thetis over the network. WaveNode systems, on the other hand, can publish useful station telemetry such as: Forward power Reflected power SWR In my station, ...

Centralized Field Day logging is one of those things that looks simple until the network hiccups, the generator burps, Windows decides it is “helping,” or one laptop thinks it is 2019 and another thinks it is next Tuesday. My club was looking for an easy-to-use solution for FD 2026 that would tie all the logging computers in our main tent together to simplify log submission and track our total progress during the event. But past attempts with a logging server brought to light many issues, especially individual station computers locking up when there were server or network issues. The goal is simple: all operators log to one reliable N3FJP server with consistent local IPs and accurate time without internet access. Here is a practical way to build a central N3FJP Field Day logging server that does not depend on the internet: One Windows server laptop or mini-PC that runs the N3FJP master FD log. The server also hands out local IP addresses using a local DHCP Server for Windows. All Field...