Aprs

I got WINE setup to run the software for RadTel. I had to install Mono for Windows inside WINE to make the RadTel CPS and Flasher work: https://askubuntu.com/a/992215 I also got serial going: https://gitlab.winehq.org/wine/wine/-/wikis/Wine-User%27s-Guide#serial-and-parallel-ports

The APRS support on the RadTel RT-880G still seems a bit broken, though. I keep seeing a stray character in the path: “WIDE1_-1” Setting the path in CPS software had the same problem. Setting the path to " WIDE1" makes it show OK in packets.

I got the BTech UV-PRO back on Friday, 2025-07-18. This one has a different serial number, so very quick replacement. I restored the configuration from the HT app on my phone. The new radio is seen on https://aprs.fi/ again and I occasionally see APRSDroid report that it’s been digipeated by a nearby node. I tested the transmit power to be 4.8W with the small meter. Power was previously not detected at all by the meter.

I joined the APRS Thursday HOTG (Hams of the Gram) net. I checked in by sending: ANSRVR CQ HOTG good Thursday morning. I guess it sent 117 messages to others, and for the 12 hours I was subscribed, I received 174 HOTG messages to my callsign from stations across the US and around the world.

APRSDroid would often fail to reconnect to the UV-PRO: java.io.IOException: read failed, socket might closed or timeout, read ret: -1 The HT app would manage to reconnect OK. I would need to cycle power on the radio to get APRSDroid to reconnect. In APRSDroid, Preferences->Connection Preferences->Channel was set to 1. I blanked that channel setting, and now it may be reconnecting between stop and start of app, bluetooth, or distance.

As a side note, having the UV-PRO monitoring a frequency other than APRS may interfere with packet reception. I don’t see as many APRS packets when monitoring another repeater, probably due to interruptions from the non-APRS audio.

The activation at King’s Gap Environmental Education Center, US-4361 was tough-going, even though I was at the top of the mountain. I used the GRA vertical whip with tapped coil. Internet access flaked early, so successfully spotted myself on APRS with APSPOT.

I had my UV-PRO and APRSDroid running at Mountain Creek in Gardners, PA, using a normal telescoping antenna. The APRS traffic I observed looked pretty familiar to what I typically see around home, with a wide range of activity and some of the same digipeaters.

I’ve been learning about the BTech UV-Pro. When scannimg, it degrades the incoming APRS, even in digital mode where it checks back to the APRS channel frequently. I’ve been using stock APRSdroid over the TNC connection, but it takes a little fiddling sometimes to get it to connect.

In the new firmware, they’ve been flip-flopping features between 8.2.x and 8.3. It has bold/yellow fonts (or not), and new button actions to access groups. NOAA alerts have also come and gone to see if they affect RX performance overall.

I recently added winlink back to my APRS ping on the UV-PRO. I immediately got a message from a Winlink gateway that I had 1 new Winlink message waiting. For the full RF experience, I fired up KISS on the UV-PRO and a session to K3IR’s Winlink gateway (145.030kHz) and checked my Winlink mail over the radio.

I needed to be careful to not let HT app start and re-enable “digital mode”. When “digital mode” is enabled, it would switch to APRS 144.390MHz every time WoAD would TX, and that doesn’t work. The hint was seeing APRS traffic in the WoAD log while waiting for my Winlink session to initialize.

The email was KC3WRY, Matthew, playing around sending Winlink via APRS. I acknowledged and responded to his message.

I caught word that ISS was passing in a moment, so I tuned UV-PRO to 145.825MHz, the APRS digipeater on ISS. I heard packets from Pittsburgh, PA; Smyrna, DE, and Atlanta, GA. I tried to ping out my location a couple times, but it looked unheard according to https://ariss.net/.

The HT app and UV-PRO digipeats APRS packets like a mesh.