Date   

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


locked Re: Not getting B4 call signs to change color

HamApps Support (VK3AMA)
 

On 20/04/2021 4:52 am, Brad@... wrote:
I’m using the new JT alert 2.5 and for some reason that I cannot figure out in the callsign window all the worked before call signs do not change their background color and font color as I set up. They say  B4 after the call sign, It’s just that the background and font color don’t change. Any suggestions to sort this out would be appreciated.

brad, KF0CUD

What color are they showing, is it always the same color or does it vary?
Post an image of the Callsigns window (NOT your entire desktop) showing the incorrect coloring.

de Laurie VK3AMA


locked Re: True eQSL users

HamApps Support (VK3AMA)
 

On 20/04/2021 4:58 am, Frode Igland wrote:
The eQSL database is regrettably set up with each account being a unique combination of call sign,  location and time period. For every change of location, including working portable, you will have to register a new account.

I work from 3-4 different locations, some mainland locations and some island (IOTA) locations. I have 152 accounts and counting. It was a job to get started, but once you are up to date it is easy to add a new account. I don't use eQSL for awards or anything like that, but I offer an eQSL AG confirmation to those who do. And sometimes the eQSL might provide some info for the log for stations not found in the online call books (QRZ.com, HamQTH.com, etc.).

I asked the eQSL team many years ago about simplifying the location data in a fashion like LoTW. They then replied that a solution like LoTW was on the to-do-list with a low priority and probably wouldn't happen in years. Now many years have passed, and a repeat question last year indicated that it is still way into the future, if ever...

73, Frode LA6VQ

Frode, thanks for the info.

de Laurie VK3AMA


locked Re: Call signs calling me #FT8

HamApps Support (VK3AMA)
 

On 19/04/2021 11:14 pm, DAVID BERNHEISEL via groups.io wrote:

If you are referring to the green thermometer, I think that shows how long they have been parked there with respect to how long before they are removed from the list.


Incorrect. The progress-bar is an indicator of how many times they called.
See the 2.50.0 features help file, Callsigns window topic for an explanation.

de Laurie VK3AMA


locked Re: Call signs calling me #FT8

HamApps Support (VK3AMA)
 

On 19/04/2021 10:20 pm, Gerald Klotz wrote:

Since the new update, I have seen where someone calling me shows up on the bottom. I like that part but I can’t find anything about the little bar under their call sign box. Can anyone tell me what this? 


Gerry
kb9pki


Rather than telling you what it is, I will tell you how to find out.
Have a look in the 2.50.0 features help file under the "Callsigns window" topic.

de Laurie VK3AMA


locked Re: True eQSL users

Frode Igland
 

The eQSL database is regrettably set up with each account being a unique combination of call sign,  location and time period. For every change of location, including working portable, you will have to register a new account.

I work from 3-4 different locations, some mainland locations and some island (IOTA) locations. I have 152 accounts and counting. It was a job to get started, but once you are up to date it is easy to add a new account. I don't use eQSL for awards or anything like that, but I offer an eQSL AG confirmation to those who do. And sometimes the eQSL might provide some info for the log for stations not found in the online call books (QRZ.com, HamQTH.com, etc.).

I asked the eQSL team many years ago about simplifying the location data in a fashion like LoTW. They then replied that a solution like LoTW was on the to-do-list with a low priority and probably wouldn't happen in years. Now many years have passed, and a repeat question last year indicated that it is still way into the future, if ever...

73, Frode LA6VQ


locked Not getting B4 call signs to change color

Brad@...
 
Edited

I’m using the new JT alert 2.5 and for some reason that I cannot figure out in the callsign window all the worked before call signs do not change their background color and font color as I set up. They say  B4 after the call sign, It’s just that the background and font color don’t change. Any suggestions to sort this out would be appreciated.

brad, KF0CUD


locked Re: JT Alert 2.50.0 stopped by FrameworkCheck

Melvin L. Nichols
 

Ed
 
Are your computers 32 bit or 64 bit?
 
 
Mel, NZ)O
 

Sent: Monday, April 19, 2021 7:07 AM
Subject: Re: [HamApps] JT Alert 2.50.0 stopped by FrameworkCheck
 
As I  mentioned in a previous post, the problem is not limited to Windows 7. I am experiencing the same issues with an up to date Windows 10 on two different computers.
 
Ed, K0KC


locked Re: Changing callsign for hamspots.net site

Mike 2E0HCE
 

de Laurie VK3AMA

many thanks for your action.

greeting from the UK

1041 - 1060 of 35329