Radio Hill Gazette

RHG Articles

SARC’s Role in Septemberfest 2026

Behind the Celebration

Above the Septemberfest crowd, a large screen carried a message worth celebrating: “Amateur ‘Ham’ Radio Serving the Community!” Beside the Schaumburg Amateur Radio Club’s logo were four simple commitments: communicating, learning, giving back, and having fun.

The photograph from Schaumburg’s 2026 Septemberfest captures that message above a Schaumburg Park District trailer, with festivalgoers passing below. At the bottom of the display, a short line brings the story home: “A proud Septemberfest partner.”

For the Schaumburg Amateur Radio Club, known as SARC, that partnership had a practical purpose. The club organized volunteers for public-service communication support during the September 5–7 celebration. Behind the public recognition was the work of preparing assignments, equipping volunteers, and answering the Village’s request for help.[1]

Members Stepped Forward Before the Festival Began

One of the clearest examples of SARC’s commitment appears in the club’s August 20 business meeting minutes.

Howard Mitchell, KD9WSV, brought the materials volunteers would need for Septemberfest: numbered identification cards, parking passes, food discount tickets, and loaner vests. Members were asked to collect their assigned items, with badges and vests to be returned after the event.

Then came a small moment that says a great deal about the club. Howard reported that just one volunteer slot remained open for the three-day event. Eliot Libner, N9EPA, volunteered to cover it.[2]

A schedule becomes a commitment when someone puts a name beside an assignment. That final offer of help is a concrete example of members taking responsibility for the work their club had agreed to support.

At the September 2 board meeting, Howard’s planning update confirmed that the Village of Schaumburg had again requested SARC’s support for all three days. The minutes also thanked members who had volunteered.[3]

What Amateur Radio Contributes to a Community Event

For someone new to ham radio, its role at a festival may not be obvious. SARC’s public-service work helps people at different locations exchange information through an organized radio network. The value comes from operators who listen carefully, report clearly, and know how to work together.[4]

The club’s 2026 Septemberfest guidance described possible assignments such as providing location updates, passing along observations, relaying requests, and maintaining contact with Net Control—the station coordinating radio traffic. Exact responsibilities depended on each assignment and the event coordinator’s instructions.[1]

That guidance defined a supporting role: volunteers were to observe, communicate accurately, and follow the event’s command structure. Police, fire, medical, and Village personnel retained their own responsibilities.

It is useful, disciplined work. A clear report can give an organizer information from a location they cannot see. An acknowledged instruction helps everyone know what happens next. Those ordinary exchanges explain why practiced communication belongs in the planning of a busy public event.

A Celebration With Many Moving Parts

Local coverage helps put that preparation in perspective. The Daily Herald identified 2026 as Schaumburg’s 55th annual Septemberfest, with a program spanning September 5–7 at the Al Larson Cultural Center and Robert O. Atcher Municipal Campus.

Its preview listed concerts, Taste of Schaumburg, arts and crafts, a Sunday drone show, and Monday’s Labor Day parade. The main-stage lineup included Night Ranger, White Lion, Warrant, and Max Weinberg’s Jukebox.[5]

A separate Village notice published by the Daily Herald detailed temporary road closures and parking restrictions, including additional changes for the September 7 parade along Summit Drive.[6]

Together, those reports illustrate the coordination behind the celebration. Entertainment schedules, vehicle access, parade movements, and volunteer reporting locations all require preparation. In that setting, SARC’s commitment to organized communication had a clear purpose.

A Partnership Built Through Previous Service

SARC brought an established Septemberfest relationship into 2026. The club’s earlier records document both the time members gave and the preparation behind their assignments.

Documented SARC Septemberfest service in earlier years
Year Reported contribution
2024 13 volunteers and more than 93 hours, including preparation and event operations, supporting the Septemberfest parade.[7]
2025 26 volunteers and more than 80 service hours, according to a Village recognition notice reproduced in SARC’s December board minutes.[8]

The 2024 report describes advance radio testing, communication between assigned locations and event command, and suggestions gathered afterward to improve future participation. In 2025, Village Emergency Management and Accreditation Manager Tracy Raimondo presented the club with a plaque recognizing its service.[7][8]

These are earlier-year records, rather than totals for 2026. They show the experience and continuing relationship behind this year’s volunteer effort.

Fifty Years of Radio, Friendship, and Giving Back

The Septemberfest partnership also fits a larger SARC milestone: the club’s 50th anniversary in 2026. Its anniversary article celebrates five decades of learning, operating, friendship, and public service.[9]

The festival photograph makes that tradition visible to people who may never have attended a club meeting. It presents amateur radio as something approachable and useful, with an invitation that needs little explanation: “All ages welcome!”

That is an encouraging introduction to the hobby. Someone passing the display might be interested in electronics, curious about communicating over the air, or looking for a meaningful way to volunteer. SARC offers a place to begin that conversation.

Thank You to the People Behind the Partnership

Thank you to the SARC members who made time for Septemberfest, to Howard Mitchell for coordinating the documented preparations, and to Eliot Libner for stepping forward when the final assignment needed a volunteer. Thanks also go to the Village staff, event organizers, public-safety personnel, and fellow volunteers whose work supports Schaumburg’s community celebrations.

The message on the screen deserves to carry beyond Labor Day weekend. Communicating, learning, giving back, and having fun are all reasons to get involved.

Curious about amateur radio? Visit a SARC meeting, explore the club’s public-service activities, or learn about joining SARC. Visitors are welcome at club meetings, including people who have not yet earned an amateur radio license.[10]

Sources and Further Reading

  1. SARC Septemberfest 2026 Public Service. Schaumburg Amateur Radio Club. Event dates, volunteer arrangements, and role guidance. ↩
  2. Business Meeting Minutes, August 20, 2026. Schaumburg Amateur Radio Club, page 6. Volunteer materials and Eliot Libner’s offer to fill the remaining assignment. ↩
  3. Board Meeting Minutes, September 2, 2026. Schaumburg Amateur Radio Club, page 4. Village request for support across all three festival days. ↩
  4. Public Service. Schaumburg Amateur Radio Club. Background on the club’s communication-support work. ↩
  5. Big names, big fun: Schaumburg Septemberfest returns Sept. 5–7. Luke Zurawski, Daily Herald. Festival preview published September 1, 2026. ↩
  6. Schaumburg to impose temporary traffic and parking restrictions around Septemberfest. Village of Schaumburg notice published by the Daily Herald, August 31, 2026. ↩
  7. Board of Directors Meeting, September 4, 2024. Schaumburg Amateur Radio Club. Historical parade-support report. ↩
  8. Board Meeting Minutes, December 3, 2025. Schaumburg Amateur Radio Club, pages 4–5. Reproduces Village recognition of the club’s 2025 Septemberfest service. ↩
  9. SARC 50th Anniversary: Celebrating 50 Years of Amateur Radio, Service, and Friendship. Schaumburg Amateur Radio Club. ↩
  10. Monthly Club Meetings. Schaumburg Amateur Radio Club. Visitor information. ↩
Operating Modes RHG Articles

Mercury vs. VARA HF

Pros, Cons, and Practical Choices for SARC

Here is a useful operating idea for Schaumburg Amateur Radio Club members: explore two ways to send messages and files over HF radio. Mercury and VARA HF offer an opportunity to learn about digital communications, compare station setups, and help newer hams make their first data connection.

The practical starting point is your intended contact. If that station uses VARA HF, choose VARA HF. If you and a partner want to explore an open-source modem, Mercury is worth a coordinated trial. The distinction between software compatibility and radio compatibility explains why.

Topic Snapshot

Mercury vs. VARA at a glance
Subject Mercury VS VARA
Post idea from Paul Meyes — KE9EJX
Audience SARC members, visitors, new hams, the public, operators, and volunteers
Focus HF messaging, file transfer, Winlink considerations, and peer-to-peer experiments
Suggested activity A paired station demonstration followed by repeatable comparison tests
Review date September 18, 2026. Check official documentation before installing or purchasing software.
Scope This comparison concerns VARA HF. VARA FM and VARA SAT are separate products.[1]

What Do These Modems Do?

A software modem converts computer data into audio that a radio can transmit. At the other station, another modem decodes the received audio. HF means high frequency; these programs use a suitable single-sideband, or SSB, radio and an audio connection.

Both Mercury and VARA HF use orthogonal frequency division multiplexing, or OFDM. In simple terms, information travels on multiple closely spaced carriers. Sharing that general technique does not make their radio signals interchangeable.[2] [1]

Mercury also documents automatic repeat request, or ARQ: the receiving station acknowledges data, and unsuccessful transfers can trigger another attempt. Its connected link takes turns transmitting and adjusts payload modes as conditions change.[3]

Mercury and VARA HF: The Main Tradeoffs

Features that affect a club station’s choice
Consideration Mercury VARA HF
License and cost Free, open-source software with a GPL-3.0 project license.[4] Proprietary software with a restricted free mode and a paid license for higher speeds. Check current terms with the developer.[1]
Operating systems The project documents Linux, Windows, macOS, and Raspberry Pi support. Installation depends on the operating system and processor.[5] A Windows modem. Linux operation can use Wine, a Windows compatibility layer; Pat documents that approach.[6]
Application connection Provides a VARA-style command and data interface, with some commands accepted without implementing the corresponding feature.[7] Explicitly supported by Winlink Express and used by VarAC.[8] [9]
Software development Members can inspect the code and contribute under its license.[4] Changes to the modem depend on its developer; it is not an open-source project.[1]
Suggested club use Coordinated experiments, native platform trials, and learning how a modem works. Contacts and exercises whose destination already requires VARA HF.

Mercury: What Works in Its Favor?

Mercury is developed by Rhizomatica as part of its HERMES project. Native support across several operating systems gives members flexibility when choosing a computer for their station.[5]

Its open-source license also creates a useful learning opportunity. A technically curious member can inspect an implementation, suggest improvements, or contribute a fix. For a club workshop, that makes software development part of the radio experiment.[4]

Meanwhile, Mercury’s release history shows work on audio handling, radio keying, client connections, and its graphical interface. Recent releases include chat-related improvements. Check the documentation for the exact release you install.[10]

Where Mercury Needs Careful Planning

Mercury needs a compatible Mercury station at the far end. Changing your local modem does not convert a VARA-only gateway into a Mercury gateway. That follows from Mercury’s own radio protocol and its separate VARA-style application interface.[3]

In addition, active development means instructions and behavior can change between releases. Recent fixes involving Pat connections and audio devices are good reasons to record both stations’ versions and repeat a short test after updating.[10]

VARA HF: What Works in Its Favor?

VARA HF has a clearly documented role in existing applications. Winlink Express lists it as a supported radio mode. VarAC provides a separate application for conversations and other messaging features over VARA.[8] [9]

Consequently, VARA is a practical starting choice when your intended gateway or operating partner already uses it. You can focus the first session on setting up audio, making a connection, and completing a message exchange.

Where VARA HF Has Tradeoffs

Its proprietary license limits opportunities to inspect or modify the modem. Higher-speed operation also involves paid registration. Confirm current licensing details on the developer’s website before buying.[1]

Linux users should plan for an additional compatibility layer. Pat can run natively on Linux, but that does not make the VARA modem itself a native Linux application. Raspberry Pi installations require particular attention to the instructions for their processor and operating system.[6] [1]

Compatibility: Check All Three Layers

Mercury provides a TCP TNC interface: a network connection through which an application controls a terminal node controller, implemented here in software. Its documented defaults are port 8300 for commands and 8301 for data. TCP stands for Transmission Control Protocol.[7]

However, matching commands is only one part of a working connection. For example, Mercury’s command reference says its compression command is acknowledged without enabling modem compression. Treat compatibility as something to verify with your chosen application and release.[7]

Three separate compatibility questions
Layer Question to answer
Application to modem Can the client control this modem and exchange data through the configured ports?
Radio link Are both stations using compatible modem protocols, releases, and bandwidth settings?
Message service Do both ends support the intended email, chat, or file-transfer application?

What About Winlink Express, Pat, and VarAC?

Winlink Express and Pat both document VARA support. Mercury’s interface makes integration possible, but a successful local client connection does not establish access to a remote Winlink gateway. Confirm Mercury support at the destination before attempting a Mercury session.[8] [6] [7]

Similarly, VarAC and VARA are different programs. VarAC supplies the user-facing chat experience; VARA supplies the modem. VarAC’s published prerequisites identify VARA HF or VARA FM. Mercury release notes mention VarAC beacon support, but that alone does not establish complete compatibility with every VarAC feature.[9] [11] [10]

Which One Should You Try First?

Start with the destination and work backward. This decision guide applies the compatibility checks above.

flowchart TD
    A["Choose a contact or gateway"] --> B{"Destination requires VARA HF?"}
    B -->|Yes| C["Use VARA HF"]
    B -->|No| D{"Mercury partner confirmed?"}
    D -->|Yes| E["Match Mercury releases and settings"]
    D -->|No| F["Arrange a compatible partner"]
    F --> A
    C --> G["Check client, audio, and radio keying"]
    E --> G
    G --> H["Exchange a short test message"]
Choose a modem that matches the destination, then verify the complete station setup.

Performance: Measure the Completed Message

Claims that Mercury always matches or beats VARA HF go beyond what the documentation reviewed here establishes. Mercury publishes mode-level measurements under specified simulated conditions. Those measurements are useful, but they do not establish a universal winner against VARA on real radio paths.[2]

For a useful comparison, distinguish the displayed modem rate from goodput: the useful information delivered per unit of time. Connection setup, acknowledgments, retries, and changing conditions affect the completed transfer. Mercury’s documentation explicitly distinguishes payload rates from ARQ goodput.[2]

Also record signal-to-noise ratio, or SNR, which compares signal strength with background noise. Treat readings from different programs cautiously unless their measurement methods and reference bandwidths match.

A Suggested SARC Comparison Test

  1. Keep the station arrangement consistent. Use the same two stations, antennas, band, and comparable occupied bandwidth. Record transmitter settings and actual power measurements where available.
  2. Record the software. Include the application, modem release, operating system, and whether VARA is registered or operating with free-mode restrictions.
  3. Send identical content. Begin with a short text message, then try a modest file. Record any compression settings.
  4. Alternate the order. Run Mercury, then VARA, and reverse that order on the next pair of trials. Repeat in both directions to reduce the influence of changing conditions.
  5. Count failures too. Record unsuccessful connections, incomplete transfers, and manual intervention. Check that the received content matches the original.
Suggested measurements for each trial
Measurement Why record it?
Connection success Shows how often a usable session begins.
Time to complete Measures from the connection attempt to confirmed delivery.
Correct delivery Checks the text or compares a file checksum, a compact fingerprint of its contents.
Operator effort Records configuration problems, restarts, and recovery steps.

Present the results as observations from those stations and conditions. A small club trial can guide local choices without proving that one modem is best everywhere.

How to Participate

Begin by telling a potential test partner which computer you plan to use and whether your goal is email, chat, or file transfer. Then agree on the modem, application, and software versions.

For a station demonstration, prepare a suitable HF radio, antenna, computer, radio audio connection, and the required cables. Follow the radio and modem instructions for audio levels and push-to-talk, or PTT, which switches the transmitter on. Mercury documents several PTT methods; the appropriate choice depends on your interface.[5]

Ask an experienced operator to help select an appropriate frequency and station settings. Listen before transmitting, begin with a short exchange, and keep notes. Visitors can follow the decoded messages or record results while the station operator handles the radio.

Suggested SARC Goals

Ways different participants can contribute
Participant Suggested goal Useful result
New hams Trace a message from the application through the modem to the receiving station. Explain the difference between the application and the radio protocol.
Visitors and the public Observe a message exchange and ask how the stations connect. See a practical example of digital amateur radio.
Linux and Raspberry Pi users Try Mercury on a supported setup with a confirmed partner. Write a repeatable installation and configuration checklist.
Winlink and chat operators Confirm the destination’s requirements before changing modems. Complete the intended message workflow.
Emergency communications volunteers Practice a short exercise message using the group’s agreed software. Document delivery, recovery, and operator handoff.
Technical members and helpers Run paired tests and help others reproduce the setup. Share measurements and clear troubleshooting notes.

Give It a Try

Choose one achievable goal: send a short message, complete a file transfer, or help another member understand the station. Mercury offers an interesting path for experimentation, while VARA HF remains the appropriate choice for destinations using VARA.

Bring your questions and a willingness to compare notes. Share which computer you use, what you want to send, and what worked. Those practical details can help the next SARC member get on the air with confidence.

References

  1. VARA Modem and VARA HF Information; VARA HF Modem, including developer replies. José Alberto Nieto Ros, EA5HVK. Accessed September 18, 2026. https://rosmodem.wordpress.com/; https://rosmodem.wordpress.com/2017/09/03/vara-hf-modem/ ↩
  2. Mercury FreeDV Data Modes. Rhizomatica, Mercury project documentation. Accessed September 18, 2026. https://github.com/Rhizomatica/mercury/blob/mercuryv2/docs/MODES.md ↩
  3. ARQ Datalink: Architecture and Protocol Reference. Rhizomatica, Mercury project documentation. Accessed September 18, 2026. https://github.com/Rhizomatica/mercury/blob/mercuryv2/docs/ARQ.md ↩
  4. Mercury Project License: GNU General Public License, Version 3. Rhizomatica repository; license text by the Free Software Foundation. Accessed September 18, 2026. https://github.com/Rhizomatica/mercury/blob/mercuryv2/LICENSE ↩
  5. Mercury: HERMES HF Modem. Rhizomatica. Accessed September 18, 2026. https://github.com/Rhizomatica/mercury ↩
  6. Pat: A Modern Winlink Client. Pat project, Martin Hebnes Pedersen and contributors. Accessed September 18, 2026. https://getpat.io/ ↩
  7. Mercury TNC Command Reference. Rhizomatica, Mercury project documentation. Accessed September 18, 2026. https://github.com/Rhizomatica/mercury/blob/mercuryv2/docs/TNC.md ↩
  8. Winlink Express. Winlink Global Radio Email, Amateur Radio Safety Foundation, Inc. Accessed September 18, 2026. https://winlink.org/WinlinkExpress ↩
  9. VarAC: HF/FM/SAT Digital Chat. VarAC, Irad Deutsch, 4Z1AC. Accessed September 18, 2026. https://www.varac-hamradio.com/ ↩
  10. Mercury Releases. Rhizomatica. Accessed September 18, 2026. https://github.com/Rhizomatica/mercury/releases ↩
  11. Download VarAC: Windows/Linux Prerequisites. VarAC, Irad Deutsch, 4Z1AC. Accessed September 18, 2026. https://www.varac-hamradio.com/download ↩
Events

SARC 2026 Summer Picnic Pics

SARC Members — A Great day to Celebrate

The SARC Picnic Sunday, August 30th at the reserved cabin in Bartlett.

We had plenty of room to eat, relax, catch up with friends, and enjoy the afternoon.

What a year it has been for SARC. Our members have stepped up again and again to support our community, providing communications assistance for events like the Chicagoland Marathon, the MS Society, the Hoffman Estates Fourth of July Parade, and many others. 

When our community called, SARC answered — and we did a fantastic job. Se we celebrated with some good company, and celebrate the work we’ve done together.

RHG Articles Software-Defined Radio

AntSDR T510 1 MHz to 6 GHz and 2 GHz Bandwidth

AntSDR T510 AI Pre-Launch

Direct RF Input Up to 2 GHz Baseband Bandwidth per Channel

Here is an ambitious software-defined radio project for SARC members who enjoy radio, software, signal processing, and hands-on experimentation. The AntSDR T510 AI combines a high-speed RF system-on-chip with an integrated NVIDIA Jetson computing module. That pairing is intended to move signal capture, digital processing, visualization, and AI-assisted analysis onto one platform.[1]

Pre-launch note: As of August 19, 2026, the official Crowd Supply page labels this project “Coming Soon.” It does not list an official price, order date, campaign date, or shipping schedule. Product details may change, so readers should check the official project page before making plans or purchases. RTL-SDR.com reported the pre-launch announcement on August 18, 2026.[1][2]

Topic Snapshot

AntSDR T510 AI topic overview
Item Details
Subject An integrated computing platform for real-time wireless sensing
Product AntSDR T510 AI
Project status Pre-launch; the official page says “Coming Soon”
Published RF coverage Direct RF input coverage from 1 MHz to 6 GHz
Published bandwidth Up to 2 GHz of baseband bandwidth per channel
Core architecture AMD Zynq UltraScale+ RFSoC ZU47DR, eight ADC channels, eight DAC channels, and an integrated NVIDIA Jetson module
Post idea from Paul Meyers – KE9EJX
Audience SARC members, visitors, new hams, the public, and operators
Key question How would you use the ANTSDR-T510?

The status and specifications in this snapshot come from the current MicroPhase project page.[1]

What Is the AntSDR T510 AI?

SDR means software-defined radio. In a conventional radio, many operating functions are fixed in hardware. An SDR moves functions such as tuning, filtering, modulation, demodulation, and spectrum display into digital processing.

The T510 AI takes that idea much further than a typical USB receiver. MicroPhase says the platform uses an AMD Zynq UltraScale+ RFSoC ZU47DR. RFSoC means radio-frequency system-on-chip. It combines high-speed RF data converters, programmable logic, and embedded processors in one device.

The RFSoC Handles Fast, Predictable Processing

The platform supports digital mixing, digital downconversion and upconversion, interpolation, decimation, buffering, and multichannel synchronization. A digital downconverter, often shortened to DDC, selects and reduces a portion of a sampled signal for further processing. A digital upconverter, or DUC, prepares a digital signal for conversion back toward RF.

The published architecture includes eight synchronized 14-bit analog-to-digital converter channels operating at up to 5 GSPS and eight synchronized 14-bit digital-to-analog converter channels operating at up to 9.85 GSPS. GSPS means billions of samples per second. The manufacturer describes this as an 8T8R architecture: eight transmit converter channels and eight receive converter channels.[1]

Those numbers describe converter resources. They do not, by themselves, confirm eight independent full-duplex radios, maximum usable sensitivity, transmitter power, or the amount of data that can be recorded from every channel at once.

The Jetson Handles Parallel Computing

The integrated NVIDIA Jetson module is intended for graphics-processing-unit, or GPU, workloads. That may include spectrum analysis, matrix calculations, feature extraction, and AI inference. Inference means applying a trained model to new data.

The official specifications identify an NVIDIA Jetson module, while the power-consumption note refers generally to “Jetson NX @15W” without giving an exact model number. RTL-SDR’s report alternates between Jetson Orin Nano and Jetson Orin NX. Therefore, neither model should be treated as confirmed until MicroPhase publishes the final configuration.[1][2]

Understanding the Headline Specifications

What the published specifications mean in practical terms
Published item Plain-language meaning Important limit or question
1 MHz to 6 GHz The official page states direct RF input coverage across this range. This is not permission to transmit everywhere in the range. The page does not separately publish complete transmitter coverage or output specifications.
Up to 2 GHz per channel This is the stated maximum baseband bandwidth available in the digital front end. It does not confirm that all eight channels can simultaneously stream or record 2 GHz each to the Jetson, a host computer, or storage.
8T8R The design includes eight ADC and eight DAC channels with synchronization. Port routing, full-duplex behavior, isolation, calibration accuracy, and phase-coherence limits still need confirmation.
Clocking and timing The page lists external, onboard oven-controlled or temperature-compensated crystal oscillator options (OCXO or TCXO), and GPS clock options, plus PPS triggering and multi-board synchronization. The required accessories and achievable timing accuracy are not stated.
High-speed connections The RFSoC side lists a 100 G QSFP28 high-speed optical interface. The platform also lists Gigabit Ethernet and USB, plus Jetson-side USB, HDMI, Ethernet, and M.2 SSD expansion. The official page does not publish an end-to-end sustained streaming or recording rate for any simultaneous-channel configuration.
Software The official page advertises Ubuntu 22.04 with NVIDIA’s GPU development platform, CUDA, plus WaveSight, GNU Radio, SoapySDR, an IQTAXI driver framework, and Python or C++ development. Drivers, examples, documentation, and open-source resources are still developing during the pre-launch period.

These published specifications are summarized from the official MicroPhase project page.[1]

MicroPhase says WaveSight is intended to visualize, monitor, record, and replay as many as eight synchronized RF channels. The same page advertises GNU Radio and SoapySDR compatibility and a SignalLab AI demonstration for classifying Wi-Fi, Bluetooth, and modulation types.[1]

MicroPhase says additional hardware references, firmware sources, high-speed transfer examples, bare-metal demonstrations, and Jetson workflows are planned. The public GitHub repository already contains image-building resources, but its README says detailed documentation will be added later. That is a useful reminder to treat the software environment as evolving.[1][3]

How It Works

The following diagram is a simplified educational view. A real station may also need band-specific filters, attenuators, amplifiers, switches, input protection, calibration, test equipment, and suitable antennas.

---
config:
  markdownAutoWrap: true
  flowchart:
    wrappingWidth: 220
    useMaxWidth: true
    nodeSpacing: 40
    rankSpacing: 50
---
flowchart TD
    A["`Choose a receive-only
or licensed experiment`"]

    B{"`Choose a
project path`"}

    C["`Connect an antenna or lab source
through suitable input protection`"]

    D["`ADC and RFSoC:
sample, synchronize, filter,
and channelize`"]

    E["`Jetson or host:
display, classify, or record`"]

    F["`Generate a test waveform
under operator control`"]

    G["`RFSoC and DAC:
process and convert`"]

    H["`Use a dummy load or shielded
test setup first`"]

    I["`Measure emissions and add
proper filtering before
connecting an antenna`"]

    A --> B

    B -->|"Receive"| C
    C --> D
    D --> E

    B -->|"Transmit"| F
    F --> G
    G --> H
    H --> I

What Could SARC Members Explore?

The ideas below are possible learning projects based on the published architecture. They are not promises about final product performance.

Build a Receive-Only Spectrum Demonstration

Start with one receive channel and a narrow, known portion of an amateur band. Use GNU Radio or WaveSight to show a waterfall, select a signal, change the sample rate, and demonstrate decimation. This gives newer hams a clear view of how bandwidth and digital filtering work.

Compare Antennas with Synchronized Channels

Two or more synchronized inputs could support experiments that compare antennas, polarization, phase, or arrival time using a known club signal or amateur beacon. Accurate direction-finding or phased-array work would require careful channel calibration, matched RF paths, and a well-designed antenna array.

Study FPGA, CPU, and GPU Workloads

If the released firmware and development files expose the required processing paths, a club team could compare how a fast Fourier transform, filter, or channelizer is implemented with embedded processing, FPGA logic, and the Jetson GPU. This would show why some work belongs in deterministic FPGA logic while other work fits a CPU or GPU. A fast Fourier transform, or FFT, converts sampled data into a frequency display.

Evaluate Signal Classification

Members interested in AI could train or test a classifier using SARC’s own labeled recordings, generated test signals, or known amateur modes. Keep a human in the loop. Compare the model’s result with a normal spectrum display and documented measurements. Classification is not the same as guaranteed identification, decoding, or understanding.

Experiment with Timing and Multiple Channels

The published clock and pulse-per-second features suggest projects involving synchronized measurements. PPS is a precise timing pulse often supplied by a GPS-disciplined source. A project could compare timestamps or phase across channels while documenting the limits of the setup.

A Practical Way to Start

  1. Write one clear question. For example: “Can two synchronized receivers measure the phase difference from a known 2-meter beacon?”
  2. Choose the smallest useful bandwidth. A voice, digital-mode, or beacon experiment does not need a 2 GHz data stream.
  3. Begin receive-only. Use a known signal and learn the software before adding a transmit path.
  4. Plan the RF front end. Select an antenna, band-pass filter, attenuator, input protection, and low-noise amplifier only when the experiment requires them.
  5. Plan the data path. Estimate channel count, sample format, rate, storage, and recording time before collecting data.
  6. Record the configuration. Note firmware, software, clock source, gain, frequency, sample rate, filter settings, cables, and antennas so another member can repeat the test.

What to Verify Before Ordering

Because the project is still in pre-launch, a careful buyer should confirm the following items on the official page:

  • Final campaign price, included hardware, ordering terms, and shipping estimate
  • Exact NVIDIA Jetson model, memory, storage, and cooling configuration
  • Receiver sensitivity, noise figure, dynamic range, and input protection
  • Transmit frequency coverage, output power, filtering, spectral purity, and port routing
  • Maximum simultaneous channel count and sustained bandwidth for display, streaming, and recording
  • Clock accuracy, channel-to-channel phase performance, and calibration procedure
  • Current GNU Radio, SoapySDR, WaveSight, IQTAXI, Python, and C++ support
  • Which schematics, firmware, examples, and APIs are published under open-source licenses
  • Power-supply requirements, accessories, warranty, support, and applicable regulatory information

Transmit and Safety Reminder

A radio that covers a wide frequency range does not authorize transmission throughout that range. In the United States, every over-the-air amateur transmission must remain within the frequencies and privileges available to the control operator. The emission type must be authorized, the occupied bandwidth must be no wider than necessary, spurious emissions must be controlled, and the minimum power needed should be used.[4]

Start transmit development into a suitable dummy load that matches the confirmed port impedance, or use a properly shielded test setup. Verify the signal with test equipment. Then add the correct filtering and confirm connector, impedance, drive-level, power, and RF-exposure requirements before connecting an antenna or amplifier.

New and unlicensed participants can help with receive-only demonstrations, software, documentation, and data analysis. Any on-air transmission should occur under the control of an amateur operator whose license privileges authorize that frequency and emission. As a practical safeguard, AI-assisted station decisions should remain under the supervision of the control operator, who must be able to stop transmission and verify that the station is operating correctly.[4]

Suggested SARC Goals

Possible AntSDR T510 AI learning goals for different club members
Member type Suggested goal Good first step
New ham or visitor Understand a waterfall, sample rate, filter width, and decimation. Join a supervised, receive-only demonstration using one channel.
Active operator Compare antennas or filters on a familiar amateur band. Define one known signal and one repeatable measurement.
Software experimenter Build a GNU Radio, SoapySDR, Python, or C++ receive workflow. Start with a narrow bandwidth and save the configuration.
RF builder Design a protected, filtered front end for one amateur band. Document expected signal levels before connecting the SDR.
AI student Evaluate a classifier with known, labeled club signals. Create a small test set and measure false identifications.
Club volunteer Prepare a safe public demonstration. Build a short receive-only lesson with a diagram and checklist.

Give It a Try

The AntSDR T510 AI is not a simple plug-in receiver. It appears to be a development platform for people who want to study wideband signals, synchronized channels, programmable logic, GPU computing, and AI-assisted analysis. That also makes it a useful discussion topic for a club with members at many experience levels.

Start with one question and one receive channel. Keep the bandwidth small. Measure what the system actually does. Then add channels, timing, or GPU processing only when the project needs them.

How would you use the ANTSDR-T510? Bring a project idea to SARC. It could become a future club demonstration, article, workshop, or team experiment.

How would you use the ANTSDR-T510?

References

  1. AntSDR T510 AI. MicroPhase Technology, hosted by Crowd Supply. Accessed August 19, 2026. https://www.crowdsupply.com/microphase-technology/antsdr-t510-ai ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h
  2. AntSDR T510 Pre-launch: A 1 MHz to 6 GHz SDR with 2 GHz Bandwidth and a Built-In NVIDIA Jetson. RTL-SDR.com. Written by admin. Published August 18, 2026. Accessed August 19, 2026. https://www.rtl-sdr.com/antsdr-t510-pre-launch-a-1-mhz-to-6-ghz-sdr-with-2-ghz-bandwidth-and-a-built-in-nvidia-jetson/ ↩a ↩b
  3. T510-AI Image Builder. MicroPhase Technology, GitHub. Accessed August 19, 2026. https://github.com/MicroPhase/T510-AI ↩
  4. 47 CFR Part 97 — Amateur Radio Service. Federal Communications Commission, Electronic Code of Federal Regulations. Accessed August 19, 2026. See especially §§ 97.13(c), 97.109, 97.301, 97.305, 97.307, and 97.313. https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97 ↩a ↩b
RHG Articles

Learn STM32 Microcontroller Programming

Full Course for EE/CS Students and Beginners

Here is a practical learning idea for SARC members who enjoy electronics, programming, test equipment, or station automation. The linked STM32 course starts with basic embedded-system concepts and builds toward hands-on projects. You do not need to be an electrical engineering (EE) or computer science (CS) student to begin.

STM32 programming gives radio builders a useful bridge between software and real hardware. Start with a small low-voltage circuit, learn what each line of code does, and grow one tested step at a time.

Topic Snapshot

STM32 learning opportunity at a glance
Item Details
Subject STM32 Microcontroller Programming – Full Course for EE/CS Students and Beginners Version 3
Post idea from Paul Meyers – KE9EJX
Audience SARC members, visitors, new hams, the public, operators, and volunteers
Format Self-paced YouTube course with 34 projects
Course length Approximately 11 hours and 3 minutes[1]
Hardware Course-compatible STM32 hardware and project parts; compare each lesson with the current kit listing before buying
Schedule or deadline None provided; learn at your own pace
Call to action Learn STM32

Start With the Full Course

BuildYourCNC presents this long-form course as a project-based introduction for students and beginners. The lessons move from the development environment and basic bit operations to physical inputs, outputs, displays, measurements, timing, communications, circuit-board work, and experiments with AI-generated code.

Build Your CNC’s full STM32 programming course for EE/CS students and beginners, Version 3.

Watch the STM32 full course on YouTube.

What Is an STM32 Microcontroller?

A microcontroller is a small computer built into one integrated circuit. It runs firmware, which is the program stored on the device. It can read switches and sensors, control LEDs and displays, measure signals, keep time, and exchange data with other equipment.

STM32 is not one interchangeable board or chip. It is a large family of 32-bit microcontrollers from STMicroelectronics based on Arm Cortex-M processor cores.[4] Different STM32 parts have different pins, memory, peripherals, and electrical limits. Always match the exact device and board named in a lesson.

Beginner reminder: Matching the word “STM32” is not enough. Confirm the complete chip or board number, pinout, programmer, supply voltage, and software setup.

Why STM32 Skills Matter to Amateur Radio

Amateur radio combines communication, electronics, software, measurement, and experimentation. A microcontroller can become the control center for a future station accessory or test project.

Possible SARC experiments include a station-status display, environmental sensor, battery monitor, practice keyer, antenna-switch controller, rotator interface, telemetry display, or test fixture. These are examples of where the skills may lead. They are not projects promised by the course.

Radio work also adds special design concerns. RF energy, ground loops, electrostatic discharge, voltage differences, and transceiver control lines can damage a board or radio. Do not connect a microcontroller pin directly to an antenna feed line, push-to-talk line, keying line, or transceiver accessory port. First verify the radio manual and design the correct buffering, level conversion, protection, or isolation.

What the Course Covers

The 34-project course follows a broad path from first setup to more involved hardware and software work.[1] It is not specifically a ham-radio course, but many of the underlying skills transfer well to club projects.

A practical learning map for the course
Learning stage Topics in the course Why the skill is useful
Foundations STM32CubeIDE setup, project creation, programming, runtime monitoring, troubleshooting, and bit manipulation Builds the basic workflow for turning source code into running firmware
Digital control LEDs, push buttons, and latching inputs Introduces general-purpose input/output, usually shortened to GPIO
Displays and data LCD interfacing, strings, pointers, integers, and floating-point output Helps a project present measurements and status information
Measurement and timing Analog-to-digital conversion, internal temperature, potentiometer input, timers, counters, pulse-width modulation, and interrupts Supports sensor reading, event timing, and controlled outputs
Communication and construction I2C accelerometer communication, USART serial communication, KiCad printed-circuit-board work, and AI-assisted coding comparisons Connects the controller to other devices and introduces a path toward a finished circuit board

I2C is a short-distance digital bus used to connect integrated circuits. USART is a hardware interface for serial data. PWM, or pulse-width modulation, controls the average power delivered to a load by changing pulse timing. An ADC, or analog-to-digital converter, turns a measured voltage into a number the program can use.

Choose the Hardware Carefully

The supplied BuildYourCNC link opens a collection, not one package containing every part for every course project. The collection includes several STM32F0 kit levels, development hardware, a programmer, a book, and related parts.[2]

For example, the currently listed beginner kit includes an STM32F030 on a breakout board, an ST-Link V2 programmer and connection cable, three solderless breadboards, jumper wires, buttons, LEDs, resistors, and capacitors. Its listing says that sensors, displays, voltage regulators, crystals, and serial adapters are not included.[3]

Therefore, watch the course overview and inspect the parts needed for the projects you want to build before ordering. Kit contents, prices, stock, and software requirements may change. Check the seller’s current page and STMicroelectronics’ official documentation.

How the Development Setup Works

Write, Build, and Debug

STM32 Cube IDE is STMicroelectronics’ C/C++ integrated development environment, or IDE. It provides tools for editing, compiling, and debugging STM32 code on supported Windows, Linux, and macOS systems.[5] The course demonstrates a specific release, so menus may look different in a newer version. Check the official download page for the current release and system requirements.

Configure the Device

STM32CubeMX is ST’s graphical configuration and code-generation tool. It can help select a device or board, assign pins, configure clocks and peripherals, and generate initialization code.[6] It saves setup time, but it does not replace the need to read the board documentation, device datasheet, and reference manual.

Program the Microcontroller

An ST-LINK is an in-circuit programmer and debugger. It can load firmware and communicate with compatible STM32 hardware through interfaces that include Serial Wire Debug, or SWD.[7] Some boards need a separate probe. Many STM32 Nucleo boards include an ST-LINK on the board, but that does not apply to every STM32 product.[8]

How the Learning Process Works

flowchart TD
    A["Choose one course project"] --> B["Confirm the exact chip, board, parts, and software"]
    B --> C["Build the low-voltage circuit with power disconnected"]
    C --> D["Connect the programmer and apply the correct power"]
    D --> E["Build and flash the firmware"]
    E --> F["Observe the result and use the debugger"]
    F --> G{"Does it work as expected?"}
    G -- "Yes" --> H["Change one item and test again"]
    G -- "No" --> I["Check power, ground, cable, device choice, pins, and code"]
    I --> D
    H --> J["Record the result and plan the next project"]

This same cycle appears in ST’s official beginner material: install the tools, run a first program, blink an LED, build and debug, and then move toward serial communication and sensors.[9]

How to Participate

  1. Open the full course and watch the introduction and setup sections first.
  2. Choose one project. Write down its exact microcontroller, board, programmer, parts, and software requirements.
  3. Compare that list with the current kit description. Do not assume one kit contains every course component.
  4. Install software only from the official publisher or another source you trust.
  5. Build with power disconnected. Then inspect every power, ground, and signal connection before applying power.
  6. Compile and flash a known example before changing the code.
  7. Change one thing at a time. Record what worked, what failed, and how you fixed it.
  8. Share useful notes and questions with other SARC builders.
  9. Build a SARC Taking the ESP32 Lightning Detector to the Next Level – Kent Ochs, W9KAO

What to Bring

Basic tools for a first STM32 learning session
Item Why it helps
Computer Runs the course video, development software, and documentation
Course-compatible STM32 board or kit Provides the exact target hardware used by the selected lesson
Programmer/debugger Loads firmware and helps diagnose code; it may be separate or built into the board
Correct data-capable USB cable Connects the development hardware to the computer
Breadboard, jumper wires, and lesson parts Supports low-voltage circuit experiments
Board documentation and device datasheet Confirms pin assignments, voltage limits, and electrical requirements
Digital multimeter Checks power, continuity, and signal levels before troubleshooting software
Notebook or project log Records settings, wiring, error messages, and successful changes

Safety note: Work only within the ratings in the official documentation. Never assume an input is 5-volt tolerant. Keep the first projects separate from a radio, amplifier, mains circuit, battery bank, antenna system, or other high-energy equipment.

A Good First Project

Begin with a known, low-risk example. Flash firmware that blinks one LED. Next, read a push button. Then send a short status message over the serial connection supported by your setup.

When that works, change only one timing value, input, or message. Rebuild, flash, test, and write down the result. This small loop teaches more than copying a large project that you cannot yet explain.

The course ends with AI-assisted coding comparisons. Treat generated firmware as an unverified draft. Read every line, keep compiler warnings visible, test on a current-limited low-voltage bench supply when appropriate, and never allow unreviewed code to control a transmitter, relay, motor, charger, or safety-related function.

Suggested SARC Goals

Possible goals for different learners
Participant Suggested goal
Curious visitor Watch the course introduction and learn what a microcontroller does
New programmer Build and flash one known working example
New ham Learn how firmware, pins, voltage limits, and external circuits work together
Experienced operator Prototype one isolated station-status or monitoring function
Hardware builder Practice reading a pinout and checking every power and signal connection
Volunteer Document setup steps and common troubleshooting lessons for other members
Club project team Select one small, repeatable project that members can build and explain

Give It a Try

You do not need to complete all 34 projects at once. Pick one lesson, match the hardware carefully, and aim for one clear result. A blinking LED may seem simple, but it proves that the computer, toolchain, programmer, microcontroller, power, and firmware are all working together.

Learn STM32: start the full course, review the current STM32 kit choices, and visit N9RJV.org for more SARC learning and project ideas.

 Watch the course and complete your first verified STM32 project

References

  1. BuildYourCNC. “Learn STM32 Microcontroller Programming – Full Course for EE/CS Students and Beginners Version 3.” YouTube. Published March 4, 2026. Accessed August 15, 2026. https://www.youtube.com/watch?v=vKyL43qXPpk ↩ ↩
  2. BuildYourCNC. “ARM (STM32) Microcontroller Kits.” Accessed August 15, 2026. https://buildyourcnc.com/collections/arm-stm32-microcontroller-kits ↩
  3. BuildYourCNC. “ARM Microcontroller Beginners Kit (STM32F0).” Accessed August 15, 2026. https://buildyourcnc.com/products/newbiehack-microcontroller-arm-stmicro-stm32f0r6-beginners-kit ↩
  4. STMicroelectronics. “STM32 Microcontrollers (MCUs).” Accessed August 15, 2026. https://www.st.com/en/microcontrollers-microprocessors/stm32-32-bit-arm-cortex-mcus.html ↩
  5. STMicroelectronics. “STM32CubeIDE | Software.” Accessed August 15, 2026. https://www.st.com/en/development-tools/stm32cubeide.html ↩
  6. STMicroelectronics. “STM32CubeMX | Software.” Accessed August 15, 2026. https://www.st.com/en/development-tools/stm32cubemx.html ↩
  7. STMicroelectronics. “ST-LINK/V2 In-Circuit Debugger/Programmer for STM8 and STM32.” Accessed August 15, 2026. https://www.st.com/en/development-tools/st-link-v2.html ↩
  8. STMicroelectronics. “STM32 Nucleo Boards.” Accessed August 15, 2026. https://www.st.com/en/evaluation-tools/stm32-nucleo-boards.html ↩
  9. STMicroelectronics STM32 MCU Wiki. “Getting Started with STM32: STM32 Step-by-Step.” Accessed August 15, 2026. https://wiki.st.com/stm32mcu/wiki/Category%3AGetting_started_with_STM32_%3A_STM32_step_by_step ↩