Date   

locked Re: v.2.3.0-rc2 sequencing not correct #IssueReport

Carl - WC4H
 

The thing is that there have been sequencing errors creeping in.

Here's another where I should have been going to CQ but a 73 was sent.


locked Re: odd bunch of signals on top band now

geoff wiggins
 

Ignore, just worked it out, cluster.

73.

On 20/11/2020 18:13, geoff wiggins via groups.io wrote:
Hi Group.

There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's going on? The call is 7Q7RU.

73 Geoff.





locked Re: v.2.3.0-rc2 sequencing not correct #IssueReport

Carl - WC4H
 

Hi Kevin.

I highlighted the wrong error... if you see the line below the RR73, my system sent a CQ.. I had to hit the 73 manually.  I posted it after having saved the screen and looked at it crossed eye.

Still a sequencing error.

Thanks.
Carl - WC4H


locked odd bunch of signals on top band now

geoff wiggins
 

Hi Group.

There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's going on? The call is 7Q7RU.

73 Geoff.


locked Re: LoTW User Error .. WAS: [WSJTX] main@WSJTX.groups.io

neil_zampella
 

I suspect you've gone from the 32 bit version to the 64 bit version (or vice versa).   The answer is you need to install the proper Open SSL library for the program type you're using.    The URL to download is listed in the WSJT-X User Guide

Neil, KN3ILZ

On 11/20/2020 10:32 AM, Cliff Lumpkin wrote:

Error Loading LoTW User Data

 

Network Error - SSL/TLS support not installed, cannot fetch: ‘https://lotw.arrl.org/lotw-user-activity.csv

 

Not an issue when loading 2.2.2.

 

KC4AIF

Cliff





locked Re: No tones on transmit- no power out on transmit.

KEN G4APB
 

Hi Bill,
I had a similar problem, I did report the text below but received no reply but I think it is related.:-
I found that in FST4W mode, if I select Tx Enable and Tx Next, although the PTT is activated, there are no transmit tones. If I select TUNE, all is well. 

It seems I have to wait for the NEXT tx cycle before the tones come through. I reported this in -rc1.
Rig is Yaseu FT897D, Windows 7 home laptop. running wsjt-x v2.3.0-rc2. Cat control and audio via laptop mic and headphone sockets. 
I actually connected a scope to the audio out from my laptop and observed no tx tones during ptt enabled and first transmission, my Tx was on but no output power (as in USB mode). When I got to the 2nd transmission (quite a lot later as I was trying FST4W 300 on 80m), tones were produced for the 300 seconds although I was unable to decode myself on a second receiver and 2nd laptop, At the end of transmission, ptt went off but there was a single tone still coming out of the audio socket, seen on the ‘scope. I had an evening of transmitting FST4W on 80m with no-one spotting me. A 2nd QRP Tx of mine running WSPR was heard all over Europe on the same evening.
hope this helps you diagnose the problem.
73 Ken G4apb 


locked Re: 2.3.0 rc2 Unexpected behavior

JP Tucson, AZ
 

Hi Tony,

The only problem with your theory is that it (wsjtx) calls on you respond & log as it starts sending out the RR73 (TX4) message. 

What you are suggesting can only be done manually, and this discussion is about the AUTO-sequencer not operating quite right.

Personally, I think the issue comes down to 2 different & apparently incompatible philosophies about the RRR vs. RR73  response & the logic bug it creates; both in software & practice. Perhaps the best choice is for wsjtx to pick one & offer only that  one choice.

Since I see about 90-95% of users use RR73... I think we should go with that.

73 - John - N7GHZ

On Fri, Nov 20, 2020, 9:07 AM Tony Collett via groups.io <tony.nbs=btinternet.com@groups.io> wrote:
I think Reino explanation is correct but not worded so that you understood?

The program only sent CQ because you had logged the QSO and cleared the fields.
If you had waited and not logged the QSO until after you saw his 73 message it would have behaved as you expected.

Perhaps there is a difference in behaviour in how it works with RRR or RR73 endings but so few now use RRR sequence that I can't be sure!

73
Tony G4NBS



locked main@WSJTX.groups.io

Cliff Lumpkin
 

Error Loading LoTW User Data

 

Network Error - SSL/TLS support not installed, cannot fetch: ‘https://lotw.arrl.org/lotw-user-activity.csv

 

Not an issue when loading 2.2.2.

 

KC4AIF

Cliff


locked Re: 2.3.0 rc2 Unexpected behavior

Tony Collett
 

I think Reino explanation is correct but not worded so that you understood?

The program only sent CQ because you had logged the QSO and cleared the fields.
If you had waited and not logged the QSO until after you saw his 73 message it would have behaved as you expected.

Perhaps there is a difference in behaviour in how it works with RRR or RR73 endings but so few now use RRR sequence that I can't be sure!

73
Tony G4NBS


locked Re: Intermittent choppy TX audio on macOS Big Sur (11.0.1)

Ross Wardrup
 
Edited


locked Re: FST4 on 160m experiment #FT4

Bruce
 

Ror NA, 160 just starts to open at 2200z. Could you please run later? I thank you in advance. Bruce, W8HW in Florida, USA

On 11/20/2020 10:24 AM, Amos Sobel 4X4MF wrote:
Hi Folks!

Join me in FST4 160m. This evening 19:00-22:00 UTC I will call CQ and listen:
1. Using WSJT-X v2.3.0 rc2
2. Mode=FST4 Single Decode
3. Frequency=1839.00 KHz
4. Tx=Rx=1500 Hz
5. F Tol=100 Hz
6. T/R=60 Sec
7. Radio bandpass filter=3000 Hz
8/ Please call me and report if I do not answer. I will report what I hear.
73's
Amos 4X4MF




locked FST4 on 160m experiment #FT4

Amos Sobel 4X4MF
 

Hi Folks!

Join me in FST4 160m. This evening 19:00-22:00 UTC I will call CQ and listen:
1. Using WSJT-X v2.3.0 rc2
2. Mode=FST4 Single Decode
3. Frequency=1839.00 KHz
4. Tx=Rx=1500 Hz
5. F Tol=100 Hz
6. T/R=60 Sec
7. Radio bandpass filter=3000 Hz
8/ Please call me and report if I do not answer. I will report what I hear.
73's
Amos 4X4MF


locked Re: Error while opening the program: (invalid ADIF header). #IssueReport

Bruce N7XGR
 

Mattia,  This is a common error message about the ADIF log file.
Locate the ADIF log file and do this,
Find the first line where it says:

WSJT-X ADIF Export<eh>

change it to:

WSJT-X ADIF Export<eoh>

Save the file, restart WSJT-X, and you should be good.

This is from a posting on the WSJT-X group.

Bruce  N7XGR

On Fri, Nov 20, 2020 at 9:42 AM mattia iu2cgb <mattia24@...> wrote:
I am looking for solution for this error.
wsjt version x 2.2.2.
windows 10 64 bit operating system.
error while opening the program: (invalid ADIF header).
when i open the program i get this error every time i open it.
error photo attached.
Thank you so much.




locked Re: 2.3.0 rc2 Unexpected behavior

Gary Rogers
 

Right in the example below, he sent RRR and when I sent 73, the logging box popped up and I clicked ok and rearmed enable Tx. My point is that previously the program would resend 73 not CQ. 


locked Re: Error while opening the program: (invalid ADIF header). #IssueReport

Bill Somerville
 

On 20/11/2020 09:28, mattia iu2cgb wrote:
I am looking for solution for this error.
wsjt version x 2.2.2.
windows 10 64 bit operating system.
error while opening the program: (invalid ADIF header).
when i open the program i get this error every time i open it.
error photo attached.
Thank you so much.
Hi Mattia,

thanks for reporting the issue. It is a known issue with WSJT-X v2.2.2 which writes an invalid ADIF header when it first creates its own ADIF log file. You can fix the header by editing the ADIF log file using Notepad.exe. The log file is in the WSJT-X log files directory ("Menu->File->Open log directory") and is called wsjtx_log.adi (alternatively accessed as "%LocalAppData%\WSJT-X\wsjtx_log.adi"). The header line contains <eh> which should be changed to <eoh>

73
Bill
G4WJS.


locked Re: Error while opening the program: (invalid ADIF header). #IssueReport

Sam Birnbaum
 

oops : wsjtx-log.adi should have been wsjtx_log.adi


Sam W2JDB



-----Original Message-----
From: Sam Birnbaum via groups.io <w2jdb@...>
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Sent: Fri, Nov 20, 2020 9:46 am
Subject: Re: [WSJTX] #wsjt-x

Hi,

Check the WSJTX-Log.adi file.

the first line should look like this : WSJT-X ADIF Export <eoh>

There was a bug that left out the <eoh> in the first line.

That should fix it.

73,


Sam W2JDB



-----Original Message-----
From: mattia iu2cgb <mattia24@...>
To: main@WSJTX.groups.io
Sent: Fri, Nov 20, 2020 4:28 am
Subject: [WSJTX] #wsjt-x

I am looking for solution for this error.
wsjt version x 2.2.2.
windows 10 64 bit operating system.
error while opening the program: (invalid ADIF header).
when i open the program i get this error every time i open it.
error photo attached.
Thank you so much.





locked Re: Error while opening the program: (invalid ADIF header). #IssueReport

Sam Birnbaum
 

Hi,

Check the WSJTX-Log.adi file.

the first line should look like this : WSJT-X ADIF Export <eoh>

There was a bug that left out the <eoh> in the first line.

That should fix it.

73,


Sam W2JDB



-----Original Message-----
From: mattia iu2cgb <mattia24@...>
To: main@WSJTX.groups.io
Sent: Fri, Nov 20, 2020 4:28 am
Subject: [WSJTX] #wsjt-x

I am looking for solution for this error.
wsjt version x 2.2.2.
windows 10 64 bit operating system.
error while opening the program: (invalid ADIF header).
when i open the program i get this error every time i open it.
error photo attached.
Thank you so much.



locked Re: v.2.3.0-rc2 sequencing not correct #IssueReport

Ken WB8UFC
 

Sequencing errors are easily induced in v2.2.2 od9b96 as follows:
While in a QSO with contact one, double-click in the left window on another contact then immediately double-click on the last received transmission from contact 1 in the right window.

If this action is taken following a received RR73, a 73 should be sent but isn't.
Instead, an RR73 is sent.

If this action is taken following a received initial signal report, the correct R+ signal report is next sent but then does not advance to the 73 message after receiving an RR73 and instead remains stuck sending another R+ signal report.


locked Error while opening the program: (invalid ADIF header). #IssueReport

mattia iu2cgb
 

I am looking for solution for this error.
wsjt version x 2.2.2.
windows 10 64 bit operating system.
error while opening the program: (invalid ADIF header).
when i open the program i get this error every time i open it.
error photo attached.
Thank you so much.


locked Intermittent choppy TX audio on macOS Big Sur (11.0.1)

Ross Wardrup
 

Hi all,

I'm having an issue with choppy audio on TX using WSJT-X 2.2.2 (build 0d9b96) on macOS Big Sur (11.0.1). The issue is intermittent and typically happens once every half hour or so. Sometimes, it'll occur on multiple transmission cycles in a row.

This is on a fresh install of the OS with no additional kernel extensions installed. Using the built-in USB audio device support to drive my IC-7300.

I've captured an error message in the console: HALC_ProxyIOContext::IOWorkLoop: skipping cycle due to overload.

Any ideas what could be causing this?

18581 - 18600 of 37039