[wsjt-devel] Problem with compound callsigns in 2.2.0

[Grant VK5GR]

Joe/Bill et al,

 

I am finding a definite problem when using a non-standard callsign in 2.2. I
am running the 64bit Windows version under Windows 7 (yes I know I should
upgrade the OS). The fault is a little obtuse and occurs in a sequence like:

 

Callsign is set to "VK20HOME" (one of the special event callsigns)

 

1)  Start WSJT-X via N1MM (I don't think this matters but mention it for
completeness)

2)  Make a series of QSOs - I've made between 25 and 100 in a sitting.
All QSOs complete fine.

3)  Leave the software idle for an extended period (usually 4-6 hours)
monitoring the channel

4)  The call CQ again

5)  Wonder why no one is answering - but then notice a lot of <...>
entries in the Band Activity window

6)  Close the program

7)  Open the program

8)  Band activity is now full of people calling me.

9)  QSOs now complete successfully again

 

It seems that the software over time in idle mode has corrupted the hash of
its own callsign and can no longer recognise it. Start it up from cold and
the problem goes away.

 

Like I said - obtuse - but repeatable. I have had it do this to me reliably
probably 5-6 times over the last 2 days I have been running WSJT-X and
VK20HOME.

 

I can of course clear the fault and continue with a restart - but when you
get a chance if you could look at that one it would be appreciated. If you
need any other logs or files let me know.

 

Regards,

Grant VK5GR 

 

Email: vk5gr.ra...@gmail.com

Website:   https://vk5gr-iota.net/

 

 

 

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

[wsjt-devel] WSJT-X build error on FC32, 64-bit

[Josh Rovero]

I just updated to FC32 (via FC31).  I receive the following error when
building from source:

Making all in tests
/home/josh/Downloads/wsjtx-2.2.0/src/hamlib-prefix/src/hamlib/tests/rigctl.c:
In function ‘main’:
/home/josh/Downloads/wsjtx-2.2.0/src/hamlib-prefix/src/hamlib/tests/rigctl.c:574:9:
error: ‘rl_readline_name’ undeclared (first use in this function)
  574 | rl_readline_name = "rigctl";
  | ^~~~
/home/josh/Downloads/wsjtx-2.2.0/src/hamlib-prefix/src/hamlib/tests/rigctl.c:574:9:
note: each undeclared identifier is reported only once for each function it
appears in
/home/josh/Downloads/wsjtx-2.2.0/src/hamlib-prefix/src/hamlib/tests/rigctl.c:577:9:
warning: implicit declaration of function ‘using_history’; did you mean
‘write_history’? [-Wimplicit-function-declaration]
  577 | using_history();/* Initialize Readline History */
  | ^
  | write_history
make[5]: *** [Makefile:1131: rigctl-rigctl.o] Error 1
make[4]: *** [Makefile:823: all] Error 2
make[3]: *** [Makefile:605: all-recursive] Error 1
make[2]: *** [CMakeFiles/hamlib-install.dir/build.make:86:
hamlib-prefix/src/hamlib-stamp/hamlib-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:192: CMakeFiles/hamlib-install.dir/all]
Error 2

Any hints?
-- 
P.J. "Josh" Rovero http://www.roveroresearch.org
Ham Radio: KK1D http://www.roveroresearch
.net
http://www.roveroresearch.info
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Need some suggestions to discover audio feedback cause.

[Marco Calistri]

Hello all,

This message aim to see if someone has faced similar issue using WSJT-X
driving a transceiver via USB to Serial port converters PL2303, one of
these to manage the PTT and the other to manage the radio CAT interface.

Note: I noticed this issue since several months now, I mean that it is
not started with latest release of WSJT-X.

When WSJT-X is transmitting on FT8, if I speak in front of my notebook
and radio, which is a YAESU FT-100, I notice display meter is moving how
if I were speaking into the FT-100 microphone.

I tried both to mute radio mic gain as well as mute the notebook
sound-card mic without success, I've not yet understood how my voice is
apparently entering into the FT-100 during WSJT-X transmission and
being modulating the RF signal.

I don't know if I've been clear enough to describe my problem.

Thanks for your attention.


-- 

73 de Marco, PY1ZRJ (former IK5BCU)


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

Re: [wsjt-devel] Release candidates - decode coloring by external application fails when containing a positive report - Additional defect

[Bill Somerville]

On 03/06/2020 22:57, Laurie, VK3AMA wrote:

Bill,

A new defect identified with the decode coloring. The HighlightLast 
flag is not being honored properly.


To work-around the non-highlighting of strings containing a '+' symbol 
I modified JTAlert to only highlight callsigns only less the report 
part of the decode. JTAlert has always used the HighlightLast flag set 
to true.


A simple test with "AX3TC" set as a wanted callsign to be highlighted 
when decoded, JTAlert correctly doesn't alert/highlight when AX3TC is 
the target of a decode..

.

Now AX3TC is decoded transmitting so JTAlert alerts and highlights the 
Callsign. WSJT-X 2.2.0-GA correctly highlights the Callsign but also 
incorrectly highlights the previous period which was previously not 
colored...



It looks to me like there is some sort of logic bug in determining the 
last period.



Rerunning the same tests with WSJT-X 2.1.2 the correct results are 
observed, no incorrect coloring of AX3TC in previous period.



de Laurie VK3AMA


Hi Laurie,

thanks for the issue report. It took me a while to reproduce reliably, 
which I have now done with help from a video demo from Mike, W9MDB. The 
defect is repaired for the next release, and the changes should include 
a small performance improvement when processing this type of UDP request 
with a long decode history.


73
Bill
G4WJS.

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

Re: [wsjt-devel] Fwd: Problem with V2.2 WSJT-X?

[Bill Somerville]

On 05/06/2020 18:20, Nik Read via wsjt-devel wrote:

I Downloaded the latest version today V2.20

Windows 10Pro


I have been using version 2.10 of WSJT-X with no issues so this 
afternoon I downloaded version 2.20. on Running the programme it 
failed to connect to my FT991 (Audio through the USB worked ok) coming 
up with a Hamlib error stating that it could not read the frequency.  
I had been using version 2.10 5 minutes previously with no issues! All 
other programmes that connect to the FT991 worked perfectly.


I re-installed version 2.10 and it connected to the radio with no issues.


Thanks for a great programme to all the development team..


Nik M5DND


Hi Nik,

thanks for the issue report, we are aware of a regression, affecting the 
-891 and FT-991, in the Hamlib library that crept into the WSJT-X v2.2.0 
release. A fix is already in place and a bugfix release of WSJT-X will 
be available shortly once a couple of other late breaking issues are 
resolved. Sorry for the inconvenience.


73
Bill
G4WJS.



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

[wsjt-devel] Fwd: Problem with V2.2 WSJT-X?

[Nik Read via wsjt-devel]

 Forwarded Message 
Subject:Problem with V2.2 WSJT-X?
Date:   Fri, 5 Jun 2020 17:10:20 +0100
From:   Nik Read 
To: wsjt-devel@lists.sourceforge.net



I Downloaded the latest version today V2.20

Windows 10Pro


I have been using version 2.10 of WSJT-X with no issues so this 
afternoon I downloaded version 2.20. on Running the programme it failed 
to connect to my FT991 (Audio through the USB worked ok) coming up with 
a Hamlib error stating that it could not read the frequency.  I had been 
using version 2.10 5 minutes previously with no issues! All other 
programmes that connect to the FT991 worked perfectly.


I re-installed version 2.10 and it connected to the radio with no issues.


Thanks for a great programme to all the development team..


Nik M5DND


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

[wsjt-devel] QSP from HA5FT

[Andras Bato]

To Whom, Who may concern,


I have difficulties accessing
https://physics.princeton.edu/pulsar/K1JT/index.html website.

Depending on the public IP my internet provider gives me I can or can
not access the site.

The 195.38.121.198 IP is working, the 92.249.140.138, 217.197.182.206
and 77.234.82.219 is not working.

I can access the website through a 4G mobile provider all the times.

With the 77.234.82.219 IP the traceroute answer is the following:

traceroute to physics.princeton.edu (128.112.100.6), 30 hops max, 60
byte packets
  1  gateway (192.168.1.4)  0.280 ms  0.445 ms  0.629 ms
  2  10.0.0.1 (10.0.0.1)  4.338 ms  4.149 ms  4.415 ms
  3  * * *
  4  78.131.3.175 (78.131.3.175)  10.322 ms  10.741 ms  11.710 ms
  5  cr02.budapesta.rdsnet.ro (213.154.126.65)  12.808 ms
bb01.budapesta.rdsnet.ro (213.154.125.65)  5.733 ms  5.750 ms
  6  * * *
  7  40ge1-3.core1.lon2.he.net (195.66.224.21)  41.054 ms * *
  8  100ge13-2.core1.nyc4.he.net (72.52.92.166)  101.941 ms 101.852 ms
100.625 ms
  9 princeton-university.10gigabitethernet1-1-6.switch1.nyc8.he.net
(216.66.49.74)  107.900 ms 100ge13-2.core1.nyc4.he.net (72.52.92.166)
101.931 ms  101.702 ms
10 princeton-university.10gigabitethernet1-1-6.switch1.nyc8.he.net
(216.66.49.74)  104.579 ms  104.847 ms core-87-router.princeton.edu
(128.112.12.66)  107.007 ms
11  core-87-router.princeton.edu (128.112.12.66)  105.727 ms 106.765 ms
105.731 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

DR. János Selmeczi,
Jani, HA5FT

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

Re: [wsjt-devel] WSJT on sourceforge

[Bill Somerville]

OM,

SourceForge is not dead. This current position is a deliberate action by 
the WSJT-X development team and is only temporary until some issues are 
resolved.


73
Bill
G4WJS.

On 05/06/2020 14:34, sourceforge@from.ec wrote:
Apropos git — has anybody suggested moving to (or mirroring to) GitHub 
or GitLab or similar?


SourceForge is, uh, dead.

On Fri, Jun 5, 2020 at 08:28, Bill Somerville > wrote:

On 05/06/2020 14:24, Alessandro Gorobey via wsjt-devel wrote:
> Hi all,
>
> I have had many problems for a couple of days on WSJT site.
>
> I need a little test.
> Can anyone go with a web browser to
>
> https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/
>
> and select History ?
>
> Or, from left menù scroll down to "Tags" --> "More Tags" ?
>
> It seems that the changes of the last few months are not accessible
> Even "git" does oddities
>
> Thanks in advance
>
> --
> 73
> Sandro
> IW3RAB

Hi Sandro,

the git repo on SourceForge is currently as at v2.1.2, it will be
updated soon once we have resolved a couple of issues. Sorry for the
temporary outage. Current v2.2.0 sources are available from the project
web site and the SourceForge files area as usual.

73
Bill
G4WJS.



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

Re: [wsjt-devel] WSJT on sourceforge

[sourceforge . net]

Apropos git — has anybody suggested moving to (or mirroring to) GitHub or 
GitLab or similar?

SourceForge is, uh, dead.

On Fri, Jun 5, 2020 at 08:28, Bill Somerville  wrote:

> On 05/06/2020 14:24, Alessandro Gorobey via wsjt-devel wrote:
>> Hi all,
>>
>> I have had many problems for a couple of days on WSJT site.
>>
>> I need a little test.
>> Can anyone go with a web browser to
>>
>> https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/
>>
>> and select History ?
>>
>> Or, from left menù scroll down to "Tags" --> "More Tags" ?
>>
>> It seems that the changes of the last few months are not accessible
>> Even "git" does oddities
>>
>> Thanks in advance
>>
>> --
>> 73
>> Sandro
>> IW3RAB
>
> Hi Sandro,
>
> the git repo on SourceForge is currently as at v2.1.2, it will be
> updated soon once we have resolved a couple of issues. Sorry for the
> temporary outage. Current v2.2.0 sources are available from the project
> web site and the SourceForge files area as usual.
>
> 73
> Bill
> G4WJS.
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT on sourceforge

[Alessandro Gorobey via wsjt-devel]

Thanks Bill for fast reply

Il 05/06/2020 15:28, Bill Somerville ha scritto:

On 05/06/2020 14:24, Alessandro Gorobey via wsjt-devel wrote:

Hi all,

I have had many problems for a couple of days on WSJT site.

I need a little test.
Can anyone go with a web browser to

https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/

and select History ?

Or, from left menù scroll down to "Tags" --> "More Tags" ?

It seems that the changes of the last few months are not accessible
Even "git" does oddities

Thanks in advance

--
73
Sandro
IW3RAB


Hi Sandro,

the git repo on SourceForge is currently as at v2.1.2, it will be 
updated soon once we have resolved a couple of issues. Sorry for the 
temporary outage. Current v2.2.0 sources are available from the project 
web site and the SourceForge files area as usual.


73
Bill
G4WJS.



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


--
73
Sandro
IW3RAB


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

Re: [wsjt-devel] WSJT on sourceforge

[Bill Somerville]

On 05/06/2020 14:24, Alessandro Gorobey via wsjt-devel wrote:

Hi all,

I have had many problems for a couple of days on WSJT site.

I need a little test.
Can anyone go with a web browser to

https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/

and select History ?

Or, from left menù scroll down to "Tags" --> "More Tags" ?

It seems that the changes of the last few months are not accessible
Even "git" does oddities

Thanks in advance

--
73
Sandro
IW3RAB


Hi Sandro,

the git repo on SourceForge is currently as at v2.1.2, it will be 
updated soon once we have resolved a couple of issues. Sorry for the 
temporary outage. Current v2.2.0 sources are available from the project 
web site and the SourceForge files area as usual.


73
Bill
G4WJS.



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

[wsjt-devel] WSJT on sourceforge

[Alessandro Gorobey via wsjt-devel]

Hi all,

I have had many problems for a couple of days on WSJT site.

I need a little test.
Can anyone go with a web browser to

https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/

and select History ?

Or, from left menù scroll down to "Tags" --> "More Tags" ?

It seems that the changes of the last few months are not accessible
Even "git" does oddities

Thanks in advance

--
73
Sandro
IW3RAB


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

Re: [wsjt-devel] Release candidates - decode coloring by external application fails when containing a positive report - Additional defect

[Bill Somerville]

Hi Mike,

thanks for that - very helpful.

73
Bill
G4WJS.

On 05/06/2020 04:35, Black Michael via wsjt-devel wrote:

Helps if I give the link
https://www.dropbox.com/s/wno7tgxt11oiq4f/ice_video_20200604-222426.webm?dl=0




On Thursday, June 4, 2020, 10:34:03 PM CDT, Black Michael via 
wsjt-devel  wrote:



Simple enough...get a few decode cycles without CQ Alert enabled.
Then turn on CQ Alert.
On the next decode cycle it will highlight all previous cycles.

Here's a video.
On the last decode cycle in this one S57VAW is decoded and it 
higlights both the current and 1st decode period in this video.

I show where it's no initially highlighted in the first decode.
So it's doing a global replace.  But maybe it's supposed to do that?  
I don't use the highlighting so not familiar with past behavior.


Mike



On Thursday, June 4, 2020, 06:23:43 PM CDT, Bill Somerville 
 wrote:



On 05/06/2020 00:17, Bill Somerville wrote:

On 04/06/2020 23:48, Black Michael via wsjt-devel wrote:
I can reproduce this on my machine.  No excessive load.  I just 
turned on the CQ Alert and next cycle it highlighted all the calls 
that matched in the history of the call.


Hi Mike,

what does "and next cycle it highlighted all the calls that matched 
in the history of the call" mean, I can relate that to the issue 
Laurie is reporting.


73
bill
G4WJS. 


Sorry - s/can/can't/




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

Re: [wsjt-devel] RC 2.2.0 - Now Working with Yaesu FT-991

[Robert A. Klahn (AD6I)]

I wrote a lengthy reply to Stephen VK3SIR post, which I just discarded. 
Ultimately, I think I was adding more noise than signal. 

I will say just this: I hope that everyone distributing changes to WSJT-X are 
following the obligations of GPLv3, including distributing the source code. To 
not do so is disrespectful, and a violation of copyright law.

Thanks. Robert. AD6I.

On Fri, Jun 5, 2020, at 2:18 AM, Stephen VK3SIR wrote:
> Bill,
> 
> >  you stated the above, that is indirect evidence that you have distributed 
> > a binary version of WSJT-X.
> 
> Indirect evidence - h ... Assumptions. Reminds me of Fleishman, 
> Pons and their "Cold Fusion" ... 
> 
> Fact: The reference to the 891 refers to equipment at an alternate site 
> listed on my licence. Fact: GNU GPLv3 has not been violated after 
> conferring with a solicitor. Qualified facts here.
> 
> Binary distros of your code are flying everywhere; people are DESPERATE 
> to overcome this debacle with changes forced onto Hamlib by the 
> premature 2.2.0 release. 
> 
> Faulty releases are still being distributed without warning hence 
> unanswered posts on the Dev forum.
>  
> Back to the opening comment - you assumed - wrongly - and pursued with 
> green-eyed venom. You targeted someone (as is not uncommon in this 
> place) - me in this case - and wrongly. The behaviours demonstrated are 
> so mixed around here ! As recent examples, some get lauded for posting 
> "false decodes" - yet I got derided the other day. 
> 
> Variable and selective behaviours ... This is what is killing AR. 
> People here as leaders should be consistent, respectful and hence 
> setting way better examples.
> 
> Comments to Mike Black - one of AR's real geniuses - are also observed 
> by many to be substandard 
> 
> Stop it ! Behave ! Think about how you are interacting with the 
> community here ! It is not about ego - it is about growth and future !
> 
> You cannot have your cake and eat it too - a Famous Aussie expression.
> 
> Grow up gentlemen. Play nicely with the kiddies. Teach, develop and 
> nurture the kiddies. Otherwise the playground will get ripped apart !
> 
> Don't respond further to this in public as it only divides AR down 
> further. I have only responded here as quite a number of emails have 
> come in from many too "scared" to express concerns.
> 
> Steve I
> VK3VM / VK3SIR
> 
> 
> ___
> 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] RC 2.2.0 - Now Working with Yaesu FT-991

[Stephen VK3SIR]

Bill,

>  you stated the above, that is indirect evidence that you have distributed a 
> binary version of WSJT-X.

Indirect evidence - h ... Assumptions. Reminds me of Fleishman, Pons and 
their "Cold Fusion" ... 

Fact: The reference to the 891 refers to equipment at an alternate site listed 
on my licence. Fact: GNU GPLv3 has not been violated after conferring with a 
solicitor. Qualified facts here.

Binary distros of your code are flying everywhere; people are DESPERATE to 
overcome this debacle with changes forced onto Hamlib by the premature 2.2.0 
release. 

Faulty releases are still being distributed without warning hence unanswered 
posts on the Dev forum.
 
Back to the opening comment - you assumed - wrongly - and pursued with 
green-eyed venom. You targeted someone (as is not uncommon in this place) - me 
in this case - and wrongly. The behaviours demonstrated are so mixed around 
here ! As recent examples, some get lauded for posting "false decodes" - yet I 
got derided the other day. 

Variable and selective behaviours ... This is what is killing AR. People here 
as leaders should be consistent, respectful and hence setting way better 
examples.

Comments to Mike Black - one of AR's real geniuses - are also observed by many 
to be substandard 

Stop it ! Behave ! Think about how you are interacting with the community here 
! It is not about ego - it is about growth and future !

You cannot have your cake and eat it too - a Famous Aussie expression.

Grow up gentlemen. Play nicely with the kiddies. Teach, develop and nurture the 
kiddies. Otherwise the playground will get ripped apart !

Don't respond further to this in public as it only divides AR down further. I 
have only responded here as quite a number of emails have come in from many too 
"scared" to express concerns.

Steve I
VK3VM / VK3SIR


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