Date   

locked Feature Request - Automatic Clearing of Alert Triggers

David
 

Using JTAlert 2.16.7 with WSJT-X 2.3.0-rc2
 
I worked the FT Roundup contest this past weekend.  For the contest, I relied on WSJT-X to log the contacts and JTAlert to inform me when a new state, VE province or DXCC was decoded.
 
To stop JTAlert from triggering on a state once I had a QSO with that state, I checked the "Auto clear triggered Alert entity after logging" option on the appropriate settings panel.  I did the same for VE provinces and DXCC settings.  This feature worked well and was very helpful in focusing my attention on new multipliers.
 
Each time a QSO was completed with an alert-able entity, JTAlert would display a pop-up telling me that the alert trigger had been cleared for that entity.
 
Problem:  JTAlert would show the pop-up every time I had a QSO even if the trigger had already been cleared.  For example, I had 30 QSOs with Texas stations.  JTAlert correctly alerted only once prior to the first Texas QSO.  But, the pop-up indicating that the alert trigger had been cleared appeared 30 times.
 
Request:  Do not display the pop-up if the trigger conditions are no longer set.  Or, add a user-settable option to stop all appearances of the pop-up.
 
Thank you.
 
David, AK2L
 


locked Re: 2.16.17 fails

Steve, N3SL
 

Fascinating....  The new url worked perfectly.   THANKS, Laurie!


On Sun, Dec 6, 2020 at 10:10 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 7/12/2020 12:24 pm, Steve, N3SL wrote:
I can't believe (or don't want to) that I'm the only one with this finding, but I've not seen any other messages....   I now have downloaded 2.16.17 on three different PCs, and every one of them gives me a near immediate message that the setup files are corrupted, and I need to get a new version.  Am I the only one?  I'm at a loss as to the cause.  I should probably mention that each machine tells me the download is suspect/potentially harmful, and do I want to continue....  Of course, that's been the case with JTAlert files for a LONG time....

Thanks for any guidance,
N3SL

Steve,

Sorry, but your the only one reporting this. The problem will be something common to all 3 of your PCs. Very likely your ISP internet connection.

Many ISPs, in order to reduce their bandwidth costs, utilize a transparent cache and will cache downloaded files, images, etc, and when another user on their network requests the exact same file they deliver the copy from their cache rather than the from the source location. My guess is that your ISP has a corrupt copy of the JTAlert setup file  in its cache that it keeps delivering it to you when requested from your other PCs.

A couple of things to try.
  1. Download the setup file using another ISP say from your Cell service if it is different provider.
  2. Fool the ISP cache into downloading and delivering what it thinks is a different file by manipulating the download url. Try appending "?v=1" to the url. I just now tested and this will still provide the file for download despite the url being changed.
    https://dnl.hamapps.com/JTAlert/eda319ab9017e7af6f5962d54a823a94?v=1

de Laurie VK3AMA



locked 73/RR73

F8RZ
 

Hello...

I just installed the last JTalert and I see that now  RR73 and 73 are on a dark green background.

Interesting feature, but as far as I know, it is not mentioned anywhere... or at least I did not see it.

 I should like to change the color, but how ?


73 to all.

F8RZ


locked Re: JTAlert not playing nice with LOG4OM V2

Laurie, VK3AMA
 



On 7/12/2020 4:47 pm, earlwg@... wrote:
Unable to confirm QSO Logged."
Is coughed up by JTAlert after logging a QSO about 2 times out of three. The QSO logs always get to LOG4OM even when the above error happens.
Sounds like confirmation of the QSO log is not reliably getting back to JTAlert somehow.
Any suggestions?

If QSOs are correctly being logged and JTAlert intermittently reports it is unable to confirm the QSO was logged then you will need to adjust the "Check QSO Log Record" time. Log4OMV2 takes much longer to log a QSO than the V1 so an increase in the time is typically needed. Try setting it to 10secs.
See the "Logging" section of the Settings window.


de Laurie VK3AMA


locked Re: LoTW FT4 download

Jacques Corbu
 

sorry Laurie I thought I had edited this post or removed it but did sort it out just after posting  the logbook is current version but had forgoten to do one step when creted the new logbook  apologies to all 

Stay safe Jacques F1VEV


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

No. I am using SQLite database.


locked Re: JTAlert not playing nice with LOG4OM V2

Michael Black
 

Do you have Use MySQL Server checked?

Inline image






On Sunday, December 6, 2020, 11:47:06 PM CST, earlwg@... <earlwg@...> wrote:


OK...it still isn't completely fixed. The error message:
"LOGGING WARNING:
Error Message: LOG4OM V2 SQLITE:
Unable to confirm QSO Logged."
Is coughed up by JTAlert after logging a QSO about 2 times out of three. The QSO logs always get to LOG4OM even when the above error happens.
Sounds like confirmation of the QSO log is not reliably getting back to JTAlert somehow.
Any suggestions?
Maybe this needs a new thread?


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

OK...it still isn't completely fixed. The error message:
"LOGGING WARNING:
Error Message: LOG4OM V2 SQLITE:
Unable to confirm QSO Logged."
Is coughed up by JTAlert after logging a QSO about 2 times out of three. The QSO logs always get to LOG4OM even when the above error happens.
Sounds like confirmation of the QSO log is not reliably getting back to JTAlert somehow.
Any suggestions?
Maybe this needs a new thread?


locked Re: AutoIT error , what to do ?

ed.n5dg@...
 

Yes you'll see me on pskreporter , I have more then on radio setup . It's working for now 
I was following along with LOG4OM , I have it seeing my log and sending the correct alerts but for the life of me I can't log a contact ... Followed ur help in jtalert https://prnt.sc/vx76g6
Thanks Ed N5DG


locked Re: AutoIT error , what to do ?

ed.n5dg@...
 

was 2.16.16. when I sent the message . Now it 1.16.17 .  I deleted the hamapps in appdata/ local , JTalerts is staying up , maybe that fixed it 
Ed N5DG


locked Re: AutoIT error , what to do ?

HamApps Support (VK3AMA)
 

On 7/12/2020 11:17 am, ed.n5dg@... wrote:
This error pops up each time I executer JTAlert ,  Is their a fix for this or a setting ? with this error JTAlert will not work . Using windows 10 64 
Thanks Ed N5DG
Ed,

I see your sending spots to HamSpots from JTAlert. So it looks to me like your running fine. What version are you running and what changes did you make that prevented the error you reported?

de Laurie VK3AMA


locked Re: AutoIT error , what to do ?

Laurie, VK3AMA
 

On 7/12/2020 11:17 am, ed.n5dg@gmail.com wrote:
This error pops up each time I executer JTAlert ,  Is their a fix for this or a setting ? with this error JTAlert will not work . Using windows 10 64
Thanks Ed N5DG
What version of JTAlert?

de Laurie VK3AMA


locked Re: 2.16.17 fails

HamApps Support (VK3AMA)
 



On 7/12/2020 12:24 pm, Steve, N3SL wrote:
I can't believe (or don't want to) that I'm the only one with this finding, but I've not seen any other messages....   I now have downloaded 2.16.17 on three different PCs, and every one of them gives me a near immediate message that the setup files are corrupted, and I need to get a new version.  Am I the only one?  I'm at a loss as to the cause.  I should probably mention that each machine tells me the download is suspect/potentially harmful, and do I want to continue....  Of course, that's been the case with JTAlert files for a LONG time....

Thanks for any guidance,
N3SL

Steve,

Sorry, but your the only one reporting this. The problem will be something common to all 3 of your PCs. Very likely your ISP internet connection.

Many ISPs, in order to reduce their bandwidth costs, utilize a transparent cache and will cache downloaded files, images, etc, and when another user on their network requests the exact same file they deliver the copy from their cache rather than the from the source location. My guess is that your ISP has a corrupt copy of the JTAlert setup file  in its cache that it keeps delivering it to you when requested from your other PCs.

A couple of things to try.
  1. Download the setup file using another ISP say from your Cell service if it is different provider.
  2. Fool the ISP cache into downloading and delivering what it thinks is a different file by manipulating the download url. Try appending "?v=1" to the url. I just now tested and this will still provide the file for download despite the url being changed.
    https://dnl.hamapps.com/JTAlert/eda319ab9017e7af6f5962d54a823a94?v=1

de Laurie VK3AMA



locked Re: 2.16.17 fails

Richard Williams
 

Steve,

Both myself and a friend downloaded 2.16.17 today, and it is running fine for both of us.

Dick, K8ZTT

Flying is the second greatest thrill known to man.
What is first, you ask? Landing, of course.
"A good aviator will always have his take-offs plus landings divisible by 2!"







On Sunday, December 6, 2020, 06:24:22 PM MST, Steve, N3SL <n3sl@...> wrote:


(My apologies if this ends up a duplicate post - I haven't seen the "original" in over an hour)

I can't believe (or don't want to) that I'm the only one with this finding, but I've not seen any other messages....   I now have downloaded 2.16.17 on three different PCs, and every one of them gives me a near immediate message that the setup files are corrupted, and I need to get a new version.  Am I the only one?  I'm at a loss as to the cause.  I should probably mention that each machine tells me the download is suspect/potentially harmful, and do I want to continue....  Of course, that's been the case with JTAlert files for a LONG time....

Thanks for any guidance,
N3SL


locked 2.16.17 fails

Steve, N3SL
 

(My apologies if this ends up a duplicate post - I haven't seen the "original" in over an hour)

I can't believe (or don't want to) that I'm the only one with this finding, but I've not seen any other messages....   I now have downloaded 2.16.17 on three different PCs, and every one of them gives me a near immediate message that the setup files are corrupted, and I need to get a new version.  Am I the only one?  I'm at a loss as to the cause.  I should probably mention that each machine tells me the download is suspect/potentially harmful, and do I want to continue....  Of course, that's been the case with JTAlert files for a LONG time....

Thanks for any guidance,
N3SL


locked AutoIT error , what to do ?

ed.n5dg@...
 

This error pops up each time I executer JTAlert ,  Is their a fix for this or a setting ? with this error JTAlert will not work . Using windows 10 64 
Thanks Ed N5DG


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

OK I fixed that one myself. I must have unchecked the UDP INBOUND for wsjt-x.
Thanks to all.


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

We....not quite perfect. QSOs are not being logged to LOG4OM any more. Error message is:
LOGGING WARNING:
Error Message: LOG4OM V2 SQLITE:
Unable to confirm QSO Logged.
So...something is fixed and something is broken.

 


locked Re: JTAlert not playing nice with LOG4OM V2

Earl
 

It worked....thanks! You guys are the best.
73


locked Re: JTAlert not playing nice with LOG4OM V2

HamApps Support (VK3AMA)
 

On 7/12/2020 6:35 am, earlwg@virga.ca wrote:
I do have 127.0.0.1 as the IP address and 2237 as the port set in JTAlert (under Logging/LOG4OM V2).
I suspect I need a different Out port/settings on LOG4OM (Program Settings/Connections UDP OUTBOUND and the incoming settings in JTAlert to match but have no idea what they should be.
The LOG4OM user manual at page 162 is of some use but has no specifics.
That will never work. 127.0.0.1 and 2237 are the defaults for WSJT-X and that is what JTAlert is listening to. Setting Log4OM to use 2237 will block all comms from WSJT-X to JTAlert.

Forget the Log4OM documentation. See the JTAlert Help file, "Settings -> Logging -> Log4OM V2" topic. It contains very simple setup instructions (with pictures).

de Laurie VK3AMA

421 - 440 of 32879