Re: [wsjt-devel] Error in Sound Input

[M Lewton]

Hello All

RFI was a problem for one of my computers, only one USB cable seems to work 
without problems, it is 24 inch long with two suppressors clamped to it.
Randomly occurs, mostly locking the transceiver to transmit with no output 
since it isn't getting sound from the computer.

My two other Windows 10 computers do not have any RFI problems regardless of 
which USB cable I use.
Transceiver IC-7300.

I am surprised how many people are still using Windows 7 when they had the 
opportunity to upgrade to Windows 10.
Even after Microsoft said they wouldn't upgrade any more, they still did, as 
I updated and old laptop way after the deadline.
You might give it a try even at this late date.

So far for me, no problems with version 2.0.0
Worked several stations with both of us at -24.
I have 3 computers running Windows 10 and one Raspberry pi, running v 2.0.0, 
so far no problems with FT8.
I haven't tried it on my old laptop which also runs Windows 10.  Not worth 
the trouble.

The Raspberry pi doesn't remember the display position exactly probably due 
to my monitor resolution 2560 X 1440.

I still wish Tx5 would stick when answering a CQ, especially on weak 
stations.

73

WA6PHR
Maurice


-Original Message- 
From: Bill Somerville
Sent: Wednesday, December 12, 2018 17:20
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Error in Sound Input


On 13/12/2018 00:30, Steve Sacco wrote:

Running WSJT-X v 2.0.0 784f75
Windows 10 Home v 1803

While attempting to work VP8LP on 30M this evening, WSJX-X threw this error:



It has been working without issue since Monday.

After that error, I shut it down and restarted WSJT-X, and worked another 
station without issue.

Please let me know what I can do to assist.



Hi Steve,

that is unlikely to be a problem within WSJT-X. It may be a disconnection of 
the audio device, this can happen with external USB connected devices if the 
plugs are a bit loose and get knocked or possibly RFI causing the connection 
to reset.

73
Bill
G4WJS.










___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7C955ab4feb7894cd159ea08d66099aced%7C84df9e7fe9f640afb435%7C1%7C0%7C636802610479867247sdata=YULsLXJ1IV2cXQ74evLOWAk2sONs2jzm3n5XLmb6BWk%3Dreserved=0
 


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

[wsjt-devel] problems with Configurations in wsjtx-2.0.0

[Rich Griffiths]

I finally got around to installing the GA version of 2.0.0 today. I 
cleaned the system of all old files in the .config, .local, /usr etc. 
directories before starting.  I used the tarball under Debian stretch 
(v9), and it seemed to install without problems using the directions in 
the INSTALL file.


However, the Configurations are behaving badly.  For example, I cloned 
the Default into a new FT8-HF and an MSK144-6m.  These operations led to 
multiple new listings on the Configuration tab, typically with names 
like  and FT8-  And none of the new items had settings in the 
General, Radio, or Audio tabs.  If I try to delete one, another will pop 
up to take its place.


What am I missing?

... Rich    W2RG


On 12/12/2018 06:36 PM, Jim Jennings wrote:

"Run better" was not a good choice of words on my part, Bill,

Specifically, after removing the older version "clutter" from 
Settings>Apps, I found that WSJT-X loaded noticeably faster when 
launched--possibly some debris left behind in the \wsjtx subdirectory 
from overwriting older versions in the installations?


V2.0.0 is running beautifully here on my hamshack laptop, and I've 
observed 77-bit signals outnumbering 75-bit on 30 and 20M FT8 today at 
my location. The migration, I'd say, is well underway. My highest 
compliments to the entire development team.  73,


Jim, W7XZ

-Original Message- From: Bill Somerville
Sent: Wednesday, December 12, 2018 10:04
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Previous versions of WSJT appear in Windows 
Control Panel


On 12/12/2018 17:44, Jim Jennings wrote:
One thing I noticed, Bill, after clearing the old entries from the 
Apps listing,  was that the installed version seemed to run better, 
although I cannot "quantify" this.  73,


Jim, W7XZ


Hi Jim,

that's not possible. The entries are just a few small key/value pairs in
the Windows registry and WSJT-X does not go near the Windows registry
when it is running, only the installer does that.

73
Bill
G4WJS.



___
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





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

Re: [wsjt-devel] 2 Bugs or maybe features?

[Bill Somerville]

Hi Attila,

comments below.

On 12/12/2018 20:24, Attila Kocis wrote:

Hi

I'm using 2.0 GA (on Win10 1803 64bit) now the third day and it works great, 
except of two problems which don't want to go away.

The first is, the SSL/LOTW error message won't disappear, also not after 
installing the SSL Tool which is mentioned in the manual. It still appears on 
every start.
Please refer to the Windows installation instructions in the User Guide 
 
particularly the part about what to do if installing the OpenSSL 
libraries does not fix the issue.


The second is, when I start WSJTX, the waterfall is always empty. No signal can 
be seen there and nothing is decoding. The signals are shown only when I select 
first a frequency in the dropdown menu or go to settings menu and back to 
WSJTX. Then the signals are showing and decoding. This wasn't happening in any 
beta RC version.
Do you have the option "Settings->General->Monitor off at startup" 
checked? That would stop receiving until you clicked "Monitor" or 
selected a working frequency. It is intended to allow you to start 
WSJT-X without disturbing the rig.


73 de dl1nux
Attila


73
Bill
G4WJS.

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

Re: [wsjt-devel] Error in Sound Input

[Bill Somerville]

On 13/12/2018 00:30, Steve Sacco wrote:

Running WSJT-X v 2.0.0 784f75
Windows 10 Home v 1803

While attempting to work VP8LP on 30M this evening, WSJX-X threw this 
error:


image.png

It has been working without issue since Monday.

After that error, I shut it down and restarted WSJT-X, and worked 
another station without issue.


Please let me know what I can do to assist.


Hi Steve,

that is unlikely to be a problem within WSJT-X. It may be a 
disconnection of the audio device, this can happen with external USB 
connected devices if the plugs are a bit loose and get knocked or 
possibly RFI causing the connection to reset.


73
Bill
G4WJS.

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

[wsjt-devel] 2 Bugs or maybe features?

[Attila Kocis]

Hi

I'm using 2.0 GA (on Win10 1803 64bit) now the third day and it works great, 
except of two problems which don't want to go away.

The first is, the SSL/LOTW error message won't disappear, also not after 
installing the SSL Tool which is mentioned in the manual. It still appears on 
every start.

The second is, when I start WSJTX, the waterfall is always empty. No signal can 
be seen there and nothing is decoding. The signals are shown only when I select 
first a frequency in the dropdown menu or go to settings menu and back to 
WSJTX. Then the signals are showing and decoding. This wasn't happening in any 
beta RC version.

73 de dl1nux
Attila



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

[wsjt-devel] Error in Sound Input

[Steve Sacco]

Running WSJT-X v 2.0.0 784f75
Windows 10 Home v 1803

While attempting to work VP8LP on 30M this evening, WSJX-X threw this error:

[image: image.png]

It has been working without issue since Monday.

After that error, I shut it down and restarted WSJT-X, and worked another
station without issue.

Please let me know what I can do to assist.

73,
Steve
NN4X
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Previous versions of WSJT appear in Windows Control Panel

[Jim Jennings]

"Run better" was not a good choice of words on my part, Bill,

Specifically, after removing the older version "clutter" from Settings>Apps, 
I found that WSJT-X loaded noticeably faster when launched--possibly some 
debris left behind in the \wsjtx subdirectory from overwriting older 
versions in the installations?


V2.0.0 is running beautifully here on my hamshack laptop, and I've observed 
77-bit signals outnumbering 75-bit on 30 and 20M FT8 today at my location. 
The migration, I'd say, is well underway.  My highest compliments to the 
entire development team.  73,


Jim, W7XZ

-Original Message- 
From: Bill Somerville

Sent: Wednesday, December 12, 2018 10:04
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Previous versions of WSJT appear in Windows 
Control Panel


On 12/12/2018 17:44, Jim Jennings wrote:
One thing I noticed, Bill, after clearing the old entries from the Apps 
listing,  was that the installed version seemed to run better, although I 
cannot "quantify" this.  73,


Jim, W7XZ


Hi Jim,

that's not possible. The entries are just a few small key/value pairs in
the Windows registry and WSJT-X does not go near the Windows registry
when it is running, only the installer does that.

73
Bill
G4WJS.



___
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 2.0 Will Not Run

[Eric Lundstrom]

Hi Bill,

The reason I suggested running as Administrator is to see if there are any 
authorization issues. If it works as Admin and does not work as non-Admin, that 
is useful information to know.

On my Ubuntu system some of the RC versions and the GA version produce a Log 
File Error message (upon clicking OK in the Log QSO dialog) popup that contains 
the text "Cannot open "/home/eric/local/share/WSJT-X/wsjtx_log.adi". If I run 
using sudo I do not get this error message box.

Eric



From: Bill Somerville 
Sent: Tuesday, December 11, 2018 13:30
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT 2.0 Will Not Run

On 11/12/2018 21:19, Eric Lundstrom wrote:
Try running "As Administrator". Right click on program icon to choose this.

Eric


Hi Eric,

this is poor advice, there is absolutely no reason to run WSJT-X with 
administrator rights, do so is a potential security risk. Just don't do it.

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

Re: [wsjt-devel] Recomended Freqs for MS, JT65

[Joe Taylor]

Hi Edfel,

On 12/12/2018 4:30 PM, Edfel Rivera KP4AJ wrote:

My question is this, when I change mode to MSK144, freq defaults to 
50.280 but when I check frequency used but stations doing contacts in 
50m, freq is 50.560.  Same goes to JT65 default freq is 50.310 but JT65 
used to use 50.276.

Which frequencies should I use when testing those modes?


North America is now using 50.260 as the default frequency for MSK144.
You should enter that value for MSK144 in the Frequencies tab.

-- 73, Joe, K1JT


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

[wsjt-devel] Recomended Freqs for MS, JT65

[Edfel Rivera]

Hi All:

WSJTX 2.0 running fine here.  Users observing few decodes should be sure
UTC time difference not more that 1 second.  BTW, FT8 RoundUp (WSJTX RC5)
was a test best, my experience contacts from Caribbean to Turkey, Hungary,
Italy, Argentina, Saudi Arabia, Bulgaria, New Zeland, Serbia, Canada,
Ukraine. France to mention a sample.  Sensitivity should not more be an
issue, IMO.

My question is this, when I change mode to MSK144, freq defaults to 50.280
but when I check frequency used but stations doing contacts in 50m, freq is
50.560.  Same goes to JT65 default freq is 50.310 but JT65 used to use
50.276.

Which frequencies should I use when testing those modes?

73'

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

[wsjt-devel] TX function lost, then have Task Manager problem

[bergeracb--- via wsjt-devel]

Have not seen my problem listed yet, so I will try to explain what I see.
Every once in a while operating, the TX function stops working. The Transmitter 
goes into transmit but there is no audio drive so no RF is produced. WSJT-X 
thinks it is working. If I shut down WSJT-X and try to restart the program I 
get the message that their is another instanceof WSJT-X running and the program 
won't start. Checking the task manager under the Running APPS shows no WSJT-X 
app listed.However if I look in the Running BACKGROUND tasks, WSJT-X
has been moved from the APPS to the BACKGROUND tasks.using END TASK there and 
then I can restart the program and use the transmitter again. Can't decide if 
it is a WSJT-X problem or aFLEX 6700 and DAX problem. but I have tried shutting 
 down andrestarting DAX several times without any success. Of course 
shuttingdown and restarting the 6700 (after the background WSJT-X task is 
closed)  also fixes the problem.  I'm wondering if any of the other
Flex owner see this problem? I have the work around so right now it is just a 
nuisance.73 Al Berger N4AB

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

Re: [wsjt-devel] bug or feature?

[Bill Somerville]

On 12/12/2018 20:34, Patrick 9A5CW wrote:
i suposed that only  shud be in the <...> but i see 
when i checked my all.txt
that normaly also the callers are marked the same... is that normal 
behaviour?

Part of the decodes on 30m today:
*134145   1  0.1 1135 ~ CR140AA  73*
*150530   7  0.1 1699 ~ DM152ZYA  73*
*152115 -10  0.2 1774 ~ OG55W  73*
*081830   5  0.6  441 ~ YO/KD6SM  RR73
*
*090015  10  0.2 1822 ~ TC630MECCA  73
*
** 085830 -16  0.4  531 ~ ** TC630MECCA RR73

Didnt find any match with SP5ORS calling any special long call station 
this afternoon. He was active CQing and mostly

working EUs but none of them its  or so.


Hi Patrik,

when a complex callsign is used in a message either it or the standard 
one can be sent as a hash code, one of them must be. The message 
generation is arranged so that each call is sent not hashed at least 
once in a standard QSO. There is a further restriction that signal 
reports can only be included in a message with a complex call if the 
complex call is sent as a hash code.


All the examples you give above are sending 73 or RR73 rather than a 
report or r-report so the message generator has chosen to hash the 
simple callsign and send the complex callsign in full. The same applies 
for RRR messages. CQ and QRZ messages never hash the callsign as that 
would nearly always be ambiguous.


The intention is to always exchange the call in full as hash collision 
can and will happen so we want to ensure that the correct callsign is 
always copied at least once per QSO.


73
Bill
G4WJS.

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

Re: [wsjt-devel] bug or feature?

[Joe Taylor]

Patrick --

On 12/12/2018 3:34 PM, Patrick 9A5CW wrote:

Hi Bill,
i suposed that only  shud be in the <...> but i see when 
i checked my all.txt
that normaly also the callers are marked the same... is that normal 
behaviour?


Please read Section 7.5, "Compound Callsigns" in the WSJT-X 2.0 User Guide.

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html#COMP-CALL

"If the message includes a grid locator or numerical signal report, the 
brackets must enclose the compound or nonstandard callsign; otherwise 
the brackets may be around either call."


The program automatically generates messages that optimize the use of 
nonstandard callsigns.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Message box at startup

[Joe Taylor]

Hi Svend,

On 12/12/2018 7:31 AM, Svend Aage Jessen LA6YJA wrote:

The info / message box that opens at startup...
How to deactivate this one, or will it deactivate by itself
at the date set in this box?


I guess you would prefer not to see the startup message.  Perhaps you
do not mind if we (the developers) would receive many hundreds of emails 
from users who do not read any documentation and complain that they see 
strong signals that do not decode.


We consider the annoyance of the startup message a very small price for 
you to pay, if it helps to ease rapid adoption of the new FT8 and MSK144 
protocols.


When the transition to v2.0 has been completed, the next program release 
will no longer bother you with having to make one extra click each time 
you start the program or select a new Configuration.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] bug or feature?

[Patrick 9A5CW]

Hi Bill,
i suposed that only  shud be in the <...> but i see when i
checked my all.txt
that normaly also the callers are marked the same... is that normal
behaviour?
Part of the decodes on 30m today:
*134145   1  0.1 1135 ~  CR140AA  73*
*150530   7  0.1 1699 ~  DM152ZYA  73*
*152115 -10  0.2 1774 ~  OG55W  73*

*081830   5  0.6  441 ~  YO/KD6SM  RR73*

*090015  10  0.2 1822 ~  TC630MECCA  73*
085830 -16  0.4  531 ~  ** TC630MECCA RR73

Didnt find any match with SP5ORS calling any special long call station this
afternoon. He was active CQing and mostly
working EUs but none of them its  or so.

73




On Wed, Dec 12, 2018 at 9:15 PM Bill Somerville 
wrote:

> On 12/12/2018 20:06, Patrick 9A5CW wrote:
> > SP5 was active 1h or more b4 i started to call the SX special call. I
> > checked that in all.txt, somehow it was exctracted from earlier
> decodes...
> >
> Hi Patrik,
>
> thanks for checking that, was the SP5 working a complex call QSO partner
> when seen by you previously and did one of the decodes include his call
> inside '<' and '>' characters?
>
> Clearly we are not making the best choice when hash collisions occur.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
9A5CW - Patrik Hrvatin
--... ...--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] V2.0.0 adoption

[Dana Myers]

On 12/12/2018 12:20 PM, Ted Gisske wrote:

I have a multi-band FT8 skimmer. It skims 7 bands from 160M-15M (excluding 60M).

I converted the skimmer to V2.0.0 yesterday about this time. Ordinarily, my 
V1.9.1 spot rate was about 10,000-12,000 spots per day. In the last 24 hours my 
V2.0.0 spot rate is 7700/day.


Marvelous bit of actual data vs speculation and anecdote. Will be interesting
to see how it increases over the next couple of weeks.


So...Either there are a huge amount of new FT8 users running V2.0.0, or users 
are converting to the new version at a very satisfyingly rapid rate.

Pretty amazing for a release 2 days old.

Indeed. Given the speed with which FT8 was initially adopted (literally
just a few weeks), I'm not surprised that the user community is agile.

73,
Dana  K6JQ



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

Re: [wsjt-devel] Split operation

[Tom Ramberg via wsjt-devel]

I've sent you a private e-mail with info on how to work JA split on 160.

73 de Tom OH6VDA

> 12. des. 2018 kl. 20:02 skrev OG55W :
> 
> Steven! The waterfall is only 3500 Hz wide and it should be more than 68000 
> Hz wide to hear 1908 kHz.
>  
> Keijo
>  
> From: Steven Greer
> Sent: Wednesday, December 12, 2018 7:52 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Split operation
>  
> Just check the keep TX frequency that way when you transmit you will be 
> transmitting where you set yourself, and the rx will goto the calling 
> station.  Thats how I do it.  Not sure if I'm allowed to comment to the 
> mailing to help others if not just let me know and I won't help out anymore 
> on easy to answer questions.
> 
>> On 12/12/18 12:45 PM, OG55W wrote:
>>  
>> 
>> I have tried to find how to operate with split..
>> JA-stations are calling me in 1908 as I am transmitting in 1840, and I do 
>> not hear them as my RX or TX change the frequency.
>> I am not allowed to transmit in 1908.
>> 
>> Somebody said that use the RIT, but with FT-2000 1908 is too far away…
>> 
>>  
>> 
>> 73 Keijo OG55W
>> 
>>  
>> 
>>  
>> 
>> 
>> 
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> -- 
> Steven Greer
> KM4OUS
> OMISS #10630
> 
> NOTE: This e-mail was made with 100% recycled electrons.  No electrons were 
> harmed, No trees were destroyed, No animals were killed, and No political 
> correctness was observed in making or sending this message.
> ___
> 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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] V2.0.0 adoption

[Ted Gisske]

I have a multi-band FT8 skimmer. It skims 7 bands from 160M-15M (excluding 60M).

I converted the skimmer to V2.0.0 yesterday about this time. Ordinarily, my 
V1.9.1 spot rate was about 10,000-12,000 spots per day. In the last 24 hours my 
V2.0.0 spot rate is 7700/day.

So...Either there are a huge amount of new FT8 users running V2.0.0, or users 
are converting to the new version at a very satisfyingly rapid rate.

Pretty amazing for a release 2 days old.

73,
Ted
K9IMM



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

Re: [wsjt-devel] bug or feature?

[Bill Somerville]

On 12/12/2018 20:06, Patrick 9A5CW wrote:
SP5 was active 1h or more b4 i started to call the SX special call. I 
checked that in all.txt, somehow it was exctracted from earlier decodes...



Hi Patrik,

thanks for checking that, was the SP5 working a complex call QSO partner 
when seen by you previously and did one of the decodes include his call 
inside '<' and '>' characters?


Clearly we are not making the best choice when hash collisions occur.

73
Bill
G4WJS.



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

Re: [wsjt-devel] bug or feature?

[Patrick 9A5CW]

Hi Bill,
Thanks for the explanation.
SP5 was active 1h or more b4 i started to call the SX special call. I
checked that in all.txt, somehow it was exctracted from earlier decodes...

Best regards,
73
Patrik 9A5CW

Datuma sri, 12. pro 2018. 20:38 Bill Somerville  On 12/12/2018 18:54, Patrick 9A5CW wrote:
> > Hi,
> > can someone explain what happend here? See part of all.txt.
> > I am 9A5CW, i am not SP5ORS?
> > How i sent that msg?
> > Yesterday saw something similar with another SP callsign in the
> > Brackets when he was calling CR150AA?!
> > I was not transmiting at that time.
> >
> > Best regards,
> > Patrik 9A5CW
> > p.s. if u need ALL.TXT i can sent it
> >
> Hi Patrik,
>
> this is a hash code collision. The hash code for 9A5CW and SP5ORS are
> the same. I am not sure quite why WSJT-X is printing  instead of
> <9A5CW> since your callsign should be newer in the hash table. The
> messages sent are exactly correct, the problem is in the printing at
> your end. It looks like our algorithm for dealing with potential hash
> collisions needs some work although there are always some scenarios when
> we can't get this right, for example if messages involving the real
> SP5ORS including their call as a hash are interleaving the same with
> your call i.e neither is most likely to be correct.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> 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] bug or feature?

[Bill Somerville]

On 12/12/2018 18:54, Patrick 9A5CW wrote:

Hi,
can someone explain what happend here? See part of all.txt.
I am 9A5CW, i am not SP5ORS?
How i sent that msg?
Yesterday saw something similar with another SP callsign in the 
Brackets when he was calling CR150AA?!

I was not transmiting at that time.

Best regards,
Patrik 9A5CW
p.s. if u need ALL.TXT i can sent it


Hi Patrik,

this is a hash code collision. The hash code for 9A5CW and SP5ORS are 
the same. I am not sure quite why WSJT-X is printing  instead of 
<9A5CW> since your callsign should be newer in the hash table. The 
messages sent are exactly correct, the problem is in the printing at 
your end. It looks like our algorithm for dealing with potential hash 
collisions needs some work although there are always some scenarios when 
we can't get this right, for example if messages involving the real 
SP5ORS including their call as a hash are interleaving the same with 
your call i.e neither is most likely to be correct.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Fwd: Psk Reporter

[Bill Somerville]

On 12/12/2018 18:36, m...@dk7rca.de wrote:
When I call a non standard call sign (Wsjt puts it in brackets), psk 
reporter does‘n log my own call, I can’t see entries on psk-reporters 
map. On standard call signs the logging seems to be ok, I can see 
where my signal was been received. Could something be wrong with my 
config?

(I‘ve updated from 1.9.1 to 2.0.0 on Win7)


73, Andreas, DK7RCA


Hi Andreas,

currently WSJT-X only spots standard message decodes with a DX call and 
a DX grid, as standard messages containing complex callsigns cannot 
include a grid-square they will not be sent to PSKReporter.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Fwd: Psk Reporter

[Mark James]

Is this because there is no grid sent on the CQ? Since the listening WSJT-X
can’t automatically populate the grid, if it sends this to psk reporter, I
don’t think it can be mapped.

If so this also explains why answering a CQ in RU mode didn’t show up on
the map when I did it?

On Wed, Dec 12, 2018 at 1:40 PM  wrote:

> Hi,
>
> When I call a non standard call sign (Wsjt puts it in brackets), psk
> reporter does‘n log my own call, I can’t see entries on psk-reporters map.
> On standard call signs the logging seems to be ok, I can see where my
> signal was been received. Could something be wrong with my config?
> (I‘ve updated from 1.9.1 to 2.0.0 on Win7)
>
>
> 73, Andreas, DK7RCA
>
> ___
> 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] Previous versions of WSJT appear in Windows Control Panel

[Bill Somerville]

On 12/12/2018 18:19, DG2YCB, Uwe wrote:
Solution: Open regedit, search for names (or fragments of names) of 
old  entries from previous installations where you are sure that this 
version is no longer there (e.g. "2.0.0-rc3"), and delete those old 
entries manually.


Uwe,

Please, please, please backup your registry before attempting this, 
editing the Windows registry manually is one of the easiest ways of 
screwing up a Windows installation irrecoverably and should not be 
attempted unless you are sure you know what you are doing.


Use the "Apps and Features" applet to remove old "phantom" entries, the 
worst damage you can do there is uninstall something you did not intend 
to remove but can be easily repaired by reinstalling.


73
Bill
G4WJS.



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

[wsjt-devel] Fwd: Psk Reporter

[mail]

Hi,

When I call a non standard call sign (Wsjt puts it in brackets), psk reporter 
does‘n log my own call, I can’t see entries on psk-reporters map. On standard 
call signs the logging seems to be ok, I can see where my signal was been 
received. Could something be wrong with my config? 
(I‘ve updated from 1.9.1 to 2.0.0 on Win7)


73, Andreas, DK7RCA 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split operation

[OG55W]

FB! Thanks Bill!
I am not the only one on TOP band, so the info was very welcome!

Keijo

-Alkuperäinen viesti- 
From: Bill Somerville

Sent: Wednesday, December 12, 2018 8:10 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split operation

On 12/12/2018 17:45, OG55W wrote:

I have tried to find how to operate with split..
JA-stations are calling me in 1908 as I am transmitting in 1840, and I do 
not hear them as my RX or TX change the frequency.

I am not allowed to transmit in 1908.


Hi Keijo,

WSJT-X does not support this using CAT control, it conflicts with the
way that WSJT-X uses CAT control to clean up Tx signals and extend Tx
coverage to at least the Rx pass band.

You can do what you wish by creating a new configuration
("Menu->Configurations") and in that new configuration turn off CAT
control ("Settings->Radio->RIg" as "None"). You can then use SPLIT on
your rig just like you would for a CW or phone QSO. Don't forget to set
WSJT-X to the correct band so that QSOs get logged on the correct band
and PSKReporter spots are accurate. I recommend setting WSJT-X to the Tx
dial frequency so that spots are in the JA band segment where the DX is
transmitting.

73
Bill
G4WJS.



___
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] Split operation

[Bill Somerville]

On 12/12/2018 17:45, OG55W wrote:

I have tried to find how to operate with split..
JA-stations are calling me in 1908 as I am transmitting in 1840, and I 
do not hear them as my RX or TX change the frequency.

I am not allowed to transmit in 1908.


Hi Keijo,

WSJT-X does not support this using CAT control, it conflicts with the 
way that WSJT-X uses CAT control to clean up Tx signals and extend Tx 
coverage to at least the Rx pass band.


You can do what you wish by creating a new configuration 
("Menu->Configurations") and in that new configuration turn off CAT 
control ("Settings->Radio->RIg" as "None"). You can then use SPLIT on 
your rig just like you would for a CW or phone QSO. Don't forget to set 
WSJT-X to the correct band so that QSOs get logged on the correct band 
and PSKReporter spots are accurate. I recommend setting WSJT-X to the Tx 
dial frequency so that spots are in the JA band segment where the DX is 
transmitting.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Previous versions of WSJT appear in Windows Control Panel

[Bill Somerville]

On 12/12/2018 17:44, Jim Jennings wrote:
One thing I noticed, Bill, after clearing the old entries from the 
Apps listing,  was that the installed version seemed to run better, 
although I cannot "quantify" this.  73,


Jim, W7XZ


Hi Jim,

that's not possible. The entries are just a few small key/value pairs in 
the Windows registry and WSJT-X does not go near the Windows registry 
when it is running, only the installer does that.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Type 13 UDP Packets - Highlight Callsign - Bulk Clearing?

[Bill Somerville]

On 12/12/2018 17:33, Brian Moran wrote:
Hi Bill, my question was related whether it is possible to clear ALL 
of the highlighting, without having to clear them separately via the 
UDP Packets. For example, if the contest is over, if the external 
program exited, if the operating mode changes, etc.

thanks,
Brian N9ADG


Hi Brian,

restart WSJT-X.

73
Bill
G4WJS.



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

Re: [wsjt-devel] What Does This Mean

[Richard Solomon]

OK, thanks for that. Now back to playing with the new version.

Tnx es HH, Dick, W1KSZ

Sent from Outlook

From: Bill Somerville 
Sent: Wednesday, December 12, 2018 9:37 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] What Does This Mean

On 12/12/2018 16:09, Richard Solomon wrote:
Installed Ver. 2.0 this AM and made a couple of Q's. No issues
to report, but one question.

I see <...> W1XYZ (using fake call so as not to upset anyone).
What does that mean ?

Not a problem here, just curious.

Tnx es HH, Dick, W1KSZ

Hi Dick,

when WSJT-X shows a callsign in an FT8 or MSK144 message enclosed in '<' and 
'>' characters it means that it was looked up from a hash code that was 
contained in the message. Hash codes can only be translated to callsigns if you 
have copied the full callsign in a recent previous message. If you have not 
copied the full callsign then WSJT-X will print '<...>' instead. This is common 
when you can on hear one side of a QSO.

Note that hash codes are only used for complex callsigns, so the other station 
is using a suffix, prefix or has more that three letters in the tail of their 
callsign.

See the WSJT-X User Guide 
.

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

Re: [wsjt-devel] Split operation

[OG55W]

Steven! The waterfall is only 3500 Hz wide and it should be more than 68000 Hz 
wide to hear 1908 kHz.

Keijo

From: Steven Greer 
Sent: Wednesday, December 12, 2018 7:52 PM
To: wsjt-devel@lists.sourceforge.net 
Subject: Re: [wsjt-devel] Split operation

Just check the keep TX frequency that way when you transmit you will be 
transmitting where you set yourself, and the rx will goto the calling station.  
Thats how I do it.  Not sure if I'm allowed to comment to the mailing to help 
others if not just let me know and I won't help out anymore on easy to answer 
questions.


On 12/12/18 12:45 PM, OG55W wrote:

   

  I have tried to find how to operate with split..
  JA-stations are calling me in 1908 as I am transmitting in 1840, and I do not 
hear them as my RX or TX change the frequency.
  I am not allowed to transmit in 1908.

  Somebody said that use the RIT, but with FT-2000 1908 is too far away…

   

  73 Keijo OG55W

   

   


   
   
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
-- 
Steven Greer
KM4OUS
OMISS #10630

NOTE: This e-mail was made with 100% recycled electrons.  No electrons were 
harmed, No trees were destroyed, No animals were killed, and No political 
correctness was observed in making or sending this message.






___
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] Split operation

[Steven Greer]

Just check the keep TX frequency that way when you transmit you will be 
transmitting where you set yourself, and the rx will goto the calling 
station.  Thats how I do it.  Not sure if I'm allowed to comment to the 
mailing to help others if not just let me know and I won't help out 
anymore on easy to answer questions.


On 12/12/18 12:45 PM, OG55W wrote:


I have tried to find how to operate with split..
JA-stations are calling me in 1908 as I am transmitting in 1840, and I 
do not hear them as my RX or TX change the frequency.

I am not allowed to transmit in 1908.

Somebody said that use the RIT, but with FT-2000 1908 is too far away…

73 Keijo OG55W



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


--
Steven Greer
KM4OUS
OMISS #10630

NOTE: This e-mail was made with 100% recycled electrons.  No electrons were 
harmed, No trees were destroyed, No animals were killed, and No political 
correctness was observed in making or sending this message.

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

[wsjt-devel] Split operation

[OG55W]

I have tried to find how to operate with split..
JA-stations are calling me in 1908 as I am transmitting in 1840, and I do not 
hear them as my RX or TX change the frequency.
I am not allowed to transmit in 1908.

Somebody said that use the RIT, but with FT-2000 1908 is too far away…

73 Keijo OG55W


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

Re: [wsjt-devel] Previous versions of WSJT appear in Windows Control Panel

[Jim Jennings]

One thing I noticed, Bill, after clearing the old entries from the Apps 
listing,  was that the installed version seemed to run better, although I 
cannot "quantify" this.  73,


Jim, W7XZ

-Original Message- 
From: Bill Somerville

Sent: Wednesday, December 12, 2018 08:08
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Previous versions of WSJT appear in Windows 
Control Panel


On 12/12/2018 16:04, Alan Rovner wrote:
Hi all, I went to uninstall another program on my ham PC, and noticed in 
the Windows Control Panel -> Programs and Features section, there are 6 
versions of WSJT displayed from previous installations.  Is this expected? 
The versions shown are 1.8.0, 1.9.0-rc2, 1.9.0-rc3, 1.9.0-rc4, 1.9.1, and 
2.0.0.


There appears to be only one version actually installed.  I'm afraid to 
uninstall the 1.8.0 item as it might uninstall 2.0.0 since it is the only 
active version now.  I'm running Windows 10 with recent updates installed.


Thanks for any info, vy 73,
Al, K7AR


Hi Al,

they are benign but if you want to clear them down you can uninstall
each of them. If you do unintentionally install one that is actually
there you can always re-install it, no log files, user data, or settings
will be lost when doing that.

73
Bill
G4WJS.



___
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] Type 13 UDP Packets - Highlight Callsign - Bulk Clearing?

[Brian Moran]

Hi Bill, my question was related whether it is possible to clear ALL of the
highlighting, without having to clear them separately via the UDP Packets.
For example, if the contest is over, if the external program exited, if the
operating mode changes, etc.
thanks,
Brian N9ADG


On Wed, Dec 12, 2018 at 9:20 AM Bill Somerville 
wrote:

> On 12/12/2018 17:00, Brian Moran wrote:
>
> Is there a way, once a new foreground / background color has been set for
> some text snippets via UDP Highlight Callsign packet for them ALL to be
> cleared?
>
> Hi Brian,
>
> yes, as stated in the UDP Message Protocol dcoumentation
> 
> you can send a Highlighting request specifying an invalid QColor value to
> reset all highlighting for that callsign. An invalid QColor value is one
> with the Invalid (0) colour spec field as opposed to, say, an RGB which has
> a colour spec of Rgb (1).
>
> 73
> Bill
> G4WJS.
> ___
> 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] Previous versions of WSJT appear in Windows Control Panel

[Jim Jennings]

When I installed V2.0.0-rc4 some weeks ago I noticed that Windows (10 Home) 
Settings>Apps showed four previous versions or RCs in the listing.  I had 
been overwriting V1.9.1 and  V2 RCs thereafter when installing the latest. 
To remove these from Apps, I uninstalled the newest, then reinstalled (from 
my Downloads directory) and immediately uninstalled each version/RC showing 
there.  I installed -rc5 after uninstalling -rc4 in Settings>Apps, and it 
left me with only the current instance.  If the older version installation 
files are needed to do this, Sourceforge keeps an archive of all the old 
stuff.  Hope this helps.  73,


Jim, W7XZ

-Original Message- 
From: Alan Rovner

Sent: Wednesday, December 12, 2018 08:04
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Previous versions of WSJT appear in Windows Control 
Panel


Hi all, I went to uninstall another program on my ham PC, and noticed in
the Windows Control Panel -> Programs and Features section, there are 6
versions of WSJT displayed from previous installations.  Is this
expected?  The versions shown are 1.8.0, 1.9.0-rc2, 1.9.0-rc3,
1.9.0-rc4, 1.9.1, and 2.0.0.

There appears to be only one version actually installed.  I'm afraid to
uninstall the 1.8.0 item as it might uninstall 2.0.0 since it is the
only active version now.  I'm running Windows 10 with recent updates
installed.

Thanks for any info, vy 73,
Al, K7AR



___
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] Type 13 UDP Packets - Highlight Callsign - Bulk Clearing?

[Bill Somerville]

On 12/12/2018 17:00, Brian Moran wrote:
Is there a way, once a new foreground / background color has been set 
for some text snippets via UDP Highlight Callsign packet for them ALL 
to be cleared?



Hi Brian,

yes, as stated in the UDP Message Protocol dcoumentation 
 
you can send a Highlighting request specifying an invalid QColor value 
to reset all highlighting for that callsign. An invalid QColor value is 
one with the Invalid (0) colour spec field as opposed to, say, an RGB 
which has a colour spec of Rgb (1).


73
Bill
G4WJS.

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

Re: [wsjt-devel] POTA - compound callsigns and grid square

[Bill Somerville]

On 12/12/2018 15:44, David Garnier wrote:
But to the GUI guys: don’t forget us minimalist operators; be it on 
SOTA or running a pileup in the

cold we are there.  We actually need very little!


Dave,

if you do not want decode highlighting then switch it off 
"Settings->General->Show DXCC, grid, and worked before status". That 
will also remove the very small CPU overhead of looking up the internal 
tables as well so may allow you to get decodes a  few milliseconds 
faster on your low powered portable PC.


73
Bill
G4WJS.

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

[wsjt-devel] Type 13 UDP Packets - Highlight Callsign - Bulk Clearing?

[Brian Moran]

Is there a way, once a new foreground / background color has been set for
some text snippets via UDP Highlight Callsign packet for them ALL to be
cleared?

I'm thinking of the instance where perhaps a callsign is colored to reflect
a particular status during a contest or operation, but then the contest or
operation ends. In my exploration of using this type of packet, after
WSJT-X is terminated and restarted, call signs are still colored.

Is there a manual way of 'un-coloring' all of the previously colored call
signs without using the API?

Thanks,
Brian N9ADG
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] POTA - compound callsigns and grid square

[David Garnier]

Good morning,
I’m a parks on the air (POTA) Op and having “space”for any 4 digit numbers is a 
big deal!  We POTApark/wilderness operators run a bare bones minimalist 
operation.  Trying to run the full blown WSJT operation with JT-alert and color 
codingup the gazoo is ridiculous and not needed. In fact Idon’t use those 
functions at home for philosophical reasons, it forces me to think and be a 
better ham (something that seems forgotten by the new crop of hams.) 
Keep up the great weak signal development Joe andcompany!!  POTA operations are 
like mini field day deployments but with compromised antennas, anyWSJT mode is 
another tool in our toolbox.But to the GUI guys: don’t forget us minimalist 
operators; be it on SOTA or running a pileup in the cold we are there.  We 
actually need very little!
73/44’s - Dave - wb9own 



Sent from Yahoo Mail for iPhone


On Tuesday, December 11, 2018, 7:18 PM, Bill Somerville  
wrote:

On 12/12/2018 00:02, Mike Maynard wrote:
> Well, I shall start with the fact that when I started doing mobile and 
> asked around, it was said that I needed to update my grid square as I 
> moved from one square to another.  thus I concluded that many people 
> would take offense to me not even using one?  I thought that the grid 
> square was part of the 'accepted' protocol for FT8 and if I were not 
> to use one, that it may offend many people.
>
> I find it interesting that we have taken a mode that everyone seems to 
> love as a 'fun' mode as its primary use to a primary contest mode, and 
> oh yeah have fun with it if you can as well.
>
> I am all about progress, improvements and furthering the hobby.  I 
> dont have any issue with upgrades, etc.  I just dont see why we have 
> to sacrifice things that were once working fine to make it happen.
>
> I am starting to see why so many people are griping about the new 
> version, which up until I tried to use my mobile callsign I fully 
> supported.
>
Hi Mike,

that doesn't seem to address my question, but I will comment on what you 
say here also.

Firstly WSJT-X is all about weak signal communications, that constrains 
the implementation domain. There is a reason why minimal QSOs are part 
of the equation. To complete QSOs in an acceptable time without using 
excessive bandwidth either the amount of information transferred must be 
limited or the sensitivity must be reduced. Sensitivity is very high on 
the list of desirable characteristics. To allow more flexibility in 
possible QSOs the envelope of allowed messages has been given a shake 
up, it is now larger with respect to the overall potential user base and 
that has been done by pushing out in a few important places. By making 
room for new groups some existing edge cases have had to be discarded, 
they couldn't all fit in. Your preferred QSO style was in a previous 
group of cases that have been discarded for a new large group (much 
larger BTW) which still allows you to make QSOs but only within the 
limitation that you cannot call CQ with a grid square. You should note 
that this is nothing new, in the 75-bit message payload all type 2 
compound callsign holders have always had that same restriction.

Regarding exchanging a grid square in a QSO, it has never been a 
requirement, the normally accepted exchange of information for a QSO is 
to exchange and acknowledge receipt of each others callsigns and to 
exchange and acknowledge another piece of QSO specific information such 
as a signal report. A grid square is not a callsign, nor is it QSO 
specific (even it you are operating mobile). As far as the WSJT-X 
developers are concerned, a grid square is sent because it is an aid to 
establishing a QSO, i.e. for aerial pointing or Doppler correction 
calculations on EME paths. The WSJT-X QSO templates started with VHF and 
up as well as EME paths where grid squares are very useful, on HF they 
are much less so but there was little justification to change them. The 
grid is effectively exchanged for free while making a general call or 
answering a call and acknowledging the callers callsign.

You should note that LoTW which is used a great deal these days to 
confirm and validate QSOs does not require a match of copied grid square 
or any other location information, quite the opposite in that if the 
time, frequency, and call match then the QSO match will actually deliver 
the other operator's grid square. Just like an old fashioned QSL card, 
there has never been any requirement to exchange location information 
except in contests where that information is explicitly required in the 
exchange.

If you are operating in an unusual grid square then you still have the 
opportunity to state that to listeners, just not in your general calls. 
You can use the standard message form I suggested in a QSO, or in your 
case with a 1 by 2 callsign, send a free text message like "K2GC/M FN03".

73
Bill
G4WJS.



___
wsjt-devel mailing list

Re: [wsjt-devel] What Does This Mean

[Bill Somerville]

On 12/12/2018 16:09, Richard Solomon wrote:

Installed Ver. 2.0 this AM and made a couple of Q's. No issues
to report, but one question.

I see <...> W1XYZ (using fake call so as not to upset anyone).
What does that mean ?

Not a problem here, just curious.

Tnx es HH, Dick, W1KSZ


Hi Dick,

when WSJT-X shows a callsign in an FT8 or MSK144 message enclosed in '<' 
and '>' characters it means that it was looked up from a hash code that 
was contained in the message. Hash codes can only be translated to 
callsigns if you have copied the full callsign in a recent previous 
message. If you have not copied the full callsign then WSJT-X will print 
'<...>' instead. This is common when you can on hear one side of a QSO.


Note that hash codes are only used for complex callsigns, so the other 
station is using a suffix, prefix or has more that three letters in the 
tail of their callsign.


See the WSJT-X User Guide . 



73
Bill
G4WJS.

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

Re: [wsjt-devel] compound callsigns and grid square

[Bill Somerville]

Hi Mike,

 comments in line below.

On 12/12/2018 16:09, Mike Maynard wrote:

I am starting to understand some...
It is tricky to explain without a full explanation of the finest details 
of how messages are source encoded (packed) into the available payload bits.


I do not get though, why on a cq it cant be included (or at least 
operator choice?).  I do understand its not going to fit on a reply to 
someone elses cq, but there are other places it could be put.
The place it will not fit is the message payload, it simply cannot be 
sent. This is because the CQ which takes up the space of one basic 
callsign and a complex callsign like your /M call use up almost all the 
available payload bits, there are not enough remaining to encode a grid 
square. What may be confusing is that both the word CQ and your /M call 
are short but that is not relevant here since both are reduced to unique 
numbers that have a fixed width. For example all standard callsigns are 
encoded as a unique 28-bit number so A1A and GM4WJS both take exactly 
28-bits of payload. A1A/M, K2GC/M, GM4WJS/PJ4, and YP4XMAS are all 
complex callsigns that take more than 28-bits of payload space.


For a work around  is there a 'Token' I can use to put in a field 
that will pull the grid from settings?  I have a script that runs 
against the GPS to give me my current grid square and inject it into 
WSJT.  If there was a 'Token' (variable  what ever you want to 
call it) that I could insert into one of the message fields that says 
"hey, put the current grid square here"  I am sure I could make it work.
We don't currently support message "macro" insertion, I doubt it will be 
added due to the 13 character restriction on free text messages which 
would undoubtedly cause many support issues when truncated messages get 
sent.


Thanks for listening to me complain
No problem Mike, we do understand that there are both winners and losers 
when changes like we have just made happen. We strive to have more 
winners than losers and in this case you are not blocked from using 
WSJT-X at all even though you may have to operate in a slightly 
different way. You can still operate using the full callsign that you 
are legally required to use and many others who were barred from using 
WSJT-X by such a restriction can now use it.


Mike
K2GC (sometimes /M!!)


73
Bill
G4WJS.



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

Re: [wsjt-devel] Run Two Versions of FT8

[Richard Solomon]

Thank you, got both running. But, from the dearth of signals
using 1.9, I may delete it shortly.

Tnx es HH, Dick, W1KSZ

Sent from Outlook

From: Peter Sumner 
Sent: Monday, December 10, 2018 3:20 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Run Two Versions of FT8

Hi Dick,
 you can run as many versions as you like, the best way is to create seperate 
config spaces by using the "wjstx.exe -r NAME"

I do this for each of my radio's with short cuts that look like this:

 C:\ham_radio\wsjtx\bin\wsjtx.exe -r 7600

 C:\ham_radio\wsjtx-2\bin\wsjtx.exe -r 910

which keeps all the config files in their seperate spots in your user profile, 
creating a sand box for each to play in and there is no cross polination of 
config files.

Regards,
Peter, vk5pj

On Tue, Dec 11, 2018 at 1:22 AM Richard Solomon 
mailto:w1...@outlook.com>> wrote:
Will there be any issues if I want to run both (1.9 & 2.0)
versions ?
I could put one in C:\WSJT1.9 and the other in C:\WSJT2.0
Directories. Create shortcuts to both.

That way, I could close down one and then open the other.

It seems to me a way to ease into the transition until the
majority switch over to 2.0.

Does anyone see any issues with doing this ?

Tnx es HH, Dick, W1KSZ

Sent from Outlook
___
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] compound callsigns and grid square

[Mike Maynard]

I am starting to understand some...

I do not get though, why on a cq it cant be included (or at least operator
choice?).  I do understand its not going to fit on a reply to someone elses
cq, but there are other places it could be put.

For a work around  is there a 'Token' I can use to put in a field that
will pull the grid from settings?  I have a script that runs against the
GPS to give me my current grid square and inject it into WSJT.  If there
was a 'Token' (variable  what ever you want to call it) that I could
insert into one of the message fields that says "hey, put the current grid
square here"  I am sure I could make it work.

Thanks for listening to me complain

Mike
K2GC (sometimes /M!!)

On Tue, Dec 11, 2018 at 8:16 PM Bill Somerville 
wrote:

> On 12/12/2018 00:02, Mike Maynard wrote:
> > Well, I shall start with the fact that when I started doing mobile and
> > asked around, it was said that I needed to update my grid square as I
> > moved from one square to another.  thus I concluded that many people
> > would take offense to me not even using one?  I thought that the grid
> > square was part of the 'accepted' protocol for FT8 and if I were not
> > to use one, that it may offend many people.
> >
> > I find it interesting that we have taken a mode that everyone seems to
> > love as a 'fun' mode as its primary use to a primary contest mode, and
> > oh yeah have fun with it if you can as well.
> >
> > I am all about progress, improvements and furthering the hobby.  I
> > dont have any issue with upgrades, etc.  I just dont see why we have
> > to sacrifice things that were once working fine to make it happen.
> >
> > I am starting to see why so many people are griping about the new
> > version, which up until I tried to use my mobile callsign I fully
> > supported.
> >
> Hi Mike,
>
> that doesn't seem to address my question, but I will comment on what you
> say here also.
>
> Firstly WSJT-X is all about weak signal communications, that constrains
> the implementation domain. There is a reason why minimal QSOs are part
> of the equation. To complete QSOs in an acceptable time without using
> excessive bandwidth either the amount of information transferred must be
> limited or the sensitivity must be reduced. Sensitivity is very high on
> the list of desirable characteristics. To allow more flexibility in
> possible QSOs the envelope of allowed messages has been given a shake
> up, it is now larger with respect to the overall potential user base and
> that has been done by pushing out in a few important places. By making
> room for new groups some existing edge cases have had to be discarded,
> they couldn't all fit in. Your preferred QSO style was in a previous
> group of cases that have been discarded for a new large group (much
> larger BTW) which still allows you to make QSOs but only within the
> limitation that you cannot call CQ with a grid square. You should note
> that this is nothing new, in the 75-bit message payload all type 2
> compound callsign holders have always had that same restriction.
>
> Regarding exchanging a grid square in a QSO, it has never been a
> requirement, the normally accepted exchange of information for a QSO is
> to exchange and acknowledge receipt of each others callsigns and to
> exchange and acknowledge another piece of QSO specific information such
> as a signal report. A grid square is not a callsign, nor is it QSO
> specific (even it you are operating mobile). As far as the WSJT-X
> developers are concerned, a grid square is sent because it is an aid to
> establishing a QSO, i.e. for aerial pointing or Doppler correction
> calculations on EME paths. The WSJT-X QSO templates started with VHF and
> up as well as EME paths where grid squares are very useful, on HF they
> are much less so but there was little justification to change them. The
> grid is effectively exchanged for free while making a general call or
> answering a call and acknowledging the callers callsign.
>
> You should note that LoTW which is used a great deal these days to
> confirm and validate QSOs does not require a match of copied grid square
> or any other location information, quite the opposite in that if the
> time, frequency, and call match then the QSO match will actually deliver
> the other operator's grid square. Just like an old fashioned QSL card,
> there has never been any requirement to exchange location information
> except in contests where that information is explicitly required in the
> exchange.
>
> If you are operating in an unusual grid square then you still have the
> opportunity to state that to listeners, just not in your general calls.
> You can use the standard message form I suggested in a QSO, or in your
> case with a 1 by 2 callsign, send a free text message like "K2GC/M FN03".
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> 

[wsjt-devel] What Does This Mean

[Richard Solomon]

Installed Ver. 2.0 this AM and made a couple of Q's. No issues
to report, but one question.

I see <...> W1XYZ (using fake call so as not to upset anyone).
What does that mean ?

Not a problem here, just curious.

Tnx es HH, Dick, W1KSZ

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

[wsjt-devel] Previous versions of WSJT appear in Windows

[Lahra Svare KT9X]

Yes. I ache version has a separate uninstall in the CP in windows.  I can’t 
tell you for sure for your install, but when I uninstalled mine past versions 
it left 2.0 intact. 

73 de KT9X 
Lahra



Sent from Flip’s iPhone



> On Dec 12, 2018, at 08:05, wsjt-devel-requ...@lists.sourceforge.net wrote:
> 
> Previous versions of WSJT appear in Windows


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

Re: [wsjt-devel] Previous versions of WSJT appear in Windows Control Panel

[Bill Somerville]

On 12/12/2018 16:04, Alan Rovner wrote:
Hi all, I went to uninstall another program on my ham PC, and noticed 
in the Windows Control Panel -> Programs and Features section, there 
are 6 versions of WSJT displayed from previous installations.  Is this 
expected?  The versions shown are 1.8.0, 1.9.0-rc2, 1.9.0-rc3, 
1.9.0-rc4, 1.9.1, and 2.0.0.


There appears to be only one version actually installed.  I'm afraid 
to uninstall the 1.8.0 item as it might uninstall 2.0.0 since it is 
the only active version now.  I'm running Windows 10 with recent 
updates installed.


Thanks for any info, vy 73,
Al, K7AR


Hi Al,

they are benign but if you want to clear them down you can uninstall 
each of them. If you do unintentionally install one that is actually 
there you can always re-install it, no log files, user data, or settings 
will be lost when doing that.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Enhanced UDP Features in 2.0.0

[Bill Somerville]

On 12/12/2018 15:58, Alan Rovner wrote:
Hi all, the user guide for 2.0.0 briefly mentions enhanced UDP 
features but doesn't provide any details.  What has been added or 
enhanced?


TU, 73,
Al, K7AR


Hi Al,

the documentation of the WSJT-X UDP message protocol is here:

https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/NetworkMessage.hpp#l5

in the large comment at the top of the file. Click the history icon 
 
at the top right for the change history of this file.


73
Bill
G4WJS.

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

[wsjt-devel] Previous versions of WSJT appear in Windows Control Panel

[Alan Rovner]

Hi all, I went to uninstall another program on my ham PC, and noticed in 
the Windows Control Panel -> Programs and Features section, there are 6 
versions of WSJT displayed from previous installations.  Is this 
expected?  The versions shown are 1.8.0, 1.9.0-rc2, 1.9.0-rc3, 
1.9.0-rc4, 1.9.1, and 2.0.0.


There appears to be only one version actually installed.  I'm afraid to 
uninstall the 1.8.0 item as it might uninstall 2.0.0 since it is the 
only active version now.  I'm running Windows 10 with recent updates 
installed.


Thanks for any info, vy 73,
Al, K7AR



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

[wsjt-devel] Enhanced UDP Features in 2.0.0

[Alan Rovner]

Hi all, the user guide for 2.0.0 briefly mentions enhanced UDP features 
but doesn't provide any details.  What has been added or enhanced?


TU, 73,
Al, K7AR



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

Re: [wsjt-devel] WSJT-X 2.0.0: GA release

[Bill Somerville]

On 12/12/2018 14:57, Richard Shaw wrote:
wjstx 2.0.0 has landed in the Fedora testing repositories for Fedora 
28, 29, Rawhide and Fedora EPEL 7 (CentOS,SL,etc)


This includes builds for ppc, ppcle, aarch64, armv7hl, s390 on Fedora. 
If you have a Fedora account and can give the package +1 karma then 
I'll be able to push it to stable sooner, otherwise after 7 days in 
testing I can push to stable.


Fedora:

dnf --enablerepo=updates-testing update wsjtx

CentOS 7 (Fedora EPEL repository must be installed):

yum --enablerepo=epel-testing update wsjtx

Of course if you remove it first change "update" to "install"

Thanks,
Richard
KF5OIM


Hi Richard,

thanks so much for this. We need more like you for other Linux 
distributions.


Upvoted.

73
Bill
G4WJS.



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

Re: [wsjt-devel] Rx Frequency doesn't move to QSO partner frequency.

[Neil Zampella]

Hi Joe,

thanks ... didn't think I had seen that happen before :(

Neil, KN3ILZ

On 12/12/2018 8:22 AM, Joe Taylor wrote:

Hi Neil,

On 12/11/2018 11:46 PM, Neil Zampella KN3ILZ wrote:

I was calling CQ with the Hold Tx Freq set.  I has just finished an 
QSO with a station, and someone replied to a CQ call a minute later.  
The Auto Sequence kicked in fine, and the QSO was completed properly. 
However, when I looked back on the exchange in the Rx Frequency 
window, I noticed that I was getting decodes in that window from my 
previous QSO partner.


Looking at the waterfall, I saw that the Rx Green Bracket had not 
moved to the new QSO partner's frequency, but stayed with the old 
one.  I have an attachment, not sure which is better keep the screen 
cap as an attachment or as an inline picture.


Looks perfectly normal to me.  The "Rx Frequency" window gets anything 
decoded within a few Hz of Rx Freq and anything containing your own 
call.  The green goal posts did not move to your new QSO partner's 
frequency because you did not double-click on his call to start the 
QSO.  You had "Call 1st" enabled, so the QSO started automatically 
when he replied to your CQ.


-- 73, Joe, K1JT



---
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] WSJT-X 2.0.0: GA release

[Richard Shaw]

wjstx 2.0.0 has landed in the Fedora testing repositories for Fedora 28,
29, Rawhide and Fedora EPEL 7 (CentOS,SL,etc)

This includes builds for ppc, ppcle, aarch64, armv7hl, s390 on Fedora. If
you have a Fedora account and can give the package +1 karma then I'll be
able to push it to stable sooner, otherwise after 7 days in testing I can
push to stable.

Fedora:

dnf --enablerepo=updates-testing update wsjtx

CentOS 7 (Fedora EPEL repository must be installed):

yum --enablerepo=epel-testing update wsjtx

Of course if you remove it first change "update" to "install"

Thanks,
Richard
KF5OIM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem - WSJT-X decoding poorly.

[WB5JJJ]

The biggest problem I see is that you are WAY behind the curve on
software.  The current version is v2.0.0 GA and all previous versions are
deemed obsolete and incompatible with v2.  I suggest you update as soon as
you can and once you do, you will see more decodes as the decoders in v2
have been vastly improved.

George - WB5JJJ

On Wed, Dec 12, 2018 at 8:25 AM Bob Seaboldt  wrote:

> Program version - wsjt-x v1.9.0-rc4
>
> Operating system - linux - Debian GNU/Linux 8 (jessie) 64-bit
>
> System - 2G ram, 1.66GHz (dual), SSD HD 240G (acer aspire one)
>
> Radio - TS2000 with SignaLink USB (Through ACC port)
>
> Concise description of the problem - It seems that wsjt-x is unable to
> decode FT8, especially signals with high amplitude.   When I first had the
> system running, I was able to decode all signals (in fact I was very
> impressed).  Now, after about a week, it has stopped decoding properly.  I
> am using NTS time utility and the clock seems to be spot on, certainly
> within 2 seconds.  I have changed the audio level out of the SignaLink from
> 10 to 80 (on wsjtx - it was running well at about 30 to 50) with no change.
> I have also tried adjusting the audio level out of the TS2000 (menu 50C)
> again with no change.
>
> Exact sequence of steps required to reproduce the problem - Problem has
> been persistent for 2 days now.  If I see a signal calling CQ (usually a
> weaker signal), then I can work them.  If I call CQ and I see a station
> attempting to reply, then I likely will not see the decode.  Just
> monitoring I will see several signals on the waterfall (lets say 5), but
> only a few will decode (lets say 1).  it seems to be louder signals that
> are affected.
>
> - NS0V
>
> ___
> 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] Problem - WSJT-X decoding poorly.

[George J. Molnar]

Probably because you are using a beta release of software two versions back. 
The FT-8 and MSK144 protocols have changed in the last week, with the release 
of version 2.0.

You should update. It should clear your issues.

73,


George J Molnar
KF2T, Arlington, Virginia, USA


Please note my new email: geo...@molnar.tv

> On Dec 12, 2018, at 9:21 AM, Bob Seaboldt  wrote:
> 
> Program version - wsjt-x v1.9.0-rc4
> 
> Operating system - linux - Debian GNU/Linux 8 (jessie) 64-bit
> 
> System - 2G ram, 1.66GHz (dual), SSD HD 240G (acer aspire one)
> 
> Radio - TS2000 with SignaLink USB (Through ACC port)
> 
> Concise description of the problem - It seems that wsjt-x is unable to decode 
> FT8, especially signals with high amplitude.   When I first had the system 
> running, I was able to decode all signals (in fact I was very impressed).  
> Now, after about a week, it has stopped decoding properly.  I am using NTS 
> time utility and the clock seems to be spot on, certainly within 2 seconds.  
> I have changed the audio level out of the SignaLink from 10 to 80 (on wsjtx - 
> it was running well at about 30 to 50) with no change. I have also tried 
> adjusting the audio level out of the TS2000 (menu 50C) again with no change.
> 
> Exact sequence of steps required to reproduce the problem - Problem has been 
> persistent for 2 days now.  If I see a signal calling CQ (usually a weaker 
> signal), then I can work them.  If I call CQ and I see a station attempting 
> to reply, then I likely will not see the decode.  Just monitoring I will see 
> several signals on the waterfall (lets say 5), but only a few will decode 
> (lets say 1).  it seems to be louder signals that are affected.
> 
> - NS0V
> 
> ___
> 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 2.0.0: GA release

[n2lo]

Moved a monitor to 160m listening loops.
Top band Two dot Oh across the pond last night.

Next.. 80m
BCNU DE N2LO~>


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

[wsjt-devel] Problem - WSJT-X decoding poorly.

[Bob Seaboldt]

Program version - wsjt-x v1.9.0-rc4

Operating system - linux - Debian GNU/Linux 8 (jessie) 64-bit

System - 2G ram, 1.66GHz (dual), SSD HD 240G (acer aspire one)

Radio - TS2000 with SignaLink USB (Through ACC port)

Concise description of the problem - It seems that wsjt-x is unable to
decode FT8, especially signals with high amplitude.   When I first had the
system running, I was able to decode all signals (in fact I was very
impressed).  Now, after about a week, it has stopped decoding properly.  I
am using NTS time utility and the clock seems to be spot on, certainly
within 2 seconds.  I have changed the audio level out of the SignaLink from
10 to 80 (on wsjtx - it was running well at about 30 to 50) with no change.
I have also tried adjusting the audio level out of the TS2000 (menu 50C)
again with no change.

Exact sequence of steps required to reproduce the problem - Problem has
been persistent for 2 days now.  If I see a signal calling CQ (usually a
weaker signal), then I can work them.  If I call CQ and I see a station
attempting to reply, then I likely will not see the decode.  Just
monitoring I will see several signals on the waterfall (lets say 5), but
only a few will decode (lets say 1).  it seems to be louder signals that
are affected.

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

Re: [wsjt-devel] Bug Report WSJT-X 2.0 - QSY QRG on MSK144

[Bill Somerville]

On 12/12/2018 13:58, Joe Taylor wrote:

Hi Alex,

On 12/12/2018 8:37 AM, DL1KDA Alex wrote:

I noticed one bug in the latest Version (2.0.0)

On MSK144 i can enter any "TX CQ ***" number in ***  but allways when 
i check to turn it on in the TX5 field appears "CQ 150 DL1KDA JO30"


You are observing the expected behavior.  Use of the "CQ nnn ..." 
feature is described in Section 10.4 of the WSJT-X 2.0 User Guide:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html#CONTROLS_CENTER 



... or page 53 of the German translation:

http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0_de.pdf 



To use this feature you must be using CAT control

Set your dial frequency to the one on which you wish to conduct a QSO, 
say 144.370.  (You can enter "370k" in the drop-down band selector box.)
Set the spinner control TX CQ to the kHz portion of the frequency on 
which you wish to call CQ, say "360".  Now while calling CQ you will 
transmit on 144.360 and receive on 144.170.  When someone answers you 
will continue the QSO on 144.370.


-- 73, Joe, K1JT 



Hi Alex,

further to Joe's comments, here is a screen capture of WSJT-X set up to 
call CQ on 144.380 MHz and expect replies on 144.360 MHz.


You can manage without CAT control by using SPLIT on your rig with care, 
set the Tx VFO to the calling frequency, the Rx VFO to the working 
frequency and WSJT-X to the working frequency then disable SPLIT when 
you get a reply, it is much easier with working CAT control.


73
Bill
G4WJS.

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

Re: [wsjt-devel] Bug Report WSJT-X 2.0 - QSY QRG on MSK144

[Joe Taylor]

Hi Alex,

On 12/12/2018 8:37 AM, DL1KDA Alex wrote:

I noticed one bug in the latest Version (2.0.0)

On MSK144 i can enter any "TX CQ ***" number in ***  but allways when i 
check to turn it on in the TX5 field appears "CQ 150 DL1KDA JO30"


You are observing the expected behavior.  Use of the "CQ nnn ..." 
feature is described in Section 10.4 of the WSJT-X 2.0 User Guide:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html#CONTROLS_CENTER

... or page 53 of the German translation:

http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0_de.pdf

To use this feature you must be using CAT control

Set your dial frequency to the one on which you wish to conduct a QSO, 
say 144.370.  (You can enter "370k" in the drop-down band selector box.)
Set the spinner control TX CQ to the kHz portion of the frequency on 
which you wish to call CQ, say "360".  Now while calling CQ you will 
transmit on 144.360 and receive on 144.170.  When someone answers you 
will continue the QSO on 144.370.


-- 73, Joe, K1JT


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

[wsjt-devel] Bug Report WSJT-X 2.0 - QSY QRG on MSK144

[DL1KDA Alex]

Dear team,

at first i want to thank you for your great work in developing this 
Software.


I noticed one bug in the latest Version (2.0.0)

On MSK144 i can enter any "TX CQ ***" number in ***  but allways when i 
check to turn it on in the TX5 field appears "CQ 150 DL1KDA JO30"



Vy 73 de Alex, DL1KDA




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

Re: [wsjt-devel] Rx Frequency doesn't move to QSO partner frequency.

[Joe Taylor]

Hi Neil,

On 12/11/2018 11:46 PM, Neil Zampella KN3ILZ wrote:

I was calling CQ with the Hold Tx Freq set.  I has just finished an QSO 
with a station, and someone replied to a CQ call a minute later.  The 
Auto Sequence kicked in fine, and the QSO was completed properly. 
However, when I looked back on the exchange in the Rx Frequency window, 
I noticed that I was getting decodes in that window from my previous QSO 
partner.


Looking at the waterfall, I saw that the Rx Green Bracket had not moved 
to the new QSO partner's frequency, but stayed with the old one.  I have 
an attachment, not sure which is better keep the screen cap as an 
attachment or as an inline picture.


Looks perfectly normal to me.  The "Rx Frequency" window gets anything 
decoded within a few Hz of Rx Freq and anything containing your own 
call.  The green goal posts did not move to your new QSO partner's 
frequency because you did not double-click on his call to start the QSO. 
 You had "Call 1st" enabled, so the QSO started automatically when he 
replied to your CQ.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Bug Report

[Joe Taylor]

Hi John,

False decodes are rare, but their frequency is not zero -- especially if 
you have checked "Decode | Enable AP".


Please read Section 12.1 of the User Guide, "AP Decoding":
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html

-- 73, Joe, K1JT

On 12/11/2018 9:56 PM, John LeRoy via wsjt-devel wrote:

  *

Program version: wsjt-x   v2.0.0

  *

Operating system:    Debian Stretch 64 bit Kernel Linux
4.9.0-8-amd64 x86_64 w/ MATE 1.16.2 desktop and libraries from
Debian Sid required for install of .deb package from wsjtx-x web
site (fortran and qt5).

  *

Concise description of the problem: I had just completed a QSO with
WA1GPO and was doing something else on the computer unrelated to
wsjt-x when this entry popped up in both panes. I stopped the
decoding so I could take a screen shot.

  *

Exact sequence of steps required to reproduce the problem: can't
reproduce, although I should note that the QSO required ten
transactions to complete - there was deep fading occurring.

73,

John W4JKL




___
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

[wsjt-devel] Message box at startup

[Svend Aage Jessen]

The info / message box that opens at startup...
How to deactivate this one, or will it deactivate by itself
at the date set in this box?

--
73 de LA6YJA
la6...@savednet.com



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

Re: [wsjt-devel] WSJT-X 2.0.0 Upgrade Video

[Unni Tharakkal]

Dear Virjil
Your U Tube video was helpful to get the LOTW error corrected.
I am a regular user of FT8 from its introduction.
I did install the latest version as per directions U have given. The
installation was successful.Another copy of 1.9. is also there.
Two problems I encountered are
THERE IS NO RX DECODING (not display in in RX window)
an error report showing - error scanning ADIF log. Invalid ADIF header
what can be the reasons.
Getting help from a regular user will be easy. Of course I am also trying
to locate the problem
So hope to hear from you Dr Virjil
Hope we can meet on band some times.

With regards to you and yours

73s
Unni
VU2TE

On Wed, Dec 12, 2018 at 12:48 AM Virgil Silhanek 
wrote:

> I upgraded to WSJT-X 2.0.0 and it's working well.  In an effort to help
> those reluctant to leave 1.9.1, I recorded a video this morning showing the
> process and how to install multiple versions at the same time.
> https://youtu.be/ClqHeHiB2hE
> Thanks,
>
> --
> *Virgil K7VZ*
>
>
> ___
> 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] Windows 7 freezes up when resizing the waterfall window

[Tom Ramberg via wsjt-devel]

 I updated the graphics device driver today, and it seems to have solved the 
problem. Thanks a lot, that was one thing that never crossed my mind!
And right now aproximately 8000 V2.0 users of a total of 21 000 WSJT-X users, 
according to Pskreporter.info. :)
73 de Tom OH6VDA

On Tuesday, December 11, 2018, 5:03:43 PM GMT+2, Bill Somerville 
 wrote:  
 
  On 11/12/2018 08:12, Tom Ramberg via wsjt-devel wrote:
  
 Possible bug? When resizing the waterfall window in v2.0.0 GA, the computer 
freezes up, and only a hard restart is possible. 
  This also happened in the 2.0.0-RC# versions. A workaround is to resize the 
window in v1.9.1, and then the problem does not occur, but since we are 
planning to stop using the old version, this is not a viable solution in the 
long run. 
 
Hi Tom,
 
no one else has reported that issue, I suspect it may be a graphics driver 
problem. Have you checked if there are any updates available for your graphics 
device drivers?
 
73
 Bill
 G4WJS.

  ___
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