[bug] FLEX-8400 v26.9.3 — AetherSDR 26.9.3: 2016 ThumbDV DV3000U not detected on macOS

What happened?

AetherSDR 26.9.3: 2016 ThumbDV DV3000U not detected on macOS

What did you expect?

Please see Info generated with ChatGPT below

Steps to reproduce

1. First step
2. …

Radio model & firmware

• Model: FLEX-8400
• Firmware: 4.2.20.41343
• Protocol: 1.4.0.0
• Callsign: DH5IS
• Serial: --****-1586
• Connection: connected

OS & version

• AetherSDR: 26.9.3
• Qt: 6.8.3
• OS: macOS 27.0 (kernel 27.0.0)
• CPU: Apple M4 (arm64)
• RAM: 16384 MB
• GPU: Auto (system default — no override)
• Build: Sep 13 2026

Recent log

(Recent log omitted from this link to keep it short — see the attached support bundle, or paste it from your clipboard.)

AetherSDR 26.9.3 – 2016 ThumbDV DV3000U not detected on macOS

Environment

• AetherSDR: 26.9.3
• Radio: Flex-8400
• Flex firmware: 4.x
• OS: macOS
• ThumbDV: DV3000U, purchased from NW Digital Radio at Hamvention 2016
• Serial device: /dev/cu.usbserial-DN00W4CR
• AetherSDR D-STAR waveform is present and the D-STAR tab is available under Tools → AetherModems.

Problem

AetherSDR does not detect/initialize the ThumbDV.

The bundled aether-dv-waveform binary explicitly contains support for both 460800 and 230400 baud and appears to automatically fall back from 460800 to 230400.

I tested the bundled executable directly:

/Applications/AetherSDR.app/Contents/MacOS/aether-dv-waveform \
  --probe-serial \
  --serial /dev/cu.usbserial-DN00W4CR

Output:

Trying to open serial port /dev/cu.usbserial-DN00W4CR

ThumbDV: the OS serial API does not expose the FTDI latency timer; continuing.

TimeOut #1

Could not reset serial port FD = 0x102f6e430

Could not detect ThumbDV at 460800 Baud. Trying 230400

TimeOut #1

Could not reset serial port FD = 0x102f6e430

Could not detect ThumbDV at 230400 Baud

AETHER_DV_ERROR No valid DV3000 reset response was received

Additional observation

strings on the bundled aether-dv-waveform shows:

Could not configure ThumbDV at 460800 Baud. Trying 230400
Could not detect ThumbDV at 460800 Baud. Trying 230400
Could not configure ThumbDV at 230400 Baud
Could not detect ThumbDV at 230400 Baud
Unable to set ThumbDV baud rate %lu
ThumbDV: the OS serial API does not expose the FTDI latency timer; continuing.
No valid DV3000 reset response was received

It also supports:

--probe-serial
--serial
AETHER_DV_THUMBDV_SERIAL
THUMBDV_SERIAL

The device therefore appears to open successfully, but the DV3000 reset response is never received at either supported baud rate.

Question

Could there be a compatibility issue with early-generation ThumbDV/DV3000U hardware from 2016 and the current AetherSDR DV3000 initialization/reset sequence on macOS?

In particular, could you confirm whether the current implementation is expected to work with the early 230400-baud ThumbDV hardware?

I can provide additional logs or test results if required.

Start by reproducing the issue with the bundled aether-dv-waveform binary using --probe-serial and the reported /dev/cu.usbserial-DN00W4CR device. Trace the ThumbDV detection and reset sequence behind the 460800/230400 baud attempts, then verify behavior with the reported early DV3000U hardware. Done means establishing whether this hardware is supported on macOS and identifying a concrete compatibility fix or documented limitation.