Date   

locked cty.dat file.

David Gould
 

I can't find the cty.dat file.   where is it supposed to be held?   A windows search does not come up with this file on my system.
How do I obtain and update this file?   
DT8A (South Shetland) is showing as South Korea so is not being shown as wanted.

73,
Dave  G3UEG


locked Re: Error msg

Frank IZ7AUH
 

Laurie,
I confirm, I make now some test, problem is WSJT-Z non compatible for some uders, with WSJT-X 2.4.0 no problem.... it's important investigate about this.


locked Re: Error msg

Frank IZ7AUH
 

Laurie, I am sure that the problem depends on who uses WSJT-Z with the original version of WSJT-X it does not show up


locked WajtX with DxLabs suite and second radio

Gerald Klotz
 

Good morning, I am presently running wajtx woth dxlabs suit for my ic7300. I have a new 9700 I want to use.

I have read up some and watched a few videos, but wondering if anyone has a set up like this and any pitfalls to watch out for or anything in particular to do?

I do need to sit down and read more and watch more videos because I do t get anything popping up saying the radio is connected when powered o like I do with the 7300.

once I get wajtx working I plan to throw another wrench into the mess and set this radio up for remote use via icons rs-ba1 software.

any suggestions or comments other than go to church every day to pray all goes well?

Gerry
kb9pki


locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

Andy k3wyc
 

On Sat, Apr 10, 2021 at 01:21 PM, HamApps Support (VK3AMA) wrote:
JTAlert 2.50.0 (to be released in 2 days) has a new Callsigns window, replacing the Callsign display grid embedded in the main JTAlert window.
Thanks. I'll look forward to using this new feature.

73,
Andy, k3wyc


locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

Barry VA7GEM
 

Duncan
Hoping to learn something here.
What is JA29? It is not a grid. Is
JA divided somehow that I am not aware of?
TVM
Barry


On Sat, Apr 10, 2021 at 02:40 PM, Duncan Campbell wrote:
I agree with Jim.  A case and point is: I need a particular JA prefecture, Fukui, there are only a handful of Hams in this Prefecture and the chances are very remote that I would get one of them (I keep trying anyway).  I call "CQ JA29" but I will take calls from anyone.  I am stating a preference or desire, not a rule.  Of course I am hoping that someone in Japan would pick up the phone and call a ham in Fukui to tell them that someone is looking for them.
 
My two-cents 73 Duncan, KF6ILA


locked Re: Small Dot

Jonathan
 

Thank you! Thank you! My search is over! I'm sure I saw this but glossed right over it.
Jonathan WD6BNY


locked Re: Keywords Alert does not function #FT8

asobel@...
 

Laurie

 

  1. Ok,  admit,  I did not understand the instructions
  2. Please consider adding to your database a fake, maybe negative, DXCC code for an entity called TEST decode with TEST callsign or prefix. This could detect the elusive TEST made by WSJT-X contest modes.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, April 10, 2021 11:09 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Keywords Alert does not function #FT8

 

On 10/04/2021 10:04 pm, asobel@... wrote:

I am trying to get JTAlert respond to "CQ TEST X1Xx" produced by WSJT-X FT8 contest modes. I did tick Enable Keywords Alert, inserted keywords CQ, CQ TEST, TEST and DX. Gave it blue color and Testing.wav and saved it. It does not respond for CQ which is not rare and very rarely gives  any responce. It did respond to HL2ZN, RD4HR, CQ MI0OBC and PY2XC. PY2XC was displayed in blue on the WSJT-X board and DX was displayed in blue on the JTAlert board.

What's wrong here? How do I get it working?
This is quite urgent. I need it for a contest next Saturday

Amos 4X4MF


The Keyword Alert is only used with Free-Text messages. It cannot be used with directed CQ's. This is not new and has always been the case.



de Laurie VK3AMA


locked Re: Sta te/Country #FT8

HamApps Support (VK3AMA)
 

On 11/04/2021 2:46 pm, Dave Tucker Nu4N wrote:
I am sorry Laurie I must be stupid be stupid or some . I go to settings menu and then go where?? Or where is the right click select columns menu?
Thanks

--
73 NU4N Dave

To bring up the Decodes Settings, "File -> Settings"
   
Then on the far right of the Settings window. select the Columns you want visible/hidden...
   

A much simpler solution is to simply right-click one of the existing column headers and click "Select Columns"...
   

de Laurie VK3AMA


locked Re: Sta te/Country #FT8

 

I am sorry Laurie I must be stupid be stupid or some . I go to settings menu and then go where?? Or where is the right click select columns menu?
Thanks

--
73 NU4N Dave


locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

HamApps Support (VK3AMA)
 

On 11/04/2021 7:40 am, Duncan Campbell wrote:
I agree with Jim.  A case and point is: I need a particular JA prefecture, Fukui, there are only a handful of Hams in this Prefecture and the chances are very remote that I would get one of them (I keep trying anyway).  I call "CQ JA29" but I will take calls from anyone.  I am stating a preference or desire, not a rule.  Of course I am hoping that someone in Japan would pick up the phone and call a ham in Fukui to tell them that someone is looking for them.
 
My two-cents 73 Duncan, KF6ILA

If it was me, I would try and get a list of active JAs in the prefectures that are needed and add them to the Wanted-Callsign Alert.

de Laurie VK3AMA


locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

Duncan Campbell
 

I agree with Jim.  A case and point is: I need a particular JA prefecture, Fukui, there are only a handful of Hams in this Prefecture and the chances are very remote that I would get one of them (I keep trying anyway).  I call "CQ JA29" but I will take calls from anyone.  I am stating a preference or desire, not a rule.  Of course I am hoping that someone in Japan would pick up the phone and call a ham in Fukui to tell them that someone is looking for them.
 
My two-cents 73 Duncan, KF6ILA


locked Re: Small Dot

HamApps Support (VK3AMA)
 

On 10/04/2021 10:14 pm, Larry Banks via groups.io wrote:
From the release notes:
Callsign QSL Indicators: Striped QSL indicators have been removed.
       Only flag style indicators are used. The position of the indicators is
       now fixed, Lotw in the top-left corner and Eqsl in the bottom-right corner
       of the Callsign display. This change is for both the main JTAlert window
       and the Decodes window.

73 -- Larry -- W1DYJ

FYI, the positions are changing with the new release (2.50.0). From the new release notes...
    - QSL flags: The Lotw and Eqsl flag positions on the Callsigns display
       and Decodes window are no longer changeable. They are fixed in location.
        Lotw -> bottom left of the Callsign.
        Eqsl -> bottom right of the Callsign.

de Laurie VK3AMA



locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

HamApps Support (VK3AMA)
 

On 11/04/2021 6:21 am, HamApps Support (VK3AMA) via groups.io wrote:
CW Badges

That should read CQ Badges.

de Laurie VK3AMA


locked Re: Clicking on callsign fails to initiate wsjt-x

HamApps Support (VK3AMA)
 

On 11/04/2021 3:15 am, geoff wiggins via groups.io wrote:
Sorry my error, having changed to wsjt-x 2.3.1 and then gone back to 2.3.0 because there is a problem with 2.3.1, I hadn't noticed that the UDP server settings were unchecked. All ok now.

73 Geoff.

I have seen a lot (too many) of these problems recently. For some reason, the existing UDP Server checkboxes are getting cleared following a new WSJT-X install.

de Laurie VK3AMA


locked Re: Enhancement suggestion/discussion - JTAlert directional/directed CQ

HamApps Support (VK3AMA)
 

On 10/04/2021 11:31 pm, Andy k3wyc wrote:
It is quite common for stations to call CQ and only want replies from stations meeting some specified condition e.g. CQ NA, CD ND, CQ EU, CQ ASIA, etc.   These CQ calls can be highlighted by a red box (default) which I take to imply "Warning - don't click me".

What if that CQ was actually directed at stations for which I'm in the wanted group?  In my case I'd want to know if someone called CQ AZ, CQ NA, or CQ USA.   Perhaps the simplest way to implement this would be to have the user specify the exact match criteria e.g.

Show all CQ (border color)
Show CQ not directed at me (border color)
Show CQ direct at me (border color)
Directed CQ match criteria - USA, US, NA, AZ

Would anyone else find this, or something similar, useful?

73,
Andy, k3wyc

JTAlert 2.50.0 (to be released in 2 days) has a new Callsigns window, replacing the Callsign display grid embedded in the main JTAlert window. Introduced with this new (resizable no-limit callsign display) window is the display of CW Badges and Borders. Rather than showing a generic indicator character of the old display, the word in a directed CQ is displayed in the badge. Someone calling "CQ VK" will have a badge showing "VK" overlaying the Callsign.

An example showing the 3 badge types, general CQ, 73 and directed CQs. The colored border display for each type is also user-controlled, here the 73 badge has the border disabled.


Currently there is no provision for high-lighting only user-defined direction words, that's on the todo list.

de Laurie VK3AMA


locked Re: Sta te/Country #FT8

HamApps Support (VK3AMA)
 

On 11/04/2021 2:12 am, Dave Tucker Nu4N wrote:
I forgot how I set the decode window to show the state or country.
Thanks 73
--
DAVE NU4N

File -> Settings menu, or right click the header of an existing column and use the "Select Columns" menu.

de Laurie VK3AMA


locked Re: Keywords Alert does not function #FT8

HamApps Support (VK3AMA)
 

On 10/04/2021 10:04 pm, asobel@... wrote:
I am trying to get JTAlert respond to "CQ TEST X1Xx" produced by WSJT-X FT8 contest modes. I did tick Enable Keywords Alert, inserted keywords CQ, CQ TEST, TEST and DX. Gave it blue color and Testing.wav and saved it. It does not respond for CQ which is not rare and very rarely gives  any responce. It did respond to HL2ZN, RD4HR, CQ MI0OBC and PY2XC. PY2XC was displayed in blue on the WSJT-X board and DX was displayed in blue on the JTAlert board.

What's wrong here? How do I get it working?
This is quite urgent. I need it for a contest next Saturday

Amos 4X4MF

The Keyword Alert is only used with Free-Text messages. It cannot be used with directed CQ's. This is not new and has always been the case.



de Laurie VK3AMA


locked Re: Keywords Alert does not function #FT8

asobel@...
 

Laurie

 

A minute ago I got on 40m   PD7LJ  displayed in blue on the WSJT-X board and CQ  displayed in blue on the JTAlert board and same  on 20m F1SEN with CQ.

What does it mean?

 

Amos 4X4MF

==========================================================================================================

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of asobel@...
Sent: Saturday, April 10, 2021 3:04 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Keywords Alert does not function #FT8

 

Laurie

I am trying to get JTAlert respond to "CQ TEST X1Xx" produced by WSJT-X FT8 contest modes. I did tick Enable Keywords Alert, inserted keywords CQ, CQ TEST, TEST and DX. Gave it blue color and Testing.wav and saved it. It does not respond for CQ which is not rare and very rarely gives  any responce. It did respond to HL2ZN, RD4HR, CQ MI0OBC and PY2XC. PY2XC was displayed in blue on the WSJT-X board and DX was displayed in blue on the JTAlert board.

What's wrong here? How do I get it working?
This is quite urgent. I need it for a contest next Saturday

Amos 4X4MF


locked Re: Clicking on callsign fails to initiate wsjt-x

geoff wiggins
 

Sorry my error, having changed to wsjt-x 2.3.1 and then gone back to 2.3.0 because there is a problem with 2.3.1, I hadn't noticed that the UDP server settings were unchecked. All ok now.

73 Geoff.

On 10/04/2021 17:17, Larry Banks via groups.io wrote:
Are you clicking on stations that are calling CQ?

73 -- Larry -- W1DYJ


-----Original Message----- From: geoff wiggins via groups.io
Sent: Saturday, April 10, 2021 12:11
To: Support@HamApps.groups.io
Subject: [HamApps] Clicking on callsign fails to initiate wsjt-x

Just started to use digi modes after a few weeks break and I find that
clicking on the callsign in the JTAlert window no longer initiates a qso.

Using 2.16.17 and wsjt-x 2.3.0

Any ideas why this should be? I checked the group msgs and noted that
there was a bug that caused this a few years ago but it's not that.

73 Geoff.








3301 - 3320 of 36991