Date   

locked Moving "QSO Logged" window?

Bill - AA4M
 

I'm using version 2.50.0 of JTAlert.  For some reason the little "QSO Logged" window has moved to the bottom of the screen.  Is there any way I can relocate it?

73, Bill  AA4M


locked Re: Wanted county #FT8

Paul&Tracy Richards
 

Hello Laurie

Gridtracker has alerts for counties and it works very well. I know they are the competition but as both JTAlert and Gridtracker are free, maybe they would be happy to divulge how they do it. I am a keen county hunter and I use GT just for county hunting and JTAlert for everything else. The GT county tracker is not perfect but neither is the data it is drawing from - it is nonetheless a very handy tool.

It amazes me the number of US based hams who do not update their LOTW, Eqsl and even their qrz info when they move. I get 2-3 confirmations per week where the Eqsl and / or LOTW does not match their actual qrz address. It is frustrating when you know you have worked a new county but the electronic confirmation sent has the wrong location details. You just have to try and work that county again.  JTA Version 2.5 working beautifully here - many thanks

Paul - vk4ma


locked Re: B4 bad decoding

HamApps Support (VK3AMA)
 

On 20/04/2021 6:21 pm, f8nhf wrote:
for HRD logboock I have been using MariaDB for a few months I had already noticed this little problem when I was using MSAccess
I have the HRD configuration in JTALert see screenshot
 
73 Denis F8NHF

Can you please send me an ADIF export from your Maria log?

de Laurie VK3AMA


locked Re: B4 bad decoding

f8nhf
 

Hello Laurie
 
thank you for your answer
for HRD logboock I have been using MariaDB for a few months I had already noticed this little problem when I was using MSAccess
I have the HRD configuration in JTALert see screenshot
 
73 Denis F8NHF


locked Re: Wanted county #FT8

Marc VK3OHM
 
Edited

Clublog has a very reliable and fast Callsign->DXCC conversion. See https://clublog.freshdesk.com/support/solutions/articles/167890-batch-lookups-of-dxccs.  It has a bulk mode which will do the translation of up to 10,000 callsigns at a time, and it is VERY fast. Been using for some years on the WIA online awards scheme. Never had an issue.

Having said that, I'm not sure if Clublog would be happy for 1000's of apps to hammer the API every 30 seconds. Might need to check with them.


locked Re: B4 bad decoding

HamApps Support (VK3AMA)
 

On 20/04/2021 4:38 pm, f8nhf wrote:
Thank you for your answer
I am attaching the screenshot "Alerts -> Worked B4" nothing checked
I checked the OH3 callsign... it is present in the HRD logboock in the JTDX log and in the JTALert/..../JTAlertX/B4logV2 log
how can i rebuild a new "B4logV2" base ?

Thank you for your help
73 Denis F8NHF

Denis,

OK, something else is happening.

Don't worry about the B4logV2 database file, it only used when there is no logger enabled in JTAlert.
All your B4 checks are done against your HRD log.

Have you confirmed that JTAlert is set to use the correct HRD Log?

What log type do you use, is it an MSAccess log? If so could you zip it up and email it to me so I can examine it?If you can send it to VK3AMA.Ham.Apps [at] gmail.com

Also, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: B4 bad decoding

f8nhf
 

 Hello Laurie

Thank you for your answer
I am attaching the screenshot "Alerts -> Worked B4" nothing checked
I checked the OH3 callsign... it is present in the HRD logboock in the JTDX log and in the JTALert/..../JTAlertX/B4logV2 log
how can i rebuild a new "B4logV2" base ?

Thank you for your help
73 Denis F8NHF


locked Re: Wanted county #FT8

Michael Black
 

Just a thought...but what if each JTAlert user uploaded the QRZ data to hamspots.net and you could build your own database?

Date tag the uploads...provide the database back to JTAlert users who could then look at the date-last-updated to determine if they should report data again next time they log them....maybe every 90 or 180 days or such.

Could just pass a 32-bit CRC + callsign and hamspots.net could return a 200 or 404 where error 200==already got it 404==don't have or must've changed.

Mike W9MDB




On Monday, April 19, 2021, 09:30:43 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 19/04/2021 5:27 am, Bob Frostholm wrote:
I was under the impression JT Alert can query QRZ.com for other information and pull it into a log.  QRZ has county information for most US hams. Why would this not be possible?

73

Bob

Ko6Lu

JTAlert does save any County data returned from an XML lookup when a QSO is logged.

What is doesn't do is query the xml service for every decode received. Querying QRZ for the data of say 60 decodes received in a 15 second period is not going to happen. As a real-time lookup service for a single callsign it is adequate, but not for multiple callsigns. In order for JTAlert to generate a County Alert, the county needs to be know, the only way that can happen in real-time is via a local database lookup of some sort.

A reliable and accurate Callsign/County database doesn't exist. While JTAlert mitigates slow online lookups by caching received data to avoid return trips to the service, at some point there will likely be multiple xml lookups in a single period. With the slowness of 
QRZ at times and variable Internet speeds, it is not practical to perform xml lookups to determine the County of individual decodes, except in the singular case when you start a QSO with someone, then the multiple second delay in data receipt is acceptable.

There are plans for a County Alert, but that is dependent on a suitable Callsign database. That is still a work-in-progress endeavor at the moment. Any database created (sourced from multiple online databases) will likely to be somewhat inaccurate. Heck even the US-CA website is not kept up to date with County name changes.  Then there are the obvious errors in xml data for miss spelt or non existent country names or no county name recorded.

At a guess, I expect any County/Callsign database to be approx 50 to 80 % accurate. The wide variation in my guess is a reflection of the difficulty involved.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 sound alerts running multiple instances

HamApps Support (VK3AMA)
 

On 20/04/2021 12:25 pm, ohmy654321 via groups.io wrote:
The sound alerts (e.g. wanted state or own call) play only in the first instance.

OM (name? callsign?)

Sounds should play on all instances.
Does the "Sound -> Test Sound Output" menu work on the instances?

de Laurie VK3AMA


locked JTAlert 2.50.0 sound alerts running multiple instances

N4CZ Doug
 

The sound alerts (e.g. wanted state or own call) play only in the first instance.


locked Re: Callsigns window disappears and reappears after a while - RESOLVED

Laurie, VK3AMA
 

This defect has been identified, corrected, and tested. It will be in the next public release.

de Laurie VK3AMA


locked Re: dB Bug (JTAlert 2.5.0) ...

HamApps Support (VK3AMA)
 

On 18/04/2021 6:36 am, Joe Subich, W4TV wrote:
I care not a whit about eQSL and had it turned off in previous versions.

73,

  ... Joe, W4TV

You can turn off the eqsl flag in 2.50.0.

re eqsl, I reached that point a few years back. I got tired of the endless fake QSL requests, especially when I rarely get on air, indicating that people are just harvesting PSKReporter or HamSpots. They forget that most spots are RX only spots.

Yo


locked Re: Wanted county #FT8

HamApps Support (VK3AMA)
 

On 19/04/2021 5:27 am, Bob Frostholm wrote:
I was under the impression JT Alert can query QRZ.com for other information and pull it into a log.  QRZ has county information for most US hams. Why would this not be possible?

73

Bob

Ko6Lu

JTAlert does save any County data returned from an XML lookup when a QSO is logged.

What is doesn't do is query the xml service for every decode received. Querying QRZ for the data of say 60 decodes received in a 15 second period is not going to happen. As a real-time lookup service for a single callsign it is adequate, but not for multiple callsigns. In order for JTAlert to generate a County Alert, the county needs to be know, the only way that can happen in real-time is via a local database lookup of some sort.

A reliable and accurate Callsign/County database doesn't exist. While JTAlert mitigates slow online lookups by caching received data to avoid return trips to the service, at some point there will likely be multiple xml lookups in a single period. With the slowness of 
QRZ at times and variable Internet speeds, it is not practical to perform xml lookups to determine the County of individual decodes, except in the singular case when you start a QSO with someone, then the multiple second delay in data receipt is acceptable.

There are plans for a County Alert, but that is dependent on a suitable Callsign database. That is still a work-in-progress endeavor at the moment. Any database created (sourced from multiple online databases) will likely to be somewhat inaccurate. Heck even the US-CA website is not kept up to date with County name changes.  Then there are the obvious errors in xml data for miss spelt or non existent country names or no county name recorded.

At a guess, I expect any County/Callsign database to be approx 50 to 80 % accurate. The wide variation in my guess is a reflection of the difficulty involved.

de Laurie VK3AMA


locked Re: I love the new release! Except...

HamApps Support (VK3AMA)
 

On 19/04/2021 8:47 pm, John P wrote:
But in the words of that famous detective Colombo, "Just one more thing". In the new messaging window (also great) we can now delete individual messages; fantastic! But there doesn't seem to be a way to delete all of them as there was in the old version.
--
John P.
WA2FZW

Clearing all messages is already coded and tested. It will be in the next public release

de Laurie VK3AMA


locked Re: B4 bad decoding

HamApps Support (VK3AMA)
 

On 19/04/2021 5:26 pm, f8nhf wrote:
B4 decoding does not always take place
B4 decoded stations in the main window are not displayed in the Callsign window
the contact is written in the mdb file of jtalert
Did I forget something?
73 Denis F8NHF

The "QSO B4" shown to the left of the log fields in the main window indicates that there is an existing QSO (same Band & Mode) in your log.

The "B4" shown to the right of a callsign in the Callsigns window depends on what settings you have set for the B4 checks. If you have a Date limit set for the B4 Alert and a QSO exists in your log before that Date the B4 will not be shown.

Check the "Alerts -> Worked B4" section of the main Settings window. Do you have the "Ignore B4 status before this date ..." checkbox ticked?

de Laurie VK3AMA


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

Ed Wilson
 

Mel,

Both of my computers are running 32-bit Windows 10.

Ed, K0KC


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

Melvin L. Nichols
 

Laurie

Thanks for the information on the refurbished computers!
Will be looking at some new ones.

Thanks again for help and insight!

Mel, NZ0O

-----Original Message-----
From: HamApps Support (VK3AMA)
Sent: Monday, April 19, 2021 2:37 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert 2.50.0 stopped by FrameworkCheck

On 19/04/2021 10:07 pm, Melvin L. Nichols wrote:
My son, who works for a large corporation, told me that the ESU is only for large companies or corporations.

Mel, NZ0O
Tnx Mel. The online documentation about the need for the ESU doesn't
specify any restriction on the type of user, individual or corporate,
but the documentation is deficient in that it doesn't provide any link
to how to obtain an ESU. A Corporate customer will likely have a
Microsoft account manager through which they deal and they would likely
be the source of the ESU.

Looks like a new (or refurbished) Win10 X64 system is in your future.
One warning on refurbished, many low cost offerings which seem very
attractive due to the cost, achieve the low cost by providing the bare
minimum in terms specs, installed memory, cpu cores, video card
capability. I have seen Win10 spec systems that I would consider just
adequate for Win XP, 4G Ram, dual core, integrated video. I'm sure your
son will steer you in the right direction.

de Laurie VK3AMA


locked Re: Not getting B4 call signs to change color

HamApps Support (VK3AMA)
 

On 20/04/2021 5:21 am, Brad@... wrote:
I'll get you a screen shot but it's always the same color (orange)....
Brad
OK.
What Alert is set to use Orange? Have a look at the "Alert Types Summary Window", it will show you quickly what Alert is triggering the orange coloring. Once you know that, check the settings for that Alert, you will likely find that you have the "Ignore B4" option enabled.

Let me know what you find.

de Laurie VK3AMA


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

HamApps Support (VK3AMA)
 

On 19/04/2021 10:07 pm, Melvin L. Nichols wrote:
My son, who works for a large corporation, told me that the ESU is only for large companies or corporations.

Mel, NZ0O
Tnx Mel. The online documentation about the need for the ESU doesn't specify any restriction on the type of user, individual or corporate, but the documentation is deficient in that it doesn't provide any link to how to obtain an ESU. A Corporate customer will likely have a Microsoft account manager through which they deal and they would likely be the source of the ESU.

Looks like a new (or refurbished) Win10 X64 system is in your future. One warning on refurbished, many low cost offerings which seem very attractive due to the cost, achieve the low cost by providing the bare minimum in terms specs, installed memory, cpu cores, video card capability. I have seen Win10 spec systems that I would consider just adequate for Win XP, 4G Ram, dual core, integrated video. I'm sure your son will steer you in the right direction.

de Laurie VK3AMA


locked Re: Not getting B4 call signs to change color

Brad@...
 

I'll get you a screen shot but it's always the same color (orange)....
Brad

2601 - 2620 of 36897