On 30/05/2021 20:15, Jim Pennino via groups.io wrote:

Since wsjt-x communicates with jtalert and dxlab via udp, is it supported configuration to run wsjt-x on a linux machine communicating with jtalert and dxlab running on a windows machine?

This would be on a local, reliable, high speed network.

Hi Jim,

as far as I know there is no issue with interoperation with DX Lab Suite across the Internet, specifically with SpotCollector, all you should need to do is open the server port in your firewall (usually 2237) for incoming UDP on the machine running SpotCollector, and specify that machine's IP address in the WSJT-X "Settings->Reporting->UDP Server" field.

With JTAlert I don't think it is possible as JTAlert does several things that require access to WSJT-X files and processes of the machine it is running on.

73
Bill
G4WJS.

Since wsjt-x communicates with jtalert and dxlab via udp, is it supported configuration to run wsjt-x on a linux machine communicating with jtalert and dxlab running on a windows machine?

This would be on a local, reliable, high speed network.

On May 29, 2021, at 03:23, Mark Steele <kd2nom@...> wrote:

Checking to see if there is an anticipated update before the clock runs out on rc4.

The update came out and was announced here on 5/24/21. Look for 2.4.0 GA.

Gary - AG0N

Thanks Roger, I had previously tried both.Lowered RF Power to minimum on the 5000 which is 5 watts.  Also had tried the dummy load.  Just tried both again, no luck.

On 30/05/2021 13:18, Bill M wrote:

Bill,
I just saw your note.The responses get lost sometimes in the voluminous email text.

There is no CI-v connection to the PW-1. Just the one cable The Navigator is connected the the ACC on the 7800. I do no use rig control and HRD is used for logging only. No other changes have been made in the several years it has been working. The only change was downloading and using 2.4.

When going to FT4 and then back to FT8 then moving the dial from 070 to 074 it begins to oscillate by itself. Meaning the VFO's began going on and off the the other going on. After switching back to 2.3(not 2.3.1) it has stopped.

I hope this gives some ideas as to the area it might be affecting.
Bill

Bill,

please don't alternate replies to the list with direct replies, I cannot answer your direct replies because AT&T block mail to you from my mail server.

73
Bill
G4WJS.

And I didn’t know you could run a PW-1 and get auto band changing WITHOUT a CI-V cable to the radio. 
--
Don
W6CZ/W6ZB
DM07bk

On 30/05/2021 13:18, Bill M wrote:

Bill,
I just saw your note.The responses get lost sometimes in the voluminous email text.

There is no CI-v connection to the PW-1. Just the one cable The Navigator is connected the the ACC on the 7800. I do no use rig control and HRD is used for logging only. No other changes have been made in the several years it has been working. The only change was downloading and using 2.4.

When going to FT4 and then back to FT8 then moving the dial from 070 to 074 it begins to oscillate by itself. Meaning the VFO's began going on and off the the other going on. After switching back to 2.3(not 2.3.1) it has stopped.

I hope this gives some ideas as to the area it might be affecting.
Bill

Bill,

I don't really understand your setup, you state "I do no use rig control and HRD is used for logging only." So is WSJT-X is not using CAT control I don;t see how it can be part of your problem?

73
Bill
G4WJS.

Bill,
I just saw your note.The responses get lost sometimes in the voluminous email text.

There is no CI-v connection to the PW-1. Just the one cable The Navigator is connected the the ACC on the 7800. I do no use rig control and HRD is used for logging only. No other changes have been made in the several years it has been working. The only change was downloading and using 2.4.

When going to FT4 and then back to FT8 then moving the dial from 070 to 074 it begins to oscillate by itself. Meaning the VFO's began going on and off the the other going on. After switching back to 2.3(not 2.3.1) it has stopped.

I hope this gives some ideas as to the area it might be affecting.
Bill

On 30/05/2021 02:33, Mike Scheidt wrote:

My WSJT-X had been working fine with my Yaesu FTdx-5000 for close to a year with hundreds of QSOs.  I also use a SignaLink USB interface. I was using a version prior to ver 2.4 when my problems started a week ago.  None of my rig menu settings nor my WSJT configuration setting have been changed.  Trying to get things working again, I installed ver 2.4.  My WSJT FT-8 continued to not work normally.  i also use Dimension 4 as a time standard for my PC and the time is updated.  My problems are not on receiving FT-8, I can receive FT-8 fine.  Problems are as follows:  Auto synch is checked, but nothing sequences automatically any longer. I can transmit if I manually always select the enable button, but after every transmission, the enable red button on WSJT automatically selects itself off.  I'd also add, that 100% of the time if I select TUNE on WSJT, I do get RF out as I should.  Finally here's a typical behavior:  If I initiate a CQ by selecting the appropriate MACRO and selecting the enable button, after the CQ is sent one time, the transmission ends (as it should) and the red enable button  extinguishes and I receive a Configuration alert.  When checking the details of the Configuration alert I see the following:
Hamlib: Target VFO unaccessible
newcat c(1163): newcat_get-ptt return(0)
newcat_set freq: pttstill on....retry#0
I am stumped   I would welcome input.  Thanks in advance.
rig c(1769)rig-set freq return (12) whilesetting frequency

That sounds as if it might be RFI on the USB. Could you try doing the same test with either a dummy load or the power turned down to minimum or both and report back?

73
Roger
GW4HZA

My WSJT-X had been working fine with my Yaesu FTdx-5000 for close to a year with hundreds of QSOs.  I also use a SignaLink USB interface. I was using a version prior to ver 2.4 when my problems started a week ago.  None of my rig menu settings nor my WSJT configuration setting have been changed.  Trying to get things working again, I installed ver 2.4.  My WSJT FT-8 continued to not work normally.  i also use Dimension 4 as a time standard for my PC and the time is updated.  My problems are not on receiving FT-8, I can receive FT-8 fine.  Problems are as follows:  Auto synch is checked, but nothing sequences automatically any longer. I can transmit if I manually always select the enable button, but after every transmission, the enable red button on WSJT automatically selects itself off.  I'd also add, that 100% of the time if I select TUNE on WSJT, I do get RF out as I should.  Finally here's a typical behavior:  If I initiate a CQ by selecting the appropriate MACRO and selecting the enable button, after the CQ is sent one time, the transmission ends (as it should) and the red enable button  extinguishes and I receive a Configuration alert.  When checking the details of the Configuration alert I see the following:

Hamlib: Target VFO unaccessible
newcat c(1163): newcat_get-ptt return(0)
newcat_set freq: pttstill on....retry#0

I am stumped   I would welcome input.  Thanks in advance.
rig c(1769)rig-set freq return (12) whilesetting frequency

Jim,

Not the rig - the *COMPUTER SOUND CARD*. Mic inputs with "jack
switching" are generally looking for the presence of an electret
mic (which is the default for computers).


73,

... Joe, W4TV

The “USB Audio CODEC” devices are now gone from my device manager, and I can’t figure out how to get them back. I have tried uninstalling and reinstalling, and deleting, USB drivers several times. I have also freshly downloaded the drivers from the Yaesu web site. I have carefully followed the instructions in HRD’s FAQs on this subject and in Yaesu’s driver installation instructions, without success.

 

I use Ham Radio Deluxe for rig control and for wsjt-x control. But I cannot set it up correctly and use it, because the USB Audio CODEC devices are missing.

 

Can someone help me reinstall my CODECs? What have I done wrong? I'm wondering if there is a faulty Registry entry of some kind?

 

Bill K1NS

 

(Windows 10; Yaesu FTdx-3000 using internal CODECs; Ham Radio Deluxe 6.7.0.357; wsjt-x 2.3.0.)

Hamlib has been changed in the latest WSJTX release....

- On MS Windows WSJT-X now ships with a DLL version of the Hamlib
library, specifically Hamlib version 4.2. This should allow Hamlib
bug fixes to resolved by the user replacing the DLL with an updated
version.
I have a 7300 and did not encounter any problems with the upgrade. Did this start after your upgrade? You might try selecting a different rig in Hamlib and then re-selecting the 7300 to see if that helps or possibly try a reinstall of the current version of WSJTX.

Good Luck
Joel
AC8WS

Yes the call-b4 is in red one the windows 7 but on the Windows 10 it shows in green but no B-4 If it wasnt for JTALERT I would not know if I had worked the station B4.
--
Thanks 73's de NU4N/Dave