Date   

locked Re: Double click on spot - with JTDX

Doug Munday
 

I've partially solved this question.  Single click on decode does forward the call to JTDX, IF the decode is a CQ.  I seem to remember that JTDX has more rigorous filters on when to go into TX mode, so as not to spam the DX if they are not CQ'ing.  Wonder if there is a work around for this, as I would still like to have the call forwarded to JTDX, just not go into TX mode, which it does not at this time. 

Thanks for any clarifications!

Doug - W7DRM


locked Double click on spot - with JTDX

Doug Munday
 

New to JTDX, and testing with latest JTAlert for JTDX (2.15.8), the double click on a spot in JTAlert is not forwarding the call to JTDX.  It does when using WSJTx and JTAlert.  Is this a limitation of JTDX, or something amiss in my settings? 

Thanks,
Doug - W7DRM


locked Re: JTAlert error messages

HamApps Support (VK3AMA)
 

On 25/01/2020 4:57 am, Michael Black via Groups.Io wrote:
Turns out Webroot was blocking JTAlert.exe.  However JTAlert_AL.exe was allowed to run so Bill is up and running now.

I've help other people with Webroot blocking stuff like this.  It's a bit too aggressive and in this case we found the option that affected this was "silent and automatic" with no way to make exceptions.  It was blocking JTAlert from getting process data.  Don't know why the alternate version works though...should be doing the same thing.

de Mike W9MDB
Mike, Tnx very much for sorting this out, your help is appreciated!

The code differences between JTAlert.exe and JTAlert_AL.exe are minimal, they share ~99% the same code. I am starting to suspect that some of these problematic Protection Software products are also triggering simply because of the executable name, JTAlert.exe, with JTAlert_AL.exe getting a pass because it is a relatively new file name.

IMO, any protection software product that causes application operation interference, deletes files or blocks access without notifying the end-user that action has been taken and/or doesn't provide a mechanism to override these unwanted actions is not much better than the malicious applications it is try to protect us from.

de Laurie VK3AMA


locked JTAlert 2.15.8 is available. Full Log4OMV2 support. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

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

This release has support for the newly released Log4OM V2. Both SQLite & MySQL logs are supported.
Log4OM V2 users should view the Help file for proper setup instructions (they are very simple).
See the "Settings -> Logging -> Log4OM V2" topic in the help file. Using the Help button when on the Log4OM V2 section of the JTAlert Settings window will take you to the relevant help topic.

de Laurie VK3AMA

The Release Notes...

2.15.8 (24-JAN-2020)

  *** Includes Callsign database file version 2020-01-24 (2020-January-24)

  New Features:

    - Log4OM V2: Full support for Log4OM V2, both SQLite and MySQL logs.

    - Log4OM V1/V2 SQLite logs: "Test" button to check log file selected is
       a valid SQLite file for the Log4OM version and contains QSO records.
       See Settings window, "Logging -> Log4OM..." sections.

    - Logging option: New "Do not check or report logging success/failure".
       This option when ticked (off by default) instructs JTAlert to not try
       and confirm that a QSO was logged by reading the Loggers log directly.
       Once the logging instruction has been sent, JTAlert goes back to normal
       operation, there are no delays or hangs as JTAlert is stuck waiting to
       confirm the QSO was logged. JTAlert will however still report a logging
       failure when it could not initially establish the TCP or UDP connection
       to the target logger.

  Changes:

    - MySQL support: libmysql.dll file updated to v6.1.10 (previously v5.1.37)

  Fixes:

    - ADIF logging: Excessive time to confirm QSO logged successfully when using
       large adif files. 200,000 record check now takes ~1 sec (previous ~45 secs)



locked Re: JTAlert error messages

Michael Black
 

Turns out Webroot was blocking JTAlert.exe.  However JTAlert_AL.exe was allowed to run so Bill is up and running now.

I've help other people with Webroot blocking stuff like this.  It's a bit too aggressive and in this case we found the option that affected this was "silent and automatic" with no way to make exceptions.  It was blocking JTAlert from getting process data.  Don't know why the alternate version works though...should be doing the same thing.

de Mike W9MDB




On Friday, January 24, 2020, 10:29:59 AM CST, Bill-KC8WSM 070-1191 <kc8wsm@...> wrote:


Good morning.  I was able to get my HRD fixed and now JTAlert opens but I am getting error messages.  These are the two I have received.  I checked the boxes as instructed in the first message then I start receiving the second one.  I'm sure It's a simple fix but I can figure it out.  Any ideas?

image.png

image.png

ReplyForward


locked Re: JTAlert error messages

Michael Ernst
 

Bill KC8WSM,

 

Here are my settings and they work on HRD First of all in WSJT-X, also check the Secondary UDP Server, as seen here (note that this one uses port 2333 in my setup, I think that is the default):

 

 

Then in JTAlert, change the port to use the one above, as shown here:

 

 

This works on mine.

 

73,

Mike, AE8U

 

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Bill-KC8WSM 070-1191
Sent: Friday, January 24, 2020 11:30 AM
To: Support@hamapps.groups.io
Subject: [HamApps] JTAlert error messages

 

Good morning.  I was able to get my HRD fixed and now JTAlert opens but I am getting error messages.  These are the two I have received.  I checked the boxes as instructed in the first message then I start receiving the second one.  I'm sure It's a simple fix but I can figure it out.  Any ideas?

 

image.png

 

image.png

 

ReplyForward

 


locked JTAlert error messages

Bill-N7RI
 

Good morning.  I was able to get my HRD fixed and now JTAlert opens but I am getting error messages.  These are the two I have received.  I checked the boxes as instructed in the first message then I start receiving the second one.  I'm sure It's a simple fix but I can figure it out.  Any ideas?

image.png

image.png

ReplyForward


locked Re: JTAlert won't open

HamApps Support (VK3AMA)
 

On 24/01/2020 2:02 pm, Bill-KC8WSM 070-1191 wrote:
Does this help?

Yes it helps. I was starting to suspect that you may have been running a non-standard WSJT-X build, but your image dispels that thought.

Regarding the JTAlert waiting for WSJT-X message, does it include any mention of an instance, like "[2nd Instance]"?
If so that indicates that JTAlert is already running, but not visible, and starting JTAlert starts a 2nd JTAlert instance and it is waiting for a 2nd instance of WSJT-X to be started. In this situation you could try and kill off the already running JTAlert using TaskManager, but that risks still leaving some parts of JTAlert running, the better solution is a PC restart to ensure all zombie processes are killed and file-locks removed.

If it is not an instance issue, then I am back to suspecting WSJT-X is running elevated. Are you sure the properties of BOTH wsjtx.exe and the shortcut used to start WSJT-X are not set to run as Administrator. You have to check both.

If your certain that WSJT-X is not running elevated and JTAlert is not trying to start a second instance, then you will need to find someone who is familiar with the programs to remote access your PC and check what is happening. Sorry, I cannot provide that sort of support, but there are some members of this Group who can, hopefully one of them will make contact.

Let me know how you get on, especially if it gets resolved, as I am curious as to what might be the cause.

de Laurie VK3AMA


locked Re: JTAlert won't open

Bill-N7RI
 

Does this help?

image.png

On Thu, Jan 23, 2020 at 5:01 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/01/2020 9:01 am, Bill-KC8WSM 070-1191 wrote:
I think I have the screen shot thing figured out.  Here is a shot of my panel.

Please post an image of your running WSJT-X window. There may be something there that will help identify why JTAlert is not detecting WSJT-X running.

de Laurie VK3AMA


locked Re: Interesting sound issue - Update

John Petrocelli
 

I have been much more vigilant as to the anomaly happening.

I am getting an  even stronger sense that it will happen if "Own Call" is decoded after a "CQ".  The result is, as I stated, that the "CQ" alert sounds but the "Own Call" does not.

Thus it would seem that in this situation, the "CQ" sound preempts the "Own Call" sound.

Note that I also have WSJT-X set to decode at the deepest level, although I doubt that this is a contributing factor.

Thanks again
John - WA2HIP

John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 1/21/2020 3:40 AM, HamApps Support (VK3AMA) wrote:

On 21/01/2020 2:19 pm, John Petrocelli via Groups.Io wrote:
All sounds are working very well in the newest version.

Yet, I have seen recently (past several weeks) that

Sometimes when there is a simultaneous "CQ" audio alert and "Own Call" audio alert the "Own Call" alert will not play.
However the "CQ" alert will play.

I am sensing that if the "CQ" decode hits JTAlert before the "Own Call" that this may happen.

I have checked the "Alerts Priority" and I do see that:
   1) there is no way to flag the "Own Call" as top priority
   2) "CQ" is shown as the top priority

Note that I have not experimented with making the "CQ" alert a lower priority, but that will be next in my efforts.

Has anyone else observed this behavior ??
-- 


John R. Petrocelli - WA2HIP

John,

I'll investigate and see if I can reproduce this behavior.

Regarding setting the "Own Call" as top priority, that is already the case and cannot be changed.
Did you miss this from the "Alerts -> Alerts Priority" section of the Settings?
 

de Laurie VK3AMA



locked Re: JTAlert won't open

HamApps Support (VK3AMA)
 

On 24/01/2020 9:01 am, Bill-KC8WSM 070-1191 wrote:
I think I have the screen shot thing figured out.  Here is a shot of my panel.

Please post an image of your running WSJT-X window. There may be something there that will help identify why JTAlert is not detecting WSJT-X running.

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

HamApps Support (VK3AMA)
 

On 24/01/2020 9:50 am, Doug Munday wrote:
Minor issue when I set up JTAlert Beta 006 and Log4OM V2 using SQLite db.  The path and file name is being written to the button label property.  Screen shot attached.  But it does work as intented, logging into V2 and good confirmation that the log entry was written. 

But upon Settings save, close and settings reopen, the path and file are where they should be.  Cosmetic issue only. 

73,
Doug - W7DRM

Tnx for reporting.

I already found that during some testing. Simple fix.

BTW, the next public release of JTAlert with full Log4OMV2 support is with the Test team. Barring any unforseen problems it should be released tomorrow sometime.

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

Doug Munday
 
Edited

Minor issue when I set up JTAlert Beta 006 and Log4OM V2 using SQLite db.  The path and file name is being written to the button label property.  Screen shot attached.  But it does work as intented, logging into V2 and good confirmation that the log entry was written. 

But upon Settings save, close and settings reopen, the path and file are where they should be.  Cosmetic issue only. 

73,
Doug - W7DRM


locked Re: JTAlert won't open

Bill-N7RI
 

I think I have the screen shot thing figured out.  Here is a shot of my panel.

image.png

On Thu, Jan 23, 2020 at 1:58 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/01/2020 7:06 am, Bill-KC8WSM 070-1191 wrote:
Thanks for the quick response.  I am running the latest version.  Attached is a screenshot of what I see when I go to the security tab under properties.  I'm not sure if that is what it is supposed to be or how to change it if it isn't.
Thanks
Bill
Bill,

Please in future don't post an image of your entire desktop, just the relevant window is all that is need. The forum has limit storage space for images and large desktop images unnecessarily consume space as well as suffering image degradation from the scaling the forum does on over-sized images.

As previously mentioned, you need to check the "Compatibility" Tab of the Properties window to see if your running WSJT-X elevated.
You need to check both the wsjtx.exe file AND the shortcut used to start WSJT-X.

   

If the "Run as administrator" is not set, please post an image of your WSJT-X window (only).

de Laurie VK3AMA


locked Re: JTAlert won't open

HamApps Support (VK3AMA)
 

On 24/01/2020 7:06 am, Bill-KC8WSM 070-1191 wrote:
Thanks for the quick response.  I am running the latest version.  Attached is a screenshot of what I see when I go to the security tab under properties.  I'm not sure if that is what it is supposed to be or how to change it if it isn't.
Thanks
Bill
Bill,

Please in future don't post an image of your entire desktop, just the relevant window is all that is need. The forum has limit storage space for images and large desktop images unnecessarily consume space as well as suffering image degradation from the scaling the forum does on over-sized images.

As previously mentioned, you need to check the "Compatibility" Tab of the Properties window to see if your running WSJT-X elevated.
You need to check both the wsjtx.exe file AND the shortcut used to start WSJT-X.

   

If the "Run as administrator" is not set, please post an image of your WSJT-X window (only).

de Laurie VK3AMA


locked Re: JTAlert won't open

Bill-N7RI
 

Laurie
Just as a follow up, on the oompatibility tab, I am not running as an administrator.
Thanks
Bill
KC8WSM

On Thu, Jan 23, 2020 at 1:06 PM Bill Fults <kc8wsm@...> wrote:
Thanks for the quick response.  I am running the latest version.  Attached is a screenshot of what I see when I go to the security tab under properties.  I'm not sure if that is what it is supposed to be or how to change it if it isn't.
Thanks
Bill

On Thu, Jan 23, 2020 at 12:48 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/01/2020 6:14 am, Bill-KC8WSM 070-1191 wrote:
Good afternoon.  I have upgraded my computer from Windows 7 to Windows 10.  I downloaded WSJT & JTAlert.  WSJT functions properly but JTAlert won't open  Even though WSJT is running, I get a message "waiting for WSJT-X to start.  WSJT-X must be running before JTAlert can continue."  Do I have a setting wrong somewhere?  Anyone have any ideas how to fix this?
Thanks
Bill

Make sure your not running WSJT-X with elevated privileges (i.e. set to run as administrator), check the Properties -> Compatibility tab of both the wsjt.exe file and the shortcut used to start WSJT-X. Also make sure your not running an old version of WSJT-X, the latest is 2.1.2

de Laurie VK3AMA



locked Re: JTAlert won't open

Bill-N7RI
 

Thanks for the quick response.  I am running the latest version.  Attached is a screenshot of what I see when I go to the security tab under properties.  I'm not sure if that is what it is supposed to be or how to change it if it isn't.
Thanks
Bill

On Thu, Jan 23, 2020 at 12:48 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/01/2020 6:14 am, Bill-KC8WSM 070-1191 wrote:
Good afternoon.  I have upgraded my computer from Windows 7 to Windows 10.  I downloaded WSJT & JTAlert.  WSJT functions properly but JTAlert won't open  Even though WSJT is running, I get a message "waiting for WSJT-X to start.  WSJT-X must be running before JTAlert can continue."  Do I have a setting wrong somewhere?  Anyone have any ideas how to fix this?
Thanks
Bill

Make sure your not running WSJT-X with elevated privileges (i.e. set to run as administrator), check the Properties -> Compatibility tab of both the wsjt.exe file and the shortcut used to start WSJT-X. Also make sure your not running an old version of WSJT-X, the latest is 2.1.2

de Laurie VK3AMA



locked Re: Long logging time

Charlie Hoffman
 

I turned off the logging to eQSL and that (almost) eliminated all my delays.
I'm now only logging to QRZ and HRDLog instantaneously and will send my logs to eQSL and LOTW as a batch at the end of my sessions.

Now I get an occasional delay and it appears that QRZ is causing the issue, not the internet, JTA software, or CPU speed.

BTW, I have 100 Mb internet with Spectrum.

TU
Charlie WD4CNO


locked Re: JTAlert won't open

HamApps Support (VK3AMA)
 
Edited

On 24/01/2020 6:14 am, Bill-KC8WSM 070-1191 wrote:
Good afternoon.  I have upgraded my computer from Windows 7 to Windows 10.  I downloaded WSJT & JTAlert.  WSJT functions properly but JTAlert won't open  Even though WSJT is running, I get a message "waiting for WSJT-X to start.  WSJT-X must be running before JTAlert can continue."  Do I have a setting wrong somewhere?  Anyone have any ideas how to fix this?
Thanks
Bill

Make sure your not running WSJT-X with elevated privileges (i.e. set to run as administrator), check the Properties -> Compatibility tab of both the wsjtx.exe file and the shortcut used to start WSJT-X. Also make sure your not running an old version of WSJT-X, the latest is 2.1.2

de Laurie VK3AMA



locked JTAlert won't open

Bill-N7RI
 

Good afternoon.  I have upgraded my computer from Windows 7 to Windows 10.  I downloaded WSJT & JTAlert.  WSJT functions properly but JTAlert won't open  Even though WSJT is running, I get a message "waiting for WSJT-X to start.  WSJT-X must be running before JTAlert can continue."  Do I have a setting wrong somewhere?  Anyone have any ideas how to fix this?
Thanks
Bill