Hi Steve
I don't think that 5CT is a valid callsign. A search on the Internet
gave no result.
73 de Michael 5p1kzx
Den 18-08-2020 kl. 08:06 skrev Stephen VK3SIR:
Hi Folks,
I am unsure whether this has been reported:
30m:
055130 -11 0.2 1626 ~ CQ CO8LY FL20 Cuba
055130 -17 0.3 134
Michael,
True and very possible. I have just done the polite thing and reported
observations - though I suspect WSJT-X behaviour is more than valid. I have
reported this just in case its not occurring by design as that can lead to
problems later down the track :-)
[ Yet WSJT-X will also pick u
Hi,
Nothing wrong with a call ;)
It is F5CT in JN08.
He probably messed up his setup in WSJT-X or any other similar problem.
Best regards and RR73 9A5CW
uto, 18. kol 2020. 10:05 Stephen VK3SIR je napisao:
> Michael,
>
> True and very possible. I have just done the polite thing and reported
> obs
Steve, I guess that your statement "WSJT-X will not pick up this call"
means that WSJT-X will not *automatically *enter this call into the "DX
Call" field, nor the locator into the "DX Grid" field. That is true, but
WSJT-X will certainly pick up the call and grid as decoded if you enter it
manually
Frode,
Thanks … By not “picking up” I was meaning you could not click, double-click or
even use a third-party product via the UDP interface to force WSJT-X to place
WSJT-X into a Tx2 mode that should have responded to the call. It’s a damn
shame that I could not catch the call quickly enough (a
JN0 is not a valid grid (you should enter at least four characters). Even so,
2.2.2 will allow you to enter both an “invalid” call and grid in the DX Call
and DX Grid boxes, press Generate Std Msgs, and call the station. Yo may need
to manually step through the QSO cycle, but it WILL work.
5CT
Patrick,
* It is F5CT in JN08.
Great detective work… and WSJT-X working as it should by blocking an invalid
from being responded to !
73
Steve I
VK3VM / VK3SIR
[ Ps: Sorry I almost missed the email! ]
From: Patrick 9A5CW
Sent: Tuesday, 18 August 2020 7:35 PM
To: WSJT software developme
Hi Steve,
5CT is not a valid RA call sign as the third character is not a number, when
the first character is a number or one of those country codes such as N, G etc.
That’s why it is not source coded properly and recognized as a call sign and
double clicking don’t work for you; message is a f
Steve, a little bit of know how should sit behind the monitor.
A callsign is designated as country code + number + minimum 1 letter. So 5CT is
definitely a false decode.
73
Enrico, OE1EQW
Holen Sie sich Outlook für Android
On Tue, Aug 18, 2020 at 2:41 PM +0200, "Stephen VK3SIR"
Enrico,
Exactly… but how do we know what currently is valid when the rules are bent by
regulators every day? The point of the initial post was to tease out of the
community whether this was designed behaviour or whether this was bi-product
i.e. to draw out understanding of behaviour not only fo
I suspect its due more to the fact that he was using the Tx5 message
with its 13 character limit, and not the Tx6 which allows the addition
of up to 4 characters between the 'CQ' and the callsign, and will also
include the full 4 character grid in the transmission.
Neil, KN3ILZ
On 8/18/2020 2:34
Hi all and Steve,
It took me 5 seconds or less to solve a partial callsign. As an HF+6m and
UP contester and DX hunter i rember well some valid very active callsigns
and dxcc prefixes. I cant remember all grid squares but i know when is
false or not or field is out of country or continent. It's go
Hi All,
The key issue is that the 5CT call sign does not fit with the source coding of
call signs. The third character needs to be a number. The 'third' is seen as
second in call signs commencing with K, G etc. as then the first one marked to
be empty. See Protocol specifications at 17.1. of Us
That's nice.
73, Carey, WB4HXE
On Tue, Aug 18, 2020 at 2:35 PM Patrick 9A5CW wrote:
> Hi all and Steve,
>
> It took me 5 seconds or less to solve a partial callsign. As an HF+6m and
> UP contester and DX hunter i rember well some valid very active callsigns
> and dxcc prefixes. I cant remember a
Patrick and all constructive responders,
Interesting discussion ( “That’s Nice” … some behaviour that many are trying
hard to eliminate from AR is emerging ) … The main reason that I questioned it
as a “by design” related to the fact that WSJT-X identified it as from Morocco
- yet later in acti
15 matches
Mail list logo
