Date   

Re: ALL.TXT

KD7YZ Bob
 

On 6/6/2020 09:25, Kenneth Grimm wrote:
One utility that I always install on every system that I own or work on is "everything."
Thank You for posting that link Ken.
It made it a snap to find "ALL" the ALL.txt files strewn around on my system.


--
73
Bob KD7YZ
AMSAT LM #901


Re: Callsign Lookup bug in 2.2.1?

Bob G8HGN
 

Hi Paul,

Strange, are you using W10? I'm on W10 64 bit Pro.

73, Bob



On 07/06/2020 09:58, Paul Turner wrote:

That’s strange Bob. I also get the “… not in CALL3.TXT” message but I can’t look up any callsigns, even though they are all listed as expected in CALL3.TXT. Version 2.2.0 works fine.

 

73, Paul.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bob G8HGN
Sent: 07 June 2020 09:26
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Callsign Lookup bug in 2.2.1?

 

Hi Paul,

I'm not seeing that, seems to work OK. However, if the call does not have an entry, I now get a pop-up box saying "G9XYZ is not in CALL3.TXT" which I have to clear. This is annoying and rather irrelevant.

Good luck with the DX this morning.

73

Bob G8HGN

On 07/06/2020 09:19, Paul Turner wrote:

Callsign lookup does work fine on 2.2.0. I will use that for now.

 

73, Paul G4IJE.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Paul Turner
Sent: 07 June 2020 09:17
To: main@WSJTX.groups.io
Subject: [WSJTX] Callsign Lookup bug in 2.2.1?

 

Have I found a bug in the callsign "lookup" feature of version 2.2.1? If I type a callsign in the "DX Call" box and click "Lookup", the DX Grid does not appear, even though the required data is in the CALL3.TXT file. If I manually add a new callsign and locator it is retrieved correctly but only during the current session. After closing and restarting the program the data is no longer retrieved when "Lookup" is clicked.

 

I will try going back to 2.2.0 and report back soon.

 

73, Paul G4IJE.

 

Virus-free. www.avast.com

 



 


    


Re: Callsign Lookup bug in 2.2.1?

Paul Turner
 

That’s strange Bob. I also get the “… not in CALL3.TXT” message but I can’t look up any callsigns, even though they are all listed as expected in CALL3.TXT. Version 2.2.0 works fine.

 

73, Paul.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bob G8HGN
Sent: 07 June 2020 09:26
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Callsign Lookup bug in 2.2.1?

 

Hi Paul,

I'm not seeing that, seems to work OK. However, if the call does not have an entry, I now get a pop-up box saying "G9XYZ is not in CALL3.TXT" which I have to clear. This is annoying and rather irrelevant.

Good luck with the DX this morning.

73

Bob G8HGN

On 07/06/2020 09:19, Paul Turner wrote:

Callsign lookup does work fine on 2.2.0. I will use that for now.

 

73, Paul G4IJE.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Paul Turner
Sent: 07 June 2020 09:17
To: main@WSJTX.groups.io
Subject: [WSJTX] Callsign Lookup bug in 2.2.1?

 

Have I found a bug in the callsign "lookup" feature of version 2.2.1? If I type a callsign in the "DX Call" box and click "Lookup", the DX Grid does not appear, even though the required data is in the CALL3.TXT file. If I manually add a new callsign and locator it is retrieved correctly but only during the current session. After closing and restarting the program the data is no longer retrieved when "Lookup" is clicked.

 

I will try going back to 2.2.0 and report back soon.

 

73, Paul G4IJE.

 

Virus-free. www.avast.com

 



 


Re: Callsign Lookup bug in 2.2.1?

Bob G8HGN
 

Hi Paul,

I'm not seeing that, seems to work OK. However, if the call does not have an entry, I now get a pop-up box saying "G9XYZ is not in CALL3.TXT" which I have to clear. This is annoying and rather irrelevant.

Good luck with the DX this morning.

73

Bob G8HGN

On 07/06/2020 09:19, Paul Turner wrote:

Callsign lookup does work fine on 2.2.0. I will use that for now.

 

73, Paul G4IJE.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Paul Turner
Sent: 07 June 2020 09:17
To: main@WSJTX.groups.io
Subject: [WSJTX] Callsign Lookup bug in 2.2.1?

 

Have I found a bug in the callsign "lookup" feature of version 2.2.1? If I type a callsign in the "DX Call" box and click "Lookup", the DX Grid does not appear, even though the required data is in the CALL3.TXT file. If I manually add a new callsign and locator it is retrieved correctly but only during the current session. After closing and restarting the program the data is no longer retrieved when "Lookup" is clicked.

 

I will try going back to 2.2.0 and report back soon.

 

73, Paul G4IJE.

 

Virus-free. www.avast.com

 



    


Re: Callsign Lookup bug in 2.2.1?

Paul Turner
 

Callsign lookup does work fine on 2.2.0. I will use that for now.

 

73, Paul G4IJE.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Paul Turner
Sent: 07 June 2020 09:17
To: main@WSJTX.groups.io
Subject: [WSJTX] Callsign Lookup bug in 2.2.1?

 

Have I found a bug in the callsign "lookup" feature of version 2.2.1? If I type a callsign in the "DX Call" box and click "Lookup", the DX Grid does not appear, even though the required data is in the CALL3.TXT file. If I manually add a new callsign and locator it is retrieved correctly but only during the current session. After closing and restarting the program the data is no longer retrieved when "Lookup" is clicked.

 

I will try going back to 2.2.0 and report back soon.

 

73, Paul G4IJE.

 

Virus-free. www.avast.com

 


Callsign Lookup bug in 2.2.1?

Paul Turner
 

Have I found a bug in the callsign "lookup" feature of version 2.2.1? If I type a callsign in the "DX Call" box and click "Lookup", the DX Grid does not appear, even though the required data is in the CALL3.TXT file. If I manually add a new callsign and locator it is retrieved correctly but only during the current session. After closing and restarting the program the data is no longer retrieved when "Lookup" is clicked.

 

I will try going back to 2.2.0 and report back soon.

 

73, Paul G4IJE.


Virus-free. www.avast.com


Re: Tnx for the FT991 fix but ...

Bob G8HGN
 

Hi,

I use a laptop with Vista for 144 & 432. I can still make QSOs with stations who are using the new releases.

However I don't get the benefit of the new decoder or contest modes changes.

Everyday contacts are fine,  I've recently had some Es QSOs on 144 with it.

So whilst it's better to upgrade, you can still use your system for now, with limitations.

73

Bob G8HGN

On 06/06/2020 21:08, neil_zampella wrote:

There is no workaround.    The system used to create WSJT-X has dropped all XP and VISTA support.   

The fixes are:
1.  Upgrade to a newer WIndows, probably 10
2.  Replace the computer with something that can run newer versions of Windows (refurb Dells can be found for under $200)
3.  Replace Windows with a good Linux distribution.

Neil, KN3ILZ

On 6/6/2020 3:57 PM, John Kirby wrote:
... still so sad and disappointed

Is there any work around to make 2.2.x run on XP ?

John
N3AAZ

  

Virus-free. www.avg.com


    


Re: WSJT-X 2.2.1 GA Release

John -AC0XY
 

This and 2.2.0 won't install on my Ubuntu 19.10:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Ubuntu 19.10"

john@hamshack:~/Downloads$ sudo dpkg -i /home/john/Downloads/wsjtx_2.2.1_amd64.deb
[sudo] password for john:
(Reading database ... 208825 files and directories currently installed.)
Preparing to unpack .../wsjtx_2.2.1_amd64.deb ...
Unpacking wsjtx (2.2.1) over (2.1.0+repack-1) ...
dpkg: error processing archive /home/john/Downloads/wsjtx_2.2.1_amd64.deb (--install):
 trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in package wsjtx-data 2.1.0+repack-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
Processing triggers for mime-support (3.63ubuntu1) ...
Processing triggers for man-db (2.8.7-3) ...
Errors were encountered while processing:
 /home/john/Downloads/wsjtx_2.2.1_amd64.deb


FT-897 CAT control problem even WSJT-X V.2.2.1 for Windows 10(64) was installed #Cat_RigControl

rickn@...
 

Thanks for resolving of FT-991/FT-991A CAT problem.
But It does not resolve on FT-897. Error message is "riglib error Target VFO unaccessible getting frequency" and CAT testing goes into  fales(RED).
I am using VFO A at this time and conneting with SCU-17 via USB. It works well under WSJT-X V 2.1.2.
--
7L1RLL / Rick


Re: The dreaded no Transmit

Gerald Klotz
 

That’s why I suggested that be checked. If the wrong audio is ticked, it will appear that everything is working but no power output.

Gerry Klotz

On Jun 6, 2020, at 10:19 PM, Wayne Newport <wazzan1@bigpond.com> wrote:

Hi Gerald, when you click the speaker icon to go into sounds on speaker you see the various speaker alternatives including USB audio codec. The default audio speaker is Realtech (which has the green tick ) and the USB audio codec has the green telephone icon next to it. I believe that the default audio device is NOT meant to be the USB audio codec
Wayne VK4WTN


Frequency CAL for VHF/UHF/Microwave Receivers

Rich Miller
 

All:

I am going through the FCAL procedure within the users guide. I am running a ICOM IC-970H, thus have no ability to tune in WWV. Would it be advisable to use a calibrated signal source with a slight modification in the procedure, or is there another method which works?

Based on some experiments I have conducted with another station, I seem to be about 500hz High for WSPR. Of course he could be off too! In the mean time, I have simply corrected this discrepancy in the station information/offset dialog in settings. I suspect his is not the correct method, but it worked so my friend across town could decode me. Of course being 500Hz high is not good for WSPR or Scatter work, so I need to conduct a real calibration. Any pointers on how I might use the procedure with a signal generator would be appreciated.

73

Rich, AJ3G



Re: The dreaded no Transmit

Wayne Newport
 

Hi Gerald, when you click the speaker icon to go into sounds on speaker you see the various speaker alternatives including USB audio codec. The default audio speaker is Realtech (which has the green tick ) and the USB audio codec has the green telephone icon next to it. I believe that the default audio device is NOT meant to be the USB audio codec
Wayne VK4WTN 


Re: The dreaded no Transmit

Gerald Klotz
 

Wayne click on the speaker icon on the bottom task bar. Make sure you have chosen the usb not the regular speakers.

KB9pki
Gerry Klotz

On Jun 6, 2020, at 7:28 PM, Wayne Newport <wazzan1@bigpond.com> wrote:

hi all, I hope someone can help me. I just changed my shack computer (Windows 10). I downloaded the driver from the Kenwood website ok. I run wsjt-x via DXCommander. Rig control via CAT is ok. Recieve decodes just fine , keys the TX via CAT ok but there appears to be no audio reaching the Kenwood TS590s. I am seeing " USB Audio codec in Sounds (speaker) and have the level turned to maximum. In Windows settings I have 2. USB AUDIO CODEC selected for both audio device both Tx and rx . The TX level slider on the wsjt-x is also set at maximum.
The settings in the TS590s are fine as the radio still works on Tx and RX when my previous computer is reconnected.
any help would greatly be appreciated
Wayne VK4WTN


Re: The dreaded no Transmit

Wayne Newport
 

Hi Herb I will look in privacy settings I think it will be the speaker rather than microphone for TX
Cheers Wayne VK4 WTN


Re: The dreaded no Transmit

Wayne Newport
 

Thanks Bill as soon as I get home I will try the steps in the procedure and get back to the group
cheers Wayne VK4WTN


Re: The dreaded no Transmit

Herb Blue - WB8ASI
 

Check in Win10 Privacy settings that the mic is turned on for WSJTX. 73 Herb WB8ASI

On June 6, 2020 at 8:28 PM Wayne Newport <wazzan1@...> wrote:

hi all, I hope someone can help me. I just changed my shack computer (Windows 10). I downloaded the driver from the Kenwood website ok. I run wsjt-x via DXCommander. Rig control via CAT is ok. Recieve decodes just fine , keys the TX via CAT ok but there appears to be no audio reaching the Kenwood TS590s. I am seeing " USB Audio codec in Sounds (speaker) and have the level turned to maximum. In Windows settings I have  2. USB AUDIO CODEC selected for both audio device both Tx and rx . The TX level slider on the wsjt-x is also set at maximum.
 The settings in the TS590s are fine as the radio still works on Tx and RX when my previous computer is reconnected.
any help would greatly be appreciated
Wayne VK4WTN

 


Re: The dreaded no Transmit

Bill Somerville
 

On 07/06/2020 01:28, Wayne Newport wrote:
hi all, I hope someone can help me. I just changed my shack computer (Windows 10). I downloaded the driver from the Kenwood website ok. I run wsjt-x via DXCommander. Rig control via CAT is ok. Recieve decodes just fine , keys the TX via CAT ok but there appears to be no audio reaching the Kenwood TS590s. I am seeing " USB Audio codec in Sounds (speaker) and have the level turned to maximum. In Windows settings I have  2. USB AUDIO CODEC selected for both audio device both Tx and rx . The TX level slider on the wsjt-x is also set at maximum.
 The settings in the TS590s are fine as the radio still works on Tx and RX when my previous computer is reconnected.
any help would greatly be appreciated
Wayne VK4WTN

Hi Wayne,

please follow the steps in this old post on how to set Tx audio levels:

https://groups.io/g/WSJTX/message/5077

let us know if that doesn't get you up and running.

73
Bill
G4WJS.


The dreaded no Transmit

Wayne Newport
 

hi all, I hope someone can help me. I just changed my shack computer (Windows 10). I downloaded the driver from the Kenwood website ok. I run wsjt-x via DXCommander. Rig control via CAT is ok. Recieve decodes just fine , keys the TX via CAT ok but there appears to be no audio reaching the Kenwood TS590s. I am seeing " USB Audio codec in Sounds (speaker) and have the level turned to maximum. In Windows settings I have  2. USB AUDIO CODEC selected for both audio device both Tx and rx . The TX level slider on the wsjt-x is also set at maximum.
 The settings in the TS590s are fine as the radio still works on Tx and RX when my previous computer is reconnected.
any help would greatly be appreciated
Wayne VK4WTN


Re: WSJT-X 2.2.1 GA Release

Gary - AG0N
 

On Jun 6, 2020, at 13:27, Gerald Klotz <KB9PKI@gmail.com> wrote:

If so, we will still have the added frequencies until we refresh them correct?
Do remember that you can add any frequency you want to the list in less than a minute.

Gary - AG0N


moderated Re: 6m Freq?

Gary - AG0N
 

On Jun 6, 2020, at 17:23, Ted <k7trkradio@charter.net> wrote:

Did I miss the memo? I thought 50.313 was the recommended spot for WSJT 6m. Is it now 50.323 ??
Not really. A few days ago, when .313 was plugged with activity, several took to the alternate of .323. Even that got fairly full for awhile, but did manage. Surprisingly, very few showed up on .318 FT4 frequency during that time. Not sure why.

I really hate spreading out over more than one frequency, because most people don’t have band scopes to discover all that alternate traffic. I know I’m in the minority though. Interestingly, I heard nothing on 50.125. :)

Gary - AG0N

18681 - 18700 of 30118