The 985 group held their winter field day at Lines Self Storage. They had 5 stations in trailers and tents. They worked some satellites and mostly HF. There was hundreds of feet of coax feed line all over the place.

I aw KC3NZT, Harvey, operating a satellite station with special hardware. Harvey also called CQ on HF. He’s a machine, logging hundreds of QSOs.

I used a headphone splitter to listen to another operator, Bob. I copied some CW, but not a lot. I listened for some digital and found a bit of RTTY, but it was for the BARTG contest, not WFD. I made some SSB contacts on others’ radios that were setup for the weekend.

I hung my rolled slim-jim to call on 146.520MHz and beacon some APRS, but I heard nothing. I could also check winlink email through the N3MEL gateway in Downingtown. I had looked it up ahead of time. In the notes in WoAD, I list the frequency where the gateway listens for packets.

I visited during daytime on both days, but did not stay overnight like some did.

I connected up to Winlink through N3FYI’s gateway on 144.950MHz. using 1/4-wave antenna hanging in the tree. I also had set my APRS message to “Winlink”, so the Winlink server pinged me over APRS when I had a message. I’m not sure I could read the APRS message on the UV-PRO, though, since I let it sit too long. I had a message icon, but I couldn’t dismiss it.

There were only 3 of us at the SPARC elmer night, but we were on the same page. I compared notes on packet/APRS and WoAD with KC3QEH, JJ. We both had these new Btech-based radios. Even on the hill, our HTs with small antennas didn’t pick up much inside the building. I tried an external antenna from another club radio and I started receiving lots of packets. Sending APRS messages worked under the Signal menu: KC3QEH-7:TEST MSG

Yet Another Radio

I got interested in AX.25 packet over RF, so the Btech UV-Pro immediately looked like an interesting jumpstart, when it got a firmware update that allowed it to operate as a KISS TNC over Bluetooth.

Application Driven

HT is the up-to-date app for interfacing with the radio. There’s a “BTech Programmer” app, but it is an older, branded version of HT.

Setup

In the radio, I’d set “General” -> “Digital” -> “Format” = “APRS”, but the HT app kept switching it back to “BSS” any time it connected to the radio. It would never let me set “APRS” until I “verified” my ham radio callsign. It wants to do it by sending your license info to some chinese site – no thanks. Instead, I used a web app to generated an APRS code that worked in the HT app.

I enabling digital mode in radio to make it periodically beacon my APRS location. I set it to a fixed channel for sending APRS. Only the HT app seems to be able to set the beacon text for APRS.

I can send messages from radio by prefixing the message with the recipient:

KC3WWC-7: hey

TNC KISS Mode

I installed WoAD on Android, and enabled TNC KISS on the radio. I paired the radio to the phone via Bluetooth. I checked the Winlink RMS map on the website to find nearby packet gateways, and set the radio to the given packet frequency for the gateway I was trying to use. I configured a session for the callsign and SSID of the Winlink gateway, and started the session. Now it’ll send and receive queued email. There’s a log in WoAD that shows what it’s doing.

WoAD also has a terminal which can be used for BBSes, like KA3TKW. I connected there to see some messages and a BBS software from 1990!

APRSDroid can also talk to KISS TNC over Bluetooth. It’s a much nicer UI than the radio or HT app. Sometimes when switching apps, I needed to cycle power on the radio, but it doesn’t usually take too much to get it going again.

Customizing actions of the ASL node isn’t all that complicated. Everything can be setup in /etc/asterisk/rpt.cfg under the [functions] section:

• added *77 to announce IP to help find it on DHCP on WIFI (hotspot):

  77 = cmd,asl-say -n 63047 -w ip4
  

• added *78 to shutdown the node via DTMF

  78 = cmd,shutdown now
  

• ensured I could disconnect all with *6

  6 = ilink,6
  

• made the node fire that *77 command on startup by adding to the (node-main) section for my node:

  startup_macro = *77
  

I activated US-1418 one nice afternoon with the GRA-1900T on 40m. I was getting desperate, so tried vertical and horizontal orientations. I wonder if I was a bit too close to the metal pavilion.

Direwolf doesn’t want to do anything without a local config in place. I had to decompressed /usr/share/doc/direwolf/conf/direwolf.conf.gz to $HOME/direwolf.conf. I customized the configuration file:

• set my callsign
• listed audio devices with arecord -L, found pipewire, and set ADEVICE pipewire in the config
• plugged the Btech APRS cable into the Quansheng and computer
• Direwolf is decoding packet (from 145.010MHz) and APRS (144.390MHz).
• -q d quiets APRS decode errors when reading plain packet
• -t 0 disables the colors
• with pipewire, I can have both my record-aprs.sh script and Direwolf decoding.
• decoded APRS from ISS on 144.825MHz via multimon-ng:

AFSK1200: fm KB9VIC-9 to DH4TLZ-0 via RS0ISS-0,WIDE2-1 UIv pid=F0
`t].l .#\`KB9VIC EM58 OLNEY IL HOME OF WHITE SQUIRRELS _%
AFSK1200: fm KA2OMQ-0 to W4BB-0 via RS0ISS-0 UI^ pid=F0
QSL? UR 59 FN13
AFSK1200: fm W4BB-0 to CQ-0 via RS0ISS-0 UI^ pid=F0
:KA2OMQ   :QSL and 73 via ISS
AFSK1200: fm W9QO-0 to STPX1V-0 via RS0ISS-0,SGATE-0,WIDE2-2 UIv pid=F0
'oIPl .-/]

My Week in Radio

• discovering some good old packet radio
  • 145.010
  • listen with multimon-ng
  • search for a terminal program for android and linux
• patched my favorite firmware (f4hwn) to better render the spectrum analyzer for wide or narrow scan ranges
  • built and tested on my own radio
  • patch was accepted to the open source project, so it’ll be in the next release
• POTA in the cold in prep for field day

Others

• W8CRW, CR:
  • new radio from HRO
• WA3VEE, Ron:
  • after 985 breakfast, at field day site, will be introducing radios for field day
• KC3RFG, Jim:
  • first Raspberry PI kit for a Ham Clock
• KC3YSM, Steve:
  • nets and POTA
    • all US: GA, AL, MI
• AB3AP, Mike:
  • hanging out on 30m
  • learning to touch-type instead of handwriting from CW
    • ARRL MP3s online
    • 15 WPM typing, 18 WPM is a challenge
    • jots keywords usually to be faster
• KC3OOK, Bill:
  • hosted last roundtable
  • net control for simplex net
  • working on ham shack
  • windy: gust of 39mph, antenna survived
• KC3SQI, Wayne:
  • couldn’t get to the repeater due to lots of QRN from powerlines, trains, etc.
• AF3Z, Jim:
  • SKCC had a weekend sprint-a-thon.
    • operated from Cornwall station as W3CRS
    • they were in 1st place until other clubs started uploading logs :)
• W3MFB, Mike:
  • experimenting using gutter and down spout and speaker wire as HF antenna
    • 10W and it worked.
    • recommending a similar setup to a friend

Questions

• WA3VEE, Ron:
  • We’re putting together some seminars/classes to share experience and knowledge.
  • What would you like to talk about? theory or operation?
  • NA3CW, Chuck:
    • get the scope and meters out and discuss impedance, etc.
  • KC3OOK, Bill:
    • Ron’s discussion on oscilloscopes
  • AF3Z, Jim:
    • general approach to trying to fix something
    • how to check equipment: bandpass filters, crystals
  • W3MFB, Mike:
    • understanding solar data
  • NA3CW, Chuck:
    • propagation
  • KB3ZIM, Bob:
    • revisit antennas and feedlines and their attributes
  • KC3WWC, John:
    • kit night to build something
    • favorite equipment on the bench that others should have
  • KC3OOK, Bill:
    • soldering technique
    • all basic test equipment
    • NA3CW, Chuck: validating readings from equipment
  • AF3Z, Jim:
    • surface mount soldering
    • NA3CW, Chuck: good tweasers
  • KC3RFG, Jim:
    • refresher on setup and use of NanoVNA
  • W3MFB, Mike:
    • soldering coax
  • KC3WWC, John:
    • digital modes old and new
  • AF3Z, Jim:
    • sorting out limitations of test equipment, signal levels
  • W3MFB, Mike:
    • tutorial for the young folks, how to build a repeater
  • KC3SQI, Wayne:
    • how do you find an interfering signal, fox hunting.
  • KC3OOK, Bill:
    • basic circuits
  • NA3CW, Chuck:
    • understanding antenna gain

I discovering some ax.25 packet radio floating around on 145.010MHz. I connected my Btech APRS audio cable from computer headphone/mic to the Quansheng, and piped the audio into multimon:

$ pw-record --channels 1 --rate 22050 - | multimon-ng -t raw -a afsk1200 /dev/stdin

Here’s some of the traffic I decode:

  AFSK1200: fm AA3RG-7 to ID-0 UI^ pid=F0
  TheNet X-1J4  (PINEGV)
  AFSK1200: fm AA3RG-7 to N3FUD-7 RR4-
  AFSK1200: fm AA3RG-7 to N3FUD-7 RR4-
  AFSK1200: fm W3AVP-5 to ID-0 via AA3RG-7 UI^ pid=F0
  W3AVP Packet System - FN10xc
  W3AVP-5: New Holland Chat
  W3AVP-10: Winlink Gateway
  AFSK1200: fm AA3RG-7 to N3FUD-7 RR4-
  AFSK1200: fm W3HZU-0 to N3FUD-7 RR4-
  AFSK1200: fm W3HZU-0 to ID-0 UI^ pid=F0
  YORKPA:W3HZU  Connect W3HZU-1 BBS & W3HZU-11 CHAT
  AFSK1200: fm AA3RG-7 to N3OGS-7 DISC+
  AFSK1200: fm AA3RG-7 to N3OGS-7 UA-
  AFSK1200: fm AA3RG-7 to N3FUD-7 RR5-
  AFSK1200: fm W3HZU-0 to N3FUD-7 RR4-
  AFSK1200: fm N3DWB-0 to QRZ-0 via KA3TKW-0,PINEGV-0 UI^ pid=F0
  N3DWB JONESTOWN FN10SJ
  N3DWB-1 Mailbox
  AFSK1200: fm N3DWB-1 to MBX-0 via KA3TKW-0,PINEGV-0 UI^ pid=F0
  Mail for: None
  AFSK1200: fm AA3RG-7 to N3FUD-7 RR5-
  AFSK1200: fm W3HZU-0 to N3FUD-7 RR4-
  AFSK1200: fm AA3RG-7 to N3UOO-7 UA-
  AFSK1200: fm W3HZU-1 to WA3USG-1 via KA3TKW-0 SABM+
  AFSK1200: fm W3HZU-1 to WA3USG-1 via KA3TKW-0 SABM+
  AFSK1200: fm WA3USG-1 to W3HZU-1 via KA3TKW-0 UA-
  AFSK1200: fm WA3USG-1 to W3HZU-1 via KA3TKW-0 I00^ pid=F0
  [KPC3P-8.3-HM$]
  95529 BYTES AVAILABLE
  THERE IS 1 MESSAGE NUMBERED 13
  ENTER COMMAND:  B,J,K,L,R,S, or Help >
  AFSK1200: fm AA3RG-7 to N3FUD-7 RR5-
  AFSK1200: fm W3HZU-1 to WA3USG-1 via KA3TKW-0 I10+ pid=F0
  [BPQ-6.0.24.33-IHJM$]
  AFSK1200: fm W3HZU-1 to WA3USG-1 via KA3TKW-0 I10+ pid=F0
  [BPQ-6.0.24.33-IHJM$]

I need to find a terminal program for Android (BPQ Term?), and read more about the anatomy of an ax25 packet.

There was a bug for a while in F4HWN 3.9 on the Quansheng radios. The spectrum analyzer graph was too narrow when number of bars exceded 128. I’d easily run into the problem when I set the scan range to 144.000MHz to 148.000MHz, and activate the spectrum analyzer.

I dug into the code a bit and fixed it, so now it scales for large and small ranges.

I submitted a pull request to the project, and it was accepted and merged to be included in the F4HWN 4.0 release. Until that release, I’ll be running my custom build.

I also made a change to allow me to map the spectrum analyzer to a programmable side button like AubsUK had, but I’m no longer convinced it’s worth the limited code space it would consume in the binary.