Date   

locked Re: Release 2.50.1 - Clicking on a Called call sign does not Enable TX in Wsjtx

Michael Black
 

It's buy design in WSJT-X -- JTAlert does not control that.

JTDX on the other hand does enable TX on those.

Mike W9MDB




On Saturday, May 8, 2021, 11:20:56 AM CDT, Greg Foster <greg.foster@...> wrote:


I have just installed release 2.50.1 and I am running WSJTX 2.2.2 and when I click on a call sign that is calling me (Red) either in the call sign window or the list of stations that are calling me it changes the “active” call sign in WSJTX but does not turn on Enable TX. Whereas if I click on a station CQing it changes the active call sign in WSJTX and turns on Enable Call sign. Is this by design and if not is it configurable and where?

 

Greg Foster

VE3PJ

Cell   613-328-6538

 


locked Re: Lost Password on Ham Spots not working

Rick W7PSK
 

just like that it shows
 

On 05/08/2021 9:19 AM w7psk <w7psk@...> wrote:
 
 
I clicked lost password and got the reset link ok.  But, It said it sent a new password but
my inbox and spam box have nothing in them.  
Email seems to have not been sent, that was 15 minutes ago. I received the reset link almost instantly.

Scotty W7PSK


locked Release 2.50.1 - Clicking on a Called call sign does not Enable TX in Wsjtx

Greg Foster
 

I have just installed release 2.50.1 and I am running WSJTX 2.2.2 and when I click on a call sign that is calling me (Red) either in the call sign window or the list of stations that are calling me it changes the “active” call sign in WSJTX but does not turn on Enable TX. Whereas if I click on a station CQing it changes the active call sign in WSJTX and turns on Enable Call sign. Is this by design and if not is it configurable and where?

 

Greg Foster

VE3PJ

Cell   613-328-6538

 


locked Lost Password on Ham Spots not working

Rick W7PSK
 

I clicked lost password and got the reset link ok.  But, It said it sent a new password but
my inbox and spam box have nothing in them.  
Email seems to have not been sent, that was 15 minutes ago. I received the reset link almost instantly.

Scotty W7PSK


locked Re: JTAlert settings

Jim Denneny
 

Thanks Joe.  Got it - Jim


locked Re: JTAlert 2.50.1 Callsigns Window Blanks When Logging Contact

DAVID MM0AMW
 


Go to JT Alert main window, Settings/Manage settings or hit F2/ Logging, then scroll down the Logging options list and second from bottom make sure Clear callsigns after logging is unticked.


73 David MM0AMW




------ Original Message ------
From: "Paul" <VE3PS@...>
To: Support@HamApps.groups.io
Sent: Saturday, 8 May, 21 At 15:27
Subject: Re: [HamApps] JTAlert 2.50.1 Callsigns Window Blanks When Logging Contact

Laurie,

I installed the latest version of WSJT-X (2.3.1) at the same time as updating to this latest version of JTAlert (2.50.1). I am thrilled with version 2.50 of JTAlert and thank you for all your excellent work on it.

However, there is one problem that I have not found a solution to, namely, the JTAlert Callsigns window blanks whenever I log a contact.

My setup is configured to ask before logging a contact (to allow me to add a comment should I so desire) and, after I click okay to log the contact, when the ‘contact logged’ confirmation window pops up, the JTAlert Callsigns window blanks.

This did not occur with the previous versions of WSJT-X and JTAlert, and I often spotted a station that I wished to call while I was engaged in a contact, and I was ready to select that ‘next’ station upon contact completion. I am not able to do that now because the window blanks and I lose the opportunity until a cycle or two later.

Can you advise where I may find a setting that would prevent this blanking from occurring, or is there a potential problem with my installation?

Thank you & 73… Paul (VE3PS)


locked Re: JTAlert 2.50.1 Callsigns Window Blanks When Logging Contact

Paul
 

Laurie,

I installed the latest version of WSJT-X (2.3.1) at the same time as updating to this latest version of JTAlert (2.50.1).  I am thrilled with version 2.50 of JTAlert and thank you for all your excellent work on it.

However, there is one problem that I have not found a solution to, namely, the JTAlert Callsigns window blanks whenever I log a contact.

My setup is configured to ask before logging a contact (to allow me to add a comment should I so desire) and, after I click okay to log the contact, when the ‘contact logged’ confirmation window pops up, the JTAlert Callsigns window blanks.

This did not occur with the previous versions of WSJT-X and JTAlert, and I often spotted a station that I wished to call while I was engaged in a contact, and I was ready to select that ‘next’ station upon contact completion.  I am not able to do that now because the window blanks and I lose the opportunity until a cycle or two later.

Can you advise where I may find a setting that would prevent this blanking from occurring, or is there a potential problem with my installation?

Thank you & 73…  Paul (VE3PS)

 


locked Re: JTAlert settings

Joe Subich, W4TV
 

There is no change in the alerting capabilities. See:
Manage settings (F2) -> Alerts then configure each alert type in
the Main Window. Those settings apply to the alerts generated
(and displayed) in the Callsigns Window.

As always, read the help files - both "Open Help File" and "Open
JTAlert 2.50 features Help file - as well as the Tutorials.

73,

... Joe, W4TV

On 2021-05-08 9:52 AM, Jim Denneny wrote:
Thanks Laurie. The prior release allowed me more choices to designated "needed DXCC by band", WAZ, etc. etc.  My recollection is hazy  I recall an extensive menu of choices. A local friend called me also about this which set me searching.
Jim K7EG


locked Re: Single/double click within callsigns window not working

BOB K5HX
 

Mike,  I am using the single click option.

Bob  K5HX


locked Re: JTAlert settings

Jim Denneny
 

Thanks Laurie. The prior release allowed me more choices to designated "needed DXCC by band", WAZ, etc. etc.  My recollection is hazy  I recall an extensive menu of choices. A local friend called me also about this which set me searching.

Jim K7EG


locked Re: Single/double click within callsigns window not working

Michael Black
 

Are you using single click or double-click?

If double-click try the single-click option.

Mike W9MDB




On Saturday, May 8, 2021, 05:35:31 AM CDT, BOB K5HX via groups.io <k5hx@...> wrote:


Laurie,

I changed the UDP Port number to 2237 and still am having no luck.  As before, every so often when clicking on a callsign in the callsigns window it works.  

The JTAlert title bar does follow WSJT-X band/mode changes.  I also use Grid Tracker which is set up to use multicast (now port 2237).  However, I am not running Grid Tracker while troubleshooting this issue.

Below is the requested "Current Operating State" information:

JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.3.1   by K1JT, G4WJS, and K9AN
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\Bob\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.3.1
WSJT-X Revision        : 0e7224
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : WSJT-X
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 239.255.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema  : 3
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 53839 53639
JTAlertV2.Manager.exe : 53587 53588 53589
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Dell AC511 USB SoundBar)
[2] DELL U2414H (Intel(R) Display Audio)
[3] Navigator Transmit (2- USB Audio CODEC )
[4] DELL U2417H-4 (NVIDIA High Definition Audio)
 
 
==================================================
JTAlertV2.Manager (2.50.1.0) status
(2021-05-08 10:33:16 utc)
--------------------------------------------------
CLR Version      : 5.0.5
NET Framework    : .NET 5.0.5
Architecture     : x64 64bit
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X)
Audio            : Initialized : YES (4 output devices)
BandData         : Initialized : YES (stopped)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (K5HX)
HamQth Xml       : Initialized : YES 
QRZ Log          : Initialized : YES 
HamQth Log       : Initialized : YES 
ClubLog Log      : Initialized : YES 
Eqsl Log         : Initialized : YES 
HrdLog Log       : Initialized : YES 
DXLab DDE        : Initialized : YES
User Alert       : Initialized : YES
Updates Check    : Initialized : YES (stopped)
Environment      : Initialized : YES (started : 3600)
Maintenance      : Initialized : YES (started : 3600)
--------------------------------------------------


Thanks again for your help.

de Bob K5HX


locked Re: Resend - All Worked B4 call sign displays are Displaying Needed, but Have Been Worked. #FT8

Brian Kassel K7RE
 

Laurie:

  You asked what the source of my ADIF File is.  It was created as a new file by me from your program when I began using your program years ago.  I have since upgraded the program many times, keeping the same file.

I changed the DXCC Alert to another color from the default yellow
as you suggested.

When I select "Individual Bands" under "Wanted DXCC", NO band selection shows ANY DXCC worked on ANY band, That is the "Wanted" window displays 340.  Also this same information is reflected
When the "Rebuild All" button is clicked in the  "Rebuild Alert Database" selection the information displayed indicates the same 340 DXCC need to be worked on all bands.  The "States Needed" display seems to be correct.



locked Re: Single/double click within callsigns window not working

BOB K5HX
 

Laurie,

I changed the UDP Port number to 2237 and still am having no luck.  As before, every so often when clicking on a callsign in the callsigns window it works.  

The JTAlert title bar does follow WSJT-X band/mode changes.  I also use Grid Tracker which is set up to use multicast (now port 2237).  However, I am not running Grid Tracker while troubleshooting this issue.

Below is the requested "Current Operating State" information:

JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.3.1   by K1JT, G4WJS, and K9AN
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\Bob\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 2.3.1
WSJT-X Revision        : 0e7224
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : WSJT-X
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 239.255.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema  : 3
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 53839 53639
JTAlertV2.Manager.exe : 53587 53588 53589
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Dell AC511 USB SoundBar)
[2] DELL U2414H (Intel(R) Display Audio)
[3] Navigator Transmit (2- USB Audio CODEC )
[4] DELL U2417H-4 (NVIDIA High Definition Audio)
 
 
==================================================
JTAlertV2.Manager (2.50.1.0) status
(2021-05-08 10:33:16 utc)
--------------------------------------------------
CLR Version      : 5.0.5
NET Framework    : .NET 5.0.5
Architecture     : x64 64bit
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X)
Audio            : Initialized : YES (4 output devices)
BandData         : Initialized : YES (stopped)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (K5HX)
HamQth Xml       : Initialized : YES 
QRZ Log          : Initialized : YES 
HamQth Log       : Initialized : YES 
ClubLog Log      : Initialized : YES 
Eqsl Log         : Initialized : YES 
HrdLog Log       : Initialized : YES 
DXLab DDE        : Initialized : YES
User Alert       : Initialized : YES
Updates Check    : Initialized : YES (stopped)
Environment      : Initialized : YES (started : 3600)
Maintenance      : Initialized : YES (started : 3600)
--------------------------------------------------


Thanks again for your help.

de Bob K5HX


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode. - DEFECT Confirmed

Michael
 

Hi Laurie

I was testing the 64bit Beta version yesterday with JTDX and so far no errors. I'll be testing the same version today with WSJT-X.

73 de Michael 5p1kzx


Den 06-05-2021 kl. 22:29 skrev HamApps Support (VK3AMA):

On 7/05/2021 2:26 am, Michael wrote:

I can reproduce the eeror by just switching to Mode FT4 and then back to Mode FT8 as sson as JTAlert has reconized that mode has been changed. And that's in both JTDX and WSJT-x. After doing that switch of mode the next QSO will be logged with FT4 as submode.

73 de Michael 5p1kzx


Tnx Michael,

I have a new Beta release of JTAlert that corrects this problem.

Please try and let me know if this defect is now fixed. I am unable to test HRD logging so need reports back from users who can test.


64bit (x64)  https://dnl.HamApps.com/Beta/JTAlert.2.50.1.build.0001.Beta.Install.X64.exe
32bit (x86)  https://dnl.HamApps.com/Beta/JTAlert.2.50.1.build.0001.Beta.Install.X86.exe


de Laurie VK3AMA


locked Re: F5 Text message windows disappears

HamApps Support (VK3AMA)
 

On 8/05/2021 8:46 am, K5FNQ, ART wrote:
At times when I attempt to type text into the F5 chat window the window disappears and loses any info almost immediately.  A an exit and restart seems to help but this condition seems to keep coming back.
I am using Win10 machine.  Any ideas? Art K5FNQ

What version of JTAlert?

Is this a recent manifestation or has it always behaved this way for this JTAlert version?

What happens if you leave the Messaging window open without composing a message, does it still close unexpectedly?

de Laurie VK3AMA


locked Re: JTAlert settings

Laurie, VK3AMA
 

On 8/05/2021 12:12 pm, Jim Denneny wrote:
With latest release, the options menu seems changed and greatly reduced.  Can I bring all those old settings back with latest release?

Jim K7EG
There is no Options menu. The new 2.50.0 windows introduced the Options popup, but not Options menus.

To what are you specifically referring? Which window is affected?

de Laurie VK3AMA


locked JTAlert settings

Jim Denneny
 

With latest release, the options menu seems changed and greatly reduced.  Can I bring all those old settings back with latest release?

Jim K7EG


locked Re: Feature Suggestion Allow specifying eQSL AG activity date#FT8

Jim N6VH
 

On 5/7/2021 4:08 PM, Joe Subich, W4TV wrote:


Another related issue is that various loggers don't necessarily have
the same listing for the counties.
ADIF have standardized spelling and format (based on the USA-CA spec.).
Simply convert the input(s) to that format.

The bigger issue will be stations in "independent cities" ...

73,

   ... Joe, W4TV
Joe,

Good point. However, the adif export  for Alaska stations, for example, lists the boroughs, not the Judicial Districts, so something would need to be done to convert to Judicial Districts. I checked Log4OM, DXLab and ACLog. Of course, that doesn't address the issue of what source would be used for JTAlert to check. If that source has the counties, boroughs, etc listed as per USA-CA, then that would be useful. And I agree, the bigger issue is definitely the independent cities.

Some other posts mentioned LOTW. As you said, it is doubtful if anything will be done for USA-CA in the near (or even distant) future. For that matter, LOTW confirmations use Alaska boroughs, not Judicial Districts. It seems the only source for electronic QSLs is eQSL, which does use Judicial Districts.

73,

Jim N6VH


locked Re: Feature Suggestion Allow specifying eQSL AG activity date#FT8

Joe Subich, W4TV
 

The best solution would be for ARRL to implement a county function
in LOTW similar to what is provided for CQ WAZ and WPX.
The first issue is an agreement between CQ and ARRL to cover USA-CA.
The second issue is that ARRL has *ZERO* developer resources to work
on USA-CA support in LotW after the Board stripped all developers
from LotW and the Director of IT left.

73,

... Joe, W4TV


On 2021-05-07 6:57 PM, Pat N6PAT via groups.io wrote:
Laurie,
The file I'm using was included in a ham call lookup app. It appears to be a very clean derivative of the FCC file and very consistent with eQSL. I just recently started concentrating on counties and have 1,020 confirmed in eQSL ,thanks in large part to JTAlert, with every QSO county agreeing with the county in the call master file.
In terms of impacting JTAlert, I imported the call file (CSV format) into Access and queries against it take about 1 second to complete so I don't think the overhead would be noticeable.
Reviewing the eQSL activity (or lack thereof) for US hams has been interesting. Using 1/1/21 as a starting point there are only about 1,600 counties listed with any activity from US hams in eQSL. This means that you must resort to paper QSL's to get beyond the 1,500 endorsement level. Given that there are over 3,000 US counties that could be an expensive and time consuming effort to get them all. The best solution would be for ARRL to implement a county function in LOTW similar to what is provided for  CQ WAZ and WPX.
I always thought there were many more US hams currently using eQSL but that appears to not be the case. I don't consider a member who hasn't uploaded a log in the past 6 months an active user.
Looking forward to the next release.
73 Pat N6PAT


locked Re: Feature Suggestion Allow specifying eQSL AG activity date#FT8

Joe Subich, W4TV
 

Another related issue is that various loggers don't necessarily have
the same listing for the counties.
ADIF have standardized spelling and format (based on the USA-CA spec.).
Simply convert the input(s) to that format.

The bigger issue will be stations in "independent cities" ...

73,

... Joe, W4TV


On 2021-05-07 6:21 PM, Jim N6VH wrote:
On 5/7/2021 1:21 PM, HamApps Support (VK3AMA) wrote:


Regarding the 777,000 master file, I assume you're referring to the official FCC database. Is that the case? My experience with that database is that County names recorded is not entirely accurate. During my County Alert implementation testing I discovered many FCC listed County names that don't exist with the official USA-CA list. What has been you're experience?

de Laurie VK3AMA

_._,_._,_
------------------------------------------------------------------------
Laurie,
Thought I would add my two cents worth. There are definitely some differences between the FCC list and the USA-CA list. A very good example is Alaska. The FCC list uses the county name (actually 22 boroughs in Alaska), while USA-CA only uses the four Judicial Districts.  Another problem is spelling. The FCC list might have one spelling for a county, while the USA-CA list might have a slightly different spelling - Saint Tammany in the FCC list, St. Tammany in the USA-CA list, for example. None of these problems are insurmountable, but I wonder if the processing would have an impact on the speed of JTAlert.
Another related issue is that various loggers don't necessarily have the same listing for the counties.
73,
Jim N6VH
USA-CA 429

2581 - 2600 of 37312