Date   

locked Re: [Ham-Apps] RE: Colour flags for LoTW/eQSL users

Laurie, VK3AMA <groups04@...>
 

Hi Phil,

Just ran a test here. I can't reproduce your observed behaviour for the same settings and callsign.
Decoded KC0W and JT-Alert correctly didn't display the LoTW flag.

Make sure you have the "Enable time limit filter" checked in the Settings.



de Laurie VK3AMA


On 15/01/2013 7:39 AM, Phil Cooper wrote:

One thing I have just noticed is that there appears to be some odd behaviour of the LoTW flag.

I base this on working KC0W recently, whose callsign appeared with a LoTW flag, and yet when you use the + at the left edge of JT-Alert, it shows his last LoTW upload was 2004.

I have all updates at the latest release, and the time function is set to one year.

 

As I have not since copied KC0W, I cannot verify this, but maybe you can see what is going on behind the scenes?



locked Re: Colour flags for LoTW/eQSL users

Phil Cooper <pcooper@...>
 

Laurie,

 

Many thanks for the info. I was beginning to wonder if I had imagined this function on the earlier release, but I can see perfectly well why you decided to change this ability.

 

One thing I have just noticed is that there appears to be some odd behaviour of the LoTW flag.

I base this on working KC0W recently, whose callsign appeared with a LoTW flag, and yet when you use the + at the left edge of JT-Alert, it shows his last LoTW upload was 2004.

I have all updates at the latest release, and the time function is set to one year.

 

As I have not since copied KC0W, I cannot verify this, but maybe you can see what is going on behind the scenes?

 

73 de Phil GU0SUP

 

 


locked Re: [Ham-Apps] JT-Alert on 160 meters

Don Hill AA5AU
 

This isn't directly related to JT-Alert and I apologize for the bandwidth, but I'm trying to get on 160 to work JT-65. I can receive well using my Pixel loop, but I do not have a transmitting antenna. Has anyone used one of these reduced 160 1/2 slopers? I have limited space but do have a tower to hang a reduced 160 1/2 sloper off of. I'm looking at this one:

http://w8amz.com/W8AMZ_SLOPERS_Page.html

Please reply directly to me:

aa5au@...

Thanks,
Don AA5AU



From: Ed Wilson To: "Ham-Apps@..."
Sent: Monday, January 14, 2013 1:12 PM
Subject: Re: [Ham-Apps] JT-Alert on 160 meters

 
Sent!


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, January 14, 2013 1:54 PM
Subject: Re: [Ham-Apps] JT-Alert on 160 meters

 
ED,

If it has been less than 2 days since you observed this behaviour (session file only holds 2 days of data) please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis. Include a note of the approximate utc time of the event.

de Laurie VK3AMA

On 15/01/2013 2:25 AM, Ed Wilson wrote:
Laurie,

First of all, let me thank you again for all of the effort that you put into JT-Alert!

I do not have an effective antenna on 160 meters, so my WAS total on that band is rather meager. I did fire-up on 160 Saturday night and a station in Virginia (which is checked as a needed state in JT-Alert) answered my CQ. I remembered that I needed Virginia, so I was surprised that an alert did not appear (I have configured JT-Alert to show the desired call with a yellow background and to beep me when I decode a needed state; I also only generate alerts for LOTW stations). I stopped and re-started JT-Alert and sure enough, the alert came through as I would have expected. During my QSO with the first station, another station from Virginia was decoded and he did not generate an alert even though the first station continued to show an alert throughout our QSO. I later worked the second station and as I recall, he did show a normal alert during our QSO. The call sign of the first station in Virginia was N4KWO and the call sign of the second station was KX4P; both stations are LOTW. I am using version 2.0.9 of JT-Alert without the file over-write update that you released recently.

160 meters is the only band where I have observed what appears to be inconsistent behaviour, but I have worked all states on bands other than 160 meters, 12 meters, and 10 meters (thanks to JT-Alert), so I do not have "Needed States" checked on most bands. I have seen other needed states generate alerts normally on 160 meters since Saturday night.

Thanks,

Ed, K0KC








locked Re: [Ham-Apps] JT-Alert on 160 meters

Ed Wilson
 

Sent!


From: "Laurie, VK3AMA"
To: Ham-Apps@...
Sent: Monday, January 14, 2013 1:54 PM
Subject: Re: [Ham-Apps] JT-Alert on 160 meters

 
ED,

If it has been less than 2 days since you observed this behaviour (session file only holds 2 days of data) please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis. Include a note of the approximate utc time of the event.

de Laurie VK3AMA

On 15/01/2013 2:25 AM, Ed Wilson wrote:
Laurie,

First of all, let me thank you again for all of the effort that you put into JT-Alert!

I do not have an effective antenna on 160 meters, so my WAS total on that band is rather meager. I did fire-up on 160 Saturday night and a station in Virginia (which is checked as a needed state in JT-Alert) answered my CQ. I remembered that I needed Virginia, so I was surprised that an alert did not appear (I have configured JT-Alert to show the desired call with a yellow background and to beep me when I decode a needed state; I also only generate alerts for LOTW stations). I stopped and re-started JT-Alert and sure enough, the alert came through as I would have expected. During my QSO with the first station, another station from Virginia was decoded and he did not generate an alert even though the first station continued to show an alert throughout our QSO. I later worked the second station and as I recall, he did show a normal alert during our QSO. The call sign of the first station in Virginia was N4KWO and the call sign of the second station was KX4P; both stations are LOTW. I am using version 2.0.9 of JT-Alert without the file over-write update that you released recently.

160 meters is the only band where I have observed what appears to be inconsistent behaviour, but I have worked all states on bands other than 160 meters, 12 meters, and 10 meters (thanks to JT-Alert), so I do not have "Needed States" checked on most bands. I have seen other needed states generate alerts normally on 160 meters since Saturday night.

Thanks,

Ed, K0KC






locked Re: [Ham-Apps] Just to confirm fix for delayed Decode

Laurie, VK3AMA <groups04@...>
 

Vince,

Thanks for the feedback.

de Laurie VK3AMA

On 15/01/2013 1:06 AM, Vince wrote:
Laurie,

Just want to confirm that the copy of the new .exe will fix the delayed decode issue previously mentioned??

Thanks
Vince
N2AIE



locked Re: [Ham-Apps] JT-Alert on 160 meters

Laurie, VK3AMA <groups04@...>
 

ED,

If it has been less than 2 days since you observed this behaviour (session file only holds 2 days of data) please use the "Settings -> Contact Support" menu to send me your Configuration and Session files for analysis. Include a note of the approximate utc time of the event.

de Laurie VK3AMA

On 15/01/2013 2:25 AM, Ed Wilson wrote:
Laurie,

First of all, let me thank you again for all of the effort that you put into JT-Alert!

I do not have an effective antenna on 160 meters, so my WAS total on that band is rather meager. I did fire-up on 160 Saturday night and a station in Virginia (which is checked as a needed state in JT-Alert) answered my CQ. I remembered that I needed Virginia, so I was surprised that an alert did not appear (I have configured JT-Alert to show the desired call with a yellow background and to beep me when I decode a needed state; I also only generate alerts for LOTW stations). I stopped and re-started JT-Alert and sure enough, the alert came through as I would have expected. During my QSO with the first station, another station from Virginia was decoded and he did not generate an alert even though the first station continued to show an alert throughout our QSO. I later worked the second station and as I recall, he did show a normal alert during our QSO. The call sign of the first station in Virginia was N4KWO and the call sign of the second station was KX4P; both stations are LOTW. I am using version 2.0.9 of JT-Alert without the file over-write update that you released recently.

160 meters is the only band where I have observed what appears to be inconsistent behaviour, but I have worked all states on bands other than 160 meters, 12 meters, and 10 meters (thanks to JT-Alert), so I do not have "Needed States" checked on most bands. I have seen other needed states generate alerts normally on 160 meters since Saturday night.

Thanks,

Ed, K0KC




locked Re: [Ham-Apps] JT-Alert on 160 meters

Ed Wilson
 

Yes, K.D., I have different "Wanted States" on each band where I still need states (160m, 12m, and  10m).

Thanks for the suggestion!

Ed, K0KC



From: K. D. Sarchet
To: Ham-Apps@...
Sent: Monday, January 14, 2013 10:39 AM
Subject: RE: [Ham-Apps] JT-Alert on 160 meters

 
Ed,

Do you have 160 checked in the Settings->Manage Settings...->Alerts->Wanted
US State->Individual Bands?

73 de WY5R - KD

dbcalc - http://dwestbrook.net/projects/ham/dBCalc/

From: Ham-Apps@... [mailto:Ham-Apps@...] On
Behalf Of Ed Wilson
Sent: Monday, January 14, 2013 9:25 AM
To: Ham-Apps@...
Subject: [Ham-Apps] JT-Alert on 160 meters

 
Laurie,

First of all, let me thank you again for all of the effort that you put into
JT-Alert!

I do not have an effective antenna on 160 meters, so my WAS total on that
band is rather meager. I did fire-up on 160 Saturday night and a station in
Virginia (which is checked as a needed state in JT-Alert) answered my CQ. I
remembered that I needed Virginia, so I was surprised that an alert did not
appear (I have configured JT-Alert to show the desired call with a yellow
background and to beep me when I decode a needed state; I also only generate
alerts for LOTW stations). I stopped and re-started JT-Alert and sure
enough, the alert came through as I would have expected. During my QSO with
the first station, another station from Virginia was decoded and he did not
generate an alert even though the first station continued to show an alert
throughout our QSO. I later worked the second station and as I recall, he
did show a normal alert during our QSO. The call sign of the first station
in Virginia was N4KWO and the call sign of the second station was KX4P; both
stations are LOTW. I am using version 2.0.9 of JT-Alert without the file
over-write update that you released recently.

160 meters is the only band where I have observed what appears to be
inconsistent behaviour, but I have worked all states on bands other than 160
meters, 12 meters, and 10 meters (thanks to JT-Alert), so I do not have
"Needed States" checked on most bands. I have seen other needed states
generate alerts normally on 160 meters since Saturday night.

Thanks,

Ed, K0KC




locked Re: [Ham-Apps] JT-Alert on 160 meters

K. D. Sarchet <wy5r@...>
 

Ed,

Do you have 160 checked in the Settings->Manage Settings...->Alerts->Wanted
US State->Individual Bands?

73 de WY5R - KD

dbcalc - http://dwestbrook.net/projects/ham/dBCalc/

From: Ham-Apps@yahoogroups.com.au [mailto:Ham-Apps@yahoogroups.com.au] On
Behalf Of Ed Wilson
Sent: Monday, January 14, 2013 9:25 AM
To: Ham-Apps@yahoogroups.com.au
Subject: [Ham-Apps] JT-Alert on 160 meters

 
Laurie,

First of all, let me thank you again for all of the effort that you put into
JT-Alert!

I do not have an effective antenna on 160 meters, so my WAS total on that
band is rather meager. I did fire-up on 160 Saturday night and a station in
Virginia (which is checked as a needed state in JT-Alert) answered my CQ. I
remembered that I needed Virginia, so I was surprised that an alert did not
appear (I have configured JT-Alert to show the desired call with a yellow
background and to beep me when I decode a needed state; I also only generate
alerts for LOTW stations). I stopped and re-started JT-Alert and sure
enough, the alert came through as I would have expected. During my QSO with
the first station, another station from Virginia was decoded and he did not
generate an alert even though the first station continued to show an alert
throughout our QSO. I later worked the second station and as I recall, he
did show a normal alert during our QSO. The call sign of the first station
in Virginia was N4KWO and the call sign of the second station was KX4P; both
stations are LOTW. I am using version 2.0.9 of JT-Alert without the file
over-write update that you released recently.

160 meters is the only band where I have observed what appears to be
inconsistent behaviour, but I have worked all states on bands other than 160
meters, 12 meters, and 10 meters (thanks to JT-Alert), so I do not have
"Needed States" checked on most bands. I have seen other needed states
generate alerts normally on 160 meters since Saturday night.

Thanks,

Ed, K0KC


locked JT-Alert on 160 meters

Ed Wilson
 

Laurie,

First of all, let me thank you again for all of the effort that you put into JT-Alert!

I do not have an effective antenna on 160 meters, so my WAS total on that band is rather meager. I did fire-up on 160 Saturday night and a station in Virginia (which is checked as a needed state in JT-Alert) answered my CQ. I remembered that I needed Virginia, so I was surprised that an alert did not appear (I have configured JT-Alert to show the desired call with a yellow background and to beep me when I decode a needed state; I also only generate alerts for LOTW stations). I stopped and re-started JT-Alert and sure enough, the alert came through as I would have expected. During my QSO with the first station, another station from Virginia was decoded and he did not generate an alert even though the first station continued to show an alert throughout our QSO. I later worked the second station and as I recall, he did show a normal alert during our QSO. The call sign of the first station in Virginia was N4KWO and the call sign of the second station was KX4P; both stations are LOTW. I am using version 2.0.9 of JT-Alert without the file over-write update that you released recently.

160 meters is the only band where I have observed what appears to be inconsistent behaviour, but I have worked all states on bands other than 160 meters, 12 meters, and 10 meters (thanks to JT-Alert), so I do not have "Needed States" checked on most bands. I have seen other needed states generate alerts normally on 160 meters since Saturday night.

Thanks,

Ed, K0KC


locked Just to confirm fix for delayed Decode

Vince
 

Laurie,

Just want to confirm that the copy of the new .exe will fix the delayed decode issue previously mentioned??

Thanks
Vince
N2AIE


locked Re: [Ham-Apps] Re: Starting JT-Alert 2.09

Laurie, VK3AMA <groups04@...>
 

Dennis,

That fix file is meant to replace the existing JT-Alert.exe executable. Running that file in any other directory than where JT-Alert is installed will generate the errors you observed.

The replacement JT-Alert.exe needs to be placed in the folder where JT-Alert is installed, overwriting the exiting file.

de Laurie VK3AMA

On 14/01/2013 6:30 PM, n6ng@... wrote:
Hello Laurie...

I uninstalled or deleted everything I could find that had anything to do with JT-Alert.
Downloaded the latest 2.0.9 and installed that.
But when I tried to install either of the fixes that you listed I got the followiing message.

There has been an error starting the SQLite database component.

Function : _SQLite_Startup()
DLL File : C:\Documents and Settings\D. Jacobson\My Documents\Downloads\sqlite3.dll - Missing.
SQLite Error Message : Library used incorrectly
SQLite Error Code : 21

This error message has been placed in the Windows Clipboard.

Program will now exit.

I would thank you for any other suggestions.

Dennis N6NG



locked Re: Starting JT-Alert 2.09

Dennis Jacobson
 

Hello Laurie...

I uninstalled or deleted everything I could find that had anything to do with JT-Alert.
Downloaded the latest 2.0.9 and installed that.
But when I tried to install either of the fixes that you listed I got the followiing message.

There has been an error starting the SQLite database component.

Function : _SQLite_Startup()
DLL File : C:&#92;Documents and Settings&#92;D. Jacobson&#92;My Documents&#92;Downloads&#92;sqlite3.dll - Missing.
SQLite Error Message : Library used incorrectly
SQLite Error Code : 21

This error message has been placed in the Windows Clipboard.

Program will now exit.

I would thank you for any other suggestions.

Dennis N6NG

--- In Ham-Apps@yahoogroups.com.au, "n6ng@..." wrote:

Just downloaded 2.09 and when I start it I get the following message
and it closes. Anyone had this problem and found an answer?
Thanks

Sorry, there has been an error!

Current Function :
Calling Function :

err.description is:
err.windescription: Variable must be of type 'Object'.
err.number is: 000000A9
err.lastdllerror is: 0
err.scriptline is: -1
err.source is:
err.helpfile is:
err.helpcontext is: 0

This error message has been placed in the Windows Clipboard.

Dennis N6NG


locked Re: LATEST JT-ALERT UPDATE FAIL

lmeeny
 

Laurie

Thanks for clearing that up! My error.

Thanks,

Ed


locked Re: [Ham-Apps] Re: HI??

Laurie, VK3AMA <groups04@...>
 

Hi Julian,

If your not using the Callsign database, then US callsigns will not have their State shown, as you have observed. JT-Alert, when detecting an Hawaiian or Alaskan callsign automatically sets the HI and AK State text and that is the reason for seeing HI (and eventually AK) but no US Based States.

I will remove that inconsistency from future JT-Alert releases.

de Laurie VK3AMA

On 14/01/2013 3:17 AM, g4ilo wrote:
Thanks, Bruce. I've never seen it display any other US State before, otherwise I might have guessed the answer.

Julian, G4ILO

--- In Ham-Apps@..., Bruce McLain  wrote:
Julian,

The call was from Hawaii.

Bruce McLain - K5WBM
Sent from my iPad

On Jan 13, 2013, at 9:17 AM, g4ilo  wrote:



This afternoon JT-Alert showed -HI after a call. I've never seen that
before. I know what B4 means but HI has me stumped.

Julian, G4ILO




locked Re: [Ham-Apps] LATEST JT-ALERT UPDATE FAIL

Laurie, VK3AMA <groups04@...>
 

Hi Ed,

That replacement file, to fix slow decodes, is not an install file, it is meant to replace the exisiting JT-Alert.exe executable. Running that file in any other directory than where JT-Alert is installed will generate the errors you observed.

The replacement JT-Alert.exe needs to be placed in the folder where JT-Alert is installed, overwriting the exiting file.

de Laurie VK3AMA

On 14/01/2013 3:23 AM, lmeeny wrote:
Hello,

On January 11 a replacement was released in response to a slow display of decoded signals.

Attempting to run the installer an error message was received.

"There has been an error starting the SQLite database component." 

farther on: SQLite error message: library used incorrectlyDLL File c:\users\ed machak\desktop\sqlite3dll. missing."

followed by:

SQLite error message: library used incorrectly.
SQLite error code 21

Ed Machak



locked Pskreporter balloons and station description.

Dan Baker
 

Hello,
On Pskreporter there are balloons that have "L" or "E" in them.
Also the station description will say;
"Last LoTW upload: Thu, 3 Jan 2013
eQSL Authenticity Guaranteed"
Does this information come from the JT-65 program?
Does anyone know where it comes from?

Thanks, Dan KM6CQ


locked LATEST JT-ALERT UPDATE FAIL

lmeeny
 

Hello,

On January 11 a replacement was released in response to a slow display of decoded signals.

Attempting to run the installer an error message was received.

"There has been an error starting the SQLite database component."

farther on: SQLite error message: library used incorrectlyDLL File c:&#92;users&#92;ed machak&#92;desktop&#92;sqlite3dll. missing."

followed by:

SQLite error message: library used incorrectly.
SQLite error code 21

Ed Machak


locked Re: HI??

g4ilo
 

Thanks, Bruce. I've never seen it display any other US State before, otherwise I might have guessed the answer.

Julian, G4ILO

--- In Ham-Apps@yahoogroups.com.au, Bruce McLain wrote:

Julian,

The call was from Hawaii.

Bruce McLain - K5WBM
Sent from my iPad

On Jan 13, 2013, at 9:17 AM, g4ilo wrote:



This afternoon JT-Alert showed -HI after a call. I've never seen that
before. I know what B4 means but HI has me stumped.

Julian, G4ILO


locked Re: [Ham-Apps] HI??

rcktscientist64
 

Julian,

The call was from Hawaii.

Bruce McLain - K5WBM
Sent from my iPad

On Jan 13, 2013, at 9:17 AM, g4ilo <julian.g4ilo@...> wrote:

 

This afternoon JT-Alert showed -HI after a call. I've never seen that before. I know what B4 means but HI has me stumped.

Julian, G4ILO


locked HI??

g4ilo
 

This afternoon JT-Alert showed -HI after a call. I've never seen that before. I know what B4 means but HI has me stumped.

Julian, G4ILO