I guess the same risk applies to 60m with so many countries having different 
allocations, hence lots of split operating going on.

 

I’d be happy if the number simply indicated my QSX/listening frequency, without 
automatically sending callers’ VFOs there.  At least then they’d have the 
chance to check if it would be in- or out-of-band for them. 

 

Meanwhile, on 60m I interleave my normal CQs with the occasional free-text QSX 
message … or operate simplex if I’m feeling lazy!

 

73,

Gary   ZL2iFB

 

From: Bill <brightl...@gmail.com> 
Sent: 07 March 2019 10:05
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Automatic QSY on 160m!!

 

Hi Gary,

 

    I think that you might have something there. I was calling CQ for a long 
time one an empty band when I saw a VK3 calling CQ. I stopped what I was doing 
to call him. I didn't notice that his message was "CQ 908 VK3XXX QF22". I 
immediately got a purple message in the RX Windows stating "QSY 1.908". My 
radio just started calling him at on 1908. I guess this is the FT8 equivalent 
of never clicking on a URL in an email! Oh well, lesson learned. I was lucky 
that I didn't get blindly sent off outside the band somewhere. I'll have to pay 
closer attention to what people are actually sending before I click on them. 
I'm sure this must be a useful feature somewhere but it seems a bit dangerous. 
While the F/H mode QSY is great this "random" QSY should be an option that you 
can click off.

 

73,

 

    Bill - AK6A

 

On Wed, Mar 6, 2019 at 12:38 PM Gary Hinson <g...@isect.com 
<mailto:g...@isect.com> > wrote:

Hi Bill.

 

It sounds to me as if you may have double-clicked a CQ message containing a 
number e.g. “CQ 1908 AB1CDE”: I think WSJT-X interprets that number as a 
frequency and automatically QSYs the radio for you – like it or not.  I don’t 
know what kind of validation or bounds checking there is, but I suspect if I 
sent “CQ 2010 ZL2IFB”, I might be sending callers well outside the 160m band.   
[Please don’t try this at home!]

 

Generally speaking, we should NOT be sending numbers in our CQ calls on HF.  
The workaround is NOT to double-click CQ messages containing numbers.  If you 
want to call someone sending numbers, you can manually enter their callsign 
into the DX call box, generate the messages then call the station without 
QSYing.

 

FWIW on HF, I would prefer to be able to disable the auto-QSY function, either 
as a user-option or by default.  In fact, it would be much more useful to allow 
directed CQ messages to contain up to 4 letters and/or digits e.g. “CQ E51 
ZL2iFB”.  At present, directional CQs can only contain up to 4 letters, no 
numbers – possibly due to conflict with the auto-QSY function.  However, that 
would require a change to the software …

 

73,

Gary   ZL2iFB

 

From: Bill <brightl...@gmail.com <mailto:brightl...@gmail.com> > 
Sent: 07 March 2019 03:50
To: WSJT software development <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> >
Subject: [wsjt-devel] Automatic QSY on 160m!!

 

I just ran into an issue while operating on 160m FT8. When I try to work JA 
stations on 160m I normally go into the WSJT-X preferences and turn the Radio 
Split operation from RIG to NONE then manually set my radio for a 1840 transmit 
and 1908 receive split. Before transmitting I make sure that I am on a clear 
frequency within the 1840 segment. This method has always worked well.

 

This morning while calling a regular CQ on the standard 1840 allocation (split 
control set to standard RIG control - normal 160m operation) WSJT-X displayed a 
purple line in the RX window saying "QSY 1908" and my rig was automatically 
sent to both transmit and receive to 1908. Where did this come from and more 
importantly how do I turn it off!! Some online research showed some information 
about a QSO partner requesting a QSY but I don't want someone else controlling 
my radio and possibly making it transmit outside of my frequency allocations.

 

I've never seen this before and needless to say I was more than surprised. I'm 
glad that I caught it in time.

 

Thanks!

 

73,

 

Bill - AK6A

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to