Bill Somerville <g4wjs@...> writes:

> 
>

Hi Bill and all -
 
>     On 06/03/2015 00:09, Eric NO3M wrote:
>       Hi Eric,
> 
>     
>       
>       I ran into a similar situation with the following message:
>       CQ NO3M DX
> 
>     CQ DX NO3M
>     is the correct form and is a standard message form, you can add your
>     locator as well just like a normal CQ call.
>     Note that this only works with "CQ" "CQ DX" "QRZ" or "DE" on the
>     front of the message. 

When decoded here, the message    CQ DX XXXXXX  is identified as a 
Philippine station ("DX") and double-clicking on the call sign  XXXXXX   
results in standard messages being generated with  DX   being the intended 
QSO partner.  E.g.,  DX WA8UGN PK08    DX WAUUGN -15    DX WA8UGN RRR

Same thing happens whenever anything follows "CQ " (that is C-Q-<space>).

I believe that the standard message form may be "CQDX" (without the space).


>       to keep stateside callers from answering.  I had assumed the "CQ"
>       would have been picked up and TX Enable persist after each
>       invocation.  However, that was not the case.  I saw other DX
>       stations at the time using the same format of message and wonder
>       how they are doing so without re-enabling the Enable TX each time;
>       perhaps something JT-Alert does for them?  Of course, JT-Alert is
>       not able to run on *nix, so that's not an option here.
>       It would be nice to be able to send a "recognized" CQ that will
>       keep the locals from dampening a DX "run".
>       73 Eric NO3M
> 
>     73
>     Bill
>     G4WJS. On 03/05/2015 04:04 PM, Guy wrote:

73 DE PAUL DU2/WA8UGN
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to