Date   

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


locked F5 Text message windows disappears

K5FNQ, ART
 

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


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

Pat N6PAT
 

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: UDP port error

CLOVIS VONGHON
 
Edited

I understood Laurie. Fortunately, I'm not using multicast.
Thanks once more for your help.
Congratulations for the fantastic JTAlert!

73 de Clovis, PY3OG


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

Jim N6VH
 


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



locked Re: JT Alert - Worked B4

Bob Frostholm
 

Yes, sort of....

but I'm only interested in contacting a worked B4 on a different band is it is a Japan station...That's the objective of their award

Here's an example... I have set Ignore Band...

I have worked JA0QVJ on 17m previously, so I don't want to call him... It also tells me I have not worked JI3VUB or JI1LET on 17m...since JI1LET just signed 73, I would call him... because he could help advance me toward the award I reference earlier. Or I might try to call JI3VUB.

I'm not interested in filling my log by working every station on every band except for Japan.

So if there were no Japan stations on the air, I might want to try to contact KL7GY...but I'm not interested to make another contact with him if I've worked him B4 on another band. I can not tell if I already have KL7GY in my log. Yes, I know I can right click and left click the JT Alert box to find out but that's cumbersome and time consuming.


73

Bob

Ko6Lu
On 5/7/2021 2:42 PM, HamApps Support (VK3AMA) via groups.io wrote:

On 8/05/2021 7:24 am, Bob Frostholm wrote:
when I see a Japan station I have worked B4 and I know I've not worked him on this band, I'll contact him

That's what the "Ignore Band" setting works. With it unchecked, A previously worked station on a different band will not show as a B4 on an un-worked Band. That's how I understand what you want from your above statement.

de Laurie VK3AMA


--
Bob
KO6LU


locked Re: JT Alert - Worked B4

HamApps Support (VK3AMA)
 

On 8/05/2021 7:24 am, Bob Frostholm wrote:
when I see a Japan station I have worked B4 and I know I've not worked him on this band, I'll contact him

That's what the "Ignore Band" setting works. With it unchecked, A previously worked station on a different band will not show as a B4 on an un-worked Band. That's how I understand what you want from your above statement.

de Laurie VK3AMA


locked Re: JT Alert - Worked B4

Bob Frostholm
 

Hi Laurie and Mike,

I am aware of "Ignore Band"... but that doesn't fit my need. Here's the situation... JARL offers an award for contacting as many cities as possible on as many bands as possible ( https://www.jarl.org/English/4_Library/A-4-2_Awards/Award_Main.htm )

So, when I see a Japan station I have worked B4 and I know I've not worked him on this band, I'll contact him. At the same time, if I see a station from, say, Australia that I've worked B4, I don't want to duplicate and call him again on this band. So I'm seeking a way to distinguish  if the worked B4 was this band I'm on now or a different band.

I'm guessing the answer is no....but wanted to ask.

73

Bob

Ko6Lu
On 5/7/2021 2:06 PM, HamApps Support (VK3AMA) via groups.io wrote:

On 8/05/2021 6:51 am, Bob Frostholm wrote:
Is there a way to set the field color and / or border color for worked B4 to distinguish if a prior contact (workedB4) was on the current band or  a different band? I know I can right click and go the qso history but I'm interested to see at a glance.

-- 
73

Bob

Ko6Lu

Untick the "Ignore Band ..." setting for the "Worked B4" Alert

   

de Laurie VK3AMA


--
Bob
KO6LU


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

HamApps Support (VK3AMA)
 

On 7/05/2021 11:33 pm, Michael Black via groups.io wrote:
I assume the circled item should be "Remove from Wanted list" ?

Mike W9MDB

Tnx. Previously reported by Jim ADIC https://hamapps.groups.io/g/Support/message/34770

It's a cosmetic only issue, the backing property is correct.

de Laurie VK3AMA


locked Re: JT Alert - Worked B4

HamApps Support (VK3AMA)
 

On 8/05/2021 6:51 am, Bob Frostholm wrote:
Is there a way to set the field color and / or border color for worked B4 to distinguish if a prior contact (workedB4) was on the current band or  a different band? I know I can right click and go the qso history but I'm interested to see at a glance.

-- 
73

Bob

Ko6Lu

Untick the "Ignore Band ..." setting for the "Worked B4" Alert

   

de Laurie VK3AMA


locked Re: JT Alert - Worked B4

Michael Black
 

If you set your filter "by band" you won't see "B4" on a different band.

Mike W9MDB




On Friday, May 7, 2021, 03:51:30 PM CDT, Bob Frostholm <bob@...> wrote:


Is there a way to set the field color and / or border color for worked
B4 to distinguish if a prior contact (workedB4) was on the current band
or  a different band? I know I can right click and go the qso history
but I'm interested to see at a glance.

--
73

Bob

Ko6Lu



--
Bob
KO6LU






locked JT Alert - Worked B4

Bob Frostholm
 

Is there a way to set the field color and / or border color for worked B4 to distinguish if a prior contact (workedB4) was on the current band or  a different band? I know I can right click and go the qso history but I'm interested to see at a glance.

--
73

Bob

Ko6Lu



--
Bob
KO6LU


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

HamApps Support (VK3AMA)
 

On 7/05/2021 4:30 pm, Pat N6PAT via groups.io wrote:
I downloaded the eQSL AG Member List Dated file containing the date of the last upload/import for each member. The raw file had 141,441 records. After filtering for US call signs the number was down to a little over 32,000 including almost 15,000 that had no activity in at least 10 years. Of the total calls only about 12,000 had uploaded or imported QSO's into eQSL since 1/1/2020 and only about 8,000 had uploaded or imported QSO's into eQSL since the beginning of 2021.

I suggest using the eQSL dated member file and adding an option to allow specifying a Last Activity Date threshold (i.e. filter for eQSL AG who had activity within the current year or last 6 months or since a specific date). There's no point in filtering for eQSL AG ops if the majority of them haven't been active in eQSL in many years and you cannot weed out the inactive members. .

It was discussed about the possibility of adding a Wanted County feature to aid in county hunting. That would only be valuable if the suggested Last Activity Date function was included as CQ currently only accepts QSO confirmations for the County award via eQSL AG and cards. Chasing down an AG op with a QTH in a wanted county who hasn't uploaded in a decade is a waste of time .

To handle this for right now I've created a database of all AG members with activity since 1/1/2021, retrieved their county from a master file of 770,000 US ham calls and compared the result to a list of the counties I still need. I then import the results in a comma delimited text file into the Wanted Call signs function. Seems to work well.

73 Pat N6PAT

Pat thanks for putting some thought and effort into documenting your request.

I am already capturing the new Eqsl AG members file ready for inclusion into the Callsigns database. It has not yet been enabled as the changed database schema will break old versions of JTAlert. I will be creating a new database distribution for future JTAlert versions. That will take a while as utilizing the Eqsl last upload date for alerting and flagging, similar to that for LoTW, will require some significant code changes.

Be assured that Eqsl by Date flagging and alerting will be implemented, but there will likely be a number of JTAlert releases before that happens.

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

3021 - 3040 of 37740