Date   

locked #FT8 Responding to FT8 "73" in QSO at end to contact not working #FT8

Dick Bingham
 

Greeting to everyone

AFTER getting FT8 to run after installing WSJT-X v2.4.0 software, I have discovered a
new problem.

I call CQ and another station responds. The software runs us thru the contact 
process and finally the calling station sends the 73 and sign-off sequence.

At this point my software ends the QSO without going thru the 73 by me. The screen
appearance then looks like it is ready to send another CQ by me or me calling
another station.

I have to be quick to activate "enable TX" and click on the "73" to let the other station
know the QSO is completed when this happens.

What's happening here ??

The station equipment:
DELL Laptop E6510 OS ===>w-7 ===> running OpenHPSDR mRX PS v3.4.7 ===> ANAN-200D SDR
WSJT-X v2.4.0

Dick - w7wkr


locked Re: Help setting up WSJTX #FT8 #Cat_RigControl #JT65

Bill Somerville
 

On 26/08/2021 23:10, Mark Finkelstein via groups.io wrote:
Well first off thank everyone for helping me. I have the software running and am copying transmissions on the band.  I can double click on CQ’s and if I enable the TX it appears to be sending. However, the radio does is not being keyed.  I tried both 20m and 40m with similar results.  I’m using the Sabrent adapter for Mac to the REM/Data port.  Tx500 radio is in Digital mode. I did a time.is and the computer clock is exact.

Any thoughts on where to look?
Hi Mark,

do you have a CAT interface?

73
Bill
G4WJS.


locked Re: Syslog Error #wsjt-x #IssueReport

Bill Somerville
 

On 26/08/2021 23:41, Pete W1RM wrote:

Can anyone help me decipher what the error was and help resolve it?

 

 

[SYSLOG][2021-08-26 19:36:45.589431][00:00:00.000620][info] Log Start

[SYSLOG][2021-08-26 19:36:45.589431][00:00:00.000651][info] WSJT-X - ForEW1   v2.3.0 0c42df  by K1JT, G4WJS, and K9AN - Program startup

[SYSLOG][2021-08-26 19:36:45.600925][00:00:00.011551][info] locale: language: English script: Latin country: United States ui-languages: en-US

[SYSLOG][2021-08-26 19:36:45.600925][00:00:00.011693][info] Loaded base translation file from :/Translations based on language en

[SYSLOG][2021-08-26 19:36:45.600925][00:00:00.011706][info] Loaded translation file from :/Translations based on language en

[SYSLOG][2021-08-26 19:36:45.773848][00:00:00.184741][info] shmem size: 48275456

[RIGCTRL][2021-08-26 19:36:45.790833][00:00:00.202356][info] Hamlib version: Hamlib 4.2~git

[SYSLOG][2021-08-26 19:36:46.758740][00:00:01.169987][warning] QObject::connect: No such signal QStatusBar::clicked(bool)

[SYSLOG][2021-08-26 19:36:46.758740][00:00:01.170010][warning] QObject::connect:  (sender name:   'statusBar')

[SYSLOG][2021-08-26 19:36:46.758740][00:00:01.170016][warning] QObject::connect:  (receiver name: 'MainWindow')

[SYSLOG][2021-08-26 20:38:59.393995][01:02:13.769695][warning] Detected dropped audio source samples: 864 (0.018 S)

[SYSLOG][2021-08-26 21:18:29.500844][01:41:43.856051][warning] Detected dropped audio source samples: 5808 (0.121 S)

[RIGCTRL][2021-08-26 22:20:36.965072][02:43:51.286163][error] failed to send command:Socket is not connected

[RIGCTRL][2021-08-26 22:20:36.969374][02:43:51.290331][error] failed:Socket is not connected

[SYSLOG][2021-08-26 22:20:36.969737][02:43:51.290717][error] handle_transceiver_failure: reason: DX Lab Suite Commander send command failed "CmdGetFreq": Socket is not connected

[RIGCTRL][2021-08-26 22:20:40.605028][02:43:54.926127][error] CmdGetFreqfailed to read reply:The remote host closed the connection

[RIGCTRL][2021-08-26 22:20:40.605028][02:43:54.926201][error] failed:Socket is not connected

[SYSLOG][2021-08-26 22:20:40.605028][02:43:54.926223][error] handle_transceiver_failure: reason: DX Lab Suite Commander send command "CmdGetFreq" read reply failed: The remote host closed the connection

[RIGCTRL][2021-08-26 22:22:42.649883][02:45:56.970052][error] CmdGetFreqretries exhausted

[RIGCTRL][2021-08-26 22:24:42.651224][02:47:56.970548][error] CmdSendTxretries exhausted

[SYSLOG][2021-08-26 22:24:42.696957][02:47:57.016656][info] Log Finish

 

 

Pete Chamalian, W1RM

W1rm@...

Hi Pete,

the only serious errors there are a failure to connect to DX Lab Suite Commander, or something that emulates that like the N1MM Logger+ WSJT-X interface module. Are you attempting to run WSJT-X from the N1MM Logger+ application?

73
Bill
G4WJS.


locked Re: Help setting up WSJTX #FT8 #Cat_RigControl #JT65

Mark Finkelstein
 

Well first off thank everyone for helping me. I have the software running and am copying transmissions on the band.  I can double click on CQ’s and if I enable the TX it appears to be sending. However, the radio does is not being keyed.  I tried both 20m and 40m with similar results.  I’m using the Sabrent adapter for Mac to the REM/Data port.  Tx500 radio is in Digital mode. I did a time.is and the computer clock is exact.

Any thoughts on where to look?


locked Syslog Error #wsjt-x #IssueReport

Pete W1RM
 

Can anyone help me decipher what the error was and help resolve it?

 

 

[SYSLOG][2021-08-26 19:36:45.589431][00:00:00.000620][info] Log Start

[SYSLOG][2021-08-26 19:36:45.589431][00:00:00.000651][info] WSJT-X - ForEW1   v2.3.0 0c42df  by K1JT, G4WJS, and K9AN - Program startup

[SYSLOG][2021-08-26 19:36:45.600925][00:00:00.011551][info] locale: language: English script: Latin country: United States ui-languages: en-US

[SYSLOG][2021-08-26 19:36:45.600925][00:00:00.011693][info] Loaded base translation file from :/Translations based on language en

[SYSLOG][2021-08-26 19:36:45.600925][00:00:00.011706][info] Loaded translation file from :/Translations based on language en

[SYSLOG][2021-08-26 19:36:45.773848][00:00:00.184741][info] shmem size: 48275456

[RIGCTRL][2021-08-26 19:36:45.790833][00:00:00.202356][info] Hamlib version: Hamlib 4.2~git

[SYSLOG][2021-08-26 19:36:46.758740][00:00:01.169987][warning] QObject::connect: No such signal QStatusBar::clicked(bool)

[SYSLOG][2021-08-26 19:36:46.758740][00:00:01.170010][warning] QObject::connect:  (sender name:   'statusBar')

[SYSLOG][2021-08-26 19:36:46.758740][00:00:01.170016][warning] QObject::connect:  (receiver name: 'MainWindow')

[SYSLOG][2021-08-26 20:38:59.393995][01:02:13.769695][warning] Detected dropped audio source samples: 864 (0.018 S)

[SYSLOG][2021-08-26 21:18:29.500844][01:41:43.856051][warning] Detected dropped audio source samples: 5808 (0.121 S)

[RIGCTRL][2021-08-26 22:20:36.965072][02:43:51.286163][error] failed to send command:Socket is not connected

[RIGCTRL][2021-08-26 22:20:36.969374][02:43:51.290331][error] failed:Socket is not connected

[SYSLOG][2021-08-26 22:20:36.969737][02:43:51.290717][error] handle_transceiver_failure: reason: DX Lab Suite Commander send command failed "CmdGetFreq": Socket is not connected

[RIGCTRL][2021-08-26 22:20:40.605028][02:43:54.926127][error] CmdGetFreqfailed to read reply:The remote host closed the connection

[RIGCTRL][2021-08-26 22:20:40.605028][02:43:54.926201][error] failed:Socket is not connected

[SYSLOG][2021-08-26 22:20:40.605028][02:43:54.926223][error] handle_transceiver_failure: reason: DX Lab Suite Commander send command "CmdGetFreq" read reply failed: The remote host closed the connection

[RIGCTRL][2021-08-26 22:22:42.649883][02:45:56.970052][error] CmdGetFreqretries exhausted

[RIGCTRL][2021-08-26 22:24:42.651224][02:47:56.970548][error] CmdSendTxretries exhausted

[SYSLOG][2021-08-26 22:24:42.696957][02:47:57.016656][info] Log Finish

 

 

Pete Chamalian, W1RM

W1rm@...

 


locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Bill Somerville
 

On 26/08/2021 21:08, Jim Pennino via groups.io wrote:
As the maximum system clock error is less than 100 microseconds, I doubt it is a factor.

Out of curiosity, how much effort does WSJTX expend on decoding signals more than a couple of hundred milliseconds off?

Too bad WSJTX isn’t more multithreaded what with 8 core being a low end system these days.

I guess I will forget about Raspberry Pi for this unless WSJTX becomes more multithreaded.
Hi Jim,

the decoding effort on all candidate signals is equivalent, obviously some that are easy to decode are processed much more quickly than others. The time offset is only relevant for choosing candidate signals to attempt to decode.

100 us off is not an issue, but an SNTP time application may be making time corrections regularly to achieve that if the update interval is set too short, and the undisiplined system clock drifts significantly. Time steps from SNTP applications cause audio stream discontinuities that can disrupt a whole decoding period.

73
Bill
G4WJS.


locked Re: Spotted on wrong gridsquare? #IssueReport #WSPR

Bill Somerville
 

On 26/08/2021 21:00, Ryan Trullinger (KC0QNB) wrote:
I had the same issue the other day DN90 is correct where did the other grid square come from?
Hi Ryan,

possibly someone in JO22li square has a call that is a hash collision with yours. As they are sending a 6-character grid they will be sending message pairs with a hash code in the second of each pair. I see a spot of your station with a 6-character grid also, do you have the "Prefer Type 1 Messages" option unchecked or checked?

73
Bill
G4WJS.


locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Jim Pennino
 

As the maximum system clock error is less than 100 microseconds, I doubt it is a factor.

Out of curiosity, how much effort does WSJTX expend on decoding signals more than a couple of hundred milliseconds off?

Too bad WSJTX isn’t more multithreaded what with 8 core being a low end system these days.

I guess I will forget about Raspberry Pi for this unless WSJTX becomes more multithreaded.


locked Re: Spotted on wrong gridsquare? #IssueReport #WSPR

Ryan Trullinger (KC0QNB)
 

I had the same issue the other day DN90 is correct where did the other grid square come from?


locked Re: Not sure if this a known problem or not #AudioIssues

William Smith
 

If your antenna system gets worse from loose or wet or corroded connections, you might have more RFI in your shack than you had last week. 

73, Willie N1JBJ



On Aug 26, 2021, at 2:15 PM, colin via groups.io <csaggers1@...> wrote:



Many thanks all for your suggestions

I have added 2 clip on ferrites to the usb cable at the scu-17 end and all now appears ok?

I have no idea why it should go from being fine to being plagued with RFI,that is beyond me ,but I`m now a happy bunny.

Thanks to all for their help

Colin

G0osk

 

 

Sent from Mail for Windows

 

From: Pietro Molina
Sent: 26 August 2021 12:09
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Not sure if this a known problem or not #AudioIssues

 

Colin, I had the same problem after upgrading WSJT-X to 2.4 with my FT817. Unexpectedly I resolved using 38.400 as baud rate instead of 9.600 for CAT, and now I'm using 2.5 beta. I think there is some time-out problem somewhere.

Pietro I2OIM

 





locked Re: Not sure if this a known problem or not #AudioIssues

colin
 

Many thanks all for your suggestions

I have added 2 clip on ferrites to the usb cable at the scu-17 end and all now appears ok?

I have no idea why it should go from being fine to being plagued with RFI,that is beyond me ,but I`m now a happy bunny.

Thanks to all for their help

Colin

G0osk

 

 

Sent from Mail for Windows

 

From: Pietro Molina
Sent: 26 August 2021 12:09
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Not sure if this a known problem or not #AudioIssues

 

Colin, I had the same problem after upgrading WSJT-X to 2.4 with my FT817. Unexpectedly I resolved using 38.400 as baud rate instead of 9.600 for CAT, and now I'm using 2.5 beta. I think there is some time-out problem somewhere.

Pietro I2OIM

 


locked Re: Is there a standard frequency used for F&H #FoxAndHound #FT8

Norman Heyen
 

Thanks everyone. This is sort of what I expected. I'll look into the other software mentioned. I guess I have to start actively monitoring the DX expeditions and get serious about it.

73,
Norman
KC9NVN

On Thu, Aug 26, 2021 at 11:37 AM Kermit Lehman via groups.io <ktfrog007=aol.com@groups.io> wrote:
This is one situation where keeping track of spots on clusters really pays off. Someone will likely post any F/H operation. It's difficult otherwise to keep track of all the bands and frequencies as well as propagation and DXpedition operating practices.


I use DX Monitor, which offers a lot of convenient sifting and sorting features.  It's shareware with a nominal one time fee. Well worth it, IMO.


Spots  from RBN and PSKReporter are always helpful, too, but they may not report on unusual operating frequencies.


73,

Ken, AB1J


-----Original Message-----
From: neil_zampella <neilz@...>
To: main@WSJTX.groups.io
Sent: Thu, Aug 26, 2021 3:22 pm
Subject: Re: [WSJTX] Is there a standard frequency used for F&H #FoxAndHound #FT8

Not really, although there are some that are frequently used, but to eliminate QRM, most DXPeditions will list on a webpage what frequencies they will be using.

Neil, KN3ILZ
On 8/26/2021 9:06 AM, Norman Heyen wrote:
I've looked and not found an answer. Is there a common frequency that DX expeditions use for Fox & Hound operations? 
73, 
Norman 
KC9NVN


    
  







locked Re: Is there a standard frequency used for F&H #FoxAndHound #FT8

Kermit Lehman
 

This is one situation where keeping track of spots on clusters really pays off. Someone will likely post any F/H operation. It's difficult otherwise to keep track of all the bands and frequencies as well as propagation and DXpedition operating practices.


I use DX Monitor, which offers a lot of convenient sifting and sorting features.  It's shareware with a nominal one time fee. Well worth it, IMO.


Spots  from RBN and PSKReporter are always helpful, too, but they may not report on unusual operating frequencies.


73,

Ken, AB1J


-----Original Message-----
From: neil_zampella <neilz@...>
To: main@WSJTX.groups.io
Sent: Thu, Aug 26, 2021 3:22 pm
Subject: Re: [WSJTX] Is there a standard frequency used for F&H #FoxAndHound #FT8

Not really, although there are some that are frequently used, but to eliminate QRM, most DXPeditions will list on a webpage what frequencies they will be using.

Neil, KN3ILZ
On 8/26/2021 9:06 AM, Norman Heyen wrote:
I've looked and not found an answer. Is there a common frequency that DX expeditions use for Fox & Hound operations? 
73, 
Norman 
KC9NVN






locked Re: Not So New Subject I suspect - WSJT-X v2.4.0 Will not transmit #Cat_RigControl #transmit

Dick Bingham
 

Greeting to everyone

I used Miguel's - ea4bas -  suggestions and now WSJT-X v2.4.0 works fine
the following settings.



Thank you to everyone who has assisted me in solving this problem.

73  Dick - w7wkr


locked Re: Is there a standard frequency used for F&H #FoxAndHound #FT8

neil_zampella
 

Not really, although there are some that are frequently used, but to eliminate QRM, most DXPeditions will list on a webpage what frequencies they will be using.

Neil, KN3ILZ

On 8/26/2021 9:06 AM, Norman Heyen wrote:
I've looked and not found an answer. Is there a common frequency that DX expeditions use for Fox & Hound operations? 
73, 
Norman 
KC9NVN




locked Re: Auto Seq Changes DX Call ? #logging

 

It looks like the TNX 2BND 73 message has been coded into a standard <CALL> <CALL> 73 format. WSJT-X is not going to know that it’s not a real call.

 

I don’t know if there’s a way for WSJT-X to be told not to.  It’s only 11 characters so there could be a way for the sender add one or two characters – say “TNX 2BND 73SK”

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Bob KM4RL
Sent: 26 August 2021 14:42
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Auto Seq Changes DX Call ? #logging

 

Here is a screenshot.

Thanks,
Bob KM4RL

 


--
73 Phil GM3ZZA


locked Is there a standard frequency used for F&H #FoxAndHound #FT8

Norman Heyen
 

I've looked and not found an answer. Is there a common frequency that DX expeditions use for Fox & Hound operations? 
73, 
Norman 
KC9NVN


locked Re: After upgrade to WSJT-X 2.4.0, an IC-7600 no longer changes bands on SPE Expert 1K-FA power amplifier #Cat_RigControl

Don Melcher
 


locked Re: Auto Seq Changes DX Call ? #logging

Bob KM4RL
 

Here is a screenshot.

Thanks,
Bob KM4RL


locked Re: #txaudio #linux WSJT-X No TX audio issue #txaudio #linux

KM4OVZ
 
Edited

do not use the system default audio devices for transmitter Tx audio
Well I did try selecting the actual device as well but the effect is the same. Default output works fine. It's gotta be an bug on WSJT-X's end because it works fine on the windows version.

10061 - 10080 of 38068