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

[Dennis Younker NE6I via wsjt-devel]

For what it’s worth, I too printed that station a couple of times (and saw 
many, many calling him). I could see that it was P4/WE9V in reality. I’m not 
clear on what the ask is, Reino. I decoded many, many messages (normal QSOs) in 
that time frame, including others calling P97USI/P.

 

240226_19593028.074 Rx FT8 13  0.3  703 CT1GYD RR73; M0JUE  
-06

 

--Dennis NE6I

 

From: Reino Talarmo via wsjt-devel  
Sent: Tuesday, February 27, 2024 3:34 AM
To: 'WSJT software development' 
Cc: Reino Talarmo 
Subject: Re: [wsjt-devel] Another fun hash collision P97USI

 

Jon,

It would be interesting to know whether you have decoded a message containing 
P97USI/P within 231900 and 232530 and what that message was?

 

73, Reino OH3mA

 

From: Jon Anhold via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, February 27, 2024 2:50 AM
To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Jon Anhold mailto:j...@anhold.com> >
Subject: [wsjt-devel] Another fun hash collision P97USI

 

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 :)

 

73 de KM8V Jon

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

Re: [wsjt-devel] Decoding Anomaly

[Dennis Younker NE6I via wsjt-devel]

Hi Reino,

 

Thanks for the explanation. That makes sense. Appreciate the information.

 

--Dennis NE6I

 

From: Reino Talarmo via wsjt-devel  
Sent: Monday, January 29, 2024 10:24 PM
To: 'WSJT software development' 
Cc: Reino Talarmo 
Subject: Re: [wsjt-devel] Decoding Anomaly

 

Hi Dennis,

There may be something to improve in the hash table(s) management as in your 
example the first message CQ PJ5/SP9FIH was sent in full (it is a non-standard 
call, but that should not matter). Why the 10 bits hash was not updated into 
the hash table, but there is DP1POL instead for the 10 bits hash and at the 
same time for PJ5/SP9FIH the longer 22 bits hash it is correct. Of course 
PJ5/SP9FIN and DP1POL don’t collide at the 12 and 22 bits long hashes. 

Well, a simple possibility is that the 10 bits hash table is in alphabetic 
order and the hash values are not updated, but there are two callsigns for the 
same hash and DP1POL is the first found. Sri, I have no fact about the hash 
tables, but in my logic the CQ PJ/SP9FIH message should have ‘updated’ a 
linkage of all hash 10, 12 and 22 values for that callsign and ‘removed’ 
linkage to DP1POL at least for the 10 bits hash for the next messages.

(By the way there are 10, 12 and 22 bits hashes also for SP9FIH in the case 
that were used and those don’t collide with DP1POL.)

 

73, Reino OH3mA

 

From: Dennis Younker NE6I via wsjt-devel 
[mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, January 30, 2024 1:59 AM
To: 'WSJT software development' mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Dennis Younker NE6I mailto:n...@cox.net> >
Subject: Re: [wsjt-devel] Decoding Anomaly

 

Thanks, what would be special about PJ5/SP9FIH in this case? I have not seen 
this with others using “portable designators.”

 

--Dennis NE6I

 

From: Jim Reisert AD1C via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Monday, January 29, 2024 3:09 PM
To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Jim Reisert AD1C mailto:jjreis...@alum.mit.edu> >
Subject: Re: [wsjt-devel] Decoding Anomaly

 

It's a callsign hash collision.  DP1POL has not been operating on those 
frequencies.

 

 

On Mon, Jan 29, 2024 at 4:07 PM V. Scott Moore via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

I saw similar decodes.  I attributed it to two stations on the same frequency.  
The PJ5 was very strong here and when multi-streaming his/her signal came down 

and revealed the less powerful (but still +10 here) Antarctic station.

 

scott

W1SSN

 

On Jan 29, 2024, at 17:47, Carl Moreschi via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

 

I just saw exactly the same things on 17 meters.

Carl Moreschi N4PY
127 River Moss Way
Hertford, NC 27944
www.n4py.com <http://www.n4py.com> 

On 1/29/2024 5:31 PM, Dennis Younker NE6I via wsjt-devel wrote:

Wondering if anyone else is seeing this issue. PJ5/SP9FIH is operating F/H. 
When he is transmitting one stream, his call is displayed correctly in the Rx 
Frequency window. When he transmits two streams, the call sign DP1POL is 
displayed instead.  See below for an example.
--Dennis NE6I
222830  -2 -0.4  492 ~  CQ PJ5/SP9FIH   Saba & St. Eustatius
222900  -4 -0.4  492 ~  N5HD  +02
222930   0 -0.4  492 ~  N5HD RR73; EA7QL  -04
223000  -4 -0.4  492 ~  EA7QL  -05
223030  -2 -0.4  492 ~  EA7QL RR73; LU7EML  -12
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



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

 

“Got time to breath, got time for music” - Brisco Darling

 

 

 

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



-- 

Jim Reisert AD1C, mailto:jjreis...@alum.mit.edu> >, 
https://ad1c.us

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

Re: [wsjt-devel] Decoding Anomaly

[Dennis Younker NE6I via wsjt-devel]

Thanks, what would be special about PJ5/SP9FIH in this case? I have not seen 
this with others using “portable designators.”

 

--Dennis NE6I

 

From: Jim Reisert AD1C via wsjt-devel  
Sent: Monday, January 29, 2024 3:09 PM
To: WSJT software development 
Cc: Jim Reisert AD1C 
Subject: Re: [wsjt-devel] Decoding Anomaly

 

It's a callsign hash collision.  DP1POL has not been operating on those 
frequencies.

 

 

On Mon, Jan 29, 2024 at 4:07 PM V. Scott Moore via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

I saw similar decodes.  I attributed it to two stations on the same frequency.  
The PJ5 was very strong here and when multi-streaming his/her signal came down 

and revealed the less powerful (but still +10 here) Antarctic station.

 

scott

W1SSN





On Jan 29, 2024, at 17:47, Carl Moreschi via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

 

I just saw exactly the same things on 17 meters.

Carl Moreschi N4PY
127 River Moss Way
Hertford, NC 27944
www.n4py.com <http://www.n4py.com> 

On 1/29/2024 5:31 PM, Dennis Younker NE6I via wsjt-devel wrote:



Wondering if anyone else is seeing this issue. PJ5/SP9FIH is operating F/H. 
When he is transmitting one stream, his call is displayed correctly in the Rx 
Frequency window. When he transmits two streams, the call sign DP1POL is 
displayed instead.  See below for an example.
--Dennis NE6I
222830  -2 -0.4  492 ~  CQ PJ5/SP9FIH   Saba & St. Eustatius
222900  -4 -0.4  492 ~  N5HD  +02
222930   0 -0.4  492 ~  N5HD RR73; EA7QL  -04
223000  -4 -0.4  492 ~  EA7QL  -05
223030  -2 -0.4  492 ~  EA7QL RR73; LU7EML  -12
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



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

 

“Got time to breath, got time for music” - Brisco Darling

 

 

 

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



-- 

Jim Reisert AD1C, mailto:jjreis...@alum.mit.edu> >, 
https://ad1c.us

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

[wsjt-devel] Decoding Anomaly

[Dennis Younker NE6I via wsjt-devel]

Wondering if anyone else is seeing this issue. PJ5/SP9FIH is operating F/H. 
When he is transmitting one stream, his call is displayed correctly in the Rx 
Frequency window. When he transmits two streams, the call sign DP1POL is 
displayed instead.  See below for an example.

--Dennis NE6I

222830  -2 -0.4  492 ~  CQ PJ5/SP9FIH   Saba & St. Eustatius
222900  -4 -0.4  492 ~  N5HD  +02
222930   0 -0.4  492 ~  N5HD RR73; EA7QL  -04
223000  -4 -0.4  492 ~  EA7QL  -05
223030  -2 -0.4  492 ~  EA7QL RR73; LU7EML  -12



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

Re: [wsjt-devel] Hamlib 4.5.2 test #hamlib

[Dennis Younker NE6I via wsjt-devel]

Repeating in plain text without html formatting (sorry).

Seems to be working fine here: Yaesu FTDX-101MP running WSJT-X v2.6.0-rc5.

--Dennis NE6I

From: Black Michael via wsjt-devel  
Sent: Tuesday, December 20, 2022 6:56 AM
To: WSJTX Group ; WSJT Software Development 

Cc: Black Michael 
Subject: [wsjt-devel] Hamlib 4.5.2 test #hamlib

Hamlib 4.5.2 is due to be released this week.
All known bugs have been fixed.

Please test and ensure everything is workingor report any bad behavior.  
This will likely be the hamlib in the WSJT-X release.

Here is a zip file for the 64-bit binaries.
https://www.dropbox.com/s/q2cf6xb50pgsr61/hamlib-4.5.2-20221220.zip?dl=0


And here is the 64-bit dll which can be placed in \WSJT\WSJT-X\bin
https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0

Mike W9MDB





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

Re: [wsjt-devel] Hamlib 4.5.2 test #hamlib

[Dennis Younker NE6I via wsjt-devel]

Seems to be working fine here: Yaesu FTDX-101MP running WSJT-X v2.6.0-rc5.

 

--Dennis NE6I

 

From: Black Michael via wsjt-devel  
Sent: Tuesday, December 20, 2022 6:56 AM
To: WSJTX Group ; WSJT Software Development 

Cc: Black Michael 
Subject: [wsjt-devel] Hamlib 4.5.2 test #hamlib

 

Hamlib 4.5.2 is due to be released this week.

All known bugs have been fixed.

 

Please test and ensure everything is workingor report any bad behavior.  
This will likely be the hamlib in the WSJT-X release.

 

Here is a zip file for the 64-bit binaries.

https://www.dropbox.com/s/q2cf6xb50pgsr61/hamlib-4.5.2-20221220.zip?dl=0

 

 

And here is the 64-bit dll which can be placed in \WSJT\WSJT-X\bin

https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0

 

Mike W9MDB

 

 

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

Re: [wsjt-devel] v2.6.0-rc5 F/H Issue

[Dennis Younker NE6I via wsjt-devel]

Thanks, Reino,

I understand now. Still not sure what happened but I'll report in if it happens 
again. Re-examining the all.txt file, I stand corrected. The fox did not send 
R-report to me (e.g. R-13). He only sent the report (without an R). Sorry for 
the confusion. 

--Dennis NE6I

-Original Message-
From: Reino Talarmo via wsjt-devel  
Sent: Thursday, December 8, 2022 8:23 AM
To: 'WSJT software development' 
Cc: Reino Talarmo 
Subject: Re: [wsjt-devel] v2.6.0-rc5 F/H Issue

Dennis,

Yes, that's correct. Only messages hound receives especially Tx3 i.e. "OH3MA 
ZL9FOX -20" (that is just a normal message) initiates frequency moves. 

If you mean by R-report e.g. R-15, then that station was *not* a fox at all. 
The only messages fox can send are Tx6 i.e. CQ, Tx3 i.e. a report -13 and TX5 
either RR73 or combined RR73 plus a report to another station. You may study 
https://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf for further 
details.

There is a derivate program that uses the combined "RR73; NE6I  -2" 
type messages and multiple carriers. That program can even be used on standard 
frequencies and on both timeslots although not recommended. Hound protocol has 
a lot of problems with it. Stations using it should be worked using normal FT8 
mode.

If that is the case and the R-report means what I said above, then on the 
reception of an R-report e.g. R-5 you should have sent RR73 or RRR, hi.

73, Reino OH3mA

- Original message -
Thanks, Reino,

Are the moves by the hound all initiated at the hound end based on what it 
receives from the fox? In other words, the fox does not "tell" the hound to 
move below 1000 Hz, correct? 

All.txt is showing the fox responding with R-report for a couple of sequences 
but does not show me responding with a report for some reason, though I 
definitely did. This happened on two attempts to work him. Very strange. On the 
third attempt to work him, it does show the proper exchange, namely fox sending 
R-report, me sending R-report and then the fox sending RR73.

--Dennis NE6I

-Original Message-
From: Reino Talarmo via wsjt-devel  
Sent: Wednesday, December 7, 2022 9:26 PM
To: 'WSJT software development' 
Cc: Reino Talarmo 
Subject: Re: [wsjt-devel] v2.6.0-rc5 F/H Issue

>The third time this happened, the fox did respond to me with RR73 but I wonder 
>what happened there? It still didn’t move me below 1,000 so I moved myself 
>down. At that point, the fox moved me to where they wanted me (681). 

Hi Dennis,

I don't know what actually happened, but the frequency movements are controlled 
at the hound station based on the received message sequence. Fox has no 
capability to move hounds as there is no frequency control in any of the 
message fox is sending.
Hound should move to fox frequency for sending the R+rpt after receiving report 
from fox. If the hound needs to repeat R+rpt, then it would by its own move 
either 300 Hz up or down. So the first movement is initiated by reception of 
the report from fox. 

By the way the frequency movements as such are not mandatory for the F/H QSO as 
such. They only provide a higher probability for less QRM. Well there are still 
stations that call fox on the fox frequency and cause the QRM! In addition Fox 
will not answer to those stations by design!

A careful study of the ALL.txt record may help to understand what happened.

73, Reino OH3mA







___
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] v2.6.0-rc5 F/H Issue

[Dennis Younker NE6I via wsjt-devel]

Thanks, Reino,

Are the moves by the hound all initiated at the hound end based on what it 
receives from the fox? In other words, the fox does not "tell" the hound to 
move below 1000 Hz, correct? 

All.txt is showing the fox responding with R-report for a couple of sequences 
but does not show me responding with a report for some reason, though I 
definitely did. This happened on two attempts to work him. Very strange. On the 
third attempt to work him, it does show the proper exchange, namely fox sending 
R-report, me sending R-report and then the fox sending RR73.

--Dennis NE6I

-Original Message-
From: Reino Talarmo via wsjt-devel  
Sent: Wednesday, December 7, 2022 9:26 PM
To: 'WSJT software development' 
Cc: Reino Talarmo 
Subject: Re: [wsjt-devel] v2.6.0-rc5 F/H Issue

>The third time this happened, the fox did respond to me with RR73 but I wonder 
>what happened there? It still didn’t move me below 1,000 so I moved myself 
>down. At that point, the fox moved me to where they wanted me (681). 

Hi Dennis,

I don't know what actually happened, but the frequency movements are controlled 
at the hound station based on the received message sequence. Fox has no 
capability to move hounds as there is no frequency control in any of the 
message fox is sending.
Hound should move to fox frequency for sending the R+rpt after receiving report 
from fox. If the hound needs to repeat R+rpt, then it would by its own move 
either 300 Hz up or down. So the first movement is initiated by reception of 
the report from fox. 

By the way the frequency movements as such are not mandatory for the F/H QSO as 
such. They only provide a higher probability for less QRM. Well there are still 
stations that call fox on the fox frequency and cause the QRM! In addition Fox 
will not answer to those stations by design!

A careful study of the ALL.txt record may help to understand what happened.

73, Reino OH3mA







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



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

[wsjt-devel] v2.6.0-rc5 F/H Issue

[Dennis Younker NE6I via wsjt-devel]

Experienced something out of the ordinary tonight chasing 3D2AG/P on 15m F/H. 
When they called me with a report, WSJT-X did not acknowledge with R-(report) 
and move down in freq despite me being in hound mode. This happened three times 
in a row. Instead, each time, I had to manually change to Tx3, but that didn’t 
actually move me below 1000 Hz offset. I manually moved myself on the next 
sequence but the fox had moved on to others.

 

The third time this happened, the fox did respond to me with RR73 but I wonder 
what happened there? It still didn’t move me below 1,000 so I moved myself 
down. At that point, the fox moved me to where they wanted me (681). I’m not 
sure that I’ve tried F/H on rc5 before tonight. Very strange. 

 

--Dennis NE6I

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

Re: [wsjt-devel] Sound Card Issue

[Dennis Younker NE6I via wsjt-devel]

To me, it sounds like you have the wrong input selected on the audio tab in 
WSJT-X. Make a note of what it is set to now and then try the other options in 
that drop down field.

 

--Dennis NE6I

 

From: crohtun--- via wsjt-devel  
Sent: Sunday, September 18, 2022 8:26 AM
To: WSJT software development 
Cc: croh...@aol.com
Subject: Re: [wsjt-devel] Sound Card Issue

 

Tried 2.6.0-rc4 to see if it would fix a problem I have with 2.5.4 on a new 
Windows 11 laptop. It didn’t. The problem is that WSJT-x is not processing 
received audio signals from the IC 7300 on the new laptop. The waterfall shows 
only ambient noise and there are no decodes. CAT anf PTT are fine and WSJT-x 
gets the W11 laptop to send audio to the 7300 and the radio transmits. But no 
audio is processed on the receive side. Yet the Windows sound settings show the 
volume on the codec going up and down with what I hear in the headphones 
connected to the 7300. So the incoming audio is with Windows but not WSJT-x.

 

Ray KN2K




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

Re: [wsjt-devel] RC4 Minor Nit

[Dennis Younker NE6I via wsjt-devel]

Well, sorry about that. It would help if I download and install rc4 rather than 
click on the wrong download link! Fixed now. Thanks!

 

--Dennis NE6I

 

From: Sam W2JDB via wsjt-devel  
Sent: Thursday, September 8, 2022 4:42 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB 
Subject: Re: [wsjt-devel] RC4 Minor Nit

 

Hi Dennis, 

 

Check the path of your program. You are starting the wrong program.  

 

73,

 

Sam W2JDB

 

 

-Original Message-
From: Dennis Younker NE6I via wsjt-devel 
To: 'WSJT software development' 
Cc: Dennis Younker NE6I 
Sent: Wed, Sep 7, 2022 8:19 pm
Subject: [wsjt-devel] RC4 Minor Nit

I notice that RC4 displays itself as 2.5.4 instead of 2.6.0-rc4. Obviously this 
does not affect performance but thought I would point it out. 

 



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

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

[wsjt-devel] RC4 Minor Nit

[Dennis Younker NE6I via wsjt-devel]

I notice that RC4 displays itself as 2.5.4 instead of 2.6.0-rc4. Obviously
this does not affect performance but thought I would point it out. 

 



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

Re: [wsjt-devel] RC2 syslog file

[Dennis Younker NE6I via wsjt-devel]

FYI, I put my brand new PC online this morning and am still getting the dropped 
audio source samples message. I don’t know that I’m experiencing any problems 
because of that but…  The new PC is an AMD Ryzen 7 5700G CPU and 32 GB of RAM, 
so it’s pretty healthy. 

 

--Dennis NE6I

 

[SYSLOG][2022-08-04 17:24:03.927396][00:00:00.000508][info] WSJT-X   v2.6.0-rc2 
994e3f  by K1JT et al. - Program startup

[SYSLOG][2022-08-04 17:24:03.943023][00:00:00.003885][info] locale: language: 
English script: Latin country: United States ui-languages: en-US

[SYSLOG][2022-08-04 17:24:03.943023][00:00:00.004002][info] Loaded Qt 
translations for current locale from resources

[SYSLOG][2022-08-04 17:24:03.943023][00:00:00.004026][info] Loaded WSJT-X base 
translation file from :/Translations based on language en

[SYSLOG][2022-08-04 17:24:03.943023][00:00:00.004043][info] Loaded WSJT-X 
translations for current locale from resources

[SYSLOG][2022-08-04 17:24:03.974275][00:00:00.046173][info] shmem size: 48275456

[RIGCTRL][2022-08-04 17:24:03.990906][00:00:00.059208][info] Hamlib version: 
Hamlib 4.5~git Sat Jul 16 15:53:03 2022 + SHA=cc7c59

[SYSLOG][2022-08-04 17:24:29.380455][00:00:25.435788][warning] Detected dropped 
audio source samples: 1056 (0.022 S)

[SYSLOG][2022-08-04 17:29:29.362707][00:05:25.385719][warning] Detected dropped 
audio source samples: -528 (-0.011 S)

[SYSLOG][2022-08-04 17:35:59.380782][00:11:55.361681][warning] Detected dropped 
audio source samples: 624 (0.013 S)

[SYSLOG][2022-08-04 17:37:59.400386][00:13:55.367659][warning] Detected dropped 
audio source samples: 624 (0.013 S)

[SYSLOG][2022-08-04 17:41:59.390903][00:17:55.332277][warning] Detected dropped 
audio source samples: 624 (0.013 S)

[SYSLOG][2022-08-04 17:45:29.385729][00:21:25.304079][warning] Detected dropped 
audio source samples: 672 (0.014 S)

[SYSLOG][2022-08-04 17:57:14.357259][00:33:10.185804][warning] Detected dropped 
audio source samples: -480 (-0.01 S)

[SYSLOG][2022-08-04 18:00:59.387195][00:36:55.191314][warning] Detected dropped 
audio source samples: 672 (0.014 S)

[SYSLOG][2022-08-04 18:07:29.382516][00:43:25.145007][warning] Detected dropped 
audio source samples: -480 (-0.01 S)

[SYSLOG][2022-08-04 18:31:29.372498][01:07:24.973350][warning] Detected dropped 
audio source samples: -528 (-0.011 S)

[SYSLOG][2022-08-04 18:43:29.383276][01:19:24.907516][warning] Detected dropped 
audio source samples: -528 (-0.011 S)

[SYSLOG][2022-08-04 18:46:21.311977][01:22:16.818273][warning] qt.network.ssl: 
QSslSocket::connectToHostEncrypted: TLS initialization failed

 

From: Dennis Younker NE6I via wsjt-devel  
Sent: Saturday, July 23, 2022 7:57 AM
To: 'WSJT software development' 
Cc: Dennis Younker NE6I 
Subject: Re: [wsjt-devel] RC2 syslog file

 

I tried changing the priority of WSJT-X this morning but do not see any 
difference. The capture below is using Priority set to Realtime. I also tried 
Above Normal and High. Note that these logged drop outs are occurring at the 
end of sequences though not every end-of-sequence produces a dropped audio 
entry.

 



 

--Dennis NE6I

 

-Original Message-
From: Black Michael via wsjt-devel  
Sent: Friday, July 22, 2022 8:44 PM
To: Dennis Younker NE6I via wsjt-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] RC2 syslog file

 

That's a pretty consistent bunch of dropped audio samples.

 

As I asked another user have you tried raising the priority of WSJT-X to see if 
making it real-time improves things?

 

Mike W9MDB

 

 

 

 

 

 

 

 

On Friday, July 22, 2022 at 07:17:20 PM CDT, Dennis Younker NE6I via wsjt-devel 
< <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net> 
wrote: 

 

 

 

 

 

Here a few lines from mine. Win10 and running v2.6.0-rc2. Are you looking for 
something in particular? I seem to get these dropped audio source alerts quite 
a bit!

 

[SYSLOG][2022-07-22 03:26:29.383606][03:15:14.093551][warning] Detected dropped 
audio source samples: -624 (-0.013 S)

[SYSLOG][2022-07-22 03:27:14.400410][03:15:59.105372][warning] Detected dropped 
audio source samples: 672 (0.014 S)

[SYSLOG][2022-07-22 03:27:29.386450][03:16:14.090066][warning] Detected dropped 
audio source samples: -672 (-0.014 S)

[SYSLOG][2022-07-22 03:28:44.382611][03:17:29.078681][warning] Detected dropped 
audio source samples: -672 (-0.014 S)

[SYSLOG][2022-07-22 03:29:14.372757][03:17:59.065692][warning] Detected dropped 
audio source samples: -576 (-0.012 S)

[SYSLOG][2022-07-22 03:32:14.370149][03:20:59.037622][warning] Detected dropped 
audio source samples: -720 (-0.015 S)

[SYSLOG][2022-07-22 03:35:40.610055][03:24:25.255064][info] Log Finish

[SYSLOG][2022-07-23 00:05:48.112279][00:00:00.004030][info] Log Start

[SYSLOG][2022-07-23 00:05:48.113466][00:00:00.004078][info] WSJT-X  v2.6.0-rc2 
994e3f  by K1JT et al. - Program startup

[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024524][info] locale: language: 
English s

Re: [wsjt-devel] Feature Request

[Dennis Younker NE6I via wsjt-devel]

Jim,

That feature is in the new release candidate and works well..

—Dennis NE6I


> On Jul 28, 2022, at 4:40 PM, Jim Brown via wsjt-devel 
>  wrote:
> 
> Please provide an option to start a new ALL.TXT for each calendar month, 
> keeping each month's file and naming it by the month. Without that option, 
> the file grows so large that it cannot be opened by any software on my 
> computer.
> 
> 73, Jim K9YC
> 
> 
> ___
> 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] RC2 syslog file

[Dennis Younker NE6I via wsjt-devel]

I tried changing the priority of WSJT-X this morning but do not see any 
difference. The capture below is using Priority set to Realtime. I also tried 
Above Normal and High. Note that these logged drop outs are occurring at the 
end of sequences though not every end-of-sequence produces a dropped audio 
entry.

 



 

--Dennis NE6I

 

-Original Message-
From: Black Michael via wsjt-devel  
Sent: Friday, July 22, 2022 8:44 PM
To: Dennis Younker NE6I via wsjt-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] RC2 syslog file

 

That's a pretty consistent bunch of dropped audio samples.

 

As I asked another user have you tried raising the priority of WSJT-X to see if 
making it real-time improves things?

 

Mike W9MDB

 

 

 

 

 

 

 

 

On Friday, July 22, 2022 at 07:17:20 PM CDT, Dennis Younker NE6I via wsjt-devel 
< <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net> 
wrote: 

 

 

 

 

 

Here a few lines from mine. Win10 and running v2.6.0-rc2. Are you looking for 
something in particular? I seem to get these dropped audio source alerts quite 
a bit!

 

[SYSLOG][2022-07-22 03:26:29.383606][03:15:14.093551][warning] Detected dropped 
audio source samples: -624 (-0.013 S)

[SYSLOG][2022-07-22 03:27:14.400410][03:15:59.105372][warning] Detected dropped 
audio source samples: 672 (0.014 S)

[SYSLOG][2022-07-22 03:27:29.386450][03:16:14.090066][warning] Detected dropped 
audio source samples: -672 (-0.014 S)

[SYSLOG][2022-07-22 03:28:44.382611][03:17:29.078681][warning] Detected dropped 
audio source samples: -672 (-0.014 S)

[SYSLOG][2022-07-22 03:29:14.372757][03:17:59.065692][warning] Detected dropped 
audio source samples: -576 (-0.012 S)

[SYSLOG][2022-07-22 03:32:14.370149][03:20:59.037622][warning] Detected dropped 
audio source samples: -720 (-0.015 S)

[SYSLOG][2022-07-22 03:35:40.610055][03:24:25.255064][info] Log Finish

[SYSLOG][2022-07-23 00:05:48.112279][00:00:00.004030][info] Log Start

[SYSLOG][2022-07-23 00:05:48.113466][00:00:00.004078][info] WSJT-X  v2.6.0-rc2 
994e3f  by K1JT et al. - Program startup

[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024524][info] locale: language: 
English script: Latin country: United States ui-languages: en-US

[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024735][info] Loaded Qt 
translations for current locale from resources

[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024775][info] Loaded WSJT-X base 
translation file from :/Translations based on language en

[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024804][info] Loaded WSJT-X 
translations for current locale from resources

[SYSLOG][2022-07-23 00:05:48.483151][00:00:00.376284][info] shmem size: 48275456

[RIGCTRL][2022-07-23 00:05:48.498778][00:00:00.402651][info] Hamlib version: 
Hamlib 4.5~git Sat Jul 16 15:53:03 2022 + SHA=cc7c59

[SYSLOG][2022-07-23 00:06:14.365843][00:00:26.254674][warning] Detected dropped 
audio source samples: 6672 (0.139 S)

[SYSLOG][2022-07-23 00:08:59.396314][00:03:11.254302][warning] Detected dropped 
audio source samples: 960 (0.02 S)

 

--Dennis NE6I

 

-Original Message-

From: Black Michael via wsjt-devel < <mailto:wsjt-devel@lists.sourceforge.net> 
wsjt-devel@lists.sourceforge.net> 

Sent: Friday, July 22, 2022 8:38 AM

To: WSJT Software Development < <mailto:wsjt-devel@lists.sourceforge.net> 
wsjt-devel@lists.sourceforge.net>

Cc: Black Michael < <mailto:mdblac...@yahoo.com> mdblac...@yahoo.com>

Subject: [wsjt-devel] RC2 syslog file

 

I'd appreciate if users could check their wsjtx_syslog.log file.

For Windows users it will be in C:\Users\[username]\Appdata\WSJT-X

For Linux users /[username]/.local/share/WSJT-X

 

Should look like this and have one warning possibly about dropped audio.  If 
you see any other warnings please report them.  

 

[SYSLOG][2022-07-09 11:40:21.572105][00:00:00.000857][info] Read logging 
configuration file: C:/Users/mdbla/AppData/Local/WSJT-X/wsjtx_log_config.ini

[SYSLOG][2022-07-09 11:40:21.572105][00:00:00.000922][info] WSJT-X  v2.6.0-rc1 
6744bc - Program startup

[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007037][info] locale: language: 
English script: Latin country: United States ui-languages: en-US

[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007155][info] Loaded Qt 
translations for current locale from resources

[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007183][info] Loaded WSJT-X base 
translation file from :/Translations based on language en

[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007201][info] Loaded WSJT-X 
translations for current locale from resources

[SYSLOG][2022-07-09 11:40:21.686366][00:00:00.115734][info] shmem size: 48275456

[RIGCTRL][2022-07-09 11:40:21.702969][00:00:00.131819][info] Hamlib version: 
Hamlib 4.5~git Fri Jul 08 21:21:34 2022 + SHA=0ec962

[SYSLOG][2022-07-09 11:40:51.067872][00:00:29.488477][warning] Detected dropped 
audio source samples: -480 (-0.01 S)

[SYS

Re: [wsjt-devel] RC2 syslog file

[Dennis Younker NE6I via wsjt-devel]

Here a few lines from mine. Win10 and running v2.6.0-rc2. Are you looking for 
something in particular? I seem to get these dropped audio source alerts quite 
a bit!

[SYSLOG][2022-07-22 03:26:29.383606][03:15:14.093551][warning] Detected dropped 
audio source samples: -624 (-0.013 S)
[SYSLOG][2022-07-22 03:27:14.400410][03:15:59.105372][warning] Detected dropped 
audio source samples: 672 (0.014 S)
[SYSLOG][2022-07-22 03:27:29.386450][03:16:14.090066][warning] Detected dropped 
audio source samples: -672 (-0.014 S)
[SYSLOG][2022-07-22 03:28:44.382611][03:17:29.078681][warning] Detected dropped 
audio source samples: -672 (-0.014 S)
[SYSLOG][2022-07-22 03:29:14.372757][03:17:59.065692][warning] Detected dropped 
audio source samples: -576 (-0.012 S)
[SYSLOG][2022-07-22 03:32:14.370149][03:20:59.037622][warning] Detected dropped 
audio source samples: -720 (-0.015 S)
[SYSLOG][2022-07-22 03:35:40.610055][03:24:25.255064][info] Log Finish
[SYSLOG][2022-07-23 00:05:48.112279][00:00:00.004030][info] Log Start
[SYSLOG][2022-07-23 00:05:48.113466][00:00:00.004078][info] WSJT-X   v2.6.0-rc2 
994e3f  by K1JT et al. - Program startup
[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024524][info] locale: language: 
English script: Latin country: United States ui-languages: en-US
[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024735][info] Loaded Qt 
translations for current locale from resources
[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024775][info] Loaded WSJT-X base 
translation file from :/Translations based on language en
[SYSLOG][2022-07-23 00:05:48.133505][00:00:00.024804][info] Loaded WSJT-X 
translations for current locale from resources
[SYSLOG][2022-07-23 00:05:48.483151][00:00:00.376284][info] shmem size: 48275456
[RIGCTRL][2022-07-23 00:05:48.498778][00:00:00.402651][info] Hamlib version: 
Hamlib 4.5~git Sat Jul 16 15:53:03 2022 + SHA=cc7c59
[SYSLOG][2022-07-23 00:06:14.365843][00:00:26.254674][warning] Detected dropped 
audio source samples: 6672 (0.139 S)
[SYSLOG][2022-07-23 00:08:59.396314][00:03:11.254302][warning] Detected dropped 
audio source samples: 960 (0.02 S)

--Dennis NE6I

-Original Message-
From: Black Michael via wsjt-devel  
Sent: Friday, July 22, 2022 8:38 AM
To: WSJT Software Development 
Cc: Black Michael 
Subject: [wsjt-devel] RC2 syslog file

I'd appreciate if users could check their wsjtx_syslog.log file.
For Windows users it will be in C:\Users\[username]\Appdata\WSJT-X
For Linux users /[username]/.local/share/WSJT-X

Should look like this and have one warning possibly about dropped audio.  If 
you see any other warnings please report them.  

[SYSLOG][2022-07-09 11:40:21.572105][00:00:00.000857][info] Read logging 
configuration file: C:/Users/mdbla/AppData/Local/WSJT-X/wsjtx_log_config.ini
[SYSLOG][2022-07-09 11:40:21.572105][00:00:00.000922][info] WSJT-X   v2.6.0-rc1 
6744bc - Program startup
[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007037][info] locale: language: 
English script: Latin country: United States ui-languages: en-US
[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007155][info] Loaded Qt 
translations for current locale from resources
[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007183][info] Loaded WSJT-X base 
translation file from :/Translations based on language en
[SYSLOG][2022-07-09 11:40:21.577965][00:00:00.007201][info] Loaded WSJT-X 
translations for current locale from resources
[SYSLOG][2022-07-09 11:40:21.686366][00:00:00.115734][info] shmem size: 48275456
[RIGCTRL][2022-07-09 11:40:21.702969][00:00:00.131819][info] Hamlib version: 
Hamlib 4.5~git Fri Jul 08 21:21:34 2022 + SHA=0ec962
[SYSLOG][2022-07-09 11:40:51.067872][00:00:29.488477][warning] Detected dropped 
audio source samples: -480 (-0.01 S)
[SYSLOG][2022-07-09 11:41:07.421339][00:00:45.836939][info] Log Finish

Mike W9MDB


___
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] Stop Measure Reference Spectrum

[Dennis Younker NE6I via wsjt-devel]

Oh, hidden in plain sight! DOH.  I was expecting it in the Tools menu. Thanks 
much.

 

--Dennis NE6I

 

From: Kari Sillanmäki via wsjt-devel  
Sent: Tuesday, July 19, 2022 11:40 AM
To: Dennis Younker NE6I via wsjt-devel 
Cc: Kari Sillanmäki 
Subject: Re: [wsjt-devel] Stop Measure Reference Spectrum

 

Dennis,

 

Where is the “Stop” that this section references? I don’t see it. I am running 
v2.6.0-rc1.

it is the button labeled "Stop" above frequency display, between "LogQSO" and 
"Monitor" buttons...

73's de Kari, oh2gqc

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

[wsjt-devel] Stop Measure Reference Spectrum

[Dennis Younker NE6I via wsjt-devel]

Hi, 

 

This is from 13.2 in the documentation:

 

“WSJT-X provides a tool that can be used to determine the detailed shape of 
your receiver’s passband. Disconnect your antenna or tune to a quiet frequency 
with no signals. With WSJT-X running in one of the slow modes, select Measure 
reference spectrum from the Tools menu. Wait for about a minute and then click 
Stop. A file named refspec.dat appears in your log directory. When you check 
Ref Spec on the Wide Graph, the recorded reference spectrum will then be used 
to flatten your overall effective passband.”

 

 

Where is the “Stop” that this section references? I don’t see it. I am running 
v2.6.0-rc1.

 

Thanks,

 

--Dennis NE6I

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

Re: [wsjt-devel] Unwanted CQ in FT8

[Dennis Younker NE6I via wsjt-devel]

Henryk,

 

It sounds as though you are mixing CQ Fans with Hunters, if I understand you 
correctly. If you are hunting, why would you quickly re-enable the ENABLE TX 
button after sending 73? Shouldn’t you wait until you receive RR73 or 73 from 
the other station?

 

I don’t believe there is a need for a TX7 because WSJT-X does not automatically 
send the next CQ unless the operator has enabled it. Even if there was a TX 7 
and it was blank, I would think that WSJT-X would enable transmit and not send 
anything, and only if the operator had quickly re-enabled ENABLE TX. Therefore, 
you would still not solve the problem you are describing. You would not be 
resending TX 4 or TX 5 to the other station. You would have your TX enabled but 
be sending nothing.

 

However, if I have missed something in your description, a possible solution is 
to clear the TX 6 field yourself during the QSO and that will give you the 
blank field that you are suggesting. 

 

I personally would not want a blank TX 7 and WSJT-X defaulting to it after I 
send 73. This would require another click on my part to generate my next CQ.

 

--Dennis NE6I

 

From: Henryk Majcher via wsjt-devel  
Sent: Wednesday, July 13, 2022 12:35 PM
To: WSJT software development 
Cc: Henryk Majcher 
Subject: Re: [wsjt-devel] Unwanted CQ in FT8

 

Hi Neil

 

You completely didn't understand what I asked.

The frame "TX 7" should be empty. It is a  stand by position.

No transmit, when it is checked.

Resume: "TX 7" is not a macro.

 

Henryk  SP3E

 

śr., 13 lip 2022 o 14:28 Neil Zampella via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
napisał(a):

That can be done using the 'Free Text' area and macros from JT
Alert.  No need to add another standard message.  As far as
'unwanted' CQs, uncheck the CALL 1ST checkbox.

Neil, KN3ILZ

On 7/12/2022 7:31 PM, Henryk Majcher wrote:
> I propose a small change in WSJT-X.
> Scenario:
> The users of WSJT-X are
> * CQ fans
> * Hunters (Squares, DXCC, Zones)
> Actually after QSO (even incomplete) the circle left of TX6 is checked
> and WSJT-X is ready to send CQ.
> It is super nice for CQ fans.
> What  WSJT-X offers for Hunters?   Nothing
>
> I propose to put an additional frame "TX 7".
> It will be named "Stand By".
> If someone don't planning CQ, then if "TX 7" is checked, WSJT-X wait
> ttil the Hunter chooses one of "TX 1", "TX 2" , "TX 3", "TX4".
> This way unwanted CQ is impossible.
>
> If during QSO DX repeat report R-XX it is better  not to transmit one
> period and choose again  "TX 4" and click Enable TX
> as send UNWANTED CQ if unfortunately first click "Enable TX".
>
> To do fully automatic we need in frame CQ:
> None
> First
> Max Dist
> to add one more row
> "Stand By".
>
> When this Stand By is checked by Hunter, after QSO WSJT-X will check
> the circle near "TX 7".
>
> Unwanted CQ is now impossible.
>
> I lost a few new DXCC when in pile-up heart pulse was 200/min
> and the unwanted CQ ruined QSO...
>
> 73
> Henryk  SP3E
>


___
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] Hamlib testing #Hamlib

[Dennis Younker NE6I via wsjt-devel]

Hello Mike,

I have installed the latest 64 bit version here and tested using my Yaesu 
FTDX-101MP. No problems noted using WSJT-X v2.6.0-rc1 in both Fake It and Split.

73, Dennis NE6I

-Original Message-
From: Black Michael via wsjt-devel  
Sent: Thursday, July 7, 2022 6:51 AM
To: WSJT Software Development ; WSJTX Group 

Cc: Black Michael 
Subject: [wsjt-devel] Hamlib testing #Hamlib

I need everyone to test the latest Hamlib please!!

All known rig bugs have been fixed.
Testing in Rig Split and Fake It would be appreciated as well as rigctld 
testing.
Successes/Failures please report.

Some recent important fixes are IC-9700 in split mode should work better now 
and split operations should be more stable for all other rigs.
 
New hamlib for installation directions

 #1 Shut down WSJTX/JTDX

 #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of 
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple 
times.
 If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and 
replace the libhamlib-4.dll that is there.
 http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
 http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
 Linux/Unix/Mac users need to compile the latest tar file from 
http://n0nb.users.sourceforge.net/

 #3 If you don't save directly you need to open a file browser and move the 
file that way.
 If you're not familiar with that here's a video on the file browser - 
https://www.youtube.com/watch?v=AyVqCJrs9dk

 Mike W9MDB



___
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] Hamlib testing

[Dennis Younker NE6I via wsjt-devel]

Works FB in Fake It and Split here. Running WSJT-X v2.5.4 to a Yaesu 
FTDX-101MP. 

 

--Dennis NE6I

 

From: Black Michael via wsjt-devel  
Sent: Tuesday, May 31, 2022 9:05 AM
To: WSJTX Group ; WSJT Software Development 

Cc: Black Michael 
Subject: [wsjt-devel] Hamlib testing

 

I need everyone to test the latest Hamlib 

Testing in Rig Split and Fake It would be appreciated.

Successes/Failures please report.

 

New hamlib for installation directions

 

#1 Shut down WSJTX/JTDX

 

#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of 
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple 
times.

 

If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and 
replace the libhamlib-4.dll that is there.

 

http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll

 

http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll

 

Linux/Unix/Mac users need to compile the latest tar file from 
http://n0nb.users.sourceforge.net/

 

#3 If you don't save directly you need to open a file browser and move the file 
that way.

 

If you're not familiar with that here's a video on the file browser - 
https://www.youtube.com/watch?v=AyVqCJrs9dk

 

Mike W9MDB

 

 

 

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

Re: [wsjt-devel] Feature Request: Hound Mode

[Dennis Younker NE6I via wsjt-devel]

Put me down for also wishing to have that on the main screen. Or more 
accurately in my case, having a check box or link on the main screen that is 
linked to Special Operating Activity. Yes, handy to quickly go to and from F/H 
mode but also convenient at the start and end of one of the contests listed on 
the Advanced tab. I have, for example, operated an NA VHF Contest over a 
weekend and then forgot to uncheck the box after the contest. And then been 
bitten for a moment later in the week when operating normal FT8 or MSK. 

 

I am not a programmer and not interested in becoming one (again). It’s great 
that the source code is available for anyone to modify to their heart’s content 
but I’m not interested in doing that. I did a lot of programming and compiling 
of code several decades ago, and spent MANY an all nighter doing that. That 
ship has now sailed for me, and I’m not interested in getting on board again.

 

I am hugely appreciative of K1JT and the entire WSJT-X team for their work. I 
for one know how much time and effort goes into this. It’s truly a labor of 
love. 

 

--Dennis NE6I

 

From: Jeff Stillinger via wsjt-devel  
Sent: Sunday, October 10, 2021 9:53 AM
To: WSJT software development 
Cc: Jeff Stillinger 
Subject: Re: [wsjt-devel] Feature Request: Hound Mode

 

Not exactly a secret.  For building on Microsoft virus, the sdk is located 
here: 

https://sourceforge.net/projects/jtsdk/

It is my understanding that it's going through some updates, but what is posted 
should work.  Last time I played with it was back in version 1.7.  I haven't 
kept up with that platform since I do everything on Linux.  





On 10/10/21 10:43 AM, Jon Anhold wrote:

Hi Jeff, 

 

Yes, I agree - I am a contributor to some other open source projects. Thanks 
for your helpful suggestion. 

 

I've given that some thought, but at least the last time I looked the build 
process / toolkit for building WSJT-X on Windows is like top secret or 
something, and I haven't spent any time recently trying to uncover it or get it 
to build.

 

Also, unfortunately, it doesn't seem that the authors are very open to pull 
requests, so I make feature suggestions here.

 

Thanks & 73 de KM8V Jon

 

On Sun, Oct 10, 2021 at 9:37 AM Jeff Stillinger via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

How about an alternative to your prediction.   WSJT-X is open source.  You have 
complete access to the source code, and one of the wonderful conveniences of 
the package is the ability to customize the software to a specific style of 
station operations.

That is the fancy and PC way to say, if you want a button somewhere specific, 
then you are free to put it there.  There are no licensing restrictions, other 
than your modification would stay local to your station.   All of the compilers 
and libraries are also free and open source. 

Have at it and let us know about your progress.






On 10/9/21 9:05 PM, Jon Anhold via wsjt-devel wrote:

I know that this is going to get ignored, or I'm going to be told to "make a 
configuration" to "solve" this problem, but I'll again put in a vote to have a 
Hound mode checkbox on the main screen to switch in and out of that mode. 

 

There are several DXPeditions right now, some running Fox/Hound mode, others 
running multi-stream NOT fox/hound mode, and I've found myself switching a LOT 
back and forth.

 

Maybe an option to enable an "expert" mode to then display some of these 
controls in an easy to use location?

 

73 de KM8V





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

Re: [wsjt-devel] Astronomincal Data Window

[Dennis Younker NE6I]

Hi Joe, 

That makes total sense. Thanks for the response.

--Dennis NE6I

-Original Message-
From: Joe Taylor  
Sent: Wednesday, June 9, 2021 5:10 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Astronomincal Data Window

Hi Dennis,

On 6/9/2021 7:59 PM, Dennis Younker NE6I wrote:
> Hello,
> 
> My apologies if this has been covered before. Is there a reason that 
> View, Astronomical Data has a grayed out "X" in the upper right 
> corner. The only way to close that window is to go back to View and
uncheck that item.
> 
> --Dennis NE6I

We wouldn't do it this way if there was not a good reason.

The astronomical data window controls important Doppler shift corrections
during EME operation.  We therefore want the window to be hard to close
accidentally.

 -- 73, Joe, K1JT


___
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] Astronomincal Data Window

[Dennis Younker NE6I]

Hello,

My apologies if this has been covered before. Is there a reason that View,
Astronomical Data has a grayed out "X" in the upper right corner. The only
way to close that window is to go back to View and uncheck that item. 

--Dennis NE6I



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

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

[Dennis Younker NE6I]

I can reproduce that here when I change the Font size to a larger value
(File, Settings, Font). Changing it to a lower value reduces or eliminates
the problem. I am on GA release v2.4.0 c19d62. I no longer have RC4
installed.

--Dennis NE6I

-Original Message-
From: Martin Davies G0HDB  
Sent: Tuesday, May 25, 2021 5:32 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] v2.4.0 GA (possible bug?)

I never got round to installing and trying any of the -RC versions of v2.4.0
but last night (Mon
24th) I downloaded and installed the 64-bit GA release, v2.4.0 (c19d62).  My
PC, a Dell 3070, is running Win10 (fully up to date); the PC has a 3.0GHz
i7-9700 8-core CPU with 16G RAM and a 256G SSD.

After installing v2.4.0 I discovered that when I opened the drop-down list
for the operating band the frequency information was truncated to only the
first few characters of the string because the width of the 'box' containing
the list of frequencies was too narrow, so it was impossible to see exactly
what the frequency was.

When I reverted to v2.3.1 the drop-down list is displayed normally and in
full, and I can see, for example:

50.313.000 MHz (6m)

I've just re-installed v2.4.0 and now all I can see is the frequency/band
drop-down list is:

50.3...(6m)

Has anyone else observed this 'feature' in v2.4.0?

--
73, Martin G0HDB


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



___
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] Click on a CQ and Get the Wrong Station

[Dennis Younker NE6I]

I have not had this happen for a while now. I *may* have been clicking on call 
signs in the RX Frequency pane but not absolutely sure. I don't think so but 
not absolutely sure.  I am currently running v2.4.0-rc3 and have intentionally 
clicked on calls in that pane and not had an issue. I've also had no issue 
double clicking on calls in the left pane. All of this being on FT8 by the way. 
Just wanted to report back on this.

As an aside, I did make a couple of QSOs on Q65 using rc2. Propagation has not 
been very cooperative here on the west coast for that mode. Folks with power 
and larger antennas make a couple QSOs each day but the rest of us not so much. 
No issues on my end with the mode and none that I have seen on one of the VHF 
chat rooms that is mostly populated with westerners.

Keep up the great work. Amazing stuff!

Am curious to see how FT8 pans out as we head up in the solar cycle in a couple 
of years. The FT8 frequencies are pretty crowded already. I can only imagine 
that some spreading out is in order soon.

--Dennis NE6I

-Original Message-
From: Dennis Younker NE6I  
Sent: Sunday, March 7, 2021 6:13 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] Click on a CQ and Get the Wrong Station

This has now happened twice tonight again. Click twice on the desired call in 
the left pane and instead I get the call of someone I tried for earlier and 
failed. Will try to gather more details and provide that here.

--Dennis NE6I

-Original Message-
From: Gary Rogers  
Sent: Sunday, March 7, 2021 4:52 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Click on a CQ and Get the Wrong Station

It hasn’t happened again since the first day that I used rc2

Sent from my iPhone

> On Mar 7, 2021, at 4:06 PM, Dennis Younker NE6I  wrote:
> 
> I was double clicking here too. I am trying to replicate this experience
> today (have not been on much though) and not having any luck (meaning WSJT-X
> is working as expected). I will provide an update if I see it happen again.
> It happened to me several times in both RC1 and RC2 in the past week or so.
> But not always...
> 
> --Dennis NE6I
> 
> -Original Message-
> From: Gary Rogers  
> Sent: Saturday, March 6, 2021 6:48 AM
> To: WSJT software development 
> Subject: Re: [wsjt-devel] Click on a CQ and Get the Wrong Station
> 
> Definitely double click
> 
>>> On Mar 5, 2021, at 9:43 PM, Gary McDuffie  wrote:
>>> 
>>> 
>>> 
>>>> On Mar 5, 2021, at 18:32, Dennis Younker NE6I  wrote:
>>> 
>>> I am clicking on the station I want in the left pane (Band Activity).
>> 
>> I assume you are DOUBLE clicking, not single clicking as you seem to be
> saying?
>> 
>> Gary - AG0N
>> 
>> ___
>> 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 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] Click on a CQ and Get the Wrong Station

[Dennis Younker NE6I]

This has now happened twice tonight again. Click twice on the desired call in 
the left pane and instead I get the call of someone I tried for earlier and 
failed. Will try to gather more details and provide that here.

--Dennis NE6I

-Original Message-
From: Gary Rogers  
Sent: Sunday, March 7, 2021 4:52 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Click on a CQ and Get the Wrong Station

It hasn’t happened again since the first day that I used rc2

Sent from my iPhone

> On Mar 7, 2021, at 4:06 PM, Dennis Younker NE6I  wrote:
> 
> I was double clicking here too. I am trying to replicate this experience
> today (have not been on much though) and not having any luck (meaning WSJT-X
> is working as expected). I will provide an update if I see it happen again.
> It happened to me several times in both RC1 and RC2 in the past week or so.
> But not always...
> 
> --Dennis NE6I
> 
> -Original Message-
> From: Gary Rogers  
> Sent: Saturday, March 6, 2021 6:48 AM
> To: WSJT software development 
> Subject: Re: [wsjt-devel] Click on a CQ and Get the Wrong Station
> 
> Definitely double click
> 
>>> On Mar 5, 2021, at 9:43 PM, Gary McDuffie  wrote:
>>> 
>>> 
>>> 
>>>> On Mar 5, 2021, at 18:32, Dennis Younker NE6I  wrote:
>>> 
>>> I am clicking on the station I want in the left pane (Band Activity).
>> 
>> I assume you are DOUBLE clicking, not single clicking as you seem to be
> saying?
>> 
>> Gary - AG0N
>> 
>> ___
>> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Click on a CQ and Get the Wrong Station

[Dennis Younker NE6I]

I was double clicking here too. I am trying to replicate this experience
today (have not been on much though) and not having any luck (meaning WSJT-X
is working as expected). I will provide an update if I see it happen again.
It happened to me several times in both RC1 and RC2 in the past week or so.
But not always...

--Dennis NE6I

-Original Message-
From: Gary Rogers  
Sent: Saturday, March 6, 2021 6:48 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Click on a CQ and Get the Wrong Station

Definitely double click

> On Mar 5, 2021, at 9:43 PM, Gary McDuffie  wrote:
> 
> 
> 
>> On Mar 5, 2021, at 18:32, Dennis Younker NE6I  wrote:
>> 
>> I am clicking on the station I want in the left pane (Band Activity).
> 
> I assume you are DOUBLE clicking, not single clicking as you seem to be
saying?
> 
> Gary - AG0N
> 
> ___
> 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] Click on a CQ and Get the Wrong Station

[Dennis Younker NE6I]

Something I am noticing is that occasionally on a busy band (IE 20m FT8),
when I click on someone calling CQ, the software starts calling the wrong
station. I am clicking on the station I want in the left pane (Band
Activity).

For example, tonight I clicked on BA4RF at 370 offset. The software had me
calling AE0TB at 801 offset. 

I also saw this in rc1. I will report more examples as I continue to see
this.

--Dennis NE6I

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

Re: [wsjt-devel] Error using WSJT-X 2.4.0-rc2

[Dennis Younker NE6I]

Just tried the FTDX10 setting here and it is working. Thanks for that tip.

 

--Dennis NE6I

 

From: Mike Lewis  
Sent: Friday, March 5, 2021 11:56 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Error using WSJT-X 2.4.0-rc2

 

I have a report from a friend that he has to use FTDX10 to make things work 
with his FTDX-101MP

 

Mike

K7MDL  EL87sm & CN88sf

 

From: Hartmut Luedtke via wsjt-devel  
Sent: Friday, March 5, 2021 14:35
To: wsjt-devel@lists.sourceforge.net
Cc: Hartmut Luedtke 
Subject: [wsjt-devel] Error using WSJT-X 2.4.0-rc2

 

Hi all,

 

WSJT-X 2.4.0-rc2 no longer works for me and my YAESU FTDX-101MP.

Same configuration as WSJT-X 2.4.0-rc1 and the following error message is 
displayed:



 

 

 

Same error message when reconfigured with a virgin INI.

Reinstalled the old version: Everything works again.

 

73 Hartmut, DB6LL

 

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

Re: [wsjt-devel] Error using WSJT-X 2.4.0-rc2

[Dennis Younker NE6I]

Same here. The FTDX-101D setting does not work either (it was working in RC1 
[and there was no 101MP in that version]).

 

--Dennis NE6I

 

From: Hartmut Luedtke via wsjt-devel  
Sent: Friday, March 5, 2021 11:35 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Hartmut Luedtke 
Subject: [wsjt-devel] Error using WSJT-X 2.4.0-rc2

 

Hi all,

 

WSJT-X 2.4.0-rc2 no longer works for me and my YAESU FTDX-101MP.

Same configuration as WSJT-X 2.4.0-rc1 and the following error message is 
displayed:



 

 

 

Same error message when reconfigured with a virgin INI.

Reinstalled the old version: Everything works again.

 

73 Hartmut, DB6LL

 

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