aethersdr / aethersdr/AetherSDR

CW Zero Beat doesn't seem to do anything

Open
#5,213 15 comments 0 reactions 1 assignee View on GitHub

@skerker is already working on this.

Since Aug 24, 2026.

bug CW GUI maintainer-review
Dominant language
C++
Stars
221
Forks
117
Avg merge
2d 7h
Merged PRs (30d)
299

Description

Report preparation
  • I used the AI-assisted bug report tool (Help → Support → File an Issue)
  • I have attached a support bundle or log file
What happened?

The Zero Beat button doesn't seem to do anything. I'm used to having it in PowerSDR but maybe I'm not doing it correctly for AetherSDR. I've tried signals that are fairly close to on-frequency on both sides and I've tried them when they were just barely in the passband. I've tried different bandwidths and I've tried it with the "Filter Edge" turned on and off with the same results. I'm using v26.8.4 but it has behaved the same on every version I've tried, at least the last 5 versions. Let me know if there's anything else I can do to help, I'm glad to be a guinea pig if there's anything I can test. If I'm doing something wrong, it won't hurt my feelings if you guys just correct me!

Thanks,
Kerry Miller
kerrygeek@gmail.com

What did you expect?

No response

Steps to reproduce
  1. Start radio
  2. Switch to CW mode
  3. Tune in a CW signal in the rx passband but not quite zero beat at any bandwidth.
  4. Click the Zero Beat button, nothing happens.
  5. Repeat with signals above and below zero beat, both close to zero beat and almost out of the passband with the same results.
    Let me know if I'm doing something wrong, if you need any more information or if there's anything else I can do to help.

Thanks,
Kerry Miller, WD5ABC
kerrygeek@gmail.com

AetherSDR version

26.8.4

Radio model & firmware

Flex 6400 hw version 4.2.20.51343

Operating system

Windows

OS version and hardware

Windows 11 25H2 build 26200.9168

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.