¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

QDX-HB problem TX WSPR


 

Hallo
My QDX:
Range is 10-12-15-17-20-30m.

QDX-Soft V1.09 (PC-Soft WSJT / JTDX)? CAT using TS-440S
Problem: TX does not work correctly in WSPR mode (RX ok at the same time)
Tested on 30 and 20m.
TX seems to works, signal also in control RX visible, frequency plausible, but no response in WSPR network or control RX. Different computer, same effect.
FT8, FT4, MFSK, RTTY, Olivia, Terminal etc ok.
WSJT only works with Vox, CAT-PTT does not work.
What could this be?
73 Reiner


 

¿ªÔÆÌåÓý

Reiner,

The following work for me using a Raspberry Pi. The serial port may be different for you if you are running some other operating system.

If you have Wsjtx 2.6.1 then the setup like this works for CAT/PTT:


For older versions of Wsjtx then use the TS-480 as the rig.


73,
Cliff, AE5ZA



On Apr 11, 2023, at 15:26, dl8lrz Reiner <dl8lrz@...> wrote:

Hallo
My QDX:
Range is 10-12-15-17-20-30m.

QDX-Soft V1.09 (PC-Soft WSJT / JTDX)? CAT using TS-440S
Problem: TX does not work correctly in WSPR mode (RX ok at the same time)
Tested on 30 and 20m.
TX seems to works, signal also in control RX visible, frequency plausible, but no response in WSPR network or control RX. Different computer, same effect.
FT8, FT4, MFSK, RTTY, Olivia, Terminal etc ok.
WSJT only works with Vox, CAT-PTT does not work.
What could this be?
73 Reiner


 

Is the high band QDX version meant to do 30m?
I was under the impression it was 10-20m.
Mike N0QBH


 

On 12/04/2023 05:36, Mike Berg wrote:
Is the high band QDX version meant to do 30m?
Mike

No, I guess it would probably work but an external LPF would be essential.

Reiner,

If only WSJT-X does not work then it would seem to be something in your configuration. What version of WSJT-X? Best use the latest. What operating system? Has Cliff helped? Note the QCX/QDX setting in Cliff's picture.

73 Alan G4ZFQ


 

Tnx to everyone for the replies.
Hello Cliff,
the QDX sends with your settings, but the signal is not decoded in the other device (PC, IC7300). If the other device is transmitting, I can receive the signal. Time difference -0.1
In the waterfall (PC, IC7300) I can see: If the QDX sends, a vertical line is generated. If I receive real WSPR signals, a small frequency shift is recognizable. The modulation of the transmission signal in the QDX seems to be missing, regardless of whether it is 20 or 30m. PWR in WSJT to 100%, QDX in sound setting (WIN-11) 100%
For the others:
I didn't use the 11m band, added the 30m band instead. The LP filter (30+20m) was taken from the QDX-LB, the RX filter for 30/20/17+15/12+10m changed.
73 Reiner

Now, brand new
All WSJT-based programs (WSJTX, JTDX) do not recognize the QDX for input, only for output.
FlDigi has no problems. Terminal works. I'm going to take a break, this is crazy.


 

On 12/04/2023 10:24, dl8lrz Reiner wrote:
If the QDX sends, a vertical line is generated. If I receive real WSPR signals, a small frequency shift is recognizable. The modulation of the transmission signal in the QDX seems to be missing, regardless of whether it is 20 or 30m. PWR in WSJT to 100%, QDX in sound setting (WIN-11) 100%
Reiner,

Do you measure power output from the QDX?
I am wondering if your receiver is just seeing an unmodulated 5351 output.
Is the LED gently pulsating, NOT flashing?
You have set the microphone privacy?

But none of these questions seem to make any sense if the QDX works correctly with different software..

73 Alan G4ZFQ


 

Have you done the reference frequency calibration? If you are not within the 200 Hz WSPR window your signal will not be decoded.

Steve N9SZ


 

Yes, WSPR also requires a < 2 sec time sync between the transmitter and receiver in addition to the 200 hz window.

73, Joe W2JEJ


On Wed, Apr 12, 2023, 8:25 AM Steve Z <zabarnick@...> wrote:
Have you done the reference frequency calibration? If you are not within the 200 Hz WSPR window your signal will not be decoded.

Steve N9SZ


 

The problem is the laptop, not the QDX
I compared again:
TRX: IC-7300 with QDX Computer; Desktop (HP) with Laptop (Huawei Matebook)
The error is only in WSPR, only on the laptop (TX without modulation, sound card lost). FT4, FT8 is ok, FLdigi is ok.
The error moves with the Matebook, the QDX also works on the PC (HP).
Something in the laptop doesn't like WSPR I think, no matter which TRX - IC7300 or QDX
Thanks for the help
73 Reiner


 

Are you using a time sync program on the non-working laptop?


On Thu, Apr 13, 2023, 7:57 AM dl8lrz Reiner <dl8lrz@...> wrote:
The problem is the laptop, not the QDX
I compared again:
TRX: IC-7300 with QDX Computer; Desktop (HP) with Laptop (Huawei Matebook)
The error is only in WSPR, only on the laptop (TX without modulation, sound card lost). FT4, FT8 is ok, FLdigi is ok.
The error moves with the Matebook, the QDX also works on the PC (HP).
Something in the laptop doesn't like WSPR I think, no matter which TRX - IC7300 or QDX
Thanks for the help
73 Reiner


 

Is your Start Time, ?Menu 6.4, ?set to an even numbered minute? ?If it is set to an odd minute you will see your waterfall trace continue through the blank period just preceding the start of an even numbered minute. ?


I thank Al Holt for leading me to the KiwiSDR website!

Bob VE3HIR


 

The problem is solved,
the QDX works with WSJT / WSPR.
The cause was a conflict of a USB driver, probably the driver of my programmer "myAVR", which the computer wanted to use to communicate with the QDX.
After uninstalling all unused USB entries, the problem went away.
Thanks to all
73 Reiner


 

Just got my new builded version of qdx... and also as in this line,, no rx or tx in wspr...
running win 11, and found that the pc-clock was 13 secs. wrong...
after a update of the clock, it worked as it should.

vy 73 de Lars oz1fjb - ou2v