¿ªÔÆÌåÓý

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

#QCX+ #QCXmini #WSPR beacon callsign length #qcxmini #wspr


 

Hello Hans,

I need to use QCX+ and QCXmini as a WSPR transmitter on my second location therefore my callsign will be YO3FFF/P.
All good but I realize that is not possible with the actual/latest FW (1.07).
To set callsign for WSPR I used menu: 6 Beacon/6.5 WSPR call
On that, one can use maximum 6 characters so, my "/P" or else does not fit in.

Any workaround please?

Thank you.

73 de YO3FFF
Cristi


 

Hi Cris, Does this link help?






Glory to God in the highest, and on earth peace, good will toward men. Luke 2:14


 

Hi Cristi

Sending extended call signs or 6-character locators in WSPR requires two WSPR transmissions. At the receiving end it makes use of the 15-bit hash-code to match up the the two transmissions. There are several disadvantages. The requirement that two transmissions are received reduces the probability of successful decodes. Furthermore since the hash-code is only 15 bits there is quite a high probability of a clash with other WSPR users having the same hash code.?

In my opinion extended format WSPR should be avoided except in cases where you need the higher resolution of 6-character Maiden head grid subsquare for example, if you are tracking a mobile transmitter.?

If you want to differentiate between transmissions from two different locations, using the same callsign, there are other ways to do it than using the double-transmissions and its inherent disadvantages. If the locations are far enough apart to be in different grid squares you'll be able to differentiate them easily anyway. Another way is to transmit in different time slots e.g. one station starts at 2, 12.22 etc minutes past the hour and the other at 4, 14, 24, etc. Or you could configure them to have different indicated power levels - it is only a coarse approximation anyway and if your TXs are both putting out 3W say, it will not matter and nobody will care, if you set one of them to 33dBm and one to 37dBm.?

These are the workarounds I can think of.?

73 Hans G0UPL
http://qrp-labs.com


-------- Original message --------
From: "cris blak via groups.io" <cyo3fff@...>
Date: Tue, Dec 14, 2021, 9:54 PM
To: "[email protected] Notification" <[email protected]>, [email protected]
Subject: [QRPLabs] #QCX+ #QCXmini #WSPR beacon callsign length
Hello Hans,

I need to use QCX+ and QCXmini as a WSPR transmitter on my second location therefore my callsign will be YO3FFF/P.
All good but I realize that is not possible with the actual/latest FW (1.07).
To set callsign for WSPR I used menu: 6 Beacon/6.5 WSPR call
On that, one can use maximum 6 characters so, my "/P" or else does not fit in.

Any workaround please?

Thank you.

73 de YO3FFF
Cristi


 

Hi Hans,

I never dig deep into WSPR to know such limitation. Before U3/QCX I've used the original WSPR/WSJT-X programs and in there such "/P" is allowed.

So I can say this is the limitation of the QCX WSPR implementation, part due to the WSPR protocol.

Thank you for clarification.

73 de YO3FFF
Cristi

Pe mar?i, 14 decembrie 2021, 22:41:19 EET, Hans Summers <hans.summers@...> a scris:


Hi Cristi

Sending extended call signs or 6-character locators in WSPR requires two WSPR transmissions. At the receiving end it makes use of the 15-bit hash-code to match up the the two transmissions. There are several disadvantages. The requirement that two transmissions are received reduces the probability of successful decodes. Furthermore since the hash-code is only 15 bits there is quite a high probability of a clash with other WSPR users having the same hash code.?

In my opinion extended format WSPR should be avoided except in cases where you need the higher resolution of 6-character Maiden head grid subsquare for example, if you are tracking a mobile transmitter.?

If you want to differentiate between transmissions from two different locations, using the same callsign, there are other ways to do it than using the double-transmissions and its inherent disadvantages. If the locations are far enough apart to be in different grid squares you'll be able to differentiate them easily anyway. Another way is to transmit in different time slots e.g. one station starts at 2, 12.22 etc minutes past the hour and the other at 4, 14, 24, etc. Or you could configure them to have different indicated power levels - it is only a coarse approximation anyway and if your TXs are both putting out 3W say, it will not matter and nobody will care, if you set one of them to 33dBm and one to 37dBm.?

These are the workarounds I can think of.?

73 Hans G0UPL
http://qrp-labs.com


-------- Original message --------
From: "cris blak via groups.io" <cyo3fff@...>
Date: Tue, Dec 14, 2021, 9:54 PM
To: "[email protected] Notification" <[email protected]>, [email protected]
Subject: [QRPLabs] #QCX+ #QCXmini #WSPR beacon callsign length
Hello Hans,

I need to use QCX+ and QCXmini as a WSPR transmitter on my second location therefore my callsign will be YO3FFF/P.
All good but I realize that is not possible with the actual/latest FW (1.07).
To set callsign for WSPR I used menu: 6 Beacon/6.5 WSPR call
On that, one can use maximum 6 characters so, my "/P" or else does not fit in.

Any workaround please?

Thank you.

73 de YO3FFF
Cristi


 

Thank you Steve. It help.

73 de YO3FFF
Cristi

Pe mar?i, 14 decembrie 2021, 21:22:20 EET, Steve via groups.io <qed28@...> a scris:


Hi Cris, Does this link help?






Glory to God in the highest, and on earth peace, good will toward men. Luke 2:14


 

Hello Cristi
?
I never dig deep into WSPR to know such limitation. Before U3/QCX I've used the original WSPR/WSJT-X programs and in there such "/P" is allowed.

Yes, you can add /P in the WSJT-X programs but the way it handles it is sending two WSPR messages instead of one, with the disadvantages I mentioned. The actual WSPR protocol can only transfer 50 bits of data, which is insufficient for the extended callsign information, this is the reason for sending two packets.??
?
So I can say this is the limitation of the QCX WSPR implementation, part due to the WSPR protocol.

Yes, QCX implements only the basic WSPR protocol, not the extended format that can handle certain callsign prefix, suffix and 6-char Maidenhead combinations. Ultimate3S DOES handle the extended format.?

In QCX WSPR was originally more of a bonus feature than a core functionality. The limited program space means it would be very difficult to implement in QCX.?

73 Hans G0UPL