Balloon Launch with APRS & WSPR Tracker

On May 5th, I had the opportunity to participate as part of a team that launched and tracked two high-altitude balloons. This was part of an educational outreach with Savannah River Academy, a school in my community. Members from my club, the Amateur Radio Club of Columbia County (ARCCC), and two meteorologists from the National Weather Service assisted the school with the balloon launch. This was part of a series of activities with the school to teach students about radio, weather and space, in preparation for a ham radio contact later this year with an astronaut aboard the International Space Station! Savannah River Academy was one of only a handful of schools in the U.S. selected to contact the ISS through the Amateur Radio on the International Space Station (ARISS) program.

The balloon launches were covered by two local TV stations and the local newspaper:
Columbia County students launch weather balloon
Students at Savannah River Academy participate in weather balloon launch
Sky is NOT the limit: Radio club partners with Grovetown students for weather balloon launch
Weather balloon camera captures breathtaking views above CSRA

The first balloon, which carried a payload with a SPOT Trace GPS tracker and a GoPro camera, was designed climb to an altitude of 70,000 – 100, 000 feet before bursting and falling back to earth. A parachute was attached to the payload so it could return to ground intact for retrieval by a chase crew. We expected the payload to land approximately 50 miles east of the launch site, but the balloon traveled much farther than anticipated. The chase teams scrambled and the payload was successfully retrieved approximately 150 miles from the launch site. The camera captured some amazing images while the balloon was in the stratosphere. Some of the best pictures are featured in the linked news stories.

Photo captured from the high altitude weather balloon shortly after launch. This camera captured lots of amazing images during this balloon flight.
One of the many spectacular views captures by the camera on the high-altitude weather balloon.

This post focuses primarily on the second “pico” balloon, which carried only a LightAPRS-W APRS and WSPR tracker as the payload, and was designed to reach an altitude of approximately 50,000 – 60,000 feet and achieve neutral buoyancy to travel for a much longer period of time. The LightAPRS-W, which is very small, was powered by two small PowerFilm 4.8V solar panels with two 5F 3V supercapacitors. With this power source, the tracker transmits APRS on VHF at .5 to 1 Watt, and WSPR on HF at 10 mW (1/100th of a Watt!).

We spent several days configuring and testing the tracker, using the configuration and programming instructions provided by QRP Labs on GitHub, and following some helpful suggestions in the Tips & Tricks for Pico Balloons wiki. The tracker also had two light wire antennas for APRS (19.4 inches) and 20 meter WSPR (16.6 feet), and a counterpoise (16.6 feet) attached.

Assembled LightAPRS-W tracker with two PowerFilm solar panels and super capacitors. It’s really small and light!

Once assembled, the tracker was easy to configure with an Arduino IDE to load the APRS callsign (K4KNS-11), WSPR callsign (K4KNS), and a few other settings. It’s best to pay very close attention to the instructions and comments in the configuration file! After the loading the configuration, we placed the tracker in the sun to test and listen for APRS and WSPR signals. We were able to confirm that the tracker was transmitting good APRS and WSPR signals. Due to the very low power of the VHF and HF transmitters, we could only confirm local reception. With the tracker stationary and in full sunlight, we noted that the LightAPRS-W transmitted an APRS packet approximately every 5 minutes, and a WSPR signal every 4-6 minutes.

Assembled and configured LightAPRS-W in the sun to test the solar panels and monitor APRS and WSPR signals.
APRS received from the LightAPRS-W during testing.
Good test of WSPR signal from K4KNS!

It’s one thing to have a good test under controlled conditions, but quite another to achieve success under field conditions. On the day of the launch, the weather was marginal, but within acceptable parameters for a launch. We double checked to ensure the tracker was powered up and transmitting, and tied it to the balloon.

Good test of the APRS signal on launch day!

We had a good launch. The balloon, with the tracker hanging 16.6 feet below the balloon (to accommodate the counterpoise) and trailing a 16.6 foot HF antenna, quickly rose to an altitude above any potential obstructions and began its journey. Within moments, we saw the first APRS positions appear on aprs.fi. A few moments later, using the WSPR Watch iPad app, we saw that the WSPR signal was being received across the U.S.!

The first APRS track for balloon K4KNS-11!
The 10 mW WSPR signal was received as far west as Oregon!

It was all going so well! We continued to watch the balloon tracking eastward and climbing, following the same track as the high-altitude balloon that had been launched about a half hour earlier. Then, after about an hour of flight, both the APRS and WSPR signal went off the air. At that time the balloon was 55 miles east of the launch site at an altitude of 37,500 feet.

The track and final position received from K4KNS-11.
Location, speed, course, speed, altitude, temperature, pressure and solar cell voltage data from K4KNS-11 exported from aprs.fi.

We’re not sure exactly why the signals were lost, but we do not believe the balloon went down in that location. We are speculating that the tracker may have been damaged due to the high wind speeds on lost power. It is unknown how much farther the balloon might have traveled. Despite the relatively short flight, we did collect some good data for the students at Savannah River Academy to evaluate. We also proved to ourselves that we could successfully launch a balloon and track it with APRS, and that a very weak WSPR signal transmitted from high altitude could be received by stations thousands of miles away!

Map on WSPRnet.org showing stations that received the K4KNS WSPR signal on May 5, 2021.
Spot Database for K4KNS on on May 5, 2021 from WSPRnet.org.

Using aprs.fi’s data export tool, we were able to export a KMZ file with the balloon’s tracking data, and use Google Earth to view the full track and altitude changes.

Google Earth map of the track and altitude changes for pico balloon K4KNS-11 on May 5, 2021.

This was an amazing experience! We captured many lessons learned, and we intend to build another more hardened version of the tracker so we can launch another balloon and hopefully track it over a much longer distance and time.

Additional information about both balloon launches is posted to the Amateur Radio Club of Columbia County Facebook page.

I got a new callsign!

I’m not sure exactly why I did it, but on a whim I decided to apply for for a few 1X2 and 2X1 vanity callsigns in call area 4 that were becoming available. Much to my surprise, yesterday I received a notice that I had been granted a new callsign – N4MI. It was not at the top of the list that I submitted to the FCC, but it turns out this is a great callsign for CW: -. ….- — ..

I did not realize how many things would need to be updated with a new callsign. To name just a few:

ARRL and Logbook of the World
VE credentials
DMR id
D-Star registration
Echolink
QRZ.com logbook and callsign page
Clublog
HRDLog.net
eQSL
DXmaps
aprs.fi
Reprogram hotspots and D-Star, DMR, APRS radios
Updating the name and domain for this website
New Email address (if it’s based on your callsign)
New QSL cards, shirts, hats, name tags (any physical item with a callsign)
New license plate with new callsign
WSJT-X, JTAlert, JS8Call, Ham Radio Deluxe, logging programs, Winlink, etc.
… and probably several other things I’ll discover later!

If you’re an active ham, when you apply for a new callsign do yourself a favor and make a list of things that will need to be updated ahead of time. Some of these changes are easy, but others are more involved and require time to complete.

ZUMSpot and openSPOT 3

I have been casually using DMR, D-STAR and YSF (Yaesu System Fusion) modes for a couple of years, using a ZUMSpot. The ZUMSpot is a small board that sits on a Raspberry Pi Zero W. It incorporates a Multimode Digital Voice Modem (MMDVM) and a 10mW UHF transceiver that operates YSF, DMR, YSF2DMR, D-Star, P25 and NXDN modes. The ZUMSpot uses Pi-Star digital voice software. Pi-Star is a custom, pre-configured SD Card image for the Raspbperry Pi, with configuration and operation performed through a web browser. The Amateur Radio Notes website has an excellent tutorial on setting up and configuring Pi-Star. While the Pi-Star configuration appears daunting at first, it is easy to set up by following the tutorial. There are also several videos on YouTube with instructions for configuring Pi-Star.

A few days ago, I was attempting to update the Pi-Star software and the ZumSpot firmware, but kept seeing errors during the firmware update. After several attempts to update the firmware, the ZumSpot wasn’t operating properly*, so I decided to purchase an openSPOT 3, which is made by SharkRF in Estonia.

The openSPOT3 is a battery powered, portable, standalone digital radio internet gateway (aka hotspot). The openSPOT 3 is also configured through a web interface, but the interface and steps for configuration are different than Pi-Star’s. The openSPOT 3 user manual is a web page that is updated frequently when there are firmware updates or features added to the device. Having learned the basics of DMR, D-STAR, and YSF with the ZUMSpot, I found configuration of the OPENSpot 3 to be fairly easy.

* After I had the openSPOT 3 up and running for a few days, I decided to attempt the ZUMSpot firmware upgrade again. It turns out I had missed a step in my earlier attempts, and this time the update was successful. So now I have two MMDVMs!

Both the ZUMSpot and OpenSPOT 3 are excellent MMDVMs. Both are capable of operating the most popular digital voice modes using a DMR, D-STAR or C4FM radio. Also, they both require a wi-fi connection and are configured through a web interface. The openSPOT 3 is great for portable operations since it has a built-in battery and the configuration web page works very well on a mobile phone web browser. Since the ZUMSpot is based on a Raspberry Pi Zero W, it could also be used portable with a USB power bank. The openSPOT 3 costs a bit more more than the ZUMSpot. There are also many other MMDVMs on the market, including inexpensive generic boards and kits available on Amazon and eBay. Digital voice modes with MMDVMs are a great way to talk to hams from all over the world using a VHF/UHF digital radio and an Internet connection.

The Pi-Star configuration panel is used to enter all of the necessary settings for the MMDVM to operate properly.
The Pi-Star Dashboard displays a call log and the current status of the MMDVM.
The Pi-Star Administration panel displays some additional status information, and options to change some of the settings for the digital mode currently in use.
The openSPOT 3 has a “Quick Setup” page to configure the openSPOT3 with the transceiver and connect to the preferred network.
The openSPOT 3 status page and call log – you can see information about the openSPOT3’s current status, and listen to call audio on this page.
openSPOT 3 in DMR mode with Anytone 878
ZUMSpot in D_STAR mode with Kenwood TH-D74
openSPOT 3 in YSF mode with Yaesu FT3D
Both the ZUMSpot and openSPOT 3 can be configured to send your station location via an APRS server

Hamshack Hotline

A local ham friend shared a link with me for Hamshack Hotline, which is a free dedicated VOIP service for the ham radio community. In order to get on this network, I purchased a used Cisco SPA504G IP phone from eBay for $29. There are several other IP phones that will work with the service, but the SPA504G works great, and the price was right! It is important when purchasing a used phone to ensure that it is unlocked. The Hamshack Hotline website has all the information necessary to get started.

Once I received the phone, and connected it to my home network, I followed the instructions on the web page, and submitted a ticket for a new line using the HHOPS Help Desk. The Help Desk web page also includes a knowledge base and downloadable documents that are a great help for installing an IP phone on their network.

Within a couple of days, I had a response from the Help Desk team with my new HH phone number, and a link to a provisioning document for my phone. The instructions were easy to follow, and the team has created a process for provisioning that is nearly foolproof. I say nearly because I did have a slight issue with my home network, but the Help Desk team came through again and got me up and running very quickly!

My Hamshack Hotline phone number is 11642.

New VUCC and WAS Award Milestones Reached!

Due to work obligations, I haven’t had much time to spend on the radio, or to update this blog. Since my last update, QSOs with several stations have been confirmed in Logbook of the World, allowing me to reach a achieve a couple of new awards.

I recently received a LoTW confirmation for a QSO on 6 meters that took place in July. This confirmation was number 300 on 6 meters, and an endorsement for the 50 MHz VUCC Award.

It took a while, but I finally confirmed 300 grids!
Grids confirmed on 6 meters for N1ADM

Also, on November 28th, I had a FT8 QSO on 12 meters with a station in Alaska, which gave me my 50th state for the Worked All States Award on 12 meters. I still need to work Alaska on 10 meters for a 5 Band WAS, so hopefully the band conditions will continue to improve!

Alaska on 12 meters, finally! Now hoping for 10 meters!
I am getting close to WAS on all HF bands!

Morning DX on 40m and 15m

It has been a while since I’ve found time to add a post, or to spend much time on the radio. On this Saturday morning, I decided to get up a little earlier than usual to check the band conditions for DX. I found some good DX to the west, in the Pacific and Asiatic Russia on 40 meters, as well as to the east in Europe and the Mediterranean on 15 meters. The propagation on both bands was very good, but there were lots of stations so breaking through the QRM made some contacts challenging. I only worked one new country on 15 meters, but it was lots of fun to see the variety of locations active on the bands.

Outdoor Antenna for PiAware ADS-B Receiver

About 3 years ago I built a PiAware ADS-B receiver with a Raspberry Pi 3B+ computer and a FlightAware Pro Stick Plus ADS-B USB Receiver with Built-in Filter. For the antenna, I used an inexpensive 1090-MHz indoor antenna mounted in the windowsill. This is a very easy, inexpensive, and fun radio project with a Raspberry Pi, and I would encourage anyone interested in radio and/or aviation to build one. The FlightAware website includes parts lists and detailed instructions for building an ADS-B receiver with a Raspberry Pi computer. You can also build an ADS-B receiver with a Raspberry Pi computer and hardware from AirNav.

Automatic dependent surveillance–broadcast (ADS–B) is a surveillance technology in which an aircraft determines its position via satellite navigation and periodically broadcasts it, enabling it to be tracked.

This setup worked fairly well, and I was able to receive position and heading information for several aircraft within a range of approximately 50 nautical miles, and sometimes a bit farther depending upon the altitude of the aircraft. An indoor antenna is a compromise solution and will generally limit the range from which ADS-B signals can be received.


This morning I replaced the indoor antenna with a FlightAware 1090 MHz ADS-B Antenna mounted outdoors on a 12-foot fiberglass push-up mast. I used 50 feet of LMR-400 coax cable terminated with N male connectors outside, and a short adapter cable with N male and SMA male for the connection to the FlightAware receiver. The antenna is compact and very light, so the installation was very easy.

After installing and attaching the outdoor antenna, there was a dramatic difference in the number of signals received, as well as the distance. The PiAware will now receive signals for almost every aircraft flying inside of 1oo nautical mile radius, and is receiving some as far away as 200 miles!

New DXCC on 20 Meters – Hong Kong

I haven’t been on the radio much over the past week, but this morning I had some time and found that 20 and 30 meters were open to the Far East. It took a bunch of tries, but I was able to complete a FT8 QSO on 20 meters with VR2XRW in Hong Kong. That’s a new DXCC entity for me, and he confirmed the QSO on Logbook of the World in just a few minutes! The new DXCC entities are becoming fewer and further between, and it’s always special to work a new one!

A few good FT8 and FT4 QSOs on 20 and 30 meters
VR2XRW confirmed our QSO on Logtbook of the World within minutes!
N1ADM’s DXCC Account Status as of August 15th, 2020

Accurate Time for Digital Modes by GPS

Accurate computer time is absolutely essential for successful QSOs using digital modes such as FT8, FT4 and JS8. While millisecond accuracy is not necessary, if the computer clock is off by more than a second, you are likely to experience problems. It is very easy to check the accuracy of your computer’s clock by using the website time.is.

A check of my computer’s clock on time.is showed that it was 0.3 seconds behind. This is well within specs for digital modes.

Recent versions of Windows will frequently update the clock through time servers, but the updates are not usually as frequent or accurate as I would like. There are also several applications that will connect to Internet time servers to periodically update the computer clock. Some examples are Meinburg NTP, BktimeSynch, Dimension 4, and NetTime. I have Dimension 4 loaded on my shack computer.

Dimension 4 periodically updates the computer clock using a low level internet protocol, called SNTP, to connect with special purpose Internet Time Servers.

But what if you don’t have Internet access, due to an outage or working in the field? Fortunately, there are computer applications that will synchronize your clock using GPS signals. To do this, you need the software and a GPS receiver for the computer.

For my computer, I use a GlobalSat BU-353-S4 USB GPS Receiver and NMEATime2 software for GPS-PC time synchronization. The GPS receiver cost me $34, and it also cost me $20 to register the software.

The GPS receiver connects to a USB port on the computer as a serial device. I have the receiver in a windowsill near the computer.

On my computer, the GPS receiver is the Prolific USB-to-Serial Comm Port (COM4).

After the GPS receiver, I installed the NMEATime2 software. It was very easy to set up the software to work with the GPS receiver. Once installed, the software runs in the background to keep the computer clock updated. There is an icon in the system tray that shows the current status.

The green satellite icon in the system tray indicates that NMEATime2 has a good GPS signal lock and the application is disciplining the computer clock.

A right click on the tray icon and selecting “Show Panel” will bring up the software control panel with menus for settings and four tabs: Status, GPS Status, Loop Status, and NMEA Output. For my purposes, the Status panel and GPS Status panel contain the most important information.

The Status panel shows the current time and overall quality of the GPS satellite signals.
The GPS Status panel shows which GPS satellite signals are being received, and the signal quality for each, as well as location information.
The Loop Status tab displays the status of digital filters that filter out any spikes or outliers before sending the filtered signal to the application’s control algorithm.
The NMEA Output tab displays the NMEA data strings as they are received from the satellites.
While running NMEATime2, my computer time is usually exact or very close.