Date   

locked Re: Wanted US State Not Updating

JP
 

Thanks for your reply Herb.  I have them all unchecked.  For about 80% of my QSOs, once I work a new state (or DXCC entity) I no longer see that state (or DXCC entity) as wanted, which is at it should be.

However, for the remaining 20%, the wanted/unwanted status does not change.

73
Jon, AI1V


locked Re: LoTW Flag not always correct

Paul AC9O
 

I did just see a case where the LoTW flag is not displayed, but it is in WSJT-X and in ACLog. The last upload date is 2020-02-16 so it's within a year. The call is ZW86LABRE. Is it possibly just a very new call that isn't in your database?


locked Re: Auto-start question

HamApps Support (VK3AMA)
 

On 26/02/2020 8:21 am, Carter wrote:
1) DX Lab Commander
2) DXKeeper
3) WSJT-X
4) JT Alert
I would put DXKeeper last.
DXKeeper can be very slow to startup. It is not critical to be running until you want to log a QSO so starting last will not present a problem.

de Laurie VK3AMA


locked Re: Auto-start question

Dave Garber
 

when I tried the autostart with my log, etc.  I always started the cat program first, the jtalert, which would call up wsjt and my log program

never an issue that way.   perhaps you start times should be spaced further, if needed.   commander needs no delay, then dxkeeper at 100 ( try, maybe need higher), then wsjt after additional time period
Dave Garber
VE3WEJ / VE3IE


On Tue, Feb 25, 2020 at 4:21 PM Carter <k8vt@...> wrote:
I used JT Alert about 3 years ago with JT65/JT9 but still consider myself a newbie, just having got back on the air with FT-8.
I manually start from desktop icons (in the order listed):
1) DX Lab Commander
2) DXKeeper
3) WSJT-X
4) JT Alert

Everything works fine - radio control, making split contacts, logging to DXKeepeer and LoTW, etc. However, it was a bit tiresome starting all those programs individually, so Auto-start seemed like a great idea!

In JT Alert: Settings>Applications>Auto-Start.

I had #1 as Commander, 1000ms
#2 as DXkeeper, 1000ms
#3 WSJT-X, which changed by itself to 1500 ms.

Then I click on the desktop icon for JT Alert. This gives a variety of errors (sorry, did not write them all down), WSJT-X no longer recognizing the radio, etc.

Any thoughts on what order I should have the auto-start programs in? Any suggestions on what I am doing wrong?

Thanks in advance and 73,
Carter  K8VT


locked Re: Auto-start question

Michael Black
 

Try starting WSTJ-X a bit later to let DX programs get going first.

de Mike W9MDB




On Tuesday, February 25, 2020, 03:21:59 PM CST, Carter <k8vt@...> wrote:


I used JT Alert about 3 years ago with JT65/JT9 but still consider myself a newbie, just having got back on the air with FT-8.
I manually start from desktop icons (in the order listed):
1) DX Lab Commander
2) DXKeeper
3) WSJT-X
4) JT Alert

Everything works fine - radio control, making split contacts, logging to DXKeepeer and LoTW, etc. However, it was a bit tiresome starting all those programs individually, so Auto-start seemed like a great idea!

In JT Alert: Settings>Applications>Auto-Start.

I had #1 as Commander, 1000ms
#2 as DXkeeper, 1000ms
#3 WSJT-X, which changed by itself to 1500 ms.

Then I click on the desktop icon for JT Alert. This gives a variety of errors (sorry, did not write them all down), WSJT-X no longer recognizing the radio, etc.

Any thoughts on what order I should have the auto-start programs in? Any suggestions on what I am doing wrong?

Thanks in advance and 73,
Carter  K8VT


locked Auto-start question

Carter
 

I used JT Alert about 3 years ago with JT65/JT9 but still consider myself a newbie, just having got back on the air with FT-8.
I manually start from desktop icons (in the order listed):
1) DX Lab Commander
2) DXKeeper
3) WSJT-X
4) JT Alert

Everything works fine - radio control, making split contacts, logging to DXKeepeer and LoTW, etc. However, it was a bit tiresome starting all those programs individually, so Auto-start seemed like a great idea!

In JT Alert: Settings>Applications>Auto-Start.

I had #1 as Commander, 1000ms
#2 as DXkeeper, 1000ms
#3 WSJT-X, which changed by itself to 1500 ms.

Then I click on the desktop icon for JT Alert. This gives a variety of errors (sorry, did not write them all down), WSJT-X no longer recognizing the radio, etc.

Any thoughts on what order I should have the auto-start programs in? Any suggestions on what I am doing wrong?

Thanks in advance and 73,
Carter  K8VT


locked JTAlert 2.15.11 is available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.15.11 is now available @ https://hamapps.com/JTAlert/

Please review the Release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.15.11 (24-FEB-2020)

  New Features:

    - Audio Play Limit Period: Individual audio alerts will play once per time
       period (max 5 minutes). Set via the "Sound" menu or the Settings window.
       Limit does not apply to "Own Call" and "Out of shack" alerts.
       (Default: No limit, Window: Settings, Section: SoundCard).

  Changes:

    - Callsign Database: Significant reduction in size due to removal of non
       active Callsigns (not spotted in last 6 months). Size is now ~2.5MB,
       previously ~33MB.

    - Callsigns Display: Improved display speed with less redraw flashing.

  Fixes:

    - ADIF Logging: SQLite error when logging "Cote d'Ivoire" country name QSOs.

    - Log4OM2 MySQL: Scan Log failing to find QSL confirmed QSOs.

    - Log4OM2 MySQL: Scan Log failing (returning all entities as need) for non-Windows
       hosted MySQL servers (Linux or MAC). Windows hosted MySQL was not affected.
       (Thanks! to Jorgen, NU1T, for uncovering the source of this defect)



locked Re: Wanted US State Not Updating

WB8ASI Herb
 

Jon,   See attached.  I have LOTW selected as my confirmation, so I still see anything as being "Wanted" until I receive the LOTW.   I imagine if you have them all unchecked, you might see it removed from your "Wanted" list upon working them, but I've never tried that.  73, Herb WB8ASI
On February 25, 2020 at 9:07 AM JP <jon.perelstein@...> wrote:

Herb

Thank you for your reply.  I can't find "required for confirmation" as a setting or filter.  Where is it located?

73
Jon, AI1V

 


locked Re: JTAlert is closing (crashing) after logging or settings change

Rich McCabe
 

Mike

Done.


locked Re: Wanted US State Not Updating

JP
 

Herb

Thank you for your reply.  I can't find "required for confirmation" as a setting or filter.  Where is it located?

73
Jon, AI1V


locked Re: JTAlert is closing (crashing) after logging or settings change

Michael Black
 

You'll need to send in a bug report via Help/Contact Support

de Mike W9MDB



On Tuesday, February 25, 2020, 07:45:44 AM CST, Rich McCabe <r.mccabe@...> wrote:


I have an issue all of a sudden where JTalert will close after logging (Log4OM V2).  I thought maybe it had something to do with log4OM so I disabled that but still happens. I can go into the settings menu and click OK to leave and it does it as well.

The calls that it crashed on are not showing as worked either.  They did make it to log4OM when I had it enabled.

Rich


locked Re: JTAlert is closing (crashing) after logging or settings change

Rich McCabe
 

And I am getting an AutoIT Error on occasion now for JTAlert_AL.exe  for variable used without being declared.


locked JTAlert is closing (crashing) after logging or settings change

Rich McCabe
 

I have an issue all of a sudden where JTalert will close after logging (Log4OM V2).  I thought maybe it had something to do with log4OM so I disabled that but still happens. I can go into the settings menu and click OK to leave and it does it as well.

The calls that it crashed on are not showing as worked either.  They did make it to log4OM when I had it enabled.

Rich


locked Re: False QSO Not Logged message with ACLog6.6

Terry Scaia
 
Edited

I don't use XML lookups (enjoy manually reading QRZ entries), and do LOTW uploads at end of day, so my internet connection is mainly keeping time in sync.  Today I changed WSJT-X, JTAlert, and ACLog, priorities from Normal to High. JTAlert reports of Logging Success dropped from 3 seconds to 1 second with no Logging Failures.
No need to turn off check of logging success/failure.

Thank you for your support, Laurie!
73 de Terry - N4IYB


locked Re: Wanted US State Not Updating

WB8ASI Herb
 

What do you have checked for required for confirmation?  It will show as still Wanted until you receive the QSL or LOTW.

On February 24, 2020 at 11:42 AM JP <jon.perelstein@...> wrote:

Running JTAlert 2.15.6

Running into this problem repeatedly
Worked a station FT8 that was a new state on the band.  After I logged it (log alert looks okay), other stations in same state still show up as needed ON THE SAME BAND with the same mode.  For example, worked W1WWB (North Carolina, grid EM95) on 40 meters - first time for that state and grid on that band.  Hours later, I'm still getting North Carolina stations as alerts as "Wanted US State". 

I have following settings 
Wanted US State - by Individual Band, by Individual Mode - Mode FT8
Wanted Grid - by Individual Band, by Individual Mode - Mode FT8
Filters - Do not show Worked Before (B4) Callsigns
Using Standard ADIF File Logging

The W1WWB contact is logged in both WSJT-X log and in JTAlert log.

Jon, AI1V

 


locked Wanted US State Not Updating

JP
 

Running JTAlert 2.15.6

Running into this problem repeatedly
Worked a station FT8 that was a new state on the band.  After I logged it (log alert looks okay), other stations in same state still show up as needed ON THE SAME BAND with the same mode.  For example, worked W1WWB (North Carolina, grid EM95) on 40 meters - first time for that state and grid on that band.  Hours later, I'm still getting North Carolina stations as alerts as "Wanted US State". 

I have following settings 
Wanted US State - by Individual Band, by Individual Mode - Mode FT8
Wanted Grid - by Individual Band, by Individual Mode - Mode FT8
Filters - Do not show Worked Before (B4) Callsigns
Using Standard ADIF File Logging

The W1WWB contact is logged in both WSJT-X log and in JTAlert log.

Jon, AI1V


locked Re: LoTW Flag not always correct

Paul AC9O
 

Yep, that's it! Sorry to bother you. Didn't think to look.

73, and thanks for a great program!

Paul


locked Re: Worked B4 Not Working

gary.sewell@...
 

Mine did the same thing when I upgraded to 2.15.10. Found out that both "Ignore Band" and "Ignore Mode" in the "Worked B4" menu had been checked. After I unchecked them everything worked correctly.

Gary


locked Re: Incorrect group?

Neil Foster
 

Thanks Laurie...this happens on only this PC, the one in the shack is OK. How to correct?
TNX
Neil


locked Re: False QSO Not Logged message with ACLog6.6

HamApps Support (VK3AMA)
 

On 24/02/2020 11:57 am, Terry Scaia wrote:
Recently I have been seeing false QSO Not Logged Errors, indicating ACLog 6.6 did not record the QSO. This happens about once per five QSOs. In all instances I have verified properly logged QSOs in ACLog. I have increased "Check QSO Record" in JTAlert 2.15.10 from default to 15 seconds. The error persists. I've also noted the time to actually record the QSO in ACLog is less than 3 seconds, and the error appears at that time, NOT after 15 seconds.

I am very happy with the WSJT-X - JTAlert - ACLog combination, and am only troubled by these false QSO Not Logged messages.

Tnx de Terry - N4IYB
Terry,

If this is random, than the "Check QSO Record" time is the correct setting to adjust.

While you may be seeing the QSO appear in ACLog within 3 seconds, that does not mean it has been written to the physical log file. JTAlert checks the physical file to confirm a QSO was logged. ACLog (like most of the other loggers) are typically performing post logging activities, like xml lookups and online log uploads all of which are affected by your Internet speed and the responsiveness of the online service. Typically it is not until the post logging activities have been completed is the QSO finally written to the log file.

Do you have ACLog set to perform online log uploads and/or an xml lookup? What type of Internet access do you have and is it subject to slowdown depending on other activities in your house (eg. video streaming)?

If you confident that QSOs logged to ACLog by JTAlert are not failing, then you can turn off the logging confirmation check performed by JTAlert. See the Logging section of the Settings window, scroll the Logging Options down to reveal the "Do not check or report logging success/failure" checkbox.

   

de Laurie VK3AMA