Re: [wsjt-devel] VFO-B behavior

[Neil Zampella]

The  WSJT Meteor Scatter and Weak Signal Group is the one you want.

Neil, KN3ILZ

On 3/6/2019 6:32 PM, John Bastin wrote:

On 6Mar 2019, at 18:17, Neil Zampella  wrote:

The semi-official WSJT support group is on Yahoo  groups.The ones on
Groups.io are not (as far as I know) offical support groups.

Which one of these Yahoo groups do you recommend?

WSJT-HF
Open forum for anyone to post and share information regarding using WSJT 
digital modes (such as JT65 and JT9) on the HF amateur radio bands. (no 
activity in the last seven days)

wsjt
(public group, 31 members) (no activity in the last seven days)
“Group description” displays a series of question marks.

WSJT Meteor Scatter and Weak Signal Group
(restricted group, 5409 members)

QST: The current General Availability (GA) release is WSJT-X 2.0.0. The FT8 and 
MSK144 protocols have been enhanced and are not backward compatible with prior 
versions. K1JT urges you to upgrade.

The WSJTGroup promotes the WSJT modes and their correct use:
1. Adherence to the Standard Operating Procedures for Schedules & Random 
Contacts
2. Promotes Off-Set method of calling CQ on recognized calling frequencies.

This last one seems to be the one most likely to have knowledge to share and 
help to give,


This has always been the development support group, which I do believe
was originally used to report bugs, and not for actual program support
other than bug issues.

Neil, KN3ILZ

That’s likely true, I’ll look into this third group in the Yahoo list as one 
likely to be a helpful source.

73,

John K8AJS
jbast...@me.com







---
This email has been checked for viruses by AVG.
https://www.avg.com



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

Re: [wsjt-devel] Automatic QSY on 160m!!

[Gary McDuffie]

> On Mar 6, 2019, at 14:05, Bill  wrote:
> 
> I'm sure this must be a useful feature somewhere but it seems a bit dangerous.

Indeed, it IS a feature.  However, I believe it should be disabled when 
operating on HF.  It is used “daily” on VHF, where a station may call CQ on a 
busy frequency with MSK144 and indicate where they are listening.  They call on 
the calling frequency, indicating where they are listening.  When someone calls 
them where they are listening, the CQ calling station’s transmitter immediately 
shifts to where they are listening and the QSO completes on that frequency, 
never automatically going back to where they called CQ.  It works quite well 
for that purpose.  Unlike convention “split” definition, it is NOT set up to 
operate conventional split with both stations remaining on different 
frequencies.  Only the CQ is sent split and then the software automatically 
takes it back to simplex on the indicated frequency as soon as the CQer is 
called by someone.  I believe it would be a good idea to NOT have that feature 
even available on FT8.  It doesn’t have a use there.

Gary - AG0N

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

Re: [wsjt-devel] VFO-B behavior

[John Bastin via wsjt-devel]

On 6Mar 2019, at 18:17, Neil Zampella  wrote:
> 
> The semi-official WSJT support group is on Yahoo  groups.The ones on
> Groups.io are not (as far as I know) offical support groups.

Which one of these Yahoo groups do you recommend?

WSJT-HF
Open forum for anyone to post and share information regarding using WSJT 
digital modes (such as JT65 and JT9) on the HF amateur radio bands. (no 
activity in the last seven days)

wsjt 
(public group, 31 members) (no activity in the last seven days)
“Group description” displays a series of question marks.

WSJT Meteor Scatter and Weak Signal Group
(restricted group, 5409 members)

QST: The current General Availability (GA) release is WSJT-X 2.0.0. The FT8 and 
MSK144 protocols have been enhanced and are not backward compatible with prior 
versions. K1JT urges you to upgrade.

The WSJTGroup promotes the WSJT modes and their correct use:
1. Adherence to the Standard Operating Procedures for Schedules & Random 
Contacts
2. Promotes Off-Set method of calling CQ on recognized calling frequencies.

This last one seems to be the one most likely to have knowledge to share and 
help to give, 

> 
> This has always been the development support group, which I do believe
> was originally used to report bugs, and not for actual program support
> other than bug issues.
> 
> Neil, KN3ILZ

That’s likely true, I’ll look into this third group in the Yahoo list as one 
likely to be a helpful source.

73,

John K8AJS
jbast...@me.com





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

Re: [wsjt-devel] Automatic QSY on 160m!!

[Frank Kirschner]

I don't believe it involved double-clicking. I experienced the same thing a
while ago, and just assumed it was a feature of the software with which I
was unfamiliar. The transceiver changed frequency with no action on my
part. I saw in a DX cluster that the DX station (a JA, as I recall), was
listening on 1908. I had called him several times on 1840 with no answer.
After the rig QSY'd, I couldn't hear him, of course, so I manually set the
rig (Flex 6600) to receive on 1840 and transmit on 1908. I worked him right
away after that.

On Wed, Mar 6, 2019 at 3:38 PM Gary Hinson  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 
> *Sent:* 07 March 2019 03:50
> *To:* WSJT software development 
> *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
> 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

Re: [wsjt-devel] VFO-B behavior

[Neil Zampella]

The semi-official WSJT support group is on Yahoo  groups.    The ones on
Groups.io are not (as far as I know) offical support groups.

This has always been the development support group, which I do believe
was originally used to report bugs, and not for actual program support
other than bug issues.

Neil, KN3ILZ

On 3/6/2019 5:52 PM, John Bastin wrote:

On 5Mar 2019, at 09:40, Marco Cali'stri  wrote:


as well as for the
possibility to have a separate mailing list dedicated specifically to
WSJT-X usage, in order to let the development topics free of everything
which is not strictly related to programming,

Not to be nit-picky, but how many groups do we need?

On groups.io, there is

FT8-Digital
WSJTX

And here we have the devel list. I try to follow all three, because the 
questions encountered may or may not seem to be actually on-topic for the 
stated purpose of the list where they are posted.

I agree, it’s a real problem to sort it out.

73,


John K8AJS
jbast...@me.com





---
This email has been checked for viruses by AVG.
https://www.avg.com



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

Re: [wsjt-devel] Automatic QSY on 160m!!

[Gary Hinson]

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  
Sent: 07 March 2019 10:05
To: WSJT software development 
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 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 mailto:brightl...@gmail.com> > 
Sent: 07 March 2019 03:50
To: WSJT software development 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  
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

Re: [wsjt-devel] VFO-B behavior

[John Bastin via wsjt-devel]

On 5Mar 2019, at 09:40, Marco Cali'stri  wrote:

> as well as for the
> possibility to have a separate mailing list dedicated specifically to
> WSJT-X usage, in order to let the development topics free of everything
> which is not strictly related to programming,

Not to be nit-picky, but how many groups do we need?

On groups.io, there is

FT8-Digital
WSJTX

And here we have the devel list. I try to follow all three, because the 
questions encountered may or may not seem to be actually on-topic for the 
stated purpose of the list where they are posted.

I agree, it’s a real problem to sort it out.

73,


John K8AJS
jbast...@me.com



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

Re: [wsjt-devel] Automatic QSY on 160m!!

[Bill]

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  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 
> *Sent:* 07 March 2019 03:50
> *To:* WSJT software development 
> *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
> 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

Re: [wsjt-devel] Automatic QSY on 160m!!

[Gary Hinson]

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  
Sent: 07 March 2019 03:50
To: WSJT software development 
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
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X: macOS users - Important - please read

[Bill]

Thanks Bill!

So far no more crashes but its too early to tell if its totally gone away.
I did find the WSJT-X_trace.log file and it was almost 800mb. I'll let the
OS background process do its work and check back in a few days to see if it
has been deleted .

I appreciate the quick response.

Now is someone can answer my question about the QSY command issue I had on
160m.

73,

Bill - AK6A

On Wed, Mar 6, 2019 at 10:18 AM George J Molnar  wrote:

> Thanks, Bill!
>
> George J Molnar
> KF2T - Virginia, USA
>
>
>
> ___
> wsjt-devel mailing list
> 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

Re: [wsjt-devel] WSJT-X: macOS users - Important - please read

[George J Molnar]

Thanks, Bill!

George J Molnar
KF2T - Virginia, USA



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

[wsjt-devel] WSJT-X: macOS users - Important - please read

[Bill Somerville]

Hi to all WSJT-X users on macOS,

there was a problem with the build of WSJT-X recently shipped as v2.0.1. 
It is both slow and liable to unexpected crashes. This was due to a slip 
up when making the release kit that included diagnostic options which 
should not be enabled for release builds.


A new DMG installer has been posted to the WSJT-X project web site 
(https://physics.princeton.edu/pulsar/k1jt/wsjtx.html) and to the 
project Source Forge files area 
(https://sourceforge.net/projects/wsjt/files/wsjtx-2.0.1/). I urge you 
to download the replacement DMG and replace your current WSJT-X v2.0.1 
application bundle using it.


One side effect of the incorrect build is that a trace file 
"$TMPDIR/WSJT-X_trace.log" will have been accumulating, you may wish to 
delete this file although the normal macOS background file cleanup tasks 
will do that itself after three days.


You may see a subtle performance improvement with the replacement v2.0.1 
since it will not be writing copious trace information to disk, also 
even if you have not experienced the crash issue that is not proof that 
it will not happen during your next QSO, so please update your application.


Sorry for the inconvenience and 73
Bill
G4WJS.



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

[wsjt-devel] Automatic QSY on 160m!!

[Bill]

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
https://lists.sourceforge.net/lists/listinfo/wsjt-devel