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?

---

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

Laurie,

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

Thanks
Vince
N2AIE

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

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

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

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

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

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

 

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