Skip to content

[memory] Restore repeater offset, tone details on memory recall#2080

Merged
ten9876 merged 1 commit into
aethersdr:mainfrom
jensenpat:aether/fix-memory-repeater-recall
Apr 27, 2026
Merged

[memory] Restore repeater offset, tone details on memory recall#2080
ten9876 merged 1 commit into
aethersdr:mainfrom
jensenpat:aether/fix-memory-repeater-recall

Conversation

@jensenpat

Copy link
Copy Markdown
Collaborator

Summary

  • Reapply recalled FM repeater direction, repeater offset, and CTCSS tone settings after memory apply
  • Derive tx_offset_freq from the recalled memory direction/offset so stale transmit offsets are cleared
  • Add a focused memory recall policy test covering up, down, simplex, and tone fix-up command generation

Root Cause

The radio restores memory fields like repeater direction and offset during recall, but the derived slice field tx_offset_freq can remain stale. Both quick recall and the Memory dialog route through MainWindow::activateMemorySpot(), so the fix-up lives there and applies to both paths.

Validation

  • ./build/memory_recall_policy_test
  • cmake --build build -j 10
  • User confirmed recalled repeater memories now work correctly on radio

Fixes #1871
Fixes #1965

👨🏼‍💻 Generated with OpenAI Codex (GPT-5.5 Pro 4/23) and tested by @jensenpat

@jensenpat jensenpat changed the title Restore repeater details on memory recall [memory] Restore repeater offset, tone details on memory recall Apr 27, 2026
@jensenpat jensenpat marked this pull request as ready for review April 27, 2026 04:24
@ten9876 ten9876 merged commit 59884f6 into aethersdr:main Apr 27, 2026
5 checks passed
ten9876 added a commit that referenced this pull request Apr 27, 2026
Local iambic CW keyer (#2079), unified sidetone controls, CW pan
slider wiring, slice capacity notification (#48), three latent
netcw protocol bugs that prevented CW transmit on FLEX-8600 v4.1.5
firmware, optimistic updates for cwIambic/iambicMode/cwSpeed/cwPitch,
PortAudio JACK preference for sub-5 ms sidetone on Linux, plus the
graceful disconnect (#1997), memory recall (#2080), per-slice
compression meter (#2073), and m_activeTxSlice (#2078) fixes from
the community.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Memory recall not setting the repeater offset correctly Incorrect transmit frequency after restore from MEM-A

2 participants