wsjt-devel — WSJT software development

Re: [wsjt-devel] RC8 trouble

[Andrew W. <k9...@ya...>]

To address my problem, Steve K9AN suggested I create a new WSTJ-X.ini 
file to see if -rc8 still crashed.

I am pleased to report that creating a new .ini file by renaming the old 
one and restarting v2.7.0-rc8 resolved the issue.  Both 250106-rc8 and 
v2.7.0-rc8 now run and decode properly.

I should have tried generating a new .ini file before posting a note 
here!  Shame on me...

My thanks to others who responded with suggestions.

73 de Drew K9CW


On 1/7/2025 8:46 PM, Andrew White via wsjt-devel wrote:
> After having no problems with any previous WSJT-X version, I 
> discovered that both WSJT-X v2.7.0-rc8 and 250106-rc8 cause an Access 
> Violation (0xc0000005) the first time the *Decode* button turns on.  I 
> am running Win10 PRO-64, and FT8/FT4 have always worked OK.  Here is 
> the error generated by 250106-rc8:
>
>
>
> My 241206-007 still works fine.  I downloaded and installed 241014-rc7 
> improved, and that version also runs OK.  Both of the -rc8 versions 
> fail the first time *Decode* turns on near the end of the receive 
> period, and the application terminates without triggering any error 
> message.  I must manually kill JT9.EXE before I can start WSJT-X again.
>
> Since I have not seen anyone else report this problem, it must be 
> something unique to my setup.  I am at a loss to know why only -rc8 
> versions fail here.  Hopefully, someone can suggest what I might try.
>
> 73 de Drew K9CW
>
>
> -- 
> **********************************************
> * K9CW Thomasboro, IL  EN50wf
> * email:k9...@ya...
> * DXCC: 363/340  CW: 351/339 (need P5!)
> *
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

-- 
**********************************************
* K9CW Thomasboro, IL  EN50wf
* email:k9...@ya...
* DXCC: 363/340  CW: 351/339 (need P5!)
*

[wsjt-devel] Workaround if RC8 crashes or cannot be started

[Uwe, D. <dg...@gm...>]

Hi all,

We have just found out that the problems encountered by some users of
RC8, i.e. that the program cannot be started or crashes in individual
cases, only occur when “Enable QSY Popups” is switched off. We are
working on finding the root cause.

But this results in the following workaround: *Leave “Enable QSY Popups”
switched on*. This should prevent the error.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB

Re: [wsjt-devel] Please Remove me from mailing list

[Shirley M. D. <shi...@gm...>]

You should be able to unsubscribe yourself by using the list info link at
the bottom of every email you receive from the list. Your client may hide
that link, in which case  you first have to use whatever command it
provides to see the entire message.

On Wed, Jan 8, 2025 at 11:30 AM Norman McCourt via wsjt-devel <
wsj...@li...> wrote:

> Please remove me from your mailing list. I accidentally got put on the
> list.
>
> ncm...@gm...
>
> Thank you Norm
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Please Remove me from mailing list

[Dan <dan...@gm...>]

I am not finding you in my contacts list (??).

What is your call sign ?

Can you forward me the last email you received from me so I can track 
down its source.

Thanks....

Dan / K7REX


------ Original Message ------
>From "Norman McCourt via wsjt-devel" <wsj...@li...>
To wsj...@li...
Cc "Norman McCourt" <ncm...@gm...>
Date 1/8/2025 9:26:30 AM
Subject [wsjt-devel] Please Remove me from mailing list

>Please remove me from your mailing list. I accidentally got put on the 
>list.
>
>ncm...@gm...
>
>Thank you Norm

[wsjt-devel] Please Remove me from mailing list

[Norman M. <ncm...@gm...>]

Please remove me from your mailing list. I accidentally got put on the list.

ncm...@gm... <mailto:ncm...@gm...>

Thank you Norm

Re: [wsjt-devel] RC8 trouble

[<al...@al...>]

Hi, RC8 runs OK here on W11 Pro 24H2 but I did have to accept it as a 
valid app under W11 Smartscreen (part of MS Defender) and again under my 
AV which objected to unsigned software trying to access my PC sound device.

The exception code below is an Access Violation so it might be your AV 
objecting?

A web search indicates it could also be many other things so I'm afraid 
I can't help any further!

Alan G0TLK



On 08/01/2025 02:46, Andrew White via wsjt-devel wrote:
> After having no problems with any previous WSJT-X version, I 
> discovered that both WSJT-X v2.7.0-rc8 and 250106-rc8 cause an Access 
> Violation (0xc0000005) the first time the *Decode* button turns on.  I 
> am running Win10 PRO-64, and FT8/FT4 have always worked OK.  Here is 
> the error generated by 250106-rc8:
>
>
>
> My 241206-007 still works fine.  I downloaded and installed 241014-rc7 
> improved, and that version also runs OK.  Both of the -rc8 versions 
> fail the first time *Decode* turns on near the end of the receive 
> period, and the application terminates without triggering any error 
> message.  I must manually kill JT9.EXE before I can start WSJT-X again.
>
> Since I have not seen anyone else report this problem, it must be 
> something unique to my setup.  I am at a loss to know why only -rc8 
> versions fail here.  Hopefully, someone can suggest what I might try.
>
> 73 de Drew K9CW
>
>
> -- 
> **********************************************
> * K9CW Thomasboro, IL  EN50wf
> * email:k9...@ya...
> * DXCC: 363/340  CW: 351/339 (need P5!)
> *
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RC8 trouble

[Uwe, D. <dg...@gm...>]

Hi Andrew,

Please download and install the package again. You are the first one
getting such an access violation. If that doesn't help, try using a
fresh WSJT-X.ini file. Which virus scanner do you use?

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB




Am 08.01.2025 um 03:46 schrieb Andrew White via wsjt-devel:
> After having no problems with any previous WSJT-X version, I
> discovered that both WSJT-X v2.7.0-rc8 and 250106-rc8 cause an Access
> Violation (0xc0000005) the first time the *Decode* button turns on.  I
> am running Win10 PRO-64, and FT8/FT4 have always worked OK.  Here is
> the error generated by 250106-rc8:
>
>
>
> My 241206-007 still works fine.  I downloaded and installed 241014-rc7
> improved, and that version also runs OK.  Both of the -rc8 versions
> fail the first time *Decode* turns on near the end of the receive
> period, and the application terminates without triggering any error
> message.  I must manually kill JT9.EXE before I can start WSJT-X again.
>
> Since I have not seen anyone else report this problem, it must be
> something unique to my setup.  I am at a loss to know why only -rc8
> versions fail here.  Hopefully, someone can suggest what I might try.
>
> 73 de Drew K9CW
>
>
> --
> **********************************************
> * K9CW Thomasboro, IL  EN50wf
> * email:k9...@ya...
> * DXCC: 363/340  CW: 351/339 (need P5!)
> *
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RC8 trouble

[Steven F. <s.j...@ic...>]

Hi Drew,

I’m sorry to hear that you’re having trouble with the RC8 release. I can’t be of much help in debugging Windows crashes, but for those who can it would be useful to know if the symptoms persist unchanged when you run with a fresh WSJT-X.ini file. For example, you might try starting wsjtx from a command prompt like this:

wsjtx —rig-name=XXX

where XXX is a unique “rig name" that you have not used in the past. This will start wsjt-x with a fresh .ini file. (The “—rig-name” option is documented in the User Manual in item 2 of the Frequently Asked Questions section. See the Platform Dependencies section of the manual for the location of the Settings, Log, and Default save directories when wsjtx is started with the “—rig-name=XXX” command-line option.) Note that you’ll have to re-enter your rig and audio settings after starting this way.

If you find that wsjtx runs OK with a fresh WSJT-X.ini file, then please go ahead and send us the problematic WSJT-X.ini file.

Regards/73
Steve k9an

> On Jan 7, 2025, at 8:46 PM, Andrew White via wsjt-devel <wsj...@li...> wrote:
> 
> After having no problems with any previous WSJT-X version, I discovered that both WSJT-X v2.7.0-rc8 and 250106-rc8 cause an Access Violation (0xc0000005) the first time the Decode button turns on.  I am running Win10 PRO-64, and FT8/FT4 have always worked OK.  Here is the error generated by 250106-rc8:
> 

> 
> My 241206-007 still works fine.  I downloaded and installed 241014-rc7 improved, and that version also runs OK.  Both of the -rc8 versions fail the first time Decode turns on near the end of the receive period, and the application terminates without triggering any error message.  I must manually kill JT9.EXE before I can start WSJT-X again.
> 
> Since I have not seen anyone else report this problem, it must be something unique to my setup.  I am at a loss to know why only -rc8 versions fail here.  Hopefully, someone can suggest what I might try.
> 
> 73 de Drew K9CW
> 
> 
>  -- 
> **********************************************
> * K9CW Thomasboro, IL  EN50wf
> * email: k9...@ya... <mailto:k9...@ya...>
> * DXCC: 363/340  CW: 351/339 (need P5!)
> *
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] RC8 trouble

[Andrew W. <k9...@ya...>]

After having no problems with any previous WSJT-X version, I discovered 
that both WSJT-X v2.7.0-rc8 and 250106-rc8 cause an Access Violation 
(0xc0000005) the first time the *Decode* button turns on.  I am running 
Win10 PRO-64, and FT8/FT4 have always worked OK.  Here is the error 
generated by 250106-rc8:



My 241206-007 still works fine.  I downloaded and installed 241014-rc7 
improved, and that version also runs OK.  Both of the -rc8 versions fail 
the first time *Decode* turns on near the end of the receive period, and 
the application terminates without triggering any error message.  I must 
manually kill JT9.EXE before I can start WSJT-X again.

Since I have not seen anyone else report this problem, it must be 
something unique to my setup.  I am at a loss to know why only -rc8 
versions fail here.  Hopefully, someone can suggest what I might try.

73 de Drew K9CW


-- 
**********************************************
* K9CW Thomasboro, IL  EN50wf
* email:k9...@ya...
* DXCC: 363/340  CW: 351/339 (need P5!)
*

Re: [wsjt-devel] rc8 Hamlib update issues

[Black M. <mdb...@ya...>]

If you read the Help file and search for TLS you'll find you need this:
https://sourceforge.net/projects/wsjt-x-improved/files/Additional%20Files/OpenSSL/Win64OpenSSL_Light-1_1_1a.msi
Mike W9MDB



 

    On Monday, January 6, 2025 at 06:07:55 PM CST, Dan Coughlin via wsjt-devel <wsj...@li...> wrote:  
 
  I recently downloaded rc8, 64bit Windows version. After I got it up and running I made an attempt to update Hamlib and got the following error:Hamlib eventually updated, or in this case downgraded. It went from 2024-12-04 to 2024-08-02. I tried again, got the same preliminary error message, and nothing else was loaded. I exited the program and attempted to restore the backed up file, and it was gone._______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  

[wsjt-devel] RC8 Message Creator request for functionality

[Scott A. <aa5...@gm...>]

Hi Guys,

Playing around with message creator to see how it works and  noticed the
VHF tab does not support FT4 or Q65 modes and EME doesn't support JT65

Can FT4 and Q65  be added to the VHF tab and JT65 to the EME tab in the
next release?

Thanks for your consideration and 73,

Scott AA5AM

[wsjt-devel] rc8 Hamlib update issues

[Dan C. <hot...@ho...>]

I recently downloaded rc8, 64bit Windows version. After I got it up and running I made an attempt to update Hamlib and got the following error:
[cid:30cb341a-5c9d-4436-9363-414e05087c08]
Hamlib eventually updated, or in this case downgraded. It went from 2024-12-04 to 2024-08-02. I tried again, got the same preliminary error message, and nothing else was loaded. I exited the program and attempted to restore the backed up file, and it was gone.

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

[Marco C. <PY...@ou...>]

Il 06/01/25 10:33, Joe Taylor via wsjt-devel ha scritto:
> Dear WSJT-X Users,
>
> We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc8 is
> ready for download and use by beta testers. This revision introduces a
> new Message System primarily intended for contests. Otherwise, RC8 is
> mostly a bug-fix release of the well-functioning RC7.
>
> The WSJT-X Message System can be used to invite your QSO partner to QSY
> to another frequency or mode (e.g. during contests), or to send some
> general short messages. It consists of the Message Creator and the QSY
> Monitor. Received messages are displayed as popups. To understand how to
> use the Message System, be sure to read Section 8 of the updated WSJT-X
> User Guide for RC8.
>
> Additional details on program changes since RC7 can be found in the
> Release Notes:
> https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc8.txt
>
> Release Candidates are intended for beta testers. If you download and
> use WSJT-X 2.7.0-rc8, please provide relevant feedback on the new
> features and anything that does not seem to work properly for you. If
> your report involves something related to received signals, be sure to
> provide one or more saved *.wav files that illustrate the perceived
> problem. As a general matter, you should use the option "Save all" when
> testing.
>
> 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-rc8".
>
> For those who like to compile from source, a source-code tarball is
> available on the WSJT-X page.
>
> 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. Currently this caution applies to all SuperFox and SuperHound
> features. We will cease making public Release Candidates 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-rc8.html#SUPPORT
>
> We hope you will enjoy using WSJT-X 2.7.0-rc8, 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; John, G4KLA; and Charlie, DL3WDG.
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Thanks to all the people that works behind this software!

Happy new year and plenty of DX!

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

[wsjt-devel] Rig selection NIT

[k0vm <k0...@mc...>]

I use Flex radios...

For some time now, each time I install a new version of WSJT-x ( 2.7.0 
RC's or 2..7.1 improved ), by installing over an existing version, the 
RIG selection is reset to ADT-200A when Flex-radio 6xxx should have been 
retained.

Its a minor issue since it only occurs when a new version of WSJT is 
installed over top of an existing version.

AL, K0VM

Re: [wsjt-devel] feature request

[Laurie, V. <_vk...@vk...>]

On 07/01/2025 5:18 am, kk7er--- via wsjt-devel wrote:
> I like to leave my  receiver running when I'm away on bands where it is rare
> to decode a signal.
> But if I'm away for a few days, it is not clear what date the decode
> happened.
> Sure, I can look in ALL.TXT to find out.
> But it would be nice to have a separator line in the band activity window
> when the UTC day changes.
> Thanks for considering the idea.
>
> 73, Mike KK7ER

HamSpots shows you spotting from JTAlert. Since you are using JTAlert 
you could have its Decodes window open which provides both a date and 
time column.

de Laurie VK3AMA
(JTAlert author)

[wsjt-devel] feature request

[<kk...@xe...>]

I like to leave my  receiver running when I'm away on bands where it is rare
to decode a signal.
But if I'm away for a few days, it is not clear what date the decode
happened.
Sure, I can look in ALL.TXT to find out.
But it would be nice to have a separator line in the band activity window
when the UTC day changes.
Thanks for considering the idea.

73, Mike KK7ER

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

[Xavi C. <ea3...@gm...>]

Thank you all for your work.

It's been a long time since there were any translation updates, how can 
we do this?

Greetings and Happy New Year

-- 
Xavi Canyadell, EA3W
Telèfon +34670243468
http://www.ea3w.cat

El 6/1/2025 a les 14:33, Joe Taylor via wsjt-devel ha escrit:
> Dear WSJT-X Users,
>
> We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc8 is
> ready for download and use by beta testers. This revision introduces a
> new Message System primarily intended for contests. Otherwise, RC8 is
> mostly a bug-fix release of the well-functioning RC7.
>
> The WSJT-X Message System can be used to invite your QSO partner to QSY
> to another frequency or mode (e.g. during contests), or to send some
> general short messages. It consists of the Message Creator and the QSY
> Monitor. Received messages are displayed as popups. To understand how to
> use the Message System, be sure to read Section 8 of the updated WSJT-X
> User Guide for RC8.
>
> Additional details on program changes since RC7 can be found in the
> Release Notes:
> https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc8.txt
>
> Release Candidates are intended for beta testers. If you download and
> use WSJT-X 2.7.0-rc8, please provide relevant feedback on the new
> features and anything that does not seem to work properly for you. If
> your report involves something related to received signals, be sure to
> provide one or more saved *.wav files that illustrate the perceived
> problem. As a general matter, you should use the option "Save all" when
> testing. 


-- 
S'ha comprovat que aquest correu no contingui virus amb el programari d'antivirus d'Avast.
www.avast.com

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

[Joe T. <jo...@pr...>]

Dear WSJT-X Users,

We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc8 is
ready for download and use by beta testers. This revision introduces a
new Message System primarily intended for contests. Otherwise, RC8 is
mostly a bug-fix release of the well-functioning RC7.

The WSJT-X Message System can be used to invite your QSO partner to QSY
to another frequency or mode (e.g. during contests), or to send some
general short messages. It consists of the Message Creator and the QSY
Monitor. Received messages are displayed as popups. To understand how to
use the Message System, be sure to read Section 8 of the updated WSJT-X
User Guide for RC8.

Additional details on program changes since RC7 can be found in the
Release Notes:
https://wsjt.sourceforge.io/wsjtx-doc/Release_Notes_2.7.0-rc8.txt

Release Candidates are intended for beta testers. If you download and
use WSJT-X 2.7.0-rc8, please provide relevant feedback on the new
features and anything that does not seem to work properly for you. If
your report involves something related to received signals, be sure to
provide one or more saved *.wav files that illustrate the perceived
problem. As a general matter, you should use the option "Save all" when
testing.

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-rc8".

For those who like to compile from source, a source-code tarball is
available on the WSJT-X page.

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. Currently this caution applies to all SuperFox and SuperHound
features. We will cease making public Release Candidates 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-rc8.html#SUPPORT

We hope you will enjoy using WSJT-X 2.7.0-rc8, 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; John, G4KLA; and Charlie, DL3WDG.

[wsjt-devel] Font problem

[ATKINSON N. <nea...@sb...>]

Hi, I wanted a darker text and font for received signal display.  I then selected Terminal and bold 10.  The problem is that when double clicking on a potential contact, you must tap only on the lowest portion of the call. Anywhere else will result in your selecting a call that is one or two spots above the desired call.  Very confusing and took a while to sort out.  I cannot get a decent dark contrast on Courier font even bold activated.  Any clue to what is happening.  The bold face font for Courier was never a problem on rc-6.
Thanks, Noel, W9FR
Sent from my iPad

Re: [wsjt-devel] Echo mode not working right in RC7

[Joe T. <jo...@pr...>]

Hi Russ,

More details about "Echo Mode in WSJT-X 2.6.0" (and later versions) are 
found in this paper published in DUBUS:

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

	-- 73, Joe, K1JT

On 1/1/2025 2:17 PM, Charles Suckling via wsjt-devel wrote:
> Hi Russ
> 
> Echo mode now always transmits a 1500Hz tone.
> 
> With Doppler set to None, the echo is shifted at audio.  You see tone on 
> waterfall but not at 1500 unless your self Doppler is 0.
> 
> More here:
> 
> https://drive.google.com/file/d/1SWQUYuZqlvlYow2Kc-OapMRaOc5b-h_n/view?usp=sharing <https://drive.google.com/file/d/1SWQUYuZqlvlYow2Kc-OapMRaOc5b-h_n/view?usp=sharing>
> 
> 73
> 
> Charlie
> 
> On Wed, 1 Jan 2025 at 19:41, k2txb--- via wsjt-devel 
> <wsj...@li... 
> <mailto:wsj...@li...>> wrote:
> 
>     Hi all.  It seems that in echo mode, WSJT-X is no longer adjusting
>     the TX
>     tone to compensate for doppler shift.
>     To test this, I set up on 2 meter EME, with Doppler Tracking enabled but
>     track mode set to none.
>     While running echo mode I also observe the frequency of the returned
>     echo on
>     the WSJT-X waterfall.
>     This morning doppler shift was at +120 Hz, and the returned echo was
>     displayed at 1620 Hz.
>     If TX frequency was being shifted, the echo should appear at 1500 Hz.
> 
>     I am quite sure that this worked properly in earlier versions.
> 
>     73, Russ - K2TXB
> 
>     PS: After writing the above I realized that I had ignored a much easier
>     test.  I turned on another receiver and monotored the tone from the
>     EME rig.
>     It always sends at 1500 Hz in echo mode, no matter if Doppler
>     Tracking is
>     enabled or not..
> 
> 
> 
> 
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     <mailto:wsj...@li...>
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>     <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
> 

Re: [wsjt-devel] Echo mode not working right in RC7

[<k2...@co...>]

Charlie and Joe,
 
Wait, In re-reading the document I see that it says that audio spectra,  not TX audio, is shifted.  And so that explains it.  But I clearly remember seeing the echo at 1500 Hz in older versions.
So I guess the method was changed at some time. 
 
73, Russ – K2TXB
 
 
From: Charles Suckling <g3...@gm...> 
Sent: Wednesday, January 1, 2025 2:17 PM
To: k2...@co...; WSJT software development <wsj...@li...>
Subject: Re: [wsjt-devel] Echo mode not working right in RC7
 
Hi Russ
 
Echo mode now always transmits a 1500Hz tone.
 
With Doppler set to None, the echo is shifted at audio.  You see tone on waterfall but not at 1500 unless your self Doppler is 0.
 
More here:
 
https://drive.google.com/file/d/1SWQUYuZqlvlYow2Kc-OapMRaOc5b-h_n/view?usp=sharing
 
73
 
Charlie
 
On Wed, 1 Jan 2025 at 19:41, k2txb--- via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote:
Hi all.  It seems that in echo mode, WSJT-X is no longer adjusting the TX
tone to compensate for doppler shift.
To test this, I set up on 2 meter EME, with Doppler Tracking enabled but
track mode set to none.
While running echo mode I also observe the frequency of the returned echo on
the WSJT-X waterfall.
This morning doppler shift was at +120 Hz, and the returned echo was
displayed at 1620 Hz.
If TX frequency was being shifted, the echo should appear at 1500 Hz.

I am quite sure that this worked properly in earlier versions.

73, Russ - K2TXB

PS: After writing the above I realized that I had ignored a much easier
test.  I turned on another receiver and monotored the tone from the EME rig.
It always sends at 1500 Hz in echo mode, no matter if Doppler Tracking is
enabled or not..




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

Re: [wsjt-devel] Echo mode not working right in RC7

[<k2...@co...>]

Hi Charlie.  From the WSJT-X users guide:
 
“2. If Doppler shift is less than 750 Hz you may set Doppler tracking to None and not use any CAT control for frequency settings. In this case, all necessary Doppler tracking will be done by shifting the audio spectra.”
 
I am positive that when this feature was first introduced it worked that way.  Something has been lost since then..
 
73, Russ – K2TXB
 
 
From: Charles Suckling <g3...@gm...> 
Sent: Wednesday, January 1, 2025 2:17 PM
To: k2...@co...; WSJT software development <wsj...@li...>
Subject: Re: [wsjt-devel] Echo mode not working right in RC7
 
Hi Russ
 
Echo mode now always transmits a 1500Hz tone.
 
With Doppler set to None, the echo is shifted at audio.  You see tone on waterfall but not at 1500 unless your self Doppler is 0.
 
More here:
 
https://drive.google.com/file/d/1SWQUYuZqlvlYow2Kc-OapMRaOc5b-h_n/view?usp=sharing
 
73
 
Charlie
 
On Wed, 1 Jan 2025 at 19:41, k2txb--- via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote:
Hi all.  It seems that in echo mode, WSJT-X is no longer adjusting the TX
tone to compensate for doppler shift.
To test this, I set up on 2 meter EME, with Doppler Tracking enabled but
track mode set to none.
While running echo mode I also observe the frequency of the returned echo on
the WSJT-X waterfall.
This morning doppler shift was at +120 Hz, and the returned echo was
displayed at 1620 Hz.
If TX frequency was being shifted, the echo should appear at 1500 Hz.

I am quite sure that this worked properly in earlier versions.

73, Russ - K2TXB

PS: After writing the above I realized that I had ignored a much easier
test.  I turned on another receiver and monotored the tone from the EME rig.
It always sends at 1500 Hz in echo mode, no matter if Doppler Tracking is
enabled or not..




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

Re: [wsjt-devel] Echo mode not working right in RC7

[Charles S. <g3...@gm...>]

Hi Russ

Echo mode now always transmits a 1500Hz tone.

With Doppler set to None, the echo is shifted at audio.  You see tone on
waterfall but not at 1500 unless your self Doppler is 0.

More here:

https://drive.google.com/file/d/1SWQUYuZqlvlYow2Kc-OapMRaOc5b-h_n/view?usp=sharing

73

Charlie

On Wed, 1 Jan 2025 at 19:41, k2txb--- via wsjt-devel <
wsj...@li...> wrote:

> Hi all.  It seems that in echo mode, WSJT-X is no longer adjusting the TX
> tone to compensate for doppler shift.
> To test this, I set up on 2 meter EME, with Doppler Tracking enabled but
> track mode set to none.
> While running echo mode I also observe the frequency of the returned echo
> on
> the WSJT-X waterfall.
> This morning doppler shift was at +120 Hz, and the returned echo was
> displayed at 1620 Hz.
> If TX frequency was being shifted, the echo should appear at 1500 Hz.
>
> I am quite sure that this worked properly in earlier versions.
>
> 73, Russ - K2TXB
>
> PS: After writing the above I realized that I had ignored a much easier
> test.  I turned on another receiver and monotored the tone from the EME
> rig.
> It always sends at 1500 Hz in echo mode, no matter if Doppler Tracking is
> enabled or not..
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

[wsjt-devel] Echo mode not working right in RC7

[<k2...@co...>]

Hi all.  It seems that in echo mode, WSJT-X is no longer adjusting the TX
tone to compensate for doppler shift.
To test this, I set up on 2 meter EME, with Doppler Tracking enabled but
track mode set to none.
While running echo mode I also observe the frequency of the returned echo on
the WSJT-X waterfall.
This morning doppler shift was at +120 Hz, and the returned echo was
displayed at 1620 Hz.
If TX frequency was being shifted, the echo should appear at 1500 Hz.

I am quite sure that this worked properly in earlier versions.

73, Russ - K2TXB

PS: After writing the above I realized that I had ignored a much easier
test.  I turned on another receiver and monotored the tone from the EME rig.
It always sends at 1500 Hz in echo mode, no matter if Doppler Tracking is
enabled or not..

Re: [wsjt-devel] Rig control fails if PST Rotator is running

[Tom M. <to...@m0...>]

Hi Charles

I think that is possibly better directed at the PST Rotator support
channels- why is PST Rotator locking a serial port you don’t believe it is
configured to use?

Best wishes
Tom

On Sat, 28 Dec 2024 at 08:22, Charles Suckling via wsjt-devel <
wsj...@li...> wrote:

> Hi All
>
> I've recently started to use PST rotator on the same (Win7) PC that I am
> using for WSJT-X.
>
> If I start PST Rotator first, then a rig error occurs with this message:
>
>
> ..................................................................................................................................
>
> Hamlib error: rig_token_lookup called for client
>
> rig_confparam_lookup called for client
>
> rig_set_conf called
>
> rig_confparam_lookup called for client
>
> rig_set_conf: client='WSJTX'
>
> frontend_set_conf: Client claims to be WSJTX
>
> rig.c(944):rig_open entered
>
> rig_settings_get_path: path=c:\Users\User/.config/hamlib_settings
>
> rig_open: cwd=C:\WSJT\wsjtx271\bin
>
> rig_open: C:\WSJT\wsjtx271\bin/hamlib_settings No such file or directory
>
> rig_open: async_data_enable=0, async_data_supported=0
>
> serial_open: COM9
>
> serial_open(230): open failed#1 No such file or directory
>
> serial_open: Unable to open COM9 - No such file or directory
>
> port_open: serial_open(COM9) status=-6, err=No such file or directory
>
> rig_open: rs->comm_state==0?=0
>
> rig.c(1176):rig_open returning2(-6) IO error
>
>
> IO error
>
> IO error
>
> while opening connection to rig
>
>
> Timestamp: 2024-12-28T08:10:14.830Z
>
>
>
> .....................................................................................................................
>
>
> **If I start WSJT-X first, all is OK and I can then start PST Rotator and
> all appears fine**.
>
>
> PST Rotator uses a different COM port (not a virtual one) to connect to an
> Arduino which then handles antenna tracking.
>
>
> COM9 is one end of a com0com virtual com port pair, used to connect WSJT-X
> to SDR Console for CAT control.
>
>
> 73
>
>
> Charlie DL3WDG
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>