Re: [wsjt-devel] WSJT-X 2.7.0-rc4

[Joe Taylor via wsjt-devel]

Hi all,

On 3/11/2024 11:02 PM, Jim Shorney NU0C via wsjt-devel wrote:


Confirmed same error, Kubuntu 22.04 up to date as of today.

Error: Symbol ‘ncand‘ at (1) is USE associated from module ‘q65‘ and cannot 
occur in COMMON
/home/nu0c/src/build/build/wsjtx-prefix/src/wsjtx/qmap/libqmap/q65c.f90:93:3:


Multiple reports of the same issue are not really necessary, especially 
after one of us in the development group has already responded.


Anyway, thanks to all for your reports.

A new tarball has been posted on the WSJT web site here:
https://wsjt.sourceforge.io/wsjtx.html

... and corrected source code (tagged 'wsjtx-2.7.0-rc4a') is available 
at the SourceForge git repository for WSJT-X.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

[Joe Taylor via wsjt-devel]

Hi Josh,

We're aware of the problem you report, but haven't yet got around to 
correcting it.  It does not affect builds on any of the systems we're 
using for development.  Compiler revisions are getting increasingly 
fussy about such things.


You can do one of the following:

1. Wait for the next release.

2. Let me know that you'd like a source-code patch, and I'll make it 
available after making the necessary changes.


3. Make the necessary changes yourself, to satisfy your compiler.

-- Joe, K1JT

On 3/11/2024 1:26 PM, Josh Rovero via wsjt-devel wrote:

On Fedora Core 39, 64 bit, (uname -a
Linux fedora 6.7.7-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Mar  1 
16:53:59 UTC 2024 x86_64 GNU/Linux, gcc version 13.2.1 20231205 (Red Hat 
13.2.1-6) (GCC))

I get the following errors building RC4:

[ 94%] Building Fortran object 
qmap/libqmap/CMakeFiles/qmap_impl.dir/q65c.f90.o

/home/josh/Downloads/wsjtx-2.7.0/src/wsjtx-prefix/src/wsjtx/qmap/libqmap/q65c.f90:24:32:

    24 |   common/decodes/ndecodes,ncand,nQDecoderDone,nWDecoderBusy,   
            &

       |                                1
Error: Symbol ‘ncand’ at (1) is USE associated from module ‘q65’ and 
cannot occur in COMMON

/home/josh/Downloads/wsjtx-2.7.0/src/wsjtx-prefix/src/wsjtx/qmap/libqmap/q65c.f90:93:3:

    93 | 999 return
       |   1
Warning: Label 999 at (1) defined but not used [-Wunused-label]
make[5]: *** [qmap/libqmap/CMakeFiles/qmap_impl.dir/build.make:323: 
qmap/libqmap/CMakeFiles/qmap_impl.dir/q65c.f90.o] Error 1
make[4]: *** [CMakeFiles/Makefile2:2157: 
qmap/libqmap/CMakeFiles/qmap_impl.dir/all] Error 2

make[3]: *** [Makefile:156: all] Error 2
make[2]: *** [CMakeFiles/wsjtx-build.dir/build.make:73: 
wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:279: CMakeFiles/wsjtx-build.dir/all] 
Error 2

make: *** [Makefile:91: all] Error 2

--
P.J. "Josh" Rovero http://www.roveroresearch.org 


Ham Radio: KK1D


___
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] Release Candidate WSJT-X 2.7.0-rc4

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc4 is 
ready for download and use by beta testers.


WSJT-X 2.7.0 Release Candidate 4 includes new features (especially for 
companion program QMAP) as well as bug fixes.  A full list of 
enhancements can be found in the Release Notes:


https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc4.txt

See also Section 1.1 of the WSJT-X User Guide for this candidate release:

https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc4.html#NEW_FEATURES

Release Candidates are intended for beta testers.  If you download and 
use WSJT-X 2.7.0-rc4, please remember to provide feedback to us on the 
new features in version 2.7, and on anything that does not seem to work 
properly for you.


Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html 
Scroll down to the heading "Candidate release:  WSJT-X 2.7.0-rc4".


For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is also available on the "Git" tab here: 
https://sourceforge.net/projects/wsjt/

It may take a short time for the code to be updated on SourceForge.


WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Feedback should be sent to this email list or one of the of the others 
mentioned here in the User Guide:


https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc4.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc4, and that you will help us 
to create a new General Availability (GA) release soon.


-- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] Another fun hash collision P97USI

[Joe Taylor via wsjt-devel]

Hi Jon,

On 2/26/2024 7:50 PM, Jon Anhold KM8V via wsjt-devel wrote:

231900 16 0.4 909 ~ BG2AUE  -25 Aruba
232530 5 0.4 909 ~ JR3UIC RR73; JA7WND  +06 DPR of Korea

Maybe some logic that checks "am I *really* North Korea?" would be good :)


That logic is you, the operator.  WSJT-X has many operator aids.  It is 
not an operator replacement.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Q65-15A Broken?

[Joe Taylor via wsjt-devel]

Hi Dwayne,

I discussed these issues at some length with Bob, KA1GT, some 1.5 years 
ago.  Here are the relevant details.


Sure, we could make a version of Q65-15A that can decode after normal 
EME delays.  It would not be a very good fit for the channel, however.


This is because the duration of a Q65 transmission is 12.8 s, and the 
transmission starts at t = 0.5 s into the 15-second sequence.  Add a 2.7 
s EME delay, and you're already 1 second into the next sequence -- even 
without any clock errors.


You could make the Tx duration smaller, say 10 s.  Then, if the 
transmission starts at t=0.5 s and there's a 2.7 s EME delay, reception 
would be complete at t=10.5 + 2.7 = 13.2 s, and (if clocks were spot on) 
the decoder would have 1.8 s to do its thing.  Even this is not really 
enough, because clocks are not always "spot on".  Moreover, you would 
lose an additional 10*log(12.8/10.0) = 1 dB of sensitivity.  WSJT moders 
do a lot to gain every 0.1 dB of sensitivity, so we certainly don't want 
to to that!


Fifteen-second sequences are not an efficient choice for a path with 
delays as large as 2.7 s.  If there were many times more EME activity 
than at present, so that very fast QSOs were desirable in contests, and 
if nearly everybody had many dB's to spare on the EME path, something 
like Q65-15A might be desirable.  As things stand, our advice is to use 
Q65-30B for EME on 1296 MHz.


-- 73, Joe, K1JT

On 1/22/2024 3:36 PM, Dwayne Sinclair wrote:

Thanks Joe for QSO and the confirmation that Q65-15A is not to be used for EME. 
Our “bad” in that in our circles we may have been referring to it as broken.

The attached article details some of the testing that has occurred to date in 
an attempt to work with what we have.

I guess the EME community (including me) are looking for a faster QSO where 
conditions and equipment support it?

Regards Dwayne AB6A


On Jan 22, 2024, at 11:54 AM, Joe Taylor  wrote:

Hi Dwayne,

Thanks for the QSO with W2ZQ, last evening.

Who is saying Q65-15A is broken, and why?

Are you (or they?) talking about EME?  If so, are you aware that the Q65-15x 
submodes are not supposed to work for EME.  The 2.5 s EME delay is too large.

-- 73, Joe, K1JT


On 1/22/2024 2:04 PM, Dwayne Sinclair via wsjt-devel wrote:
There have been ongoing reports from various operators best summarized in the 
post attached that Q65-15A is “broken”. What is current consensus on this and 
if it is broken, is there any plans to address the issues?
Q65-15A Part II Testing and Sensitivity Bob Atkins - KA1GT 
<https://www.bobatkins.com/radio/Q65-15_eme_II.html>
bobatkins.com <https://www.bobatkins.com/radio/Q65-15_eme_II.html>
favicon.ico <https://www.bobatkins.com/radio/Q65-15_eme_II.html>
<https://www.bobatkins.com/radio/Q65-15_eme_II.html>
Regards Dwayne AB6A
___
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] Q65-15A Broken?

[Joe Taylor via wsjt-devel]

Hi Dwayne,

Thanks for the QSO with W2ZQ, last evening.

Who is saying Q65-15A is broken, and why?  Are you (or they?) talking 
about EME?  If so, are you aware that the Q65-15x submodes are not 
supposed to work for EME.  The 2.5 s EME delay is too large.


-- 73, Joe, K1JT

On 1/22/2024 2:04 PM, Dwayne Sinclair via wsjt-devel wrote:
There have been ongoing reports from various operators best summarized 
in the post attached that Q65-15A is “broken”. What is current consensus 
on this and if it is broken, is there any plans to address the issues?


Q65-15A Part II Testing and Sensitivity Bob Atkins - KA1GT 


bobatkins.com 
favicon.ico 



Regards Dwayne AB6A


___
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] Q65-15A Broken?

[Joe Taylor via wsjt-devel]

Hi Dwayne,

Thanks for the QSO with W2ZQ, last evening.

Who is saying Q65-15A is broken, and why?

Are you (or they?) talking about EME?  If so, are you aware that the 
Q65-15x submodes are not supposed to work for EME.  The 2.5 s EME delay 
is too large.


-- 73, Joe, K1JT

On 1/22/2024 2:04 PM, Dwayne Sinclair via wsjt-devel wrote:
There have been ongoing reports from various operators best summarized 
in the post attached that Q65-15A is “broken”. What is current consensus 
on this and if it is broken, is there any plans to address the issues?


Q65-15A Part II Testing and Sensitivity Bob Atkins - KA1GT 


bobatkins.com 
favicon.ico 



Regards Dwayne AB6A


___
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] MSK144 in jt9.exe

[Joe Taylor via wsjt-devel]

Hi Alex,

Thanks for providing additional details.  I have merged your 
contribution into our 'develop' branch.  The next release of WSJT-X will 
include MSK144 decode capability in the jt9[.exe] executable.


-- 73, Joe, K1JT

On 1/7/2024 10:58 AM, Alex, VE3NEA via wsjt-devel wrote:

Hi Joe,

Thank you for considering my submission. This change will allow jt9.exe 
to be used for decoding the MSK144 signals either from a wav file or 
from the shared memory. There were requests for such improvement in the 
past, see for example this posting:


(https://sourceforge.net/p/wsjt/mailman/message/36905061/)

I am working on an open source program that sits in the system tray and 
decodes the WSJT-X modes on multiple frequencies 24/7. This program uses 
jt9.exe for decoding, that is why I need these changes: it is better to 
use jt9.exe from the official distribution rather than a custom built 
command-line program.


As I already mentioned, this does not affect the way MSK144 is decoded 
in WSJT-X and only adds a new option to jt9.exe for those who need it.


73 Alex VE3NEA



On 2024-01-07 08:50, Joe Taylor via wsjt-devel wrote:

Hi Alex,

Thanks for your suggested changes to jt9.exe.

As you know, decoding of MSK144 has always been done immediately as 
new data are acquired, rather than at the end of a timed receive 
sequence in the jt9[.exe] executable.  Before we make any decision 
about merging your suggestions into the main branch of WSJT-X, could 
you elaborate just a bit about your intended purpose and any supposed 
advantages?


 -- 73, Joe, K1JT

On 1/6/2024 8:12 AM, Alex, VE3NEA via wsjt-devel wrote:

Hello team,

I have made changes to the jt9.exe code to allow it decode MSK144. 
This does not affect the existing functions of WSJT-X, so it is a low 
risk change, and I would like it to be merged to the main branch. The 
modified files are attached. Do I need to do anything else to make my 
submission accepted?


73 Alex VE3NEA


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

Re: [wsjt-devel] MSK144 in jt9.exe

[Joe Taylor via wsjt-devel]

Hi Alex,

Thanks for your suggested changes to jt9.exe.

As you know, decoding of MSK144 has always been done immediately as new 
data are acquired, rather than at the end of a timed receive sequence in 
the jt9[.exe] executable.  Before we make any decision about merging 
your suggestions into the main branch of WSJT-X, could you elaborate 
just a bit about your intended purpose and any supposed advantages?


-- 73, Joe, K1JT

On 1/6/2024 8:12 AM, Alex, VE3NEA via wsjt-devel wrote:

Hello team,

I have made changes to the jt9.exe code to allow it decode MSK144. This 
does not affect the existing functions of WSJT-X, so it is a low risk 
change, and I would like it to be merged to the main branch. The 
modified files are attached. Do I need to do anything else to make my 
submission accepted?


73 Alex VE3NEA


___
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] Release Candidate WSJT-X 2.7.0-rc3

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc3 is 
ready for download by beta testers.


WSJT-X 2.7.0 Release Candidate 3 includes new features as well as bug 
fixes.  A full list of enhancements can be found in the Release Notes:


https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc3.txt

See also Section 1.1 of the WSJT-X User Guide for this candidate release:

https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc3.html#NEW_FEATURES

Release Candidates are intended for beta testers.  If you download and 
use WSJT-X 2.7.0-rc3, please remember to provide feedback to us on the 
new features in version 2.7, and on anything that does not seem to work 
properly for you.


Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html 
Scroll down to the heading "Candidate release:  WSJT-X 2.7.0-rc3".


For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is also available on the "Git" tab here: 
https://sourceforge.net/projects/wsjt/

It may take a short time for the code to be updated on SourceForge.


WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Feedback should be sent to this email list or one of the of the others 
mentioned here in the User Guide:


https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc3.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc3, and that you will help us 
to create a new General Availability (GA) release soon.


-- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] callsigns in <>

[Joe Taylor via wsjt-devel]

Hi Bruce,

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

https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.6.1.html#COMP-CALL

Take particular notice of this sentence:

"Except for the special cases involving /P or /R used in VHF contesting, 
WSJT-X 2.6 offers no support for two nonstandard callsigns to work each 
other."


In such a situation you should work WB0GAG/1 as WB0GAG.

-- 73, Joe, K1JT

On 12/27/2023 10:37 AM, Bruce Dagel via wsjt-devel wrote:

WSJT-X version 2.6.1

My mistake, I was going from memory.
The actual problem comes with a longer call.  WB0GAG/1  R+11 
transmits as WB0GAG 


73,
Bruce, WB0GAG


___
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] QMAP query

[Joe Taylor via wsjt-devel]

Hi David,

It seems that SDR Console stopped sending its I/Q data stream to QMAP, 
or for some reason QMAP closed its input port.  Unless you can find a 
way to replicate this unwanted condition at will, I have no particular 
suggestions.  I have never seen a comparable fault in the Linrad-to-QMAP 
setups that I use regularly.


-- 73, Joe, K1JT

On 12/18/2023 6:19 PM, David Hilton-Jones via wsjt-devel wrote:

I am using rc2, SDRconsole with RSPDx, and QMAP


Today, all was running fine. I clicked on a station in “Active 
stations”, and WSJT-x took me to transmit, and the QSO ran as normal.


However, after my first transmit period, on return to receive, QMAP was 
showing no input signal, whilst SDRconsole was displaying normally. 
WSJT-x was working normally. I closed QMAP, and re-opened it, then it 
was working again.


I obviously need to try again a few more times, but didn’t have time today.

Any thoughts?

David, G4YTL

Sent from the all-new AOL app for iOS 




___
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 noise estimates

[Joe Taylor via wsjt-devel]

Hi Joe,

On 12/9/2023 9:56 PM, w0fy--- via wsjt-devel wrote:
Been wondering how WSJT-X generates the noise power estimate it uses to 
calculate SNR for each FT8 signal.  Does it simply collect all the 
signals and noise over the bandwidth selected on the waterfall and call 
that the noise power level or does it take a quick snapshot of  the 
background noise level during the brief quiet period at the end of each 
15 second FT8 sequence? Or is it more complicated than that?


This question has been asked and answered many times on this and similar 
forums.  WSJT-X measures noise power by computing the spectrum of the 
receiver's output, averaged over the reception interval, and fitting a 
baseline to the regions that have no discernible signal present.  The 
resulting value -- effectively a noise power density, or power per unit 
bandwidth -- is then scaled to yield noise power in 2500 Hz bandwidth.


I am plagued with a S2 -S3 noise level on 6 meters nearly all the time 
that if not AWGN is pretty close to it.  10 meters is even worse. The 
DSP noise blanker in my TS590 will reduce it slightly. I estimate this 
is degrading my ability to decode FT8 signals on 6 by nearly 20 dB 
compared to the noise level generated by a 50 ohm resistor.  I don’t use 
an LNA ahead of the radio – would be pointless.  I don’t use the noise 
reduction feature in the radio either as it tends to lose very weak 
signals completely.


It's OK to use your receiver's noise blanker to remove impulsive noise.

Do NOT use "noise reduction" features, and do NOT use a receiver 
bandwidth narrower than about 2.5 kHz.  Wider bandwidths are even 
better, up to 4 or 5 kHz.  WSJT-X does all necessary narrow-band 
filtering in software.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

[Joe Taylor via wsjt-devel]

I agree.  It's good enough as you have it.

-- Joe

On 12/8/2023 2:50 PM, Uwe, DG2YCB via wsjt-devel wrote:

Hi all,

Once again regarding my question about EU / AS Turkey: My commit only 
changes the displayed country name. Theoretically, the distinction 
between continents etc. should therefore remain unaffected. I have just 
looked up how LotW and QRZ.com do it. There is also only one entry 
there, namely "Turkey". So this should not be wrong if this is also the 
case with WSJT-X in the future. If someone wants to differentiate 
between the two, all they have to do is activate the "Include extra WAE 
entites" checkbox. And why should this be treated differently for AF 
Italy than for EU Turkey?


How do you see it?

73 de Uwe, DG2YCB


Am 08.12.2023 um 18:50 schrieb Uwe, DG2YCB via wsjt-devel:
This may all be correct, but at least to me, the decisive factor is 
what the DXCC rules are. And according to the DXCC list 
 available 
to me, there is only one "Turkey", namely DXCC No. 390.


TA-TC* Turkey EU/AS 39 20 390

73 de DG2YCB,
Uwe

German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB


Am 08.12.2023 um 18:22 schrieb robert evans LAST_NAME via wsjt-devel:
East Thrace or Eastern Thrace, also known as Turkish Thrace or 
European Turkey, is the part of Turkey that is geographically a part 
of Southeast Europe. It accounts for 3.03% of Turkey's land area and 
15% of its population. The largest city is Istanbul, which straddles 
the Bosporus between Europe and Asia.

Asiatic Turkey is east of the Bosporus.
The Bosporus is where the Aegean and Mediterranean Seas broke through
and flooded the Black Sea.
I spent some time in Karamursel, Sinop, and Incirlik which are in
Asiatic Turkey.
Karamursel had a elephant cage AN/FLR-9 until they bombed
Cyprus and they closed this base when USA came out against it.
Sinop is a spit of land that sticks out in the Black Sea and was a NATO
listening post just south of Crimea and might still be.
Incirlik is still a very busy base down near the Mediterranean Sea.
Merhaba Arkadaslar. Nasiliniz?
On 12/08/2023 11:38 AM EST Uwe, DG2YCB via wsjt-devel 
 wrote:

Hi Jim and all,

I have analyzed our WSJT-X code regarding this aspect. Results: 
There seems to be nowhere specified which countries the WAE entities 
shall be assigned to when the "Include extra WAE entites" checkbox 
is *not* checked, neither in the CTY.DAT file nor in WSJT-X. This 
means, if these entities are not queried, "" appears as a country 
name. Quite logical in my eyes.


Therefore, I reprogrammed it in a way, that the WAE entities are now 
always queried but that these special country names are replaced by 
the correct DXCCs later in case the "Include extra WAE entites" 
checkbox is not checked.


The first tests look already promising. (My setup: Two instances 
connected via virtual audio, meaning that nothing goes over HF, and 
I can simulate almost each QSO situation.)




By the way, what is with "European Turkey"? Must both "Asiatic 
Turkey" and "European Turkey" then be displayed as "Turkey" if the 
"Include extra WAE entites" checkbox is not checked?


Did I forget anything else?

73 de DG2YCB,
Uwe

German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB


Am 07.12.2023 um 02:50 schrieb Jim Reisert AD1C via wsjt-devel:
This message is rather long, but I want to address this issue so it 
can be fixed before WSJT-X 2.7 is released.  Also note that this 
message contains a lot of formatting.  If it doesn't pass through 
the mailing list correctly, please contact me and I can send you 
the original copy.

I recently received this message:

On Tue, Nov 28, 2023 at 9:03 AM Dave Garber ve3wej 
 wrote:


I am getting 4u1a on ft4 today, and wsjt-x is showing it as
Italy.  I have downloaded the updated cty-3388 file, and put
the cty.dat file ( which does show Austria , not Italy.  and
put it the the save folder of each of my wsjt versions..   am I
in the wrong folder, because it still shows Italy still

Ron Whitsel, W3RJW also wrote me:

4U1A comes up as 'Italy' in WSJT-X Band Activity window.   
Should be Austria


He later wrote:

OK I fixed it:

Added:

Removed 4U from Italy

Now 4U1A comes up as Austria in WSJT-X.

After some back-and-forth with Brett VR2BG today, I think I might 
understand the problem.  I believe that WSJT-X is either parsing or 
using the country file incorrectly.

First some background:
The CQWW DX contest uses two different country lists.  It uses the 
ARRL DXCC lists, plus five (5) entities which are multipliers for 
the WAEDC contest, plus one other:

https://www.darc.de/der-club/referate/conteste/wae-dx-contest/en/wae-rules/
Look at the bottom of that page for "WAE Country List".  It lists 
these 

Re: [wsjt-devel] 160m S/N needs advanced mode

[Joe Taylor via wsjt-devel]

Hi Glenn,

Searching the User Guide for a keyword is often a helpful way to find a 
section of interest, but it's hardly a substitute for actually reading 
the Guide.  The second and third paragraphs of the whole Guide introduce 
each of the supported protocols and provide a few words about what it's 
designed for.  Here's what is said about FST4:


"FST4 is designed especially for the LF and MF bands."

For what it's worth: I note that the "CTRL-F" search that you mentioned 
does take you directly to Table 7 in Section 17.2 -- the summary I drew 
to your particular attention.


-- 73, Joe, K1JT

On 12/7/2023 5:41 PM, Glenn Williams via wsjt-devel wrote:

Thanks for the guidance.

So I'll take the hit for overlooking FST4 and FST4W for the needed low 
S/N. I jumped to conclusions too quickly. I do that too
often in life. This happened after operating FT8 since 2021.  My 
oversight is due to the following reliance on a method of quickly

scanning for the assumed discussion early in the User Guide.

I started from the top of the User Guide PDF file and did a CTRL-F 
("find") for "S/N". The third "Find" hit on "S/N" occurs in
Section 7.1 of the User Guide. The fourth hit on "S/N" occurs in 
17.2.10. Between those two points, and in "1. Introduction" no
tabulation of S/N advantages occurs, when S/N is such a key value for 
all WSJT-X modes. Albeit, discussions do occur about
weak-signal conditions on  LF, HF, and VHF between those two points in 
the Guide, but "how weak" is not as often emphasized.


--73, Glenn, AF8C

On 12/7/2023 2:55 PM, Reino Talarmo via wsjt-devel wrote:

Hello Glenn,
I think that you wish is already heard and fulfilled.
The suitable mode is FST4. There are seven modes with
transmission periods from 15 to 1800 seconds. The
performance of the FST4-120 is about the same as for
WSPR. For longer transmission periods transmitter
frequency stability requirement is higher as the used
bandwidth goes down. See user guide 17.2.10. Summary. Of
course the (un)stability of the propagation path on 160m
band may prevent usage of the slowest modes.

73, Reino OH3mA


-Original Message-
From: Glenn Williams via wsjt-devel [mailto:wsjt-
de...@lists.sourceforge.net]
Sent: Thursday, December 7, 2023 5:46 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Glenn Williams 
Subject: [wsjt-devel] 160m S/N needs advanced mode

Hello,

FT8 on 160m pales.

WSJT-X operators customarily running FT8 and FT4 on
80m through 10m HF bands are likely disappointed with
trials on 160m. As one of those operators I recently

ran

WSPR on 160m in comparison to working FT8 QSOs on
160m. In NA EST daytime operation at 2220Z WSPR
faultlessly listed a
-28 dBm decode.

Here I suggest we need an improved decode sensitivity
for 160m QSOs, likely needing to be done with a new
mode. Granted, the TX and RX times would have to be
increased (Shannon-Hartley Theorem). That would
require additional operator patience and associated
protocols for the extended timing.

--73, Glenn, AF8C

--
This email has been checked for viruses by Avast
antivirus software.
www.avast.com


___
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] 160m S/N needs advanced mode

[Joe Taylor via wsjt-devel]

Hi Glenn,

FT4 and FT8 are a tiny fraction of what's available in WSJT-X.  Modes 
that meet the needs you describe are already available in the program.


Spend some time reading the WSJT-X User Guide.  Pay particular attention 
to Section 17.2.  Its Table 7 summarizes the threshold sensitivities of 
many of the available modes and submodes.  For weak signal work on 160m 
you might want to look at the FST4-xxx submodes.  These submodes offer 
sensitivities from 3 dB to 22 dB better than FT8 on an AWGN channel, and 
comparable improvements on most channel conditions likely to be found on 
our MF bands, including 160m.


-- 73, Joe, K1JT

On 12/7/2023 10:46 AM, Glenn Williams via wsjt-devel wrote:

Hello,

FT8 on 160m pales.

WSJT-X operators customarily running FT8 and FT4 on 80m through 10m HF 
bands are likely disappointed with trials on 160m. As one of those 
operators I recently ran WSPR on 160m in comparison to working FT8 QSOs 
on 160m. In NA EST daytime operation at 2220Z WSPR faultlessly listed a 
-28 dBm decode.


Here I suggest we need an improved decode sensitivity for 160m QSOs, 
likely needing to be done with a new mode. Granted, the TX and RX times 
would have to be increased (Shannon-Hartley Theorem). That would require 
additional operator patience and associated protocols for the extended 
timing.


--73, Glenn, AF8C




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

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

[Joe Taylor via wsjt-devel]

Geoff --

I was not trying to justify our code that posts only the first decode of 
duplicates in the same Rx sequence, just to tell you what the code does.


I'm sure you can find many places where we have done something simple 
and straightforward, "just to get it going," even when something 
arguably "better" can be imagined.  The "something better" might be done 
at some later time.


If you would like to submit a patch, please do so.

-- 73, Joe, K1JT

On 12/1/2023 3:53 AM, Geoff Van der Wagen VK2WA via wsjt-devel wrote:

Puzzled by your response.  I agree with not uploading dupes, but I can't 
fathom why you wouldn't compare dupes and pick the strongest one.  In a 
situation like this, clearly the strongest signal is representative of 
the real conditions. I can't think of a use for uploading any other 
decode, besides as punishment for any stations that dare to have their 
spurs strong enough to be heard (ironically the worse their transmitter 
is, the less they get punished).


Anyway, it sounds like a conscious choice, so good luck with it.

Regards,

Geoff VK2WA



On 1/12/23 13:14, Joe Taylor via wsjt-devel wrote:

Hi Geoff,

On 11/30/2023 9:03 PM, Geoff Van der Wagen VK2WA via wsjt-devel wrote:
I just had a funny one with a close station, S9+10dB, the 
transmission was +32 SNR but WSJT-X uploaded only the first decode at 
-19dB:


Queried for all spots me + target, unique NOT ticked:

Would have been better to upload the 32dB spot!


Perhaps that would be your choice.  It was not ours.

We don't post duplicate decodes.  Any decode of a message identical to 
one already staged for posting in the same Rx sequence is considered a 
dupe and discarded.


-- Joe


___
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] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

[Joe Taylor via wsjt-devel]

Hi Geoff,

On 11/30/2023 9:03 PM, Geoff Van der Wagen VK2WA via wsjt-devel wrote:
I just had a funny one with a close station, S9+10dB, the transmission 
was +32 SNR but WSJT-X uploaded only the first decode at -19dB:


Queried for all spots me + target, unique NOT ticked:

Would have been better to upload the 32dB spot!


Perhaps that would be your choice.  It was not ours.

We don't post duplicate decodes.  Any decode of a message identical to 
one already staged for posting in the same Rx sequence is considered a 
dupe and discarded.


-- Joe


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

Re: [wsjt-devel] FST4 Doppler Spread Overshoot Calculation

[Joe Taylor via wsjt-devel]

Hi Ryan,

Many thanks for pointing out the error in calculating the value of 
Doppler Spread for FST4 decodes!  You are (almost) 100% correct, and the 
bug will be fixed in the next release of WSJT-X.  In Fortran subroutine 
lib/fst4_decode.f90 the line


  xi1=i - 1 + (sum2-0.25*sum1)/(sum2-sum2z)

will be replaced by

  xi1=i - 1 + (0.25*sum1-sum2)/(sum2-sum2z)

I say 'almost' only because there was a stray right-parenthesis after 
'sum1' in your rendering of the corrected line of code.


Thanks again for catching this error!

-- 73, Joe, K1JT

On 11/21/2023 12:53 PM, Tolboom, Ryan via wsjt-devel wrote:

Good Evening,

I'm looking at lib/fst4_decode.f90, specifically the code where it 
calculates the frequency in the channel gain function, /g/, at which it 
reaches a certain percentage of the signal power. This can be found on 
line 999 of lib/fst4_decode.f90 
.


To prevent zero Doppler Spreads it uses a linear interpolation to get a 
floating point "index" between bins of the FFT. It does this by setting 
xi1 (and xi2, xi3 in a similar fashion) to the current index minus one 
plus the difference between the current power (sum2) and the power we're 
looking for (sum2 * 0.25, for xi1) divided by the difference between the 
current power (sum2) and the previous power (sum2z):


xi1=i-1+(sum2-0.25*sum1)/(sum2-sum2z)

If I'm interpreting this correctly this will not yield a correct result.

Let me give you an example:

For simplicity, assume we have four bins with powers 1, 2, 9, 2, and 1 
respectively. Assume the bins are enumerated from zero.


image.png

The total power would be 15 and 25% of that would be 3.75. As we look 
for that 25% mark, we'd find it in the do loop when i hits 2, sum2 is 
12, and sum2z is 3. xi1 would then be set to:


xi1 = 2 - 1 + (12 - 3.75)/(12 - 3) = 1 + 8.25/9 = 1.92

In other words, 92% of the way to bin 1 from bin 2. Shouldn't this be 
the other way around? Shouldn't it be 92% of the way working backwards 
from bin 2 to bin 1 or 8% of the way from bin 1 to bin 2? It seems like 
3.25 is only slightly larger than 3 and significantly less than 12.


i believe the overshoot correction should be the difference between the 
power we're looking for and the previous power divided by the difference 
between the current power and the previous power:


xi1 =  i - 1 + (0.25 * sum1) - sum2z)/(sum2 - sum2z)

Which in this case would yield:

xi1 = 2 - 1 + (3.75 - 3)/(12 - 3) = 1 + 0.75/9 = 1.08

Please let me know if I'm missing something and thanks for your time,

-Ryan Tolboom N2BP


___
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] Fortran runtime error in MAP65 3.0.1

[Joe Taylor via wsjt-devel]

Hi Erik,

Can you reproduce this error?  If so, please send me your file map65.ini 
and a sequence of steps that will reproduce the crash.


-- Joe, K1JT

On 10/17/2023 7:17 AM, Erik Icket via wsjt-devel wrote:

Dear developers,

The following Fortran runtime error occurred a number of times in MAP65.exe
:

Running: C:\WSJT\wsjtx\bin\m65 -s
At line 13 of file C:\JTSDK64-Tools\WSJTX\BBdevelop\lib\pctile.f90
Fortran runtime error: Index '-240641' of dimension 1 of array 'tmp' below
lower bound of 1

Error termination. Backtrace:

Could not print backtrace: libbacktrace could not find executable to open
#0 0x
#1 0x
#2 0x
#3 0x
#4 0x
#5 0x
#6 0x
#7 0x
#8 0x
#9 0x
#10 0x
#11 0x
#12 0x
#13 0x
#14 0x
#15 0x
#16 0x


I have the impression this error occurs more frequently in the presence of
strong interference signals in the passband of MAP65.
Also, MAP65 runs with selected mode Q65A and JT65B.

For information, MAP65 (and QMAP) received its baseband feed from the new
MAP65/QMAP interface built into SDRConsole 3.3

73's Erik
ON4PB




___
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.7.0-rc2 Switching caller in TX1 message

[Joe Taylor via wsjt-devel]

On 10/10/2023 8:25 PM, Clay Couger N5YJZ via wsjt-devel wrote:

There is another bug in both 2.6.1 and 2.7.0 RC2 where the first call is 
always picked to respond to even if max dist is slected.


This behavior is not a bug.  "CQ Max Dist" is effective only when the 
Active Stations window is displayed, which apparently you have not done.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] [wsjtgroup] Solar Eclipse participation #general

[Joe Taylor via wsjt-devel]

Does not matter.  You don't even need to run PSKReporter.  Just activate 
reporting to PSKReporter in WSJT-X.


-- Joe, K1JT

On 9/17/2023 8:50 AM, Glenn Williams via wsjt-devel wrote:

PSKReporter should be running in the same computer as WSJT-X? !!

--73, Glenn, AF8C

On 9/15/2023 1:04 PM, Mike Black W9MDB via groups.io wrote:
If you have a recent version of WSJTX (like RC2) we would appreciate 
you turning on PSKReporter to support the upcoming solar eclipse Oct 
14th. If you can turn on PSKReporter now and keep it on until at least 
Oct 16th it would be appreciated.


We implemented special PSKReporter ability in WSJT-X during solar 
eclipses.  All spots will go through where normally duplicates are 
ignored.  Phillip Gladstone at PSKReporter has implemented special 
collection recording to support this.


This is  to support the HamSCI community solar eclipse analysis.

Mike W9MDB

_._,_._,_

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#1104)  
| Reply To Group 
 | Reply To Sender  | Mute This Topic  | New Topic 

Mute #general 
Your Subscription  | 
Contact Group Owner  | Unsubscribe 
 
[a...@alumni.caltech.edu]


_._,_._,_





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

Re: [wsjt-devel] #Echo Echo shifts TX frequency when clicking "Set RX & TX offset" - should be disabled

[Joe Taylor via wsjt-devel]

Hi Andreas,

We would not have imagined anyone would try to use Echo mode without 
already having checked "Enable VHF and submode features".  Obviously 
that has been your problem, from the beginning.


-- 73, Joe, K1JT

On 8/4/2023 5:31 PM, Andreas Junge via wsjt-devel wrote:
Thank you Charlie DL3WDG, Bob KA1GT  and Mike W9MDB for looking into the 
code and putting your finger on it!


I can confirm that all 3 radios IC-705, IC-910H and the Flex6700 behave 
the same now depending on the "VHF and sub mode features” setting.


   VHF on = correct (fixed 1500 HZ)

   VHF off = tone shift based on previous mode setting or wide graph click

And yes, the IC-705 profile was the only one that had it unchecked.

Great find! Mystery solved.

73, Andreas, N6NU


On Aug 4, 2023, at 2:24 AM, Reino Talarmo via wsjt-devel 
 wrote:


Hi Andreas,
It would be nice for you, if the echo mode had a ‘fail safe’ setting 
that forces the transmission to 1500 Hz. The source code is available 
and you may add that into the program. Otherwise the instructions are 
clear how to use the echo mode.

73, Reino OH3mA
*From:*Andreas Junge via wsjt-devel 
[mailto:wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net>]

*Sent:*torstai 3. elokuuta 2023 22.16
*To:*WSJT software development <mailto:wsjt-devel@lists.sourceforge.net>>

*Cc:*Andreas Junge mailto:andr...@n6nu.org>>
*Subject:*Re: [wsjt-devel] #Echo Echo shifts TX frequency when 
clicking "Set RX & TX offset" - should be disabled

Joe,
Yes, I have read it. I also read Bob's (KA1GT) article. Please have a 
look at this short recorded screen session:

https://icecreamapps.com/v/fkkg3dt <https://icecreamapps.com/v/fkkg3dt>
Either right-clicking into the wide graph and setting the offset - 
which should not work since it should be fixed to 1500- or by 
previously being in Q65 with an offset will cause this.
It follows the pattern of @0-500 offset will subtract 1500Hz, 
@501-1000 will subtract 1000Hz, @1001-1500 will subtract 500Hz and so 
on until +1500Hz
I think this feature is used to keep the tones in the middle of the TX 
passband, but it also requires a frequency shift of the generated tone 
which does not happen because it's set to a fixed 1500Hz.
In short, yes, there should not be a frequency shift on TX in the 
first place and that is a bug IMHO.
I enabled logging for the rig transactions and the radio is indeed 
commanded to go to the wrong offset on VFO B it should be 144065000.
          rig_set_split_freq called vfo=VFOB, curr_vfo=VFOA, 
tx_freq=144064000
It works fine when I right click on 1500Hz in the wide graphs or when 
1500 was selected in the previous mode.

 73, Andreas, N6NU
On Thu, Aug 3, 2023 at 11:45 AM Joe Taylor via wsjt-devel 
<mailto:wsjt-devel@lists.sourceforge.net>> wrote:

Hi Andreas,

Have you read the full-length paper about Echo mode in WSJT-X 2.6.0 and
later? See item #34 in the list of WSJT-related references here:
https://wsjt.sourceforge.io/refs.html 
<https://wsjt.sourceforge.io/refs.html>.


As described there, in Echo mode the transmitted audio-frequency tone
should always be 1500 Hz.

        -- 73, Joe, K1JT

On 8/2/2023 10:47 AM, Andreas Junge via wsjt-devel wrote:
> I posted my initial question on thegroups.io 
<http://groups.io/>list as well, but Charlie, DL3WDG suggested to 
post it here as well.

>
> This is reproducible. In Echo Mode right click in the Wide Graph 
and select “Set RX & TX Offset” it seems to change the TX.

>
> Steps:
> - In the radio settings set "Split Mode" to Radio or Fake (No 
difference)

> - Select "Echo Mode"
> - Select 23 cm -> 1296.065 (Default)
> - Select Doppler Tracking mode to "Own Echo"
> - Display shows 1296.065 +/- My Doppler
> - Enable TX
> - The frequency will initially show 1296.06500 and the immediately 
change to 1296.064500

> - On RX the frequency goes back to the correct 1296.06500 +/- Doppler
> - The Echoes will be shown at the @1000 offset and not @1500, which 
is expected, but wrong.

>
> After a few tries I found that selecting “Set RX & TX Offset” in 
the Wide Graph

>
> If I click on @1000 I get 64.5000, @1500 65., @2000 65.5000
>
> The audio should be fixed at @1500 and the Set RX & TX feature 
should be ignored.

>
> I think this if half of the feature that keeps the audio in the 
sweet spot of the bandpass? However, it does not do the necessary 2nd 
step of shifting the audio to adjust for it.

>
> 73, Andreas, N6NU
>
> ___
> wsjt-devel mailing list
>wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net>
>https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>

Re: [wsjt-devel] #Echo Echo shifts TX frequency when clicking "Set RX & TX offset" - should be disabled

[Joe Taylor via wsjt-devel]

Hi Andreas,

On 8/3/2023 3:16 PM, Andreas Junge N6NU via wsjt-devel wrote:

It works fine when I right click on 1500Hz in the wide graphs or when 
1500 was selected in the previous mode.


Yes.  That's exactly what it's supposed to do.

We could, of course, force the TxFreq setting to 1500 Hz when you select 
Echo mode.  We chose not to do this because because it could lead to 
unexpected side effects when you switch back from Echo mode to (say) 
Q65-60C mode.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] #Echo Echo shifts TX frequency when clicking "Set RX & TX offset" - should be disabled

[Joe Taylor via wsjt-devel]

Hi Andreas,

Have you read the full-length paper about Echo mode in WSJT-X 2.6.0 and 
later? See item #34 in the list of WSJT-related references here: 
https://wsjt.sourceforge.io/refs.html .


As described there, in Echo mode the transmitted audio-frequency tone 
should always be 1500 Hz.


-- 73, Joe, K1JT

On 8/2/2023 10:47 AM, Andreas Junge via wsjt-devel wrote:

I posted my initial question on the groups.io list as well, but Charlie, DL3WDG 
suggested to post it here as well.

This is reproducible. In Echo Mode right click in the Wide Graph and select “Set RX 
& TX Offset” it seems to change the TX.

Steps:
- In the radio settings set "Split Mode" to Radio or Fake (No difference)
- Select "Echo Mode"
- Select 23 cm -> 1296.065 (Default)
- Select Doppler Tracking mode to "Own Echo"
- Display shows 1296.065 +/- My Doppler
- Enable TX
- The frequency will initially show 1296.06500 and the immediately change to 
1296.064500
- On RX the frequency goes back to the correct 1296.06500 +/- Doppler
- The Echoes will be shown at the @1000 offset and not @1500, which is 
expected, but wrong.

After a few tries I found that selecting “Set RX & TX Offset” in the Wide Graph

If I click on @1000 I get 64.5000, @1500 65., @2000 65.5000

The audio should be fixed at @1500 and the Set RX & TX feature should be 
ignored.

I think this if half of the feature that keeps the audio in the sweet spot of 
the bandpass? However, it does not do the necessary 2nd step of shifting the 
audio to adjust for it.

73, Andreas, N6NU

___
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] Release Candidate WSJT-X 2.7.0-rc2

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc2 is 
ready for download by beta testers.


WSJT-X 2.7.0 Release Candidate 2 is mostly a bug-fix release.  A full 
list of enhancements can be found in the Release Notes:


https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc2.txt

Release Candidates are intended for eta testers.  If you download and 
use WSJT-X 2.7.0-rc2, please remember to provide feedback to us on the 
new features in version 2.7, and on anything that does not seem to work 
properly.


Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html 
Scroll down to the heading "Candidate release:  WSJT-X 2.7.0-rc2".


For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is also available on the "Git" tab here: 
https://sourceforge.net/projects/wsjt/

It may take a short time for the code to be updated on SourceForge.


WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Feedback should be sent to this email list or one of the of the others 
mentioned here in the User Guide:


https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc2.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc2, and that you will help us 
to create a GA release of this version very soon.


-- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

[wsjt-devel] Release Candidate WSJT-X 2.7.0-rc2

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc2 is 
ready for download by beta testers.


WSJT-X 2.7.0 Release Candidate 2 is mostly a bug-fix release.  A full 
list of enhancements can be found in the Release Notes:


https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc2.txt

Release Candidates are intended for eta testers.  If you download and 
use WSJT-X 2.7.0-rc2, please remember to provide feedback to us on the 
new features in version 2.7, and on anything that does not seem to work 
properly.


Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html 
Scroll down to the heading "Candidate release:  WSJT-X 2.7.0-rc2".


For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is also available on the "Git" tab here: 
https://sourceforge.net/projects/wsjt/

It may take a short time for the code to be updated on SourceForge.


WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Feedback should be sent to this email list or one of the of the others 
mentioned here in the User Guide:


https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc2.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc2, and that you will help us 
to create a GA release of this version very soon.


-- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG3YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] New subscriber :)

[Joe Taylor via wsjt-devel]

Hi Thomas,

Thanks for your message.  This list is indeed the best place for 
suggestions of the sort you have made.


Since the first days of WSJT-X we have had great difficulty getting any 
feedback about EU VHF Contest mode, or even reports of its widespread 
use.  Exchanging 6-character locators with 77-bit messages requires a 
number of compromised changes to the usual message sequences in QSOs 
using the FT4, FT8, MSK144, and Q65 modes.  If you have specific 
suggestions for code changes, and if you believe the usage of EU VHF 
Contest mode would be significant, we would be happy to listen.


-- 73, Joe, K1JT

On 6/14/2023 5:58 AM, Thomas Nilsson, SM0KBD via wsjt-devel wrote:

Hi,

my name is Thomas, SM0KBD. I am a sort of a SW interested ham.

I have no idea how you use this list, I mean if it is only for 
merge-proposals and bug reports and all other administrative task for 
WSJT-X or if it is also for discussing improvement proposals?


Yesterday I wrote about a proposal for changing the auto-sequencer state 
machine for FT4/FT8/... on the normal WSJT-X list. But then I realised 
that maybe this is the place / list for such a thing?


BTW: I am well aware of that if you propose something you are expected 
to do a bit of the work! :)


73 de

/Thomas, SM0KBD




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

Re: [wsjt-devel] PSE Fixed patch for CMakeFiles/qmap_impl.dir/q65c.f90.o

[Joe Taylor via wsjt-devel]

Marco,

As far as I'm aware your problem involves only an attempt to build 
program QMAP.  Almost certainly you have no current use for QMAP, and no 
real interest in building it for Linux.


I suggest the simple expedient of moving the statement "endif ()", line 
1435 of the top-level CMakeFiles.txt down by two lines so that it comes 
after the statement "add_subdirectory (qmap)".  Then you will not run 
into the fussy compiler warnings that are currently bothering you.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Memory leak in 2.7.0 rc1?

[Joe Taylor via wsjt-devel]

Hi Björn,

I have not been able to reproduce anything like the behavior you 
describe.  For one example, I started WSJT-X in FT8 mode, monitoring a 
fairly busy 15 m band.  Memory usage reported by Windows TaskManager 
over the first ~5 hours looks like this:


 UTC  Memory
--
1930  97.1 MB
1950  99.5
2140  96.0
0105  94.2

So far, I have seen no evidence of any memory leak.

-- 73, Joe, K1JT


On 5/25/2023 3:49 PM, Brian Moran via wsjt-devel wrote:

Greetings; can you describe what mode you are using? If you left it going for a 
few days without deciding any signals (e.g. with no antenna) same behavior? 
What radio and interface to the radio? Any other information you could share 
would be most appreciated.

Thanks!
-Brian N9ADG


Sent via iPhone


On May 25, 2023, at 12:11 PM, Björn Ekelund via wsjt-devel 
 wrote:


My RAM (8 Gbyte) fills up if I let rc1 run for a few days. It does not happen 
with 2.6.1.

Interestingly enough the task manager does not show WSJT-X to be the culprit 
but when
I stop it, up to 5Gbyte are freed up.

Also, sometimes rc1 allocates 630Mbyte of RAM when started. Other times 
90Mbyte. It seems random.

2.6.1 is always around 90Mbyte.

I am running Swedish Windows.

Does anyone else experience the same anomalies?

Björn SM7IUN

___
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] Candidate Release WSJT-X 2.7.0-rc1

[Joe Taylor via wsjt-devel]

Too many mistakes, this morning.

At the bottom of my email announcing availability of Candidate Release 
WSJT-X 2.7.0-rc1, I listed my colleague Uwe Risse's callsign as DG3YCB. 
 As most of you know, and as I know perfectly well, his callsign is 
DG2YCB.  Moreover, Uwe had already drawn my attention to this typo in a 
previous announcement.  Forgetting about that, I simply copied the typo 
from the previous message.


Mea culpa, mea maxima culpa, Uwe.  Let's hope the software performs 
better than one of its authors has done.


Maybe I can blame it on my health.  I came down with COVID yesterday, 
and am feeling very poorly.


-- 73, Joe, K1JT


On 5/12/2023 11:52 AM, Joe Taylor wrote:

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc1 is 
ready for download by beta testers.


WSJT-X 2.7.0 Release Candidate 1 introduces a new program called "QMAP",
a new Special Operating Activity known as "Q65 Pileup", and a number of
other program enhancements and bug fixes.  A full list of enhancements 
can be found in the Release Notes:


https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc1.txt

Release Candidates are intended for Beta testers.  If you download and 
use WSJT-X 2.7.0-rc1, please remember to provide feedback to us on its 
new features -- and on anything that does not seem to work properly.


Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html

Scroll down to the heading "Candidate release:  WSJT-X 2.7.0-rc1".

For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is also available on the "Git" tab here:
https://sourceforge.net/projects/wsjt/  It may take a short time for the 
code to be updated on SourceForge.



WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Feedback should be sent to this email list or one of the of the others 
mentioned here in the User Guide:


https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc1.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc1, and that you help us to 
create a GA release of this version very soon.


    -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG3YCB;
     Brian, N9ADG; and John, G4KLA



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

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc1

[Joe Taylor via wsjt-devel]

Sorry, all -- I hit "send" by mistake.  A complete email on this topic 
should appear in less than an hour.


-- 73, Joe, K1JT

On 5/12/2023 11:20 AM, Joe Taylor via wsjt-devel wrote:

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc1 is
ready for download by beta testers.



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

[wsjt-devel] Candidate Release WSJT-X 2.7.0-rc1

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc1 is 
ready for download by beta testers.


WSJT-X 2.7.0 Release Candidate 1 introduces a new program called "QMAP",
a new Special Operating Activity known as "Q65 Pileup", and a number of
other program enhancements and bug fixes.  A full list of enhancements 
can be found in the Release Notes:


https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc1.txt

Release Candidates are intended for Beta testers.  If you download and 
use WSJT-X 2.7.0-rc1, please remember to provide feedback to us on its 
new features -- and on anything that does not seem to work properly.


Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html

Scroll down to the heading "Candidate release:  WSJT-X 2.7.0-rc1".

For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is also available on the "Git" tab here:
https://sourceforge.net/projects/wsjt/  It may take a short time for the 
code to be updated on SourceForge.



WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Feedback should be sent to this email list or one of the of the others 
mentioned here in the User Guide:


https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc1.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc1, and that you help us to 
create a GA release of this version very soon.


   -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG3YCB;
Brian, N9ADG; and John, G4KLA


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

[wsjt-devel] Release Candidate WSJT-X 2.7.0-rc1

[Joe Taylor via wsjt-devel]

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc1 is
ready for download by beta testers.




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

Re: [wsjt-devel] Enough

[Joe Taylor via wsjt-devel]

OK folks, Emergency Moderation has been turned on.  Please think long 
and hard before hitting "Send" on your email client.


-- Joe, K1JT


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

[wsjt-devel] Enough

[Joe Taylor via wsjt-devel]

Please, folks, no more email about "Split".

Multiple messages on the same topic by the same few individuals are 
seldom helpful -- and in my view most certainly have not been, in this 
instance.


Regarding terminology used in the WSJT-X user interface: English and 
most other modern languages often use the same work to mean somewhat 
different things in different contexts.  In the present case, "Split 
Operation" is clearly defined when first used in the WSJT-X User Guide. 
Here's the full entry, quoted from near the end of Section 4.2:


"Split Operation: Significant advantages result from using Split mode 
(separate VFOs for Rx and Tx) if your radio supports it. If it does not, 
WSJT-X can emulate such behavior. Either method will result in a cleaner 
transmitted signal, by keeping the Tx audio always in the range 1500 to 
2000 Hz so that audio harmonics cannot pass through the Tx sideband 
filter. Select Rig to use the radio’s Split mode, or Fake It to have 
WSJT-X adjust the VFO frequency as needed, when T/R switching occurs. 
Choose None if you do not wish to use split operation."


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Repeated crashes with large number of decodes

[Joe Taylor via wsjt-devel]

Hi Björn,

Thanks for your report.  Of course you are correct about the cause of 
this bug.  The issue was reported in January, and supposedly corrected 
in bug release 2.6.1.  Alas, it was corrected in only one of two 
necessary places.


It will be fixed in the next release.

-- 73, Joe, K1JT

On 5/2/2023 1:51 PM, Björn Ekelund via wsjt-devel wrote:
Decoding the DX0NE pile-up repeatedly crashes WSJT-X 2.6.1. There are a 
lot of decodes. From what it seems, over 100.


My guess is that the array mentioned in the crash report simply runs out 
because nobody thought there

would ever be more than 100 decodes in a cycle.

Has anyone else experienced this?

Björn SM7IUN

Subprocess Error
Subprocess failed with exit code 2

Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin 
-a C:\Users\SM7IUN\AppData\Local\WSJT-X -t 
C:\Users\SM7IUN\AppData\Local\Temp\WSJT-X

At line 222 of file C:\JTSDK64-Tools\WSJTX\BBdevelop\lib\ft8_decode.f90
Fortran runtime error: Index '101' of dimension 1 of array 'allsnrs' 
above upper bound of 100


Error termination. Backtrace:

Could not print backtrace: libbacktrace could not find executable to open
#0  0x
#1  0x
#2  0x
#3  0x
#4  0x
#5  0x
#6  0x
#7  0x
#8  0x
#9  0x
#10  0x
#11  0x
#12  0x





___
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] Repeated crashes with large number of decodes

[Joe Taylor via wsjt-devel]

Hi Björn,

Thanks for your report.  Of course you are correct about the cause of 
this bug.  The issue was reported in January, and supposedly corrected 
in bug release 2.6.1.  Alas, it was corrected in only one of two 
necessary places.


It will be fixed in the next release.

-- 73, Joe, K1JT

On 5/2/2023 1:51 PM, Björn Ekelund via wsjt-devel wrote:
Decoding the DX0NE pile-up repeatedly crashes WSJT-X 2.6.1. There are a 
lot of decodes. From what it seems, over 100.


My guess is that the array mentioned in the crash report simply runs out 
because nobody thought there

would ever be more than 100 decodes in a cycle.

Has anyone else experienced this?

Björn SM7IUN

Subprocess Error
Subprocess failed with exit code 2

Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin 
-a C:\Users\SM7IUN\AppData\Local\WSJT-X -t 
C:\Users\SM7IUN\AppData\Local\Temp\WSJT-X

At line 222 of file C:\JTSDK64-Tools\WSJTX\BBdevelop\lib\ft8_decode.f90
Fortran runtime error: Index '101' of dimension 1 of array 'allsnrs' 
above upper bound of 100


Error termination. Backtrace:

Could not print backtrace: libbacktrace could not find executable to open
#0  0x
#1  0x
#2  0x
#3  0x
#4  0x
#5  0x
#6  0x
#7  0x
#8  0x
#9  0x
#10  0x
#11  0x
#12  0x





___
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] Q65 false decode

[Joe Taylor via wsjt-devel]

Hi Gary,

On 4/26/2023 7:59 AM, K9RX wrote:
I had sent this on the 16^th of April but did not get a response… I 
believe these are germane questions – and as far as I’ve been able to 
tell they are not addressed in the manual. These pertain to the use of 
“average” when running Q65. I’ve asked these questions in the EME group 
– no one knew the answers but were also interested.


 1. /Does average apply to each of multiple signals in the window?/

Yes


 2. /Is there a separate average queue for 1^st and 2^nd sequence?
(would be great if RXing both looking for stns)/

Yes


 3. /IF each signal has its own average: and if Auto Clear is on does it
only clear the averages for those that have now decoded or /
 4. /if only one station decodes and there are say 3 stations there (in
the averages) do all the averages now get cleared out?/


"Auto Clear Avg after decode" clears the averaging accumulator for the 
relevant Odd or Even sequence when decoding at the selected offset 
frequency is successful.  The accumulator for the other sequence remains 
intact.


The small window near center of the status bar (see attached screen 
shot) shows the number of Rx intervals available in the accumulator for 
each sequence.


I assumed 4. Which is why I turned off auto clear since if it is 4 above 
it would never do an average if Lance, in the even cycle, always 
decoded.  And as mentioned I went from 0 averages in the AVG DEC window 
with it on to several ongoing with it off.


-- 73, Joe, K1JT___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Q65 false decode

[Joe Taylor via wsjt-devel]

Hi Gary and Don:

Those are not false decodes.  They are not spurious decodes.  Evidently 
you have "Enable averaging" turned on, but not "Auto Clear Avg after 
decode".  And you did not do a "Clear Avg" manually.  Not a good plan, 
generally, for the type of operating you are doing.  You must learn to 
use these tools -- it's not all automated, nor could it be.  The 
operator is important, and must make informed choices.


Like all other settings, the "Save all" setting is specific to each 
Configuration you have defined.


-- 73, Joe, K1JT

On 4/16/2023 9:55 AM, Don Hawbaker via wsjt-devel wrote:
I have noticed a similar problem.  Spurious decode.  Sometimes the old 
decode can even be from a previous contact.  Very strange.  Never did 
this before.  v2.6


Sent from my iPad

On Apr 16, 2023, at 9:30 AM, K9RX via wsjt-devel 
 wrote:




Hello all.

I was running Q65-60A on 6M EME this morning. I am using version 2.6.0 
b15b7. I have DEEP and ENA AVG turned on. I decoded the station I was 
calling every sequence. However twice WSJT decoded the “proper” signal 
(right doppler and seq) but then decoded, in the AVG window, a 2^nd 
that was one sequence previously. Unfortunately I didn’t see that my 
TX then reverted back to the original and was not the follow on 
(proper one).


This happened again the next sequence but I caught it that time. 
Unfortunately I do not normally have SAVE turned on so I don’t have 
the data file.


I mentioned this as an FYI re false decodes. I don’t remember ever 
getting this before (this version).


But I have a question: I have Q65-60A as a configuration and switch to 
it when doing EME. Can I set the SAVE as on for this config and will 
it then be off for the other configs I have built?


Gary

K9RX

You can see below at 1303 I got, at -24, his RX3. WSJT started to send 
TX4 at 1304. Then it (almost) immediately decoded his TX1 and WSJT 
switched back to TX2. I did not catch this. The next sequence you can 
see this repeated at 1307. I have since turned on SAVE DECODED and 
finally you can see false (AVG) decodes at 1309 – 1317. He was not 
transmitting during these sequences. I can send tis file if that would 
help.


*1302 Tx 1500 : W5WP K9RX -26*

*1303 -24 2.8 1442 : K9RX W5WP R-32  q3*

*1304 Tx 1500 : W5WP K9RX RRR*

*1303 -24 2.8 1447 : K9RX W5WP EM00  q35*

*1304 Tx 1500 : W5WP K9RX -24*

*1305 -19 2.8 1439 : K9RX W5WP R-32  q3*

*1306 Tx 1500 : W5WP K9RX RRR*

*1307 -24 2.8 1439 : K9RX W5WP RRR  q3*

*1308 Tx 1500 : W5WP K9RX 73*

*1307 -23 2.8 1441 : K9RX W5WP R-32  q37*

*1308 Tx 1500 : W5WP K9RX 73*

*1309 -24 2.8 1441 : K9RX W5WP R-32  q38*

*1311 -26 2.8 1441 : K9RX W5WP R-32  q39*

*1313 -28 2.8 1441 : K9RX W5WP R-32  q3**

*1315 -29 2.8 1441 : K9RX W5WP R-32  q3**

*1317 -31 2.8 1441 : K9RX W5WP R-32  q3**

*1319 -32 2.8 1441 : K9RX W5WP R-32  q3**

Sent from Mail  for 
Windows


___
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] Sourceforge download

[Joe Taylor via wsjt-devel]

On 4/8/2023 9:22 AM, Gary Rogers via wsjt-devel wrote:

Seeing multiple reports that WSJT-X cannot be downloaded from the Source forge 
website. I’ve tried both the WSJTX site and Source forge sites and have not 
been able to download WSJTX.


Something is wrong at SourceForge.  I suggest going to
https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.1/
and selecting the file you need.

-- Joe, K1JT


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

Re: [wsjt-devel] Feature or Flaw

[Joe Taylor via wsjt-devel]

Hi John,

As has been stated many times, both here and elsewhere:

When exchange of standard QSO messages does not go as expected, it's up 
to you to take any explicit action required.


Auto-sequencing is an operator convenience, not an operator replacement.

-- 73, Joe, K1JT

On 4/4/2023 6:20 PM, John McKee via wsjt-devel wrote:
I tried sending this from my gmail account, and it was held for review, 
presumably because I am not registered with WSJTX under that account.
So, I am sending it again under my att.net  account for 
your review:


*


I was today attempting a QSO with ZD7CTO, and after a long series of 
calls to him, I finally received a response at 213015 to which I replied 
at 213030.  No response from ZD7CTO, so I sent two more responses at 
213100 and 213130.  Then, the WSJT-X changed me from Tx 3 to Tx 1, and 
began the QSO process again as seen at 213200… this happened several 
times more, necessitating my repeatedly changing to Tx 3 to complete the 
QSO finally at 213930……
My question: is this a feature (being changed back to Tx 1 after a QSO 
is answered by the DX station), OR is it a flaw in the program??

John, NT5EE
452EA862503543238BA3234D848ABD1F.png



1F58A8AEC7204CED928B6084F5ABF298.png


___
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] Future of Hamlib #hamlib

[Joe Taylor via wsjt-devel]

Hi Mike,

Just a note to say I'm very sorry to learn of your health issues.  I 
hope they can be addressed in the best possible way, for you.


-- Joe


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

Re: [wsjt-devel] Q65 Doppler Mode / Flex Radio 6400 (with 2 Slices only)

[Joe Taylor via wsjt-devel]

Hi Dwayne,

On 2/27/2023 3:52 PM, Dwayne Sinclair AB6A via wsjt-devel wrote:

There is a nasty bug which destroyed two EME sessions for me. Not sure where 
the problem lies (WSJT-X/Hamlib/Flex etc) …

If SmartSDR 3.4 has two Slices active when starting WSJT-X, enabling Q65 
Doppler Tracking will cause CAT to fail. CAT turns from Green to Orange and 
stops responding to WSJT-X CAT commands.

After experimentation, the bypass is to ensure only one Slice is active with 
starting WSJT-X. In Radio settings, Split operations is set to Rig Control.

73 Dwayne AB6A


So, what (if anything) are you suggesting should be done?  Have you 
already solved your problem satisfactorily?  What, exactly, is the nasty 
bug to which you refer?


As a general matter, WSJT-X controls just one "rig".  In your case I 
suppose this means one slice.


-- Joe, K1JT


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

Re: [wsjt-devel] Possible issue with ECHO mode - 2.6.0

[Joe Taylor via wsjt-devel]

Gary --

I'll repeat what I said before.  I believe if you configure WSJT-X as 
described in the User Guide and the referenced paper, its behavior will 
be as it should be.


You have not said if you are using CAT control.  If YES, and you choose 
"Own Echo", you'll see your dial frequency change from Rx to Tx.  On 6m, 
Doppler shifts are small enough that you don't need to use CAT control. 
In that case WSJT-X will do Echo-mode Doppler control in software, at 
audio frequencies.


In either case, the echo peak in the Echo graph should be centered at 0. 
SNR measurements are made only for a peak centered at 0.  The "-99 dB" 
you are seeing means that there is no peak centered at 0, and this means 
something is not being done correctly.


-- Joe, K1JT

On 2/22/2023 12:05 PM, K9RX via wsjt-devel wrote:
Lance, Thanks – but the issue is that the operation and displayed 
results – changed! It first was showing, on the Echo graph centered (0). 
And at the same time it showed on the wide graph as the echo was where 
it should be – i.e. 1596Hz for a 96Hz echo doppler shift. And it decoded 
a signal with a level provided (-14.6, twice, w/ a Q of 10!).


But then later – w/o changing anything other than time (i.e. later)… the 
echo showed on the Echo graph at -93 Hz (now the expected echo was 93 
Hz)… the wide graph showed it just above 1500Hz and although there was 
clearly an echo – the tabulated results remained at a level of -99.9!


This is all clear in the screen shot if anyone wants to see it.

After reading the doc I did see that it was set to “on own echo”. I 
changed that to “none” and now it seems to work as expected – the echo 
is now at 1576Hz on the wide graph and is at +76Hz on the Echo graph – 
and it gave a proper numeric value (this time -20.3).


So again – its that it changed and when it changed it was no longer 
functional as, even though the echo was clearly there, the value for SNR 
was ‘stuck’ at -99.9.


Gary

Sent from Mail  for Windows

*From: *Lance Collister, W7GJ via wsjt-devel 


*Sent: *Wednesday, February 22, 2023 11:57 AM
*To: *K9RX via wsjt-devel 
*Cc: *Lance Collister, W7GJ 
*Subject: *Re: [wsjt-devel] Possible issue with ECHO mode - 2.6.0

Hi Gary,

I have not followed the ECHO mode documentation, but it may be that on 
the Wide


Graph, you see the trace coming back as doppler shifed, but (at least in 
previous


versions) the ECHO mode moves the frequency around, along with its 
receiver, and just


displays the sum total of the average echoes received. The program knows 
where it is


transmitting, so knows where to listen for the signal. I don't think you 
need to pay


any attention to what is shown on the Wide Graph...GL and VY 73, Lance

On 2/22/2023 16:13:35, K9RX via wsjt-devel wrote:

 >

 > Thank you – I’ll look this over to see if it addresses the echo 
appearing


 > differently in both the wide and echo graph.

 >

 > Gary

 >

 > Sent from Mail  for 
Windows


 >

 > *From: *Charles Suckling via wsjt-devel 



 > *Sent: *Wednesday, February 22, 2023 10:53 AM

 > *To: *WSJT software development 

 > *Cc: *Charles Suckling 

 > *Subject: *Re: [wsjt-devel] Possible issue with ECHO mode - 2.6.0

 >

 > Hi Gary

 >

 > Have a look at these, which will hopefully help.

 >

 > https://wsjt.sourceforge.io/Echo_Mode_in_WSJT-X_2.6.0.pdf

 >

 > http://www.bobatkins.com/radio/EME_WSJTX_echo_mode_basic_guide.html

 >

 > 73

 >

 > Charlie DL3WDG

 >

 > On Wed, 22 Feb 2023 at 16:37, K9RX via wsjt-devel

 >  wrote:

 >

 > I like to use ECHO to test the station on 6M EME.

 >

 > But the latest version has changed enough I was wondering if 
there was a short


 > help file for it?

 >

 > Also: The Echo graph will at times show the echo centered – and 
other times


 > show it offset. I have a jpg showing a recent echo run where the 
echo was very


 > strong – and it was showing it as the right numeric doppler 
shift, 96 Hz, but


 > it was showing it on the graph as -96Hz and there was no SNR 
value reported


 > (-99.0 shown). You can see the echo on the wide graph – you can 
see the echo on


 > the echo graph – but both have it lower than it should be…

 >

 > A few minutes earlier I had 2 echos at -14.6 and others in to the 
low 20’s –


 > these were all showing on the spreadsheet – and “properly” on 
both the wide and


 > echo graphs.

 >

 > Gary Myers

 >

 > K9RX

 >

 > Sent from Mail  
for Windows


 >

 > ___

 > wsjt-devel mailing list

 > wsjt-devel@lists.sourceforge.net

 > 

Re: [wsjt-devel] Possible issue with ECHO mode - 2.6.0

[Joe Taylor via wsjt-devel]

Hi Gary,

On 2/22/2023 10:28 AM, K9RX via wsjt-devel wrote:

I like to use ECHO to test the station on 6M EME.

But the latest version has changed enough I was wondering if there was a 
short help file for it?


Better than a short help file: there's a full paper about Echo mode. 
See item #34 here: https://wsjt.sourceforge.io/refs.html .


Also: The Echo graph will at times show the echo centered – and other 
times show it offset. I have a jpg showing a recent echo run where the 
echo was very strong – and it was showing it as the right numeric 
doppler shift, 96 Hz, but it was showing it on the graph as -96Hz and 
there was no SNR value reported (-99.0 shown). You can see the echo on 
the wide graph – you can see the echo on the echo graph – but both have 
it lower than it should be…


A few minutes earlier I had 2 echos at -14.6 and others in to the low 
20’s – these were all showing on the spreadsheet – and “properly” on 
both the wide and echo graphs.


Gary Myers
K9RX


Set up Echo mode as described in the paper referenced above.  Be sure to 
check Doppler tracking on the Astronomical Data window, and select "Own 
Echo" for Doppler Tracking mode.  Your echo should always be centered at 
frequency offset 0.  SNR values are accurate and reliable.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

[Joe Taylor via wsjt-devel]

Hi Barry,

There have been *many* announcements in a variety of places about our 
switch from the Princeton University site to SourceForge.  The tarfile 
you want is now linked at the bottom of this web page:


https://wsjt.sourceforge.io/wsjtx.html

The direct link to the tarfile is:

https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.1/wsjtx-2.6.1.tgz

-- Joe, K1JT

On 2/13/2023 5:35 PM, Barry Jackson via wsjt-devel wrote:

On 16/01/2023 14:22, Joe Taylor via wsjt-devel wrote:
The WSJT Development Team is pleased to announce that today the Solar 
Flux Index is 234 and Sunspot Number is 195.


Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now 
available for free download from SourceForge.




Hi Joe,

error: Could not download file 
https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-2.6.1.tgz


I maintain wsjtx for Mageia and we have always used the above URL path 
for downloading the official sources.


Has this changed permanently, or is this an oversight, or a server issue?

Barry



___
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] Q65 T/R Cycle Submode Tracking

[Joe Taylor via wsjt-devel]

Hi Dwayne,

On 2/6/2023 1:59 PM, Dwayne Sinclair AB6A via wsjt-devel wrote:

There are technical discussions and associated websites that describes the 
optimal submode for the various T/R Cycles -

T/R 15 Seconds Submode A
T/R 30 Seconds Submode B
T/R 60 Seconds Submode C
T/R 120 Seconds Submode D
T/R 300 Seconds Submode E

Would it be possible to add a switch to setting to track submode to T/R cycle 
since both settings have to be changed when we switch T/R cycles?

Regards Dwayne AB6A


Yes, it would be possible, but it would not be desirable.

As a general matter we shy away from having user-interface controls 
affect the status of other user-controllable options, where this might 
lead to unexpected behavior.


Even more important: If you're working 6m EME, you might think that the 
optimal Q65-60x sunmode is Q65-60A.  But 2m EME is done with Q65-60B, 
1296 MHz EME with Q65-60C, and 10 GHz EME with Q65-60D.  There are good 
reasons for all these choices, and many others -- and that's why so many 
submodes are offered.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X

[Joe Taylor via wsjt-devel]

Hi Gary,


On 2/5/2023 11:41 AM, Gary IoW G7RES via wsjt-devel wrote:

Hello devs,
great program, but may I suggest a small edit? Could you make it so that 
when the band is changed from the drop down in the program it will 
automatically switch to TX6?


As an older software developer myself (.NET, ASP, JSON, Java, C# VB etc) 
I know this wouldn't be a difficult fix.


Thanks and regards,
Gary, G7RES.


Thanks for your suggestion.

As a general policy, we are often skeptical about having seemingly 
unrelated items on the GUI affect one another in potentially unexpected 
ways.  You ask that what now requires two simple mouse actions (or one 
mouse action followed by hitting "F4" on the keyboard) might be reduced 
to the first action alone.  Doesn't sound like a big step forward, to 
me.  Moreover, there are many circumstances -- perhaps especially on VHF 
bands -- where one does not not wish to clear DxCall and DxGrid after a 
band change, and does not plan to call CQ right away.


One of the reasons the WSJT project has has an open source policy for 
most of its 22-year history is to that users with programming skills can 
modify it as they choose.  Of course, you are welcome to do so within 
the normal GPLv3 licensing rules.


-- 73, Joe, K1JT


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

[wsjt-devel] WSJT-X 2.6.1 GA Release

[Joe Taylor via wsjt-devel]

The WSJT Development Team is pleased to announce that today the Solar 
Flux Index is 234 and Sunspot Number is 195.


Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now 
available for free download from SourceForge.


Version 2.6.1 is a bug-fix release.  It corrects a flaw in Q65 mode that 
prevented display of the T/R period spinner, makes initialization of the 
decoded text font more robust, does more complete initialization when 
the program is started in FT8 Hound mode, and corrects a bug causing 
program crash with more than 100 decodes in a single FT8 sequence. 
Additional details can be found in the Release Notes:

https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.6.1.txt

The WSJT Home Page is now located here: https://wsjt.sourceforge.io/
Direct links to installation packages for Windows, Linux, and macOS can 
be found on the WSJT-X page https://wsjt.sourceforge.io/wsjtx.html


For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is available on the "Git" tab here:

https://sourceforge.net/projects/wsjt/

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Bugs should be reported by following instructions found here in the User 
Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.4.html#_bug_reports

We hope you will enjoy using WSJT-X 2.6.1.

   -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG3YCB;
Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] WSJT-X 2.6.0 Array Warnings

[Joe Taylor via wsjt-devel]

Jeff --

Program ft8sim is a stand-alone utility that is not part of WSJT-X.  It 
is never called recursively, or from multiple threads.


Have another cup of coffee and don't waste your time trying to resolve 
such a warning message.  Or, if you prefer, change the code to make such 
a useless message go away.


-- 73, Joe, K!JT

On 1/8/2023 12:20 PM, Jeff Stillinger via wsjt-devel wrote:

Greetings,

I have built WSJT-X 2.6.0 on LMDE 5 and have run across the array 
warnings in:


Building Fortran object CMakeFiles/ft8sim.dir/lib/ft8/ft8sim.f90.o

Warning: Array ‘cwave’ at (1) is larger than limit set by 
‘-fmax-stack-var-size=’, moved from stack to static storage. This makes 
the procedure unsafe when called recursively, or concurrently from 
multiple threads. Consider using ‘-frecursive’, or increase the 
‘-fmax-stack-var-size=’ limit, or change the code to use an ALLOCATABLE 
array. [-Wsurprising]


I will admit it's only my first cup of coffee this morning and I have 
not gotten too deeply into it.  Wondering if anyone has a optimal 
setting for the max-stack-var-size.  I would like to resolve the warning 
before I move it over to my Enterprise desktop.





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

Re: [wsjt-devel] Decodes

[Joe Taylor via wsjt-devel]

Bobby --

On 1/7/2023 5:01 PM, Bobby Chandler via wsjt-devel wrote:

Thanks much Joe,

Just didn't want to click on wrong time sequence. Thanks to the team for 
a super program and support.


You can click on a decode that appears after the next sequence starts. 
The program will know which sequence to transmit in.


-- Joe, K1JT


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

Re: [wsjt-devel] Decodes

[Joe Taylor via wsjt-devel]

Hi Bobby,

When in the NORMAL decode mode and band is busy (35 to 50+) the decode 
indicator flashes 3 times and the last is several seconds (up to 5) into 
next time slot. Does this affect the number of decodes in the Band 
Activity window?


The three flashes you mention occur at roughly these times into the FT8 
receive sequence:


11.8 s: Attempt to decode many of the stronger signals, even before
their transmissions are finished.

13.6 s: Main decoding pass. Subtract signals from all previous decodes 
from the received data stream.  Decode all possible remaining signals.


15.0 s: Subtract signals from all decodes in Pass 2.  Make a final 
decoding attempt on what's left, with particular attention to signals 
that might be another transmission from a station on that frequency two 
sequences ago.


In all passes, attention is focused first on your selected Rx audio 
frequency, then on all other frequencies displayed in the waterfall, 
from bottom up.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

[Joe Taylor via wsjt-devel]

Sorry, Marco, I misunderstood your question.  We are not yet up-to-date 
with incorporating UI translations for the new release.  We will do so 
as time allows.


-- Joe, K1JT

On 1/6/2023 11:01 PM, Marco Calistri wrote:

Il 06/01/23 19:58, Joe Taylor ha scritto:

On 1/6/2023 5:14 PM, Marco Calistri PY1ZRJ via wsjt-devel wrote:

I1ve successfully compiled and started WSJT-X 2.6.0, but I notice now 
that the updated Italian translations have not been included into the 
current release!


It should be obvious that updated translations cannot be posted until 
translators have sufficient time after receiving the new English 
version.  The new English User Guide was posted today. Further updates 
are possible.


Translations for the WSJT-X 2.6.0 User Guuide will be posted when they 
become available.


-- Joe, K1JT


Dear and respectable Joe,

I mean the translations of the program UI itself, that once time ago 
were managed by the good Bill Somerville, G4WJS.


I was contributing to the Italian translations for Linux, it was coming 
as a Qt Linguist *.TS file.


The last file I've translated has been for the WSJT-X 2.6.0-RC2 release.

The button on Main Window to select CQ None, CQ First, CQ Max Dist, has 
not been translated in current 2.6.0 GA release, but I did sent the TS 
file containing the corresponding translation for the Italian.



Apologies in case I'm doing confusion on this topic.


Regards,
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**



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

Re: [wsjt-devel] Impact of multi stream on SNR

[Joe Taylor via wsjt-devel]

On 1/7/2023 9:28 AM, José Nunes CT1BOH via wsjt-devel wrote:

I wonder if anyone can confirm this?!

In FT8 if I copy a DX station TX, with only one stream, at -10dB:

  * If the station goes F/H with two streams, then the signal of each of
the two streams goes down to -13,01 dB because the energy of one
stream is split by half
  * If the station goes F/H with three streams, then the signal of each
of the three streams goes down to -14.77 dB because the energy of
one stream is split by three

Are the two sentences above correct?


No, this is not correct.  With two streams, each stream will be weaker 
than the one-stream case by 6 dB.  See "Important Note for Fox 
Operators" on page 9 of the "FT8 DXpedition Mode User Guide":

https://wsjt.sourceforge.io/FT8_DXpedition_Mode.pdf
https://wsjt.sourceforge.io/FT8_DXpedition_Mode_Portuguese.pdf

-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

[Joe Taylor via wsjt-devel]

On 1/6/2023 5:14 PM, Marco Calistri PY1ZRJ via wsjt-devel wrote:

I1ve successfully compiled and started WSJT-X 2.6.0, but I notice now 
that the updated Italian translations have not been included into the 
current release!


It should be obvious that updated translations cannot be posted until 
translators have sufficient time after receiving the new English 
version.  The new English User Guide was posted today.  Further updates 
are possible.


Translations for the WSJT-X 2.6.0 User Guuide will be posted when they 
become available.


-- Joe, K1JT


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

[wsjt-devel] WSJT-X 2.6.0 GA Release

[Joe Taylor via wsjt-devel]

The WSJT Development Team is pleased to announce the WSJT-X 2.6.0 
General Availability (GA) release.  Program changes from version 2.5.4, 
released one year ago, are described in the Release Notes:

https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.6.0.txt

Be sure to read the full Release Notes entry for today's date, January 6 
2023.  Program enhancements since program version 2.5.4 and extensive.


We call to your attention, once again, that the WSJT Home Page has moved 
to a new URL:

https://wsjt.sourceforge.io/

Direct links for downloading pre-built installation packages for 
Windows, Linux, and macOS, can be found on the WSJT-X page:

https://wsjt.sourceforge.io/wsjtx.html

For those who like to compile from source, a complete source-code 
tarball is available at the WSJT-X page. Public access to the git 
repository for the WSJT project is available on the "Git" tab here:

https://sourceforge.net/projects/wsjt/

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Bugs should be reported by following instructions found here in the User 
Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.4.html#_bug_reports

We hope you will enjoy using WSJT-X 2.6.0.

   -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG3YCB;
Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] Link to latest WSJT-X source .tgz for use on the command-line?

[Joe Taylor via wsjt-devel]

Hi Onno,

I'm not sure that I understand your exact problem.  Does this link not 
work for your purpose?


https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.0-rc5/wsjtx-2.6.0-rc5.tgz/download

-- 73, Joe, K1JT

On 12/30/2022 1:23 AM, Onno Benschop via wsjt-devel wrote:
Having spent several days attempting to find the answer in the 
documentation and the sourceforge HowTo information, I'm stuck.


Is there a static link to the latest version of the source .tgz file, so 
I can automate the compilation of the latest released version under Linux?



According to the sourceforge documentation the link to the latest 
version is:


  * https://sourceforge.net/projects/wsjt/files/latest


Unfortunately that link only ever returns a Windows .exe file when using 
wget. I've not been able to discover a way to provide either URL options 
or tweak the user-agent of my wget command, to actually ever get the 
.tgz file.



Although I can download a specific version using version numbers like 
this, this means that the URL is hard-coded and version dependent which 
defeats the purpose of what I'm working on:


  * 
https://downloads.sourceforge.net/project/wsjt/wsjtx-2.6.0-rc5/wsjtx-2.6.0-rc5.tgz 



I can clone it with git, which takes a long time, even at depth=1, but 
that requires another separate clone and build for hamlib. This works, 
mostly, but it means that I'm not actually testing the latest source 
code .tgz file:


  * git clone --progress --depth 1 https://git.code.sf.net/p/wsjt/wsjtx



Is there a symbolic link to the latest version, cunningly named 
something like "wsjtx-latest.tgz" which doesn't change between versions?




--
Onno Benschop

()/)/)()        ..ASCII for Onno..
|>>?            ..EBCDIC for Onno..
--- -. -. ---   ..Morse for Onno..

If you need to know: "What computer should I buy?" http://goo.gl/spsb66 



ITmaze   -   ABN: 56 178 057 063   -  ph: 04 1219    - 
o...@itmaze.com.au 



___
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] Link to latest WSJT-X source .tgz for use on the command-line?

[Joe Taylor via wsjt-devel]

Sorry Onno, I should have read more carefully to the end of your email. 
I really don't know how SourceForge's "latest" links are supposed to 
work.  I suppose we could consider something like your suggestion of a 
symbolic link like "wsjtx-latest.tgz".  In the meantime, you'll need to 
work around the need to use a specific version name.


-- Joe, K1JT

On 12/30/2022 1:23 AM, Onno Benschop via wsjt-devel wrote:
Having spent several days attempting to find the answer in the 
documentation and the sourceforge HowTo information, I'm stuck.


Is there a static link to the latest version of the source .tgz file, so 
I can automate the compilation of the latest released version under Linux?



According to the sourceforge documentation the link to the latest 
version is:


  * https://sourceforge.net/projects/wsjt/files/latest


Unfortunately that link only ever returns a Windows .exe file when using 
wget. I've not been able to discover a way to provide either URL options 
or tweak the user-agent of my wget command, to actually ever get the 
.tgz file.



Although I can download a specific version using version numbers like 
this, this means that the URL is hard-coded and version dependent which 
defeats the purpose of what I'm working on:


  * 
https://downloads.sourceforge.net/project/wsjt/wsjtx-2.6.0-rc5/wsjtx-2.6.0-rc5.tgz 



I can clone it with git, which takes a long time, even at depth=1, but 
that requires another separate clone and build for hamlib. This works, 
mostly, but it means that I'm not actually testing the latest source 
code .tgz file:


  * git clone --progress --depth 1 https://git.code.sf.net/p/wsjt/wsjtx



Is there a symbolic link to the latest version, cunningly named 
something like "wsjtx-latest.tgz" which doesn't change between versions?




--
Onno Benschop

()/)/)()        ..ASCII for Onno..
|>>?            ..EBCDIC for Onno..
--- -. -. ---   ..Morse for Onno..

If you need to know: "What computer should I buy?" http://goo.gl/spsb66 



ITmaze   -   ABN: 56 178 057 063   -  ph: 04 1219    - 
o...@itmaze.com.au 



___
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] RC5 multiple decode

[Joe Taylor via wsjt-devel]

Don --

Charlie, DL3WDG, has already responded to your questions.  A few 
additional points:


1. If you saved a file with multiple signals that you think should have 
decoded, but did not, please send us that file and a copy of your file 
WSJT-X.ini.


2. Population of the table of frequencies is ultimately a user 
responsibility.  You can define an Echo-mode default frequency on 902 
MHz wherever you choose.  The program will remember it.


-- 73, Joe, K1JT

On 12/17/2022 5:35 PM, Don Hawbaker via wsjt-devel wrote:

I seem to have lost the ability to do multiple decodes.  The single decode is 
turned off.  No matter how many signals are on the waterfalls, I only get 
decode on the one where the cursor is sitting.  It used to do multiple decodes.

Second item.  In echo mode, the frequency 902 MHz is missing from the frequency 
list.  In RC4, it appeared.

73s





___
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] WSJT Home Page is temporarily unavailable

[Joe Taylor via wsjt-devel]

Hi all,

The WSJT Home Page is down because we are being transitioned to a new 
web server.  The downtime may be at least several days.  In the 
meantime, our files are available for downloading at SourceForge.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X v2.6.0-rc5

[Joe Taylor via wsjt-devel]

Hi Andy,

Thanks for reporting this unwanted behavior, and for your patience 
waiting for us to respond.  The bug has been fixed, and will be OK in 
the next release.


-- Joe, K1JT

On 12/11/2022 10:08 PM, Andrew Neumeier via wsjt-devel wrote:
I had reported this issue in rc4.  When moving from JT9-G Fast mode on 
10m (a few of us have been running some 10 meter meteor scatter) to Q65 
on 6 meters, the Q65 decoder does not start.  It is necessary to
move to another mode first, and then move on to Q65 to cause the decoder 
to activate.


Just letting the team know.

73 and thank you,
Andy, ka2uqw




___
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] V2.6.0-rc5

[Joe Taylor via wsjt-devel]

Hi Rex,

Thanks for calling our attention to this anomaly.  It has been corrected 
and will be OK in the next release -- thanks to Charlie, G3WDG, who sent 
us the corrected code.


-- Joe, K1JT

On 12/11/2022 5:28 PM, Rex Moncur via wsjt-devel wrote:

Hi Joe and the Development Group

We have been testing RC5 during our weekly weak signal terrestrial QSO 
party on 1296 MHz in Tasmania.  These tests have shown that the RC5 
version works similarly to earlier versions and works well.


I notice one small change to the way that the Linear Average "Yellow 
Graph" mouse indicator works.  It now shows a dB level rather than a 
frequency.  We use single tones to identify the presence of very weak 
stations and in the past have found it useful to use the mouse to 
confirm the calling station using the mouse frequency indicator.  While 
it is possible to read the frequency from the top of the waterfall the 
mouse indicator on the Yellow graph is more accurate.  I am not asking 
for a change but just pass on that I found the mouse frequency indicator 
useful.


73 Rex VK7MO



___
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] Release Candidate WSJT-X 2.6.0-rc5

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc5 is 
ready for download by beta testers.  The list of changes since Release 
Candidate 4 is extensive.  Be sure to read the Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links for downloading WSJT-X 2.6.0-rc5 can be found on the WSJT-X Home 
Page, https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to find "Candidate release:  WSJT-X 2.6.0-rc5".

Installation files for Raspberry Pi are not yet available, but will be 
posted as soon as possible.


We hope you will enjoy using this beta release of WSJT-X 2.6.0.  As a 
beta tester you should report on your experiences using one of the 
relevant WSJT forums.  Bugs should be reported by following instructions 
found here in the User Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc5.html#_bug_reports

WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU 
General Public License (GPLv3).  Development of this software is a 
cooperative project to which many amateur radio operators have 
contributed.  If you use our code, please have the courtesy to let us 
know about it.  If you find bugs or make improvements to the code, 
please report them to us in a timely fashion.  Additional licensing 
details can be found here:

https://physics.princeton.edu//pulsar/k1jt/devel.html

 73 from the WSJT Core Development Team
 Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] Program crash

[Joe Taylor via wsjt-devel]

Tony --

Yes, you were using the executable called jt9.exe.  That program 
provides the decoding for all slow modes in WSJT-X.


Rebooting is not necessary.  Simply use Windows Taskmaster to kill the 
still-executing jt9.exe.


A report of program failure is useful only if you can provide details of 
what may have caused the crash.  Obviously it doesn't happen most of the 
time, or we would not have released the beta-test version.  If possible, 
we need to know what was special about your usage that resulted in a crash.


-- 73, Joe, K1JT

On 10/24/2022 2:16 PM, Tony ZL3HAM via wsjt-devel wrote:

Hi Dennis,

I use DX Lab Suite and JT Alert and I got a Fatal Error message and also 
one that said JT9 failed to close but I wasn't using JT9.


The program just closed and I had to reboot the PC to correct it.

This happened the same as it did on earlier rc versions.

Thanks.

73 Tony, ZL3HAM


On 25/10/2022 6:58 am, Dennis W1UE via wsjt-devel wrote:

Tony
Were you just using WSJT only, or were you using it with N1MM+

Any error messages, or did the WSJT entry window just "disappear"?

Dennis W1UE


On Mon, Oct 24, 2022 at 1:52 PM Tony ZL3HAM via wsjt-devel 
 wrote:


Hi All,
>
> I'm running Ver 2.6.0-rc4 on Windows 11 Pro and the program has
just
> crashed for the second time and it needed a PC reboot to
restore. At
> the time I was on 20m FT4 after having a few QSO's and it crashed
> whilst in listening mode.
>
> 73 Tony, ZL3HAM



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

Re: [wsjt-devel] YBDXPI Contest Performance

[Joe Taylor via wsjt-devel]

Hi Dennis,

Thanks for your helpful report.  I guess it's not yet perfectly clear 
whether using the hamlib4.dll from v2.5.4 helped, or whether you were 
just lucky for the last 7 hours of the contest.


In any event, it seems that there must be some kind of negotiation issue 
between N1MM+ and WSJT-X.  Somehow we need to isolate this problem and 
see what can be done to make the negotiation more forgiving of delays, 
or whatever, and not simply shut down the channel.


-- Joe, K1JT

On 10/24/2022 8:54 AM, Dennis W1UE via wsjt-devel wrote:
I started the contest using 2.6.0RC4.  I operate with WSJT in 
conjunction with N1MM+, using the DX Lab Suite Commander to a K30/Mini, 
through a Remote Rig
unit to the remote transmitting site.  I used SO1V mode for this 
contest- no SO2R.  The combination worked perfectly for about 6 hours, 
then the WSJT-X for EW1 just "disappeared" with the TCP error from 
N1MM+.  I opened Task Manager, killed the orphan JT process, and was 
back on the air- for maybe 15 minutes, when it happened again.  This 
time I Restarted the computer, started up again, and within 30 minutes 
it happened again.


Remembering a conversation i had with Joe K1jt a while ago, I then 
substituted the 2.5.4 hamlib4.dll for the 2.6.0 dll, restarted the 
computer, and started operating again.  It lasted about 30 minutes, and 
the same error again.  I deleted the orphan JT9 process and started up 
again.  That was the end of the errors- it never happened again for the 
next 7 hours of operation.


In his write-up on 3830, Ty, K3MM, also tried 2.6.0rc4 to start the 
contest.  Within an hour of the start, he had his WSJT-X EW2 window just 
disappear.  Rather than fight it, he went back to 2.5.4 and had no more 
"disappearances" the rest of the contest (about 27 hours).


I typically use 100w or less in contests, but did use 800-1000w for this 
contest.  I saw no difference in "disappearances" between the two power 
categories.


Thanks  to all for their work in supporting WSJT-X. Its truly a great 
program!


Dennis w1UE





___
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.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

[Joe Taylor via wsjt-devel]

Hi Frode,

On 10/13/2022 5:05 AM, Frode Igland LA6VQ via wsjt-devel wrote:


I have used -rc4 since it was released and have found it quite stable with 
three notable exceptions:


I believe Dennis has already given you correct information about "CQ Max 
Dist".  This control is mentioned in Sections 1.1 and 7.3 of the RC4 
User Guide.  As noted there and in its Tool Tip, this feature is 
designed for use in the ARRL International Digital Contest, which uses 
distance-based scoring.  I believe it works as intended, selecting a 
response to your CQ that yields maximum score under these contest rules. 
 Be sure to activate the Active Stations window, as shown in User Guide 
Section 10.1.4.  Remember that Dupes yield 0 points and that no score 
can be calculated until a station's locator has been received.


As far as we are aware your Problem #1 is a hamlib issue.  Please 
communicate directly with Mike Black about it.


If you find a way to reliably reproduce your Problem #3, please let us 
know.  At the same time, please remember that convenience features like 
this one are intended as operator aids, not operator replacement.  You 
should override any selection made by the program if you prefer 
responding to someone else.


-- 73, Joe, K1JT

On 10/13/2022 1:29 PM, Frode Igland via wsjt-devel wrote:

Hi, Jarmo.
Does that mean that "CQ: Max Dist" is setup to work /only/ with the ARRL 
International Digital Contest?
Neither the Release Notes nor the -rc4 User Guide say anything about 
"CQ: Max Dist", so it is  difficult to say. "CQ: Max Dist" looks like 
the FT8 version of the "Best S+P" functionality in FT4, which works also 
outside contests, although FT4 was developed primarily for contesting. 
Then I find it strange that similar functionality in the general usage 
FT8 mode should work only in contest, and even only in one contest of 
the year.


The ARRL International Digital Contest  ran on 4-5 June 2022, whilst the 
WSJT-X 2.6.0-rc1 introducing "CQ: Max Dist"  was published only on 20 
June, i.e. shortly after this year's contest. If your information is 
correct,  I guess it will not be possible to test this functionality 
until next June.  Then it is strange that it was introduced almost a 
year before it was needed or useful.


The hover-over help text reads "Max*Pts*", not "Max Dist", probably a 
small typo.


73, Frode LA6VQ

tor. 13. okt. 2022 kl. 16:33 skrev jarmo via wsjt-devel 
>:


Thu, 13 Oct 2022 08:34:37 -0400
Dennis W1UE via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net>> kirjoitti:

Problem2 in not a problem, hover mouse over text, you can see, that
shoud wor with ARRL contest.

jarmo, oh1mrr
 > I can also confirm problem #1.  It is the same problem that
existed in
 > version 2.6.0 RC1,2,3 and 4.
 >
 > Since I use WSJT in combination with N1MM+ for logging, I get a "TCP
 > Error" when the program closes.
 > If I'm not using the combo, WSJT just closes.  I have not noticed
 > that the closing occurs when using
 > only FT8; it may also occur when using FT4, but there isn't enough
 > activity on FT4 to see if it happens.
 >
 > A couple of additional observations:
 > 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4
 > with the same dll from 2.5.4.  The closing
 > seemed to stop.  This only works if your rig is supported by the
 > earlier dll.
 > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation
 > before it closes.  Once it starts closing, it will
 > continually do it.
 >
 > I have not seen the issues with "CQ MAX DIST".  Are you sure it's not
 > picking the correct call?
 > 1. Calls without a grid are never selected unless they are the only
 > reply to your CQ.
 > 2. Band/Mode dupes are given a score of zero and only selected if the
 > only caller.
 > 3. Call selection is based on the point score generated by the
program
 > calculations; I know SP is further than
 > DL, but if they have the same point total and the DL is before the SP
 > in the decode window, the WSJT will
 > select the DL station to call.
 >
 > Dennis W1UE
 >
 >
 > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel <
 > wsjt-devel@lists.sourceforge.net
> wrote:
 >
 > > I can confirm problem 1, as it happened to me less than an hour
ago,
 > > including the orphaned JT9 decoding application.  Running Win 10 on
 > > a Lenovo X1 Carbon laptop.  I had been on FT8 for about an hour
 > > when it happened.
 > >
 > >
 > >
 > > Ed N4II.
 > >
 > >
 > >
 > > *From:* Frode Igland via wsjt-devel
 > > mailto:wsjt-devel@lists.sourceforge.net>> *Sent:* Thursday, October 13,
 > > 2022 5:06 AM *To:* WSJT software development
 > > mailto:wsjt-devel@lists.sourceforge.net>> 

Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

[Joe Taylor via wsjt-devel]

Hi Frode,

On 10/13/2022 5:05 AM, Frode Igland LA6VQ via wsjt-devel wrote:


I have used -rc4 since it was released and have found it quite stable with 
three notable exceptions:


I believe Dennis has already given you correct information about "CQ Max 
Dist".  This control is mentioned in Sections 1.1 and 7.3 of the RC4 
User Guide.  As noted there and in its Tool Tip, this feature is 
designed for use in the ARRL International Digital Contest, which uses 
distance-based scoring.  I believe it works as intended, selecting a 
response to your CQ that yields maximum score under these contest rules. 
 Be sure to activate the Active Stations window, as shown in User Guide 
Section 10.1.4.  Remember that Dupes yield 0 points and that no score 
can be calculated until a station's locator has been received.


As far as we are aware your Problem #1 is a hamlib issue.  Please 
communicate directly with Mike Black about it.


If you find a way to reliably reproduce your Problem #3, please let us 
know.  At the same time, please remember that convenience features like 
this one are intended as operator aids, not operator replacement.  You 
should override any selection made by the program if you prefer 
responding to someone else.


-- 73, Joe, K1JT

On 10/13/2022 1:29 PM, Frode Igland via wsjt-devel wrote:

Hi, Jarmo.
Does that mean that "CQ: Max Dist" is setup to work /only/ with the ARRL 
International Digital Contest?
Neither the Release Notes nor the -rc4 User Guide say anything about 
"CQ: Max Dist", so it is  difficult to say. "CQ: Max Dist" looks like 
the FT8 version of the "Best S+P" functionality in FT4, which works also 
outside contests, although FT4 was developed primarily for contesting. 
Then I find it strange that similar functionality in the general usage 
FT8 mode should work only in contest, and even only in one contest of 
the year.


The ARRL International Digital Contest  ran on 4-5 June 2022, whilst the 
WSJT-X 2.6.0-rc1 introducing "CQ: Max Dist"  was published only on 20 
June, i.e. shortly after this year's contest. If your information is 
correct,  I guess it will not be possible to test this functionality 
until next June.  Then it is strange that it was introduced almost a 
year before it was needed or useful.


The hover-over help text reads "Max*Pts*", not "Max Dist", probably a 
small typo.


73, Frode LA6VQ

tor. 13. okt. 2022 kl. 16:33 skrev jarmo via wsjt-devel 
>:


Thu, 13 Oct 2022 08:34:37 -0400
Dennis W1UE via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net>> kirjoitti:

Problem2 in not a problem, hover mouse over text, you can see, that
shoud wor with ARRL contest.

jarmo, oh1mrr
 > I can also confirm problem #1.  It is the same problem that
existed in
 > version 2.6.0 RC1,2,3 and 4.
 >
 > Since I use WSJT in combination with N1MM+ for logging, I get a "TCP
 > Error" when the program closes.
 > If I'm not using the combo, WSJT just closes.  I have not noticed
 > that the closing occurs when using
 > only FT8; it may also occur when using FT4, but there isn't enough
 > activity on FT4 to see if it happens.
 >
 > A couple of additional observations:
 > 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4
 > with the same dll from 2.5.4.  The closing
 > seemed to stop.  This only works if your rig is supported by the
 > earlier dll.
 > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation
 > before it closes.  Once it starts closing, it will
 > continually do it.
 >
 > I have not seen the issues with "CQ MAX DIST".  Are you sure it's not
 > picking the correct call?
 > 1. Calls without a grid are never selected unless they are the only
 > reply to your CQ.
 > 2. Band/Mode dupes are given a score of zero and only selected if the
 > only caller.
 > 3. Call selection is based on the point score generated by the
program
 > calculations; I know SP is further than
 > DL, but if they have the same point total and the DL is before the SP
 > in the decode window, the WSJT will
 > select the DL station to call.
 >
 > Dennis W1UE
 >
 >
 > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel <
 > wsjt-devel@lists.sourceforge.net
> wrote:
 >
 > > I can confirm problem 1, as it happened to me less than an hour
ago,
 > > including the orphaned JT9 decoding application.  Running Win 10 on
 > > a Lenovo X1 Carbon laptop.  I had been on FT8 for about an hour
 > > when it happened.
 > >
 > >
 > >
 > > Ed N4II.
 > >
 > >
 > >
 > > *From:* Frode Igland via wsjt-devel
 > > mailto:wsjt-devel@lists.sourceforge.net>> *Sent:* Thursday, October 13,
 > > 2022 5:06 AM *To:* WSJT software development
 > > mailto:wsjt-devel@lists.sourceforge.net>> 

Re: [wsjt-devel] Shared memory bug

[Joe Taylor via wsjt-devel]

Hi Mike,

I cannot confirm that anything you mention needs to be fixed.

You mention file 'constants.h', which does not exist.  I think you must 
mean 'constants.f90'.


File constants.f90 defines the constant NMAX to have the value 
30*60*12000 -- the size necessary to hold 30 minutes of data samples at 
12000 samples per second.


File jt9com.f90 then allocates storage for this many samples in array 
id2(NMAX) -- just as required.


I do not understand your comment about "his WAV file".  What file is 
this?  And what leads you to suggest that NSMAX=6827 is an incorrect value?


-- 73, Joe, K1JT

On 9/27/2022 5:14 PM, Black Michael via wsjt-devel wrote:
I think this needs to be fixed -- seems lib/jt9com.f90 got out of sync 
with constants.h


His WAV file also shows that NSMAX may need to be increased to 6912

diff --git a/lib/constants.f90 b/lib/constants.f90
index 36e81c77b..4f39e1aba 100644
--- a/lib/constants.f90
+++ b/lib/constants.f90
@@ -3,3 +3,4 @@
    integer, parameter :: NDMAX=NTMAX*1500 !Sample intervals at 1500 Hz rate
    integer, parameter :: NSMAX=6827       !Max length of saved spectra
    integer, parameter :: MAXFFT3=16384
+  integer, parameter :: RX_SAMPLE_RATE=12000
diff --git a/lib/jt9com.f90 b/lib/jt9com.f90
index 5b2970c05..b653bba75 100644
--- a/lib/jt9com.f90
+++ b/lib/jt9com.f90
@@ -54,6 +54,6 @@
       real(c_float) :: ss(184,NSMAX)
       real(c_float) :: savg(NSMAX)
       real(c_float) :: sred(5760)
-     integer(c_short) :: id2(NMAX)
+     integer(c_short) :: id2(NTMAX*RX_SAMPLE_RATE)
       type(params_block) :: params
    end type dec_data


Debug output where nsps=6912

Starting program: 
C:\JTSDK64-Tools\tmp\wsjtx-output\qt\5.15.2\2.6.0\Debug\install\bin\jt9.exe 
-9 -b G -f 700 -F 300 \Users\mdbla\Downloads\220926_104120.wav

[New Thread 23484.0x628c]
[New Thread 23484.0x6ce4]
[New Thread 23484.0x55c8]
[New Thread 23484.0x6bf8]

Thread 1 received signal SIGSEGV, Segmentation fault.
0x0041466a in symspec (
     shared_data=which is more than max-value-size>, k=6912,
     trperiod=2.1219957909652723e-314, nsps=6912, ingain=0, 
blowsidelobes=.FALSE., nminw=1, pxdb=0, s=...,

     df3=8.59003392e+09, ihsym=0, npts8=0, pxdbmax=0,
     npct=)
     at C:\JTSDK64-Tools\tmp\wsjtx\lib\symspec.f90:40
40        if(TRperiod+npct.eq.-999.9) stop             !Silence compiler 
warning






___
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] New Feature Request

[Joe Taylor via wsjt-devel]

Hi Alan,

On 9/19/2022 1:01 PM, Alan Altman AG7XS via wsjt-devel wrote:

Greetings,

Thank you for all the great work on creating and improving WSJT-X.

You are probably aware of the ADX transceiver designed by WB2CBA. It is a 
simple open source digital HF rig designed for home brewing. We are working on 
replacing the Arduino with a RPi PICO. Due to differences in internal 
peripherals and timers, it is more complicated to measure the TX frequency in 
order to send it to the Si5351 DDS we use.

In rethinking the problem, it occurred to me that WSJT-X must first generate a 
digital  list or table of tones for each transmission before they are sent to 
the sound card and on to the rig as an analog signal.


FT8 signals are not generated from a list of tones.  Abrupt frequency 
changes from one tone to the next would generate unwanted sidebands with 
amplitudes far above those of a properly generated FT8 signal.  For 
relevant details see Figure 3 and the associated text in our QEX paper 
describing the FT4 and FT8 protocols:

https://physics.princeton.edu//pulsar/k1jt/FT4_FT8_QEX.pdf

-- 73, Joe, K1JT


What would greatly simplify the transition to PICO is if the TX audio 
frequencies could be sent out over USB in a directly useable format that could 
be directly added to the base frequency and on to the DDS. The best solution 
for ADX would be the final 0 to 3000 Hz tone frequency value be sent upon start 
of TX and each subsequent change in value or at a preset interval until the end 
of TX (stop value appended to release TX mode)  or some other system if it is 
easier to implement on the WSJT-X side. Timing would be controlled by the 
WSJT-X. We have been using VOX or CAT control for PTT, but could update that to 
CAT only.

In addition if USB CAT polling interval requests could be blocked during TX 
periods, that would be even great as it prevent dropouts and data conflicts if 
using a USB hub with audio dongle.

73,
Alan
AG7XS



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

Re: [wsjt-devel] WSJT-X 2.6.0 rc4 - Not a bug but a possible change

[Joe Taylor via wsjt-devel]

Sam --

LA100B is not a standard callsign.  CQ messages for such callsigns never 
include a grid.  See the User Guide here:


https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.6.0-rc4.html#COMP-CALL

-- 73, Joe, K1JT

On 9/7/2022 10:13 AM, Sam W2JDB via wsjt-devel wrote:

Hi Joe,

In testing RC 4 I came across a CQ message from LA100B that did not 
include a grid.


I used TX5 to send a message "LA100B GRID?" to try to tell him/her that 
the grid is missing.


While not a bug, you might want to disable someone from sending CQ where 
the Grid is missing in the settings.


73,


Sam W2JDB



___
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] Release Candidate WSJT-X 2.6.0-rc4

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc4 is 
ready for download by beta testers. A list of its essential changes from 
previous releases can be found in the Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links for downloading WSJT-X 2.6.0-rc4 can be found on the WSJT-X Home 
Page, https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to find "Candidate release:  WSJT-X 2.6.0-rc4".

An installation file for macOS is not presently available.  One will be 
posted as soon as possible.


We hope you will enjoy using this beta release of WSJT-X 2.6.0.  As a 
beta tester you should report on your experiences with its new features, 
successful and otherwise, on one of the relevant WSJT forums.  Bugs 
should be reported by following instructions found here in the User Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc4.html#_bug_reports

WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU 
General Public License (GPLv3).  Development of this software is a 
cooperative project to which many amateur radio operators have 
contributed.  If you use our code, please have the courtesy to let us 
know about it.  If you find bugs or make improvements to the code, 
please report them to us in a timely fashion.  Additional licensing 
details can be found here:

https://physics.princeton.edu//pulsar/k1jt/devel.html

 73 from the WSJT Core Development Team
 Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] WSJT-x Stopping

[Joe Taylor via wsjt-devel]

Hi Dennis and Ron,

Thanks for your reports.  This message is off-list, since your needs are 
rather specialized -- but I have CC'd other members of our core 
development group.


On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote:
I had high hopes for 2.6.0 rc3.  I ran it for 25 hours decode time using 
an SO2R setup.  It never stopped working nor crashed.2.6.0 rc1 and rc2- 
the EW just disappeared from the screen and I got an error box related 
to TCP.  Since that first stoppage- or crash- I've had 4 more crashes.  
The longest I've operated since then has been about 40 minutes.


So, the bug that is causing the program to suddenly close, has not been 
found.  And it was looking so good!


On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote:
Same here, running N1MM with 2 instances it keeps crashing and locking 
everything down when it does. It took a long time for the first 
occurrence  but now its lucky to stay up 30 min.


...


I'll be single op.
If anyone makes it work with the Max Distance feature they will have a distinct 
advantage. Sadly it's back to 2.54 for me, I could not make it work reliably. 
I'll run it again this evening to try and get some screen shots and data that 
might help the Smart people, before I swap back to the stable version.
Good luck, Dennis ! You rocked the last one.


We'll be happy to help you guys to isolate the problem you're having, 
apparently with communication between WSJT-X and N1MM+, but I must 
caution you that it may take some time.  Moreover, in the immediate 
future my time is largely committed to a paper on the EME Echo mode 
features in WSJT-X 2.6.0.


None of our program versions 2.6.0-rc1, -rc2, or -rc3 have intentional 
changes to the way communications take place with an external program 
such as N1MM+.  At present I don't know the details of what happens when 
you say it (I suppose you mean WSJT-X) crashes.  Any error message? 
What was happening just before the failure?  Is WSJT-X doing any rig 
control?   Can you stress-test the situation in a way that reliably 
forces a failure?


These release-candidate versions of WSJT-X 2.6.0 have been bullet-proof 
in my own usage patterns, including in the ARRL-DIGI contest back in 
June at W2ZQ.  But we were using it alone, not with N1MM.  Of course, 
WSJT-X does not have built-in SO2R features.  Are there other reasons 
that you want N1MM in addition to WSJT-X for, say, the WW-DIGI contest?


None of us is a regular user of the N1MM + WSJT-X combination, so we 
really need your help -- and possibly that of the N1MM development 
group, to track down what's flaky about this two-program kludge.


-- 73, Joe, K1JT


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

[wsjt-devel] Release Candidate WSJT-X 2.6.0-rc3

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc3 is 
ready for download by beta testers. A list of its essential changes from 
previous releases can be found in the Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links for downloading WSJT-X 2.6.0-rc3 can be found on the WSJT-X Home 
Page, https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to find "Candidate release:  WSJT-X 2.6.0-rc3".

We hope you will enjoy using this beta release of WSJT-X 2.6.0.  As a 
beta tester you should report on your experiences with its new features, 
successful and otherwise, on one of the relevant WSJT forums.  Bugs 
should be reported by following instructions found here in the User Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc3.html#_bug_reports

WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU 
General Public License (GPLv3).  Development of this software is a 
cooperative project to which many amateur radio operators have 
contributed.  If you use our code, please have the courtesy to let us 
know about it.  If you find bugs or make improvements to the code, 
please report them to us in a timely fashion.  Additional licensing 
details can be found here:

https://physics.princeton.edu//pulsar/k1jt/devel.html

 73 from the WSJT Core Development Team
 Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] WSJT-X 2.6.0-rc2 - possible bug

[Joe Taylor via wsjt-devel]

Hi Josh,

Thanks for reporting this bug, which I have been able to reproduce. 
We'll track it down ASAP.


-- Joe, K1JT

On 7/21/2022 10:35 AM, Josh Rovero via wsjt-devel wrote:
Built from source on 64-bit Fedora Core 36.  NTP and chronyc show time 
sync to less than 13 ms.


WSPR mode.  Receive cycles are timed correctly.  The transmit cycles end 
after 90 seconds, instead of going for 2 minutes.


The release 2.5.4 version of WSJT-X does not have this issue.

--
P.J. "Josh" Rovero http://www.roveroresearch.org 


Ham Radio: KK1D


___
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] Release Candidate WSJT-X 2.6.0-rc2

[Joe Taylor via wsjt-devel]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc2 is 
ready for download by beta testers. A list of its essential changes from 
previous releases can be found in the Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links for downloading WSJT-X 2.6.0-rc2 can be found on the WSJT-X Home 
Page, https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to find "Candidate release:  WSJT-X 2.6.0-rc2".

We hope you will enjoy using this beta release of WSJT-X 2.6.0.  As a 
beta tester you should report on your experiences with its new features, 
successful and otherwise, on one of the relevant WSJT forums.  Bugs 
should be reported by following instructions found here in the User Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc2.html#_bug_reports

WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU 
General Public License (GPLv3).  Development of this software is a 
cooperative project to which many amateur radio operators have 
contributed.  If you use our code, please have the courtesy to let us 
know about it.  If you find bugs or make improvements to the code, 
please report them to us in a timely fashion.  Additional licensing 
details can be found here:

https://physics.princeton.edu//pulsar/k1jt/devel.html

 73 from the WSJT Core Development Team
 Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; Uwe, DG2YCB;
 Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] Download samples

[Joe Taylor via wsjt-devel]

Hi Sandro,

Thanks for reporting this issue.  I will look into why the file is missing.

-- Joe, K1JT

On 7/4/2022 7:20 PM, Alessandro Gorobey via wsjt-devel wrote:

Hi All,

I see that in v2.6.0-rc1 any OS Menu-->Help-->Download samples give 
error.


The cause is 
https://sourceforge.net/projects/wsjt/files/samples/contents_2.6.json 
file do not exist.


Thank in advance




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

Re: [wsjt-devel] Q65 question

[Joe Taylor via wsjt-devel]

Hi Andy,

On 6/30/2022 4:37 PM, Andrew Neumeier KA2UQW via wsjt-devel wrote:
When running Q65, can someone explain what the two boxes at the bottom 
of the main WSJTx screen represent?  Those boxes are to the right of the 
Last TX: box.  I assume they are counting the number of

sequences received.  Can someone enlighten me further?


Those values are the number of receive intervals currently accumulated 
for potential decoding in the Even and Odd Rx sequences.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSPR Drift

[Joe Taylor via wsjt-devel]

In WSPR mode, displayed "Drift" is frequency change in Hz over the full 
transmission.


-- Joe, K1JT

On 6/20/2022 11:41 AM, Pino Zollo via wsjt-devel wrote:

Please how shall I interpret Drift = 3 in a WSPR message ?

In which unit is it expressed ?

Thanks

Pino ZP4KFX



___
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] RC1 UI bug

[Joe Taylor via wsjt-devel]

Al --

Your screen shot shows an inadvertent user error, not a program bug.

It seems you have mistakenly checked "SWL Mode" on the View menu.

-- Joe, K1JT

On 6/17/2022 3:50 PM, Marco Calistri via wsjt-devel wrote:

Il 17/06/22 12:17, Al via wsjt-devel ha scritto:

( 2.6.0-rc1, W11)

Some how while transmitting and looking at mode in title bard I ended 
up with this and could not recover this missing controls until I 
restored my .ini from daily backup.



AL, K0VM


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

What is that "FT8-D" mode?

Thanks!
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**


___
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] RC1 UI bug

[Joe Taylor via wsjt-devel]

Marco --

On 6/17/2022 3:50 PM, Marco Calistri via wsjt-devel wrote:


What is that "FT8-D" mode?


There is no mode FT8-D.  That label on the K0VM screen shot is a name he 
selected for a Configuration.


-- Joe, K1JT


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

Re: [wsjt-devel] Ver 2.6.1 rc1: Possible bug in writing out the WSJT-X.ini file

[Joe Taylor via wsjt-devel]

Hi Sam,

You did not explain why you think there is a bug.  Or (except perhaps 
for curiosity?) why you need to examine the contents of file WSJT-X.ini.


Anyway, the line you want looks like this:

RespondCQ=2

The value will be 0 for "CQ: None", 1 for "CQ: First", or
2 for "CQ: Max Dist".

-- 73, Joe, K1JT



On 6/17/2022 10:53 AM, Sam W2JDB via wsjt-devel wrote:

Hi,

In testing RC1 and trying to find the place where the new option of Max 
Distance is recorded in the WSJT-X.ini file
I compare the file where Call First is selected with the file where Max 
Distance is selected.


It seems that the wsjt-x.ini file was changed on line 46 which has 
nothing to do with the currently selected configuration.


Below are the 2 lines from the 2 files

The top line is from the ini file where Max Distance was selected
The bottom line is from Call first selected.

IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64)

IC7300%20NoBridge\Common\pwrBandTuneMemory=@Variant(\0\0\0\x1c\0\0\0\x4\0\0\0\x6\0\x34\0\x30\0m\0\0\0\x2\0\0\0\x95\0\0\0\x6\0\x33\0\x30\0m\0\0\0\x2\0\0\0\x63\0\0\0\x6\0\x32\0\x30\0m\0\0\0\x2\0\0\0\x64\0\0\0\b\0\x31\0\x36\0\x30\0m\0\0\0\x2\0\0\0\x95)

In both cases the CallFirst was set to true in the currently selected 
configuration.


Running latest Win/10.

73,

Sam W2JDB





___
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] Release Candidate WSJT-X 2.6.0-rc1

[Joe Taylor via wsjt-devel]

Dear WSJT-X and MAP65 Users,

We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc1 is 
ready for download by beta testers.


This release has new capabilities beyond WSJT-X 2.5.4.  A full list of 
enhancements can be found in the Release Notes:


https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

Links for downloading WSJT-X 2.6.0 can be found on the WSJT-X Home Page, 
https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to find "Candidate release:  WSJT-X 2.6.0-rc1".

We hope you will enjoy using this beta release of WSJT-X 2.6.0 and MAP65 
3.0.0, and exercising the new mode Q65.  As a beta tester you should 
report on your experiences with new features, successful and otherwise, 
on one of the relevant WSJT forums.  Bugs should be reported by 
following instructions found here in the User Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc1.html#_bug_reports

WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU 
General Public License (GPLv3).  Development of this software is a 
cooperative project to which many amateur radio operators have 
contributed.  If you use our code, please have the courtesy to let us 
know about it.  If you find bugs or make improvements to the code, 
please report them to us in a timely fashion.  Additional licensing 
details can be found here:

https://physics.princeton.edu//pulsar/k1jt/devel.html

  -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS;
 Uwe, DG2YCB; Brian, N9ADG; and John, G4KLA


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

Re: [wsjt-devel] ARRL International Digital Contest

[Joe Taylor via wsjt-devel]

Hi Sam,

On 5/28/2022 6:18 PM, Sam W2JDB wrote:


2. Go to "File | Settings | Colors", check "My Call in message" and "New
Call on Band", and uncheck everything else. Check the box "Highlight
also messages with 73 or RR73." Click OK to dismiss the Settings dialog.

Not on the color page. Where ?


Sorry, my mistake.  The option "Highlight also messages with 73 or RR73" 
is available in our development code branch but is not present in WSJT-X 
2.5.4.


-- 73, Joe, K1JT


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

[wsjt-devel] ARRL International Digital Contest

[Joe Taylor via wsjt-devel]

Hi all,

In response to questions I've received, here are some details and 
suggestions for operating in the new ARRL-sponsored digital contest.


Contest Period: 1800 UTC June 4 through 2359 UTC June 5.

Bands: 160, 80, 40, 20, 15, 10, and 6m

Modes: any digital mode, except no traditional RTTY.  In practice most 
contest participants will likely use FT4 and FT8.


Exchange: Four-character grid locator

Scoring: one point per QSO, plus an additional point for every 500 km of 
distance or portion thereof, with distances measured between grid centers.


Power categories: Low Power (100 W or less) and QRP (5 W or less).  No 
High Power category.


Full details and contest rules are available here:
https://contests.arrl.org/ContestRules/Digital-Rules.pdf

In particular, take note of the recommended sub-bands and advice about 
operating frequencies.  Here are the essentials taken from the Contest 
Rules document:


##
FT4 Recommended Sub-bands:
1.836-1.840
3.580-3.590
7.080-7.090
14.080-14.090
21.080-21.090
28.080-28.090
50.330 to 50.340

FT8 Recommended Sub-bands:
1.840-1.844
3.590-3.600 (No Digital above 3600)
7.090-7.100
14.090-14.100
21.090-21.100
28.090-28.100
50.340 to 50.350

When choosing your operating frequency, set the radio dial at the bottom 
of the sub-band and QSO with stations on audio frequencies within the 
radio passband typically 2.5-4 kHz wide. If a sub-band becomes crowded, 
move the radio dial frequency up in 2 kHz increments, as needed. (For 
example: 7,090, 7.092, 7.094, 7.096 and 7.098).

##

Finally, a few suggestions for configuring WSJT-X 2.5.4 for the contest:

1. Go to "File | Settings | Advanced", check "Special operating 
activity" and "NA VHF Contest".  (Of course this is not a VHF contest, 
but the exchange and recommended message sequence is the same.)


2. Go to "File | Settings | Colors", check "My Call in message" and "New 
Call on Band", and uncheck everything else.  Check the box "Highlight 
also messages with 73 or RR73."  Click OK to dismiss the Settings dialog.


3. Select "File | Reset Cabrillo log".

4. Before the contest starts, select "File | Open log directory", and 
rename the file wsjtx_log.adi to something else, say wsjtx_log.adi.bak. 
This ensures that you will start the contest with an empty log.  (After 
the contest, you will probably want to append your contest QSOs to your 
backup log and then rename it back to the original "wsjtx_log.adi".)


-- 73, Joe, K1JT



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

Re: [wsjt-devel] WSPR used for astronomical observations — Reaching out to Prof. Taylor

[Joe Taylor via wsjt-devel]

Hi Serge,

I can find no record of an email from you last August.

The best published reference to the WSPR protocol and the WSPRnet 
database is this one:


J. Taylor, K1JT, and B. Walker, W1BW, "WSPRing Around the World," in 
QST, November 2010, pp. 30-32.


A copy of the paper's manuscript is available as item 16 on this page of 
the WSJT web site:


https://physics.princeton.edu//pulsar/k1jt/refs.html

-- 73, Joe, K1JT

On 5/7/2022 6:08 PM, Serge Stroobandt via wsjt-devel wrote:


Hi, this is Serge, ON4AA,
mostly known from https://hamwaves.com/propagation/

I am writing to this mailing list in a desperate attempt to contact 
Prof. Joe Taylor, K1JT.
Late last August, I tried reaching Joe on his Princeton e-mail address 
but got no response, most probably due to the pandemic.


Here is the deal:

WSPR can be used to observe the largest structure in our solar system: 
the heliospheric current sheet (HCS).


I have been aggregating, over the course of almost four years, the data 
of nearly 42 million individual WSPR reports and
have compared this with satellite data at the L1 Lagrange point and 
other data sets.


Statistical analysis (I was formally trained at this) shows that WSPR is 
far superior to other Earth-based methods for observing the HCS. This 
finding also has an important consequence for our understanding about 
amateur radio propagation; but more on that later.


At the moment, I am preparing a paper which I hope to publish in ACU 
Space Weather, a peer-reviewed scientific journal.
I would love to acknowledge the contribution of Joe and other WSPR & 
wsprnet.org developers and this is why I am writing here.


I am looking forward to someone here putting me in direct contact with 
Joe, or for Joe to write me at: serge(at)stroobandt.com Thanks!


73 de Serge, ON4AA


___
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] wsprd cli options

[Joe Taylor via wsjt-devel]

Hi Jim,


Where can I find detailed info or guidance on the use of the options, -C
etc that can be applied to wsprd?


For information more detailed than already provided in the help message, 
you'll need to read the wsprd.c source code.


The default value for the maximum number of decoder cycles is 1.  I 
do not know why you might think 500 is used here.


You will find that decoding performance depends only weakly on the value 
chosen.


If you have a specific question, please feel free to ask.

-- 73, Joe, K1JT


On 5/1/2022 9:10 AM, Jim Lill via wsjt-devel wrote:

yes a bit more info would be desirable...

for example the default that wsjt-x uses for -C is 500 yet wsprd itself 
has a default of 1




On 5/1/22 07:48, Black Michael via wsjt-devel wrote:

Are you looking for more than this?

/wsprd: invalid option -- '?'

Usage: wsprd [options...] infile

       infile must have suffix .wav or .c2



Options:

       -a  path to writeable data files, default="."

        -B disable block demodulation - use single-symbol noncoherent 
demod


        -c write .c2 file at the end of the first pass

        -C maximum number of decoder cycles per bit, default 1

        -d deeper search. Slower, a few more decodes

        -e x (x is transceiver dial frequency error in Hz)

        -f x (x is transceiver dial frequency in MHz)

        -H do not use (or update) the hash table

        -J use the stack decoder instead of Fano decoder

        -m decode wspr-15 .wav file

        -o n (0<=n<=5), decoding depth for OSD, default is disabled

        -q quick mode - doesn't dig deep for weak signals

        -s single pass mode, no subtraction (same as original wsprd)

        -v verbose mode (shows dupes)

        -w wideband mode - decode signals within +/- 150 Hz of center

        -z x (x is fano metric table bias, default is 0.45)










On Sunday, May 1, 2022, 06:14:36 AM CDT, Jim Lill via wsjt-devel 
 wrote:







Where can I find detailed info or guidance on the use of the options, -C
etc that can be applied to wsprd?

tnx es 73

-Jim

WA2ZKD



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

[wsjt-devel] Are you building WSJT-X ?

[Joe Taylor via wsjt-devel]

When I started work on WSJT some 21 years ago, my principal goal was to 
help bring amateur weak-signal communication techniques into the 
twenty-first century -- and in doing so, to help spread knowledge of 
modern communication theory into the amateur radio community.


By 2005 WSJT was well established but mostly used for special purposes 
like meteor scatter and EME ("moonbounce").  A stable development path 
had been established: the program was fully Open Source, licensed under 
the GNU General Public License, and it could be built by anyone from 
source code using freely available compilers and development tools.  At 
this time WSJT was coded in a combination of Python, Fortran, and C.  A 
re-write in 2012 created the present program, WSJT-X, using the Qt 
platform and C++ language in addition to Fortran and C.


To help gauge the extent to which my original educational goals are 
being met, we in the core development team are interested to know how 
many WSJT-X users are currently building the program for themselves, 
from source code.  If you are doing so, we would appreciate an email 
response -- either publicly, to this list, or in a private email to me. 
All responses will be appreciated, but particular things you might want 
to mention in your message include these:


 - Building on what platform?  Windows, Linux, macOS, or other?

 - What are your particular programming skills and interests?

 - Are you making changes to the code?  If so, toward what end?

 - What portions of the code have you studied well enough to understand?

Many thanks -- I look forward to hearing from you!

-- 73, Joe, K1JT


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

Re: [wsjt-devel] non standard calls and WSJT-X

[Joe Taylor via wsjt-devel]

TO7GJ is perfectly acceptable as a standard callsign.

As described in the User Guide, the list of acceptable prefixes and 
suffixes applies only to the case of a Type 1 add-on prefix or suffix, 
which Lance will not be using.


-- Joe, K1JT

On 3/19/2022 2:29 PM, Lance Collister, W7GJ via wsjt-devel wrote:

Hi Rick,

Yes, I THINK I will be OK using the callsign of TO7GJ for both FT8 and 
Q65-60A modes, but it sure will be interesting to hear definitively from 
Joe as to whether I will suffer in any way by not having "TO" in the 
list of official "Type 1" prefixes.


MNI TNX and VY 73, Lance

On 3/19/2022 18:15:29, K5GZR - Rick wrote:


Lance,

WSJT-X modes with 77-bit message payloads (FST4, FT4, FT8, MSK144, and 
Q65) can handle QSOs between a standard and a compound/nonstandard call.


WSJT-X modes with 72-bit message payloads (JT4, JT9, JT65) have a much 
more restrictive set of rules. The documentation has separate sections 
for those two message payload lengths…  I found it easy to get lost in 
the discussion of the 72-bit payloads, which apply to modes you might 
not be using.


Note that the comment about the table of prefixes and suffixes is 
contained in the 72-bit section, not the 77-bit section.


So… I would suggest that if you have a Type 1 callsign  and use the 
modes with 77-bit message payloads, you should not have a problem 
working stations with compound/nonstandard calls as long as they are 
using a current version of WSJT-X, or some other software that is 
‘compatible’.


As we all understand, the latest version of WSJT-X is compatible with 
another copy of the latest version of WSJT-X…. HOWEVER… You, as the 
dxpedition station, can’t guarantee compatibility with any other 
software…   and callers using other software are ‘on their own’.   
Kinda ugly when you put it that way, but it is the same as saying ‘Our 
SSB QSOs will use English’ and having stations expect you to be able 
to understand Farsi, or Swahili, or French (LOL).


The ‘gotcha’ with 77-bit messages and compound/nonstandard callsigns 
really only gets involved if the station with the compound/nonstandard 
call is calling CQ.


In that case, the CQ message does not include the CQ caller’s grid.

However(!) with 77-bit messages and non-compound/standard callsigns 
(like what Joe suggested, and what I think you will be using) CQ is 
not a problem


The CQ message for a non-compound/standard callsign DOES include the 
CQ caller’s grid.


It will be interesting to see the ‘official’ response from Joe.

73,  Rick  -  K5GZR




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

Re: [wsjt-devel] WSPR source code

[Joe Taylor via wsjt-devel]

Hi Stan,

Compiling the old (circa 2014) version of WSPR is fine as a learning 
exercise.  It can give you a lightweight program that's relatively easy 
to modify and play with.  As Tom noted, however, it will not provide top 
WSPR performance.  It has not been kept up to date, and we view it as 
obsolescent because it is superseded by the WSPR capabilities in WSJT-X.


-- Joe, K1JT

On 3/4/2022 2:14 PM, Stan Gammons via wsjt-devel wrote:

I got it to compile successfully by changing

integer iclock(12)

to

integer iclock(33)

in wspr2.f90

Don't know that was the "right thing" to do, but it seems to work.


73

Stan
KM4HQE


On 3/4/22 12:17, Stan Gammons via wsjt-devel wrote:
I fetched the source using git clone 
https://git.code.sf.net/p/wsjt/wspr wsjt-wspr  and tried to build it 
on Kubuntu 20.04 but I get this error


Warning:Legacy Extension: Comma before i/o item list at (1)
gfortran  -O2 -Wall -fbounds-check -fno-second-underscore 
-Wno-conversion -Wno-character-truncation -fPIC -c wqencode.f90
gfortran  -O2 -Wall -fbounds-check -fno-second-underscore 
-Wno-conversion -Wno-character-truncation -fPIC -c wspr2.f90

wspr2.f90:68:23:

  68 |   call random_seed(PUT=iclock)
 | 1
Error:Size of ‘put’ argument of ‘random_seed’ intrinsic at (1) too 
small (12/33)

make: *** [Makefile:92: wspr2.o] Error 1


Ideas?


73

Stan
KM4HQE


On 3/3/22 20:04, halst...@gmail.com wrote:

Stan,

 WSPR source: https://sourceforge.net/p/wsjt/wspr/ci/master/tree/

WSPR-X source: https://sourceforge.net/p/wsjt/wsprx/ci/master/tree/

JTSDK packages to help you build the source: 
https://sourceforge.net/projects/jtsdk/


Links obtained from: 
https://physics.princeton.edu//pulsar/K1JT/devel.html


Warren
KN6HXP

On Thu, Mar 3, 2022, 17:07 Stan Gammons via wsjt-devel 
 wrote:


Is the source code for WSPR available somewhere?  I tried to
install the
.deb package on Kubuntu 20.04 but it fails with the "cannot satisfy
dependencies" error.


73

Stan
KM4HQE





___
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] Memorial service for Bill Somerville, G4WJS

[Joe Taylor via wsjt-devel]

I write to let you know that a Memorial service for Bill Somerville, 
G4WJS. will take place at Chilterns Crematorium, Amersham, Milton 
Chapel, at 13:00 (I believe this means 1300 UTC) on Friday, January 28.


You can view the service remotely, as follows:

https://www.wesleymedia.co.uk/webcast-view

Webcast Login PIN: 273-9083

Webcast Viewing Instructions are available here:

https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fclientportal.wesleymedia.co.uk%2Femail-template%2Fwebcast_viewing_instructions.pdf=04%7C01%7C%7C7579efac53b1463cbdfd08d9dc19a66b%7C84df9e7fe9f640afb435%7C1%7C0%7C637782825000764798%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=8CzOfX%2FqTLEudSP7jnFOKW%2Bs4eG7ek7cUvwKCPRy3S8%3D=0

I take the instructions to mean that you can view the webcast starting 
at any time after the service has begun.


Bill did not have many close family members.  Many of his friends were 
fellow ham radio enthusiasts, scattered all over the world, so it is 
good to have this option for a way to pay our last respects to a dear 
colleague.


With best wishes to all,

-- 73, Joe Taylor, K1JT


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

Re: [wsjt-devel] Bill Somerville, G4WJS, SK

[Joe Taylor via wsjt-devel]

I am forwarding a message from Paul Welford, G4YKQ:

#
I have been requested to post this to The Group Re: The Late G4WJS Bill.

Bill"s funeral will take place on Friday 28th January at 1-0 p.m at 
Amersham Crematorium, Whielden Lane, Amersham, Buckinghamshire. HP7 OND.


A toast to Bill will be raised afterwards at The Fleur De Lis Public 
House. Oxford Road,Stokenchurch, High Wycombe, Buckinghamshire. HP14 3TZ.


It"s acknowledged that Bill had made many friends Worldwide especially 
as being a major contributor to WSJT-X and solved many a user problems.


As in the way of thanks please give a thought and raise a glass or two 
wherever you are on this day to Bill.


I personally know of the countless hours he devoted to the group and 
helping others.As I have said before "He loved it"!!


If you are going to attend ALL ARE WELCOME  please inform me due to food 
numbers, etc.


I have just been informed that the short Humanist service will be 
available online .Please contact me for further details.

g4ykq@yahoo .co.uk

Many Thanks Paul
#
On 1/14/2022 9:56 AM, Joe Taylor via wsjt-devel wrote:
There is a nice piece in the February issue of QST about our departed 
friend Bill Somerville, G4WJS.


In case you do not subscribe to QST, I have posted a copy here:
https://physics.princeton.edu//pulsar/k1jt/G4WJS.jpg

 -- 73, Joe, K1JT



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

[wsjt-devel] Bill Somerville, G4WJS, SK

[Joe Taylor via wsjt-devel]

There is a nice piece in the February issue of QST about our departed 
friend Bill Somerville, G4WJS.


In case you do not subscribe to QST, I have posted a copy here:
https://physics.princeton.edu//pulsar/k1jt/G4WJS.jpg

-- 73, Joe, K1JT


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

Re: [wsjt-devel] Q65 decoder only decodes only one of multiple signals in passband

[Joe Taylor via wsjt-devel]

Hi Peter, Ed, and all,

Best WSJT-X operating practices are not necessarily the same for all 
modes.  Q65 is the youngest mode in the program: since October 2020 it 
has been developed and optimized with special attention to its use for 
propagation modes mentioned in its Quick-Start Guide such as 
tropospheric scatter, rain scatter, ionospheric scatter, TEP, and EME.

These optimizations require example *.wav files recorded by WSJT-X.

So far we have no such files for the December-January openings between 
the Americas and VK/ZL on 6 meters.  Please help us in this regard! 
It's a big help to us if you always operate with "Save all" checked on 
the save menu -- at the very least, do this when operating in unusually 
interesting propagation conditions.  Then, remember to send us a few 
examples of interesting files.  You can always invoke "File | Delete all 
*.wav & *.c2 files in SaveDir" to clean out unwanted files.


On specifics of best operating practices for Q65 modes: many recommended 
settings are explicitly mentioned in the Quick-Start Guide to Q65 or 
shown in the screen shot there.  It is no longer necessary to set


I generally use FTol = 100, or even less, and set the Rx Freq on the 
sync tone of the station I'm trying to work.  If "Single decode" is 
unchecked on the "Settings | General" tab you will normally see decodes 
of other signals in the passband as well as the one at the selected 
frequency.  If you see a signal that does not decode, you can always 
double-click on its sync tone to force a decoding attempt there.  For 
EME signals you must always check "Decode after EME delay".


Q65 decoding can take longer than for other modes, so I generally use 
the Fast setting on the Decode menu.  If you have a fast shack computer 
you might want to experiment with Normal or Deep.  However, note that 
with the Fast setting you get quick decodes of most decodable signals, 
and when you double-click on a signal the decoder always uses Deep 
parameters.  So then you're covered, both ways.


Peter, your comments about q3 decodes of the signal carrying message 
"K1JT K9AN R-16" suggest that you haven't yet quite understood the "q#" 
meanings.  With MyCall set to K1JT and DxCall set to K9AN, you'll get q3 
decodes because both calls are as specified.  With MyCall = K1JT and 
DxCAll set to something else (or blank), you can gen a q2 decode.  With 
MyCall = something other than K1JT, you can only get a q0 decode.  For 
the example in the Quick Start Guide, you get a q03 average decode after 
three files are processed.


Please send us some files with good intercontinental DX signals!

-- 73, Joe, K1JT

On 1/5/2022 6:25 AM, Peter Sumner wrote:

Hello Joe and others.

It would seem I am the creator of my own problems, I have been chatting 
with Charlie G3WDG and he made mention that he was using a narrow Ftol 
value and could decode all signals from my shared test WAV file and the 
multiple signals in the files he created and sent to me.


I have been setting my Ftol to be a large value (1,000Hz) which was 
covering many of the wanted signals in the passband, something I thought 
I needed to do, which is a bit of a hangover from using JT65 I guess.


As soon as I set my Ftol down to 20 Hz like Charlie and I now notice you 
also made mention of 20Hz in your quick start guide, I am able to decode 
all signals in my sample files and those from Charlie on a complete 
range of WSJT-X instance I have on the shack PC's and Raspberry PI's I 
use for WSPR duties.


For those who like to test it for themselves, my test file for Q65-A 
30sec period is here: https://vk5pj.com/wsjtx/220103_224100.wav 
<https://vk5pj.com/wsjtx/220103_224100.wav>

If successful you will see these three decodes:

224100  -7  0.3 1173 :  CQ OC W4TAA EL87  q0
224100 -11  0.2 1520 :  CQ AC4TO EM70      q0
224100 -17  0.2 2510 :  CQ KD5M EM60      q0

I suspect there are many more than I with this wrong setting, so would 
encourage people to check their Q65 setup.


regards,
Peter, vk5pj


On Wed, Jan 5, 2022 at 2:43 AM Joe Taylor <mailto:j...@princeton.edu>> wrote:


Hi Peter,

I tries WSJT-X 2.5.4 on the Q65 sample Q65 files.   I see all the
decodes for Q65-60A and Q65-30A that are mentioned in the "Quick-Start
Guide to Q65," so I have no idea what may be causing you trouble.  If
you haven't figured it out, you could send me a copy of file WSJT-X.ini
in your log directory, and I'll look further...

         -- 73, Joe, K1JT

On 1/4/2022 5:16 AM, Peter Sumner via wsjt-devel wrote:
 > Hi,
 >    at some point the Q65 decoder engine has stopped showing
decodes from
 > multiple signals in the WSJT-X passband and I am at a loss to
explain
 > how or when this has occurred.
 >
 > I have downloaded the sample files from the main Pulsar web site and
 >

Re: [wsjt-devel] Q65 decoder only decodes only one of multiple signals in passband

[Joe Taylor via wsjt-devel]

Hi Peter,

I tries WSJT-X 2.5.4 on the Q65 sample Q65 files.   I see all the 
decodes for Q65-60A and Q65-30A that are mentioned in the "Quick-Start 
Guide to Q65," so I have no idea what may be causing you trouble.  If 
you haven't figured it out, you could send me a copy of file WSJT-X.ini 
in your log directory, and I'll look further...


-- 73, Joe, K1JT

On 1/4/2022 5:16 AM, Peter Sumner via wsjt-devel wrote:

Hi,
   at some point the Q65 decoder engine has stopped showing decodes from 
multiple signals in the WSJT-X passband and I am at a loss to explain 
how or when this has occurred.


I have downloaded the sample files from the main Pulsar web site and 
tried to follow the Q65 quick start guide to no avail.


At this point none of the Q65-30A sample WAV files produce a decode for 
me, the single sample for Q65-60A seems to have two signals but can not 
get either to decode no matter what combination of Fast, Deep or Normal 
I have tried.


While I have successfully had some Q65 contacts to the USA today from 
Australia, it is making me doubt the results of the decoder.


Does anyone in the group have some proven Sample WAV files with multiple 
stations in a period I could try? (other than the ones from the WSJT-X 
web site)


So far tried WSJT-X version, 2.4, 2.50, 2.51 and 2.54 with the 
same result.  I know this used to work for me as in June July it was 
doing multi pass decoding on the openings to the EU and was working on 
EME during the recent W7GJ trip away.


I am leaning to this being a problem with a windows update as going back 
and testing with v2.4 should have given me good results but alas no


Still scratching my head.

Regards,
Peter, vk5pj


___
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] Generating an audio file of WSPR or JT-65

[Joe Taylor via wsjt-devel]

Hi Peter,

Hardly surprisingly, we have written simulators for all modes developed 
for WSJT and WSJT-X.  The simulators are used extensively during 
development, but much less thereafter.


Recently we have included only a few of them (e.g., fst4sim, mapsim, 
q65sim) in the packaged distributions of WSJT-X.  Source code for all of 
them is present in the SourceForge repository and the packaged source 
tarball, so you could compile your own.  If you would like a prebuilt 
copy of wsprsim[.exe] or jt65sim[.exe], please let me know off list.


-- 73, Joe, K1JT

On 1/4/2022 7:40 AM, Peter Berrett via wsjt-devel wrote:


Dear Developers

Can someone please help me with a question about making an audio file of 
a WSPR or JT65 transmission?


I see that there is a program for simulating a JT65 transmission (SIMJT) 
however I do not see any way of specifying the offset of the 
transmission. I vagually recall, from a couple of years ago, being able 
to generate a WSPR or JT65 audio file but being able to specify at what 
hertz the transmission started. I have forgotten how I did it however.


So for example I might have been able to generate a Wspr transmission 
starting at 0-200 hz and then another at 200-400 hz etc.


Is there a program that will allow me to generate a Wspr or JT-65 signal 
in this way or must I use WSJT to generate the audio?


Thanks Peter



___
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.5.4 GA Release

[Joe Taylor via wsjt-devel]

Hi Saku,

I was too busy after yesterday's GA rlease of WSJT-X 2.5.4, and did not 
get around to updating the SourceForge repository.  It should be up to 
date now.


Best wishes for 2022 -- I hope it will be a better year for all of us!

-- 73, Joe, K1JT

On 1/4/2022 3:57 AM, Saku via wsjt-devel wrote:


Joe Taylor via wsjt-devel kirjoitti 3.1.2022 klo 18.54:

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated. 


Is the [remote "origin"]
     url = https://git.code.sf.net/p/wsjt/wsjtx
     fetch = +refs/heads/*:refs/remotes/origin/*

not in use any more?

"git pull" gives: "Already up to date" there and it is over month since 
last "git pull" was issued.





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

Re: [wsjt-devel] WSJT-X 2.5.4 GA Release

[Joe Taylor via wsjt-devel]

Tnx Jeff.  Compiler warnings have been very low on our priority list 
recently, hi.  We will silence them, in due course.  :-)


-- Joe, K1JT

On 1/3/2022 1:51 PM, Jeff Stillinger via wsjt-devel wrote:
The source build went well.   However, it's time for one of those code 
clean ups.  Several misc. warnings popping up during the build.




On 1/3/22 10:54, Joe Taylor via wsjt-devel wrote:
Please welcome two new members of the core WSJT Development group: 
Chet Fennell, KG4IYS, and Uwe Risse, DG2YCB.  Each brings important 
skills and experience to the project, after the loss of Bill 
Somerville, G4WJS.


The newly constituted group has been working to redefine standard 
operating procedures for new releases.  WSJT-X 2.5.4, a bug-fix 
release correcting these two flaws in release 2.5.3, is now available 
as a General Availability (GA) release.


Changes from v2.5.3 are:

WSJT-X: Repair a defect that caused occasional crashes when in QSO with
stations using nonstandard callsigns.

MAP65: Correct a bug that prevented "Best-fit Delta phi" solutions 
from  being displayed to the user.


Links to WSJT-X 2.5.4 installation packages for Windows and Linux are 
available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Thanks to John Nelson, G4KLA, the installation package for macOS will 
be added soon.


You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If 
you use our code, please have the courtesy to let us know about it. If 
you find bugs or make improvements to the code, please report them to 
us in a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) 
release of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this 
request is ignored.


Bugs should be reported by following instructions found here in the 
User Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.4.html#_bug_reports 



We hope you will enjoy using WSJT-X 2.5.4.

   -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; and
   Uwe, DG3YCB.


___
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.5.4 GA Release

[Joe Taylor via wsjt-devel]

Hi Joe,

"CQ MA RI CALLSIGN" is not a standard message.  It can be sent only as 
free test, and that will work only for a 3- or 4-letter callsign.


Double-clicking on a free text message is not supported, and results are 
undefined.


You can work a station sending such a message, but you'll need to enter 
his call in DxCall manually.


-- Joe, K1JT

On 1/3/2022 1:36 PM, Joe Dzekevich via wsjt-devel wrote:

Looks good

The problem with CAT with the IC 9700 that was in 2.5.3 (and was OK in
2.5.2) is resolved in 2.5.4.  All is OK.  No problems with a TS-590SG or the
IC-9700.  All works fine.  Good job.

Now I did notice this.
A station was calling in the format:
CQ MA RI CALLSIGN
(also no grid square in his text string)
So, I figured I would give him MA, and I double clicked on him, and 2.5.4
would not reply.  I figured that particular format was not valid.  But just
in case, this is just a FYI.  I had never seen that string format before, so
I have no info if it would have worked in earlier revisions.

In working some So Americans this afternoon on 10m, replying to their CQs
worked just fine.

73
Joe, K1YOW




___
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] WSJT-X 2.5.4 GA Release

[Joe Taylor via wsjt-devel]

Please welcome two new members of the core WSJT Development group: Chet 
Fennell, KG4IYS, and Uwe Risse, DG2YCB.  Each brings important skills 
and experience to the project, after the loss of Bill Somerville, G4WJS.


The newly constituted group has been working to redefine standard 
operating procedures for new releases.  WSJT-X 2.5.4, a bug-fix release 
correcting these two flaws in release 2.5.3, is now available as a 
General Availability (GA) release.


Changes from v2.5.3 are:

WSJT-X: Repair a defect that caused occasional crashes when in QSO with
stations using nonstandard callsigns.

MAP65: Correct a bug that prevented "Best-fit Delta phi" solutions from 
 being displayed to the user.


Links to WSJT-X 2.5.4 installation packages for Windows and Linux are 
available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Thanks to John Nelson, G4KLA, the installation package for macOS will be 
added soon.


You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Bugs should be reported by following instructions found here in the User 
Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.4.html#_bug_reports

We hope you will enjoy using WSJT-X 2.5.4.

   -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; and
   Uwe, DG3YCB.


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