Date   

locked Re: Audio CODEC required changes #AudioIssues

Chris Levingston
 

Thanks, Cliff - will try.

73s

Chris    VK5SA


locked Re: #IC-705 and #WSJT-X crashing #Icom #wsjt-x

Michael Black
 

What what error is in the "Details" of the WSJTX error box?

Mike W9MDB




On Sunday, July 18, 2021, 05:25:02 PM CDT, pthorpe <pthorpe@...> wrote:


[Edited Message Follows]

 I am using WSJT-X as follows:
 
IC-705 in WLAN
MS Surface Pro 3 connected via same WLAN
Using ICOM RS-BA-1 software
I am not using USB cable
All of these work perfectly and establish a good connection
 
I start WSJT-X configured for the correct virtual COM and VIrtual audio provided by the connection to RS-BA-1 software
Every time I start from scratch it all works perfectly.
 
BUT . . . the second I manually spin the 705 frequency dial WSJT-X instantly disconnects from the CAT. Other manual adjustments on the 705 will do the same.
 
When I try to re-connect it sends all kinds of CAT errors but audio is still connected
To get it working again I have to power everything off.and start all over.
 
Thanks . . . grateful for any help on this one
73 K0PLT Peter




locked Re: WSJT-X 2.4.0 - Kenwood TS890S Split Operation Issue #Cat_RigControl

Bill Somerville
 

On 18/07/2021 22:20, Bill Somerville wrote:
On 18/07/2021 14:42, Fred (G4XWM) via groups.io wrote:
Hi Bill,

Hopefully this is what you need.
Many thanks for your help with this.
As before please let me know if you need any other info.

73
Fred
G4XWM

Hi Fred,

thanks for that. It looks like you had the rig set with VFO B as the current VFO before you started WSJT-X. If so, can you try another test run with VFO A set as current before starting WSJT-X. I would like to see how Hamlib behaves in that case. In theory it should not matter which VFO on your rig is selected for Rx and Tx but I suspect Hamlib is not handling it correctly.

73
Bill
G4WJS.

Hi again Fred,

please can you send me the new log directly (g4wjs <at> classdesign <dot> com) so that it does not use up the limited attachment storage space on the free plan Groups.io list.

73
Bill
G4WJS.


locked Re: WSJT-X 2.4.0 - Kenwood TS890S Split Operation Issue #Cat_RigControl

Bill Somerville
 

On 18/07/2021 14:42, Fred (G4XWM) via groups.io wrote:
Hi Bill,

Hopefully this is what you need.
Many thanks for your help with this.
As before please let me know if you need any other info.

73
Fred
G4XWM
Hi Fred,

thanks for that. It looks like you had the rig set with VFO B as the current VFO before you started WSJT-X. If so, can you try another test run with VFO A set as current before starting WSJT-X. I would like to see how Hamlib behaves in that case. In theory it should not matter which VFO on your rig is selected for Rx and Tx but I suspect Hamlib is not handling it correctly.

73
Bill
G4WJS.


locked Re: #JT9+JT65 combined menu option

Bill Somerville
 

On 18/07/2021 21:57, Karza wrote:
Panos,

Hi the menu mode contains already 12 selections I am sure there will not be any problem with one more so, please bring back the old  JT9+JT65 selection . I didn't understand why dissapeared; I am sure that the authors when add new modes can avoid to delete old selections 73.


It's not about the number of menu options. The mode just was not used all that much and it was difficult to maintain, so the developers decided to drop it.

I don't believe it will ever come back.

All is not lost however. I f you just cannot live without the 'JT9+JT65' mode you can install WSJT-X version 2.3.1 onto a separate folder than your current version.

73's de Kari, oh2gqc

P.S: I sure hope one of the developers would confirm the death of 'JT9+JT65' mode.

Ohterwise this thread will run till doomsday...

Karza and Panos,

I do not see what else can be said, the reasons were stated clearly in the release notes for the version when Dual JT9+JT65 mode was removed.

73
Bill
G4WJS.


locked Re: #JT9+JT65 combined menu option

Karza
 

Panos,

Hi the menu mode contains already 12 selections I am sure there will not be any problem with one more so, please bring back the old  JT9+JT65 selection . I didn't understand why dissapeared; I am sure that the authors when add new modes can avoid to delete old selections 73.

It's not about the number of menu options. The mode just was not used all that much and it was difficult to maintain, so the developers decided to drop it.

I don't believe it will ever come back.

All is not lost however. I f you just cannot live without the 'JT9+JT65' mode you can install WSJT-X version 2.3.1 onto a separate folder than your current version.

73's de Kari, oh2gqc

P.S: I sure hope one of the developers would confirm the death of 'JT9+JT65' mode.

Ohterwise this thread will run till doomsday...


locked Re: When Callsign/8 portable is used the Grid Locator is not sent in a CQ

Jim Brown
 

On 7/18/2021 12:48 PM, Karl Beckman wrote:
Since WA5MD Tim's stated question "Is this not the proper way to log these vacation contacts" is about uploading to LoTW, he might also consider asking in the LoTW Groups.io topic, or at the ARRL web site, since they operate the LoTW program.
For over 45 years.Part 97 of the FCC Rules has nether required nor mentioned the /P ID format. The generally accepted method of identifying when operating within the USA but away from your home QTH is your assigned call with no added prefix or suffix.  The message formats utilized in WSJTx FT8 do not allow for insertion of random free text characters (such as /P), but when using WSJTx digital modes you do send your current grid square. Logging enhancement programs such as JT Alert or GridTracker DO check the grid square when qualifying a true duplicate contact.
Exactly right. JTAlert adds the capability to automatically log to several general logging programs. I've used one of them, DXKeeper, since getting back on the air in 2003. It is VERY good at keeping track of details like this by establishing a Station Location which we can assign to any QSO or group of QSOs, and which are then used to upload to LOTW. It's FREE, and the author, AA6YQ, is one of those who made LOTW work faster several years ago. DXKeeper is also great for keeping track of all sorts of awards, and even organizes DXCC applications in a form that makes it easy to submit to ARRL.

73, Jim K9YC

73, Jim K9YC


locked Re: When Callsign/8 portable is used the Grid Locator is not sent in a CQ

Karl Beckman WA8NVW - NNV5BH
 

Since WA5MD Tim's stated question "Is this not the proper way to log these vacation contacts" is about uploading to LoTW, he might also consider asking in the LoTW Groups.io topic, or at the ARRL web site, since they operate the LoTW program.
 
For over 45 years.Part 97 of the FCC Rules has nether required nor mentioned the /P ID format.  The generally accepted method of identifying when operating within the USA but away from your home QTH is your assigned call with no added prefix or suffix.  The message formats utilized in WSJTx FT8 do not allow for insertion of random free text characters (such as /P), but when using WSJTx digital modes you do send your current grid square.  Logging enhancement programs such as JT Alert or GridTracker DO check the grid square when qualifying a true duplicate contact. 
--
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io


locked Re: #JT9+JT65 combined menu option

Panos
 

Hi the menu mode contains already 12 selections I am sure there will not be any problem with one more so, please bring back the old  JT9+JT65 selection . I didn't understand why dissapeared; I am sure that the authors when add new modes can avoid to delete old selections 73.


locked Re: Copying Windows config files and logs to #FT8 #install

Reid Lanham
 

Ok, thank you Bill. I’ll check it out when I get home later. I’ve done it between 2 Windows PCs, just never with Linux.   73!


locked Re: #BugReport #logging Failure to log contact correctly #IssueReport #logging

Jim Brown
 

On 7/18/2021 9:07 AM, Philip Rose via groups.io wrote:
Normally I wait for the QSO partner to indicate they received my RR73 before logging.
I log as soon as I receive or send RRR or RR73. I will resend RRR or RR73 if the other station sends my report and R again. I learn whether the other station considers the QSO complete when he does or does not appear as an LOTW confirmation.

73, Jim K9YC


locked Re: #BugReport #logging Failure to log contact correctly #IssueReport #logging

Bill Somerville
 

Hi Phil,

have you tried unchecking the WSJT-X settings option "Settings->Reporting->Clear DX call and grid after logging"?

73
Bill
G4WJS.

On 18/07/2021 19:17, Philip Rose via groups.io wrote:

Thanks Bill,

 

Does that mean if I log the first QSO, then click on the caller to start the next it will work as I want? That means I won’t start the new QSO until a second or two into the next slot. I have issues with not being able to double click accurately enough.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Bill Somerville
Sent: 18 July 2021 18:18
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #BugReport #logging Failure to log contact correctly

 

On 18/07/2021 17:07, Philip Rose via groups.io wrote:

> Normally I wait for the QSO partner to indicate they received my RR73 before logging. If they send me the 73, and at the same time I get called by a third party, I will double click on the third party to initiate a QSO with them, then log the first QSO. The new QSO fails to set the DxCall and DxGrid values and report values. When I log this QSO I have to check what info is missing.

> Also when I see a DxCall value in my logger, I display the position on DxAtlas (either the DxGrid or the centre of the prefix area). As this is not present in this circumstance, I can't do this.

> -- 73 Phil GM3ZZA

 

Hi Phil,

 

WSJT-X only supports automatic filling in of proposed log entry fields

for a basic sequential logging process, i.e. you must complete one QSO,

including logging, before starting the next. Obviously that cannot

always happen due to possibly abandoned QSOs being revived, in that case

you must check the Loq QSO fields and fill in any missing or incorrect

information manually.

 

73

Bill

G4WJS.

 

 


--
73 Phil GM3ZZA



locked Re: #BugReport #logging Failure to log contact correctly #IssueReport #logging

 

Thanks Bill,

 

Does that mean if I log the first QSO, then click on the caller to start the next it will work as I want? That means I won’t start the new QSO until a second or two into the next slot. I have issues with not being able to double click accurately enough.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: Bill Somerville
Sent: 18 July 2021 18:18
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #BugReport #logging Failure to log contact correctly

 

On 18/07/2021 17:07, Philip Rose via groups.io wrote:

> Normally I wait for the QSO partner to indicate they received my RR73 before logging. If they send me the 73, and at the same time I get called by a third party, I will double click on the third party to initiate a QSO with them, then log the first QSO. The new QSO fails to set the DxCall and DxGrid values and report values. When I log this QSO I have to check what info is missing.

> Also when I see a DxCall value in my logger, I display the position on DxAtlas (either the DxGrid or the centre of the prefix area). As this is not present in this circumstance, I can't do this.

> -- 73 Phil GM3ZZA

 

Hi Phil,

 

WSJT-X only supports automatic filling in of proposed log entry fields

for a basic sequential logging process, i.e. you must complete one QSO,

including logging, before starting the next. Obviously that cannot

always happen due to possibly abandoned QSOs being revived, in that case

you must check the Loq QSO fields and fill in any missing or incorrect

information manually.

 

73

Bill

G4WJS.

 

 


--
73 Phil GM3ZZA


locked Re: Contest mode? #ContestMode

Bill Somerville
 

On 18/07/2021 17:25, w5ec wrote:
Sometimes I am answered by several stations at the same time. In order to contact as many as possible in a short time,
can I go to a contest mode to shorten the contact time?
Bill W5EC
Hi Bill,

the contest modes in WSJT-X require all parties to switch to contest mode, with one minor exception that I know of QSOs will not progress without user intervention unless both ends have mutually switched to the right operations mode. This is one important reason why we recommend that contest organizers, who require exchanges supported by the WSJT-X special operating modes, include in their rules that contest QSOs should not take place on regular FT8, FT4, or MSK144 watering-hole frequencies.

73
Bill
G4WJS.


locked Re: #BugReport #logging Failure to log contact correctly #IssueReport #logging

Bill Somerville
 

On 18/07/2021 17:07, Philip Rose via groups.io wrote:
Normally I wait for the QSO partner to indicate they received my RR73 before logging. If they send me the 73, and at the same time I get called by a third party, I will double click on the third party to initiate a QSO with them, then log the first QSO. The new QSO fails to set the DxCall and DxGrid values and report values. When I log this QSO I have to check what info is missing.

Also when I see a DxCall value in my logger, I display the position on DxAtlas (either the DxGrid or the centre of the prefix area). As this is not present in this circumstance, I can't do this.

-- 73 Phil GM3ZZA
Hi Phil,

WSJT-X only supports automatic filling in of proposed log entry fields for a basic sequential logging process, i.e. you must complete one QSO, including logging, before starting the next. Obviously that cannot always happen due to possibly abandoned QSOs being revived, in that case you must check the Loq QSO fields and fill in any missing or incorrect information manually.

73
Bill
G4WJS.


locked Re: WSJT-X rev 2.4.0 Split Operation Issue #Cat_RigControl

Bill Somerville
 

On 18/07/2021 16:46, Stephen Malyszka wrote:
At times WSJT-X does not command my radio (K3) to the WSJT-x  receive frequency after completing a transmission. The only way to return the radio to the correct receive frequency is to reselect the band frequency in the pull down menu. I'm using the latest version of windows 10 with a AMD quad core processor. I didn't see this issue on previous versions and my radio/hardware is the same.  Has anyone experienced this problem? Is this a bug or is there possibly a setting that I might have changed along the way. Any help in resolving this would be appreciated.

Steve
AG2J
Frankford Radio Club
Hi Steve,

give WSJT-X v2.5.0 RC3 a try and let us know how it goes please?

73
Bill
G4WJS.


locked Re: Disabled Xmit and 73 #FT8

Bill Somerville
 

On 18/07/2021 15:54, JJ Knight wrote:
Is this happening while still in the QSO cycle of the contact? I'm running a FT991 with 2.5.0rc3 but I had the issue that would get to the point where I'm supposed to transmit 73 back to my contact and it had disabled TX and sat there never confirming the 73. I have actually worked guys that did the same thing to them also and I never got their confirmations. If I don't see it confirmed, I don't save it.

What I did was backup all of my log files from the "C:\Users\n5mnx\AppData\Local\WSJT-X" on my Win10 Laptop, Uninstalled WSJT-X, Deleted all of the old folders left behind including the "C:\Users\n5mnx\AppData\Local\WSJT-X" folder.

Then I reinstalled 2.5.0rc3, dropped all my logs back into the "C:\Users\n5mnx\AppData\Local\WSJT-X" folder and she came up running clean, and it corrected a whole bunch of weird multi-installation issues I was having with the scrolling and text positioning of the receive window and the qso windows. Anyway that fixed my 73 skipping issue.
JJ
N5MNX
AR EM34WJ
JJ,

confirming a 73 message is not required and is in fact futile. Please read up on the Two Generals' Problem, which is exactly what you would need a solution to if you wish to confirm a 73 message:

https://en.wikipedia.org/wiki/Two_Generals%27_Problem

73
Bill
G4WJS.


locked Re: Audio CODEC required changes #AudioIssues

Cliff Fox (KU4GW)
 

Hi Chris,
               I've been using a freeware app called SoundVolumeView that allows me to save my audio configurations in separate files named for whichever rig model I save them for and then I can choose between my FT-1000MP Mark-V, FT-897D, or FT-991A audio settings config file before or after I start the rig control software whether it be Ham Radio Deluxe or flRig.  I first go to the SoundVolumeView icon that appears near the PC clock and I right click it and tell it which ever saved audio config file I choose from the ones I've saved and it loads it and works great on Windows 10 version 10.0.19042 (Build 19042). You can download the latest version, SoundVolumeView v2.23, in either a 32-bit or 64-bit version at https://www.nirsoft.net/utils/sound_volume_view.html  Scroll to the bottom of the page for the download links. NirSoft says it works with Windows 10, Windows 8, and Windows 7. Hope this may be helpful to you.

Very 73,
Cliff, KU4GW

 


locked Re: Copying Windows config files and logs to #FT8 #install

Bill Somerville
 

On 18/07/2021 14:36, Reid Lanham wrote:
I have been using WSJT-X for FT8 on Win10 for many years, and now I want to run it on Linux.  I've got another PC running Linux Mint Cinnamon, and I have WSJT-X loaded fine.  How can I copy my Win10 config and log over to Linux so that all of my settings are the same, and my contacts are properly color coded?  Thanks!
Hi Reid,

all the settings and log files are portable between platforms. The locations of the files are documented in the WSJT-X User Guide:

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.4.0.html#_file_locations

The important files are the settings file WSJT-X.ini and the main ADIF log file wsjtx_log.adi. Note that the configuration files directory on Linux and macOS systems is not the same as the log files directory, whereas on MS Windows they reside in the same directory.

73
Bill
G4WJS.


locked Contest mode? #ContestMode

w5ec
 

Sometimes I am answered by several stations at the same time. In order to contact as many as possible in a short time,
can I go to a contest mode to shorten the contact time?
Bill W5EC

11321 - 11340 of 37978