ADD Spot "Forward to DX Cluster" does not work

[luigiverdicchio1-prog]

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 Forward to Dx Cluster function doesn't work. Only Manual spots are sent.
To this day, I haven't understood the difference between the Manual function and the Forward to Dx Cluster function.

What did you expect?

No response

Steps to reproduce

Flex6400

AetherSDR version

26.5.2.1

Radio model & firmware

Flex6400 V.4.1.5

Operating system

Windows

OS version and hardware

Windows 10 Pro

[aethersdr-agent]

Thanks for the report — and for the good question about the difference between the two paths. Let me explain, then ask a few targeted questions so we can pin down why the forward isn't reaching the cluster.

What the two paths do

When you submit the Add Spot dialog:

1. Always — AetherSDR creates a local spot on the panadapter labelled source=Manual. That's where the "Manual" label you're seeing comes from. It's just a name for "this spot was created locally in the GUI by me," not a separate transport.
2. Only if "Forward to DX Cluster" is checked — AetherSDR also sends a DX <freq-khz> <call> <comment> line to whatever cluster is connected on the DX Cluster tab (see MainWindow.cpp:11023-11032).

So the local panadapter spot always says "Manual" regardless of whether you forwarded it. The forward part is a separate side-effect that goes over the DX Cluster telnet socket.

Likely root causes

Looking at the code path, the forward is silent in three cases — none of which give you any feedback:

• The DX Cluster tab is not connected (m_dxCluster->isConnected() is false at MainWindow.cpp:11024). If you only have the RBN tab connected, the forward is skipped — RBN is read-only and is a separate client.
• The cluster received the command but rejected it. DX Spider's dx command requires a non-empty <remark>. If the Comment field in the dialog is left empty, the command sent becomes DX 14025.0 W1AW (trailing space, no remark) and most cluster software silently drops it.
• The cluster accepted it but didn't echo it back to you. Some clusters don't return your own DX spot, so you'd only know if another connected user saw it.

Three quick questions to narrow it down

1. On the DX Cluster tab (not RBN), is the status showing Connected at the moment you submit the Add Spot dialog?
2. After clicking OK with "Forward to DX Cluster" checked, does the DX Cluster console show an outgoing line starting with > DX ... (the > prefix marks lines we sent)?
3. Was the Comment field empty, or did you type something into it?

If you can grab a snippet of the DX Cluster console around the time you submit the dialog (or attach the dxcluster.log from your support bundle), that would tell us in one shot whether the command is going out and what the cluster is doing with it.

---

_{📍 Citation health check (Foundry Constitution Principle I): 0 resolved, 2 unresolved against /Users/aetherclaude/workspace/AetherSDR at origin/main.}

Unresolved citations (2)

Citation	Reason
MainWindow.cpp:11023-11032	file not found in workspace
MainWindow.cpp:11024	file not found in workspace

[luigiverdicchio1-prog]

In my opinion, I would eliminate these options, making the option more streamlined.
Add Spot sends directly to the connection cluster with the current display of the same on PAN.

[aethersdr-agent]

Understood — handing this to a maintainer to decide on direction.

Summary for maintainer

Reporter: AetherSDR 26.5.2.1 on Windows 10 Pro, Flex 6400 (FW 4.1.5).

Two things are tangled in this thread:

1. Bug: "Forward to DX Cluster" checkbox in the Add Spot dialog has no observable effect for the reporter. The local "Manual" spot appears on the panadapter, but the cluster doesn't receive the DX command (or doesn't echo it back). I asked three diagnostic questions (DX Cluster tab connected? outgoing > DX … line in console? empty Comment field?) — the user didn't answer; they reframed as a UX request.

2. UX request: "I would eliminate these options, making the option more streamlined. Add Spot sends directly to the connection cluster with the current display of the same on PAN." I.e. drop the checkbox and the dual-action model — one button, always local-spot + forward-if-connected.

Code pointers

• Dialog construction (checkbox): src/gui/SpectrumWidget.cpp:3844 — forwardCheck = new QCheckBox("Forward to DX Cluster").
• Forward path: src/gui/MainWindow.cpp:11023-11032 — only fires when forwardToCluster && m_dxCluster && m_dxCluster->isConnected(). Silent on all failure modes: not connected, empty comment producing trailing-space DX 14025.0 W1AW (DX Spider drops these), or cluster accepts but doesn't echo to spotter.
• Signal signature: src/gui/SpectrumWidget.h:496 carries bool forwardToCluster through.

Suggested options for the maintainer

• Smallest fix that addresses the bug as reported: add user-visible feedback when forward is skipped/rejected — log "Forwarded to DX Cluster" or "DX Cluster not connected — spot not forwarded" to the DX Cluster console (and/or a status-bar toast). That alone would have answered the user's question and converted "doesn't work" into a clear cause.
• If the UX simplification is accepted: remove the checkbox; always forward when m_dxCluster->isConnected(); show the same feedback above so the behaviour is discoverable.
• Independent of either: require a non-empty Comment when forwarding (DX Spider rejects empty remarks) — either validate in the dialog or substitute a default like "de <mycall>".

Tagging for maintainer review.

[jensenpat]

@AetherClaude what does this mean: ADD Spot "Forward to DX Cluster" does not work

Help explain the user's use case because I don't understand it.