Skip to content

Flexradio 6700 missing 144 and 70Mhz #695

Description

@Juanjo-EA1CJ

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?

Add 2m (144 MHz) and 4m (70 MHz) Band Support for FlexRadio 6700

Labels: enhancement, GUI, protocol, external devices


What

Add 2m (144 MHz) and 4m (70 MHz) to the band selector for the FlexRadio 6700
model. Currently, these amateur bands are absent from the band list in
AetherSDR when connected to a 6700, making it impossible to tune to those
frequencies via the band selector UI.


Why

The FlexRadio 6700 supports 2m (144–148 MHz) and 4m (70–70.5 MHz, region
dependent) natively. These are active DX and contesting bands — especially
2m EME/tropo and 4m Es — and the omission forces users to manually type
frequencies into the VFO widget as a workaround instead of using the
standard band selector. This is a regression compared to what the radio
itself advertises and what SmartSDR exposes.


How Other Clients Do It

  • SmartSDR (Windows): Exposes 144 and 70 as selectable bands in
    the Band drop-down for 6700. Historical SmartSDR versions had a known
    crash/hang on 144 MHz band selection for the 6700 (fixed in later
    firmware), so care is needed with the FlexLib command flow.
  • GQRX / SDR++: Frequency is entered directly; no radio-model-aware
    band gating is relevant.
  • Ham Radio Deluxe: Populates band list based on radio capabilities
    reported at connection time.

Suggested Behavior

  1. On connection to a FlexRadio 6700, AetherSDR queries the radio's
    supported band list via FlexLib.
  2. The Band Selector (AppletPanel / VfoWidget band drop-down) displays
    2m (144 MHz) and 4m (70 MHz) entries alongside existing HF bands.
  3. Selecting 2m tunes the active RxApplet VFO to 144.200 MHz (SSB
    calling frequency) as a sensible default; selecting 4m tunes to
    70.200 MHz.
  4. Band edges are enforced: 144.000–148.000 MHz for 2m; 70.000–70.500 MHz
    for 4m (or region-configurable).
  5. Band memory (if implemented) persists mode and frequency per band, as
    it does for HF bands.

Protocol Hints

FlexLib / VITA-49 relevant commands (to be verified against FlexLib source):

What did you expect?

  • 2m (144 MHz) appears in the band selector when connected to a
    FlexRadio 6700 running firmware ≥ 3.x or 4.x
  • 4m (70 MHz) appears in the band selector when connected to a
    FlexRadio 6700 (hardware-dependent; should be hidden if radio
    reports 4m as unsupported)
  • Selecting either band tunes the VFO to the correct calling frequency
    without a crash or hang
  • Band selector does not show 2m/4m for radio models that do not
    support those bands

Environment

  • OS: Windows 11 (reported via AetherSDR; also relevant to Linux/Mac
    builds since band list logic is shared)
  • Radio model: FlexRadio 6700
  • Firmware: 4.1.5
  • AetherSDR version: (please fill in)

Steps to reproduce

No response

Radio model & firmware

Flex 6700 4.1.5

Linux distro & Qt version

Windows 11

Metadata

Metadata

Assignees

No one assigned

    Labels

    GUIUser interfacebugSomething isn't workingenhancementImprovement to existing featuremaintainer-reviewRequires maintainer review before any action is takenprotocolSmartSDR protocol

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions