Date   

locked Re: #FT8 How to restore grid to 'needed' status for alerts #FT8

Pietro Molina
 

Well, the solution by Reino is more elegant.. you won't loose the qso, but only restore the grid as unworked.

73

I2OIM

Pietro (via Tablet)


Il lun 19 lug 2021, 13:10 Reino Talarmo <reino.talarmo@...> ha scritto:

Bob, look at that call in the wsjtx_log.adi file and delete it.

Pietro I2OIM

Hi,

There are two more sensible or logical solutions as well.

If the actual grid is known, replace the current by it, otherwise change gridsquare length to “0” and delete the current one.
In Both solutions the grid is “not worked” on the WSJT-X point of view. Well, a Rescan or WSJT-X closing and opening is needed to update PC knowledge.

73, Reino OH3mA





locked Re: #FT8 How to restore grid to 'needed' status for alerts #FT8

Reino Talarmo
 

Bob, look at that call in the wsjtx_log.adi file and delete it.

Pietro I2OIM

Hi,

There are two more sensible or logical solutions as well.

If the actual grid is known, replace the current by it, otherwise change gridsquare length to “0” and delete the current one.
In Both solutions the grid is “not worked” on the WSJT-X point of view. Well, a Rescan or WSJT-X closing and opening is needed to update PC knowledge.

73, Reino OH3mA


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

Stephen Malyszka
 

Thanks to all who have responded. It looks like WSJT-X ver 2.5.0-rc3 has solved the problem. I appreciate your help in resolving this issue.

Steve
AG2J
Frankford Radio Club


locked Re: #Transmit #K4 - Split Operation -> DATA-R Mode on Elecraft K4 #transmit #Elecraft

Bill Somerville
 

On 19/07/2021 02:38, Rick Tavan wrote:
I'm running WSJT-X 2.4.0 on a Dell XPS-13 laptop, running Windows 10 Home 19.09 connected to an Elecraft K4 in DATA mode. Settings | Radio | Split Operation = Rig in order to position the transmit tone in the passband. I believe SPLIT was working a few WSJT-X releases ago. Now, when I double-click a CQ in the left-hand window, it puts the K4 VFO B into DATA-R mode ("reverse") and the K4 complains on its screen that that type of split mode isn't allowed. I suppose it also returns an error to WSJT-X because it then refrains from using SPLIT mode. Instead, it transmits on VFO A which remains at the bottom of the band. I'm pretty sure this was introduced in a recent release of WSJT-X. Any thoughts?

Thanks & 73,

/Rick N6XI
Hi Rick,

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

73
Bill
G4WJS.


locked Re: #JT9+JT65 combined menu option

Reino Talarmo
 

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.

Bill,
Just an observation for same reason the current release notes no more state the removal. JT9 is mentioned last time in V2.3.0.
Reino


locked Re: #Transmit #K4 - Split Operation -> DATA-R Mode on Elecraft K4 #transmit #Elecraft

ve3ki
 

Two possible work-arounds:

1. In the WSJT-X settings, set Mode to None so WSJT-X won't try to change the rig's mode.

2. In the WSJT-X settings, for Split Operation use Fake It instead of Rig, so WSJT-X won't try to use VFO B.

73,
Rich VE3KI


On Sun, Jul 18, 2021 at 11:02 PM, Rick Tavan wrote:
I'm running WSJT-X 2.4.0 on a Dell XPS-13 laptop, running Windows 10 Home 19.09 connected to an Elecraft K4 in DATA mode. Settings | Radio | Split Operation = Rig in order to position the transmit tone in the passband. I believe SPLIT was working a few WSJT-X releases ago. Now, when I double-click a CQ in the left-hand window, it puts the K4 VFO B into DATA-R mode ("reverse") and the K4 complains on its screen that that type of split mode isn't allowed. I suppose it also returns an error to WSJT-X because it then refrains from using SPLIT mode. Instead, it transmits on VFO A which remains at the bottom of the band. I'm pretty sure this was introduced in a recent release of WSJT-X. Any thoughts?
 
Thanks & 73,
 
/Rick N6XI
 
--
--

Rick Tavan
Truckee and Saratoga, CA


locked Re: #FT8 How to restore grid to 'needed' status for alerts #FT8

Pietro Molina
 

Bob, look at that call in the wsjtx_log.adi file and delete it.

Pietro I2OIM


locked Re: Operating portable #WSJTX_config #FT8

Jim Shorney
 

See section 7.5 of the user's manual on Nonstandard Callsigns.

73

-Jim
NU0C

On Sun, 18 Jul 2021 20:34:12 -0700
"Dana Roode K6NR" <dana.roode@...> wrote:

Thanks Jim; I realize there is no need to use a portable designation, it is just my personal preference.  However, since I can't figure out how to get WSJT-X to do it and still send the grid, on FT8 I do not use it.

I've been a ham for 52 years.

Dana


locked Re: Operating portable #WSJTX_config #FT8

Dana Roode K6NR
 

Thanks Jim; I realize there is no need to use a portable designation, it is just my personal preference.  However, since I can't figure out how to get WSJT-X to do it and still send the grid, on FT8 I do not use it.

I've been a ham for 52 years.

  Dana


locked Re: Operating portable #WSJTX_config #FT8

Jim Brown
 

On 7/18/2021 7:59 PM, Dana Roode K6NR wrote:
What am I missing?
Hi Dana,

That there is zero need to sign /7, or /P, or /M, or /R because sending our grid provides far better information about where callers should point their beam. Such designations are not illegal, but not required, and except for certain contests that may require them for scoring purposes, there's rarely a good reason to use them.

I'm old enough to remember the FCC changing the regs so that such designators were not required.

73, Jim K9YC


locked Operating portable #WSJTX_config #FT8

Dana Roode K6NR
 

Apologies if this is a dumb question, something I've never figured out.

When I operate portable on FT8 with WSJT-X I'd like to set my call appropriately - K6NR/7.  When I do this the CQ string omits the grid square; IE CQ K6NR/7 rather than CQ K6NR/7 DM35.  However I see other stations operating portable and they do send their grid in the CQ.

What am I missing?

  Dana, K6NR


locked #Transmit #K4 - Split Operation -> DATA-R Mode on Elecraft K4 #transmit #Elecraft

Rick Tavan
 

I'm running WSJT-X 2.4.0 on a Dell XPS-13 laptop, running Windows 10 Home 19.09 connected to an Elecraft K4 in DATA mode. Settings | Radio | Split Operation = Rig in order to position the transmit tone in the passband. I believe SPLIT was working a few WSJT-X releases ago. Now, when I double-click a CQ in the left-hand window, it puts the K4 VFO B into DATA-R mode ("reverse") and the K4 complains on its screen that that type of split mode isn't allowed. I suppose it also returns an error to WSJT-X because it then refrains from using SPLIT mode. Instead, it transmits on VFO A which remains at the bottom of the band. I'm pretty sure this was introduced in a recent release of WSJT-X. Any thoughts?

Thanks & 73,

/Rick N6XI

--
--

Rick Tavan
Truckee and Saratoga, CA


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

Tony Collett
 

No issues with my K3 using V2.4 Steve.

Only error I sometimes have has been constant over many versions. If I have used the K3 on CW on a band before I select that band via WSJT I might have an offset equivalent to my chosen CW pitch. So I might see 10.136.70 instead of 10.136.00 for example. Reselecting the band clears it but I don't always notice it immediately.

GL
Tony G4NBS


locked Re: Audio CODEC required changes #AudioIssues

Chris Levingston VK5SA
 

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

13121 - 13140 of 39791