Date   

locked Re: JT Alert 2.50.0 update and now nothing works on JT Alert app

HamApps Support (VK3AMA)
 

On 16/04/2021 11:27 pm, Ed K0iL wrote:
So why isn't the JTAlertV2.Manager Application running as installed?  Hmmm.

The Manger is installed, it is your Norton protection software that is interfering with its execution.

See https://hamapps.groups.io/g/Support/message/34373

de Laurie VK3AMA


locked Re: JT Alert 2.50.0 update and now nothing works on JT Alert app

HamApps Support (VK3AMA)
 

On 16/04/2021 11:25 pm, Ed K0iL wrote:
JTAlertV2.Manager Application is installed in the pluginsX folder, but it is not running per Task Manager.

If it is not running that is the problem.

JTAlert automatically tries to restart the program if it is found not running. If you're not seeing the Manager process being started and stopped approx every 2 seconds, that indicates that something is clamping down very hard on it getting executed.

You mention Norton in one of your other message. That will be the problem. Depending on Norton settings, low-use
(based on Norton users-base counts) files, which Ham based applications are, suffer from lack of reputation and Norton is notorious for this time of reputation application blocking. You will need to set Norton to consider JTAlert safe, and likely remove any blocks it has already put in place.

Sorry, I can't offer any informed advice on how to setup Norton to stop its inappropriate blocking, you're best to engage with Norton support direct.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0

HamApps Support (VK3AMA)
 

On 17/04/2021 1:15 am, Walter Reinert wrote:
When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Walt,

Another user had a similar issue, different line number. It was ultimately resolved by deleting the JTAlert config file. I suspect some setting within the file is the root cause, unfortunately neither my self or the Test Team have encountered the error.

Try temporarily renaming the JTAlert config file so that when JTAlert starts it creates a new file. Does the error occur after doing that?

The JTAlert help file (NOT the 2.50.0 features help file),  "Troubleshooting -> Setting Changes Not Remembered" section discusses where the config file is located and also how to roll-back to an earlier version of the config if needed. The help file can be access via the "HamApps JTAlert" Windows start-menu group if you're unable to from within JTAlert.

If JTAlert still throws the error despite being started without a config file, my suggestion at this time is to rollback to JTAlert 2.16.17

If JTAlert stops throwing the error after renaming the config.sqlite file, please zip it up and send to me direct (not via this group) so I can try and reproduce the problem.

Let me know your results.

de Laurie VK3AMA


locked Re: JTAlert - 73 Badge

HamApps Support (VK3AMA)
 

On 17/04/2021 4:38 am, Craig wrote:
Thanks Jim for your note / comments. Yes, sure seems reasonable to me that clicking on a 73 Badge would enable TX... that is the intent of showing the 73 badge - but as far as I can tell it doesn't work, and it is not obvious (as yet) that there is an option to make it work.  Should operate as CQ Badge does...

Maybe Laurie can add some perspective on this...

73, Craig

I already answered here https://hamapps.groups.io/g/Support/message/34362

I cant make JTAlert perform a WSJT-X function that WSJT-X itself does not support. I'm good, but not that good ;-)

de Laurie VK3AMA


locked Re: JTAlert 2.50.0

HamApps Support (VK3AMA)
 

On 17/04/2021 2:12 am, Angus G0UGO wrote:

That’s exactly what’s happening with me

 

Angus G0UGO


What line number, is it the same as the original poster 11087 ?

de Laurie VK3AMA


locked Re: JTAlert 2.50.0

HamApps Support (VK3AMA)
 

On 17/04/2021 1:56 am, Steve H. wrote:
I got the same issue. It happens when a variable is used but not declared first . 

There are NO undeclared variables with the JTAlert code-base. I have the compiler set to abort compilation if undeclared variables are encountered.

These type of AutoIT errors are notorious for producing an incorrect error cause description along with sometime very inaccurate line numbers.

What line number did you get for your error, is it the same as the original poster, 11087 ?

de Laurie VK3AMA


locked Re: Issues after moving to a new Win10 PC

HamApps Support (VK3AMA)
 

On 17/04/2021 2:41 am, Phil Cooper via groups.io wrote:

Thanks for that, but I am not a member of that group, so am unable to post there.


Phil,

Since you already have a groups.io membership, other wise you could not post here in this group, it is a simple matter to join additional groups.io groups, there is no need for additional accounts.

If your non-membership of the WSJTX group is by choice, then disregard my advice. I understand not being a member of a group for personal reasons, there are several that I am not a member of for personal reasons.

No need for a reply.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 upgrade Callsign Window

HamApps Support (VK3AMA)
 

On 16/04/2021 8:24 pm, OM Marlon via groups.io wrote:
I can click / double click callsigns and jtdx would respond. 

I was referring to my station callers, they will now be listed, multiple if several others called too, below callsign list. After concluding qso with a callsign listed in callers, i was wondering if, by just clicking the other callers listed, i can trigger jtdx. That woul have been nice, but for now use it to remind me, the callsigns i have not concluded qso, the will all be listed in users. I hope I described the situation better hihi. Thanks

Marlon

I understand.

The callsigns in your Callers display behave the same as the callsigns in the main Callsigns display with respect to click/double-clink events. Both events use the exact same code internally.

Are you clearing decodes in JTDX regularly?

If a Callsign in JTAlert is clicked, WSJT-X and JTDX will not respond if the original decode for that Callsign is no longer available.

Are you clicking older callsigns that have had their original decode cleared in JTDX?

de Laurie VK3AMA


locked Re: JTAlert - 73 Badge

Craig
 

Thanks Jim for your note / comments. Yes, sure seems reasonable to me that clicking on a 73 Badge would enable TX... that is the intent of showing the 73 badge - but as far as I can tell it doesn't work, and it is not obvious (as yet) that there is an option to make it work.  Should operate as CQ Badge does...

Maybe Laurie can add some perspective on this...

73, Craig

On Fri, Apr 16, 2021 at 1:34 PM Jim Cooper <jim.w2jc@...> wrote:
On 16 Apr 2021 at 12:19, Craig wrote:

> Do have a question - when the 73
> decode badge window appears, was it
> intended that double-clicking would
> not enable TX?   Do not see the
> option on this.

my experience is that clicking on a call
showing the 73 badge SETS UP the
messages for that call in WSJT-X, but
does not enable the Enable Tx (which seems
reasonable, as the operator should decide
when to start calling a 'tail ender' call --
if you don't have the Tx freq locked, you
would start calling on top of the ending
part of the current QSO).   

When you click on a call with the CQ badge,
it does enable Enable Tx because it's known
that you want to start calling right away.




locked "Callers" Display v2.50.0

Ron W3RJW
 
Edited

In order to save screen space my "Callsigns" decoded window is arranged to be 2 columns wide, with rows from top to the bottom of the screen.  The "callers" display is a neat feature, but when you select the display position to be "bottom" (for instance) I only see at most two of the callers.  If there are more then two (often), they propagate off Callsigns display to the right.  I guess I expected that they would fill up from the bottom. two columns wide or whatever the width of the window was set to.

I don't know if that's possible or even practicable.

Thanks for some great new features.

--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.0, HRD Deluxe v6.7.0.323
FTdx-3000, SignaLink USB


locked Re: Another Callsign Window Issue

HamApps Support (VK3AMA)
 

On 17/04/2021 12:26 am, Tom Job wrote:
I have noticed that the callsign window does not always clear the old callsigns.  I have experienced the window populating 6 or 7 decode cycles before clearing. It's not a constant issue but rather an intermittent one. This is the first version of JTAlert that I have seen this.  Of course, I can clear it with the escape key but that shouldn't have to be done.  Could it be a Windows "thing"?  I am using Windows 8.1.

Has anyone else experienced this? 

Thanks....Tom VE3II

I have not seen any other reports of this behavior. It might be win8.1 related, but I am inclined to think a PC capability issue perhaps since you're running Win8.

What are your hardware specs, CPU core count, installed Ram?

What CPU usage numbers (percentage) are you getting at the end of a decode period when WSJT-X is at its busiest?

Is WSJT-X still displaying decodes from the previous period when the new period starts?

When this occurs, is it on very busy bands, like 20m & 40m where there are dozens of decodes per period?

de Laurie VK3AMA



locked Re: JTAlert 2.50.0

Angus G0UGO
 

JTDX current release candidate version

Angus G0UGO 

-------- Original message --------
From: "Michael Black via groups.io" <mdblack98@...>
Date: 16/04/2021 19:09 (GMT+00:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0

What version of WSJTX or JTDX are you using?

Mike W9MDB




On Friday, April 16, 2021, 01:02:40 PM CDT, Angus G0UGO <angus.g0ugo@...> wrote:


That’s exactly what’s happening with me

 

Angus G0UGO

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Walter Reinert
Sent: 16 April 2021 16:15
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.50.0

 

When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: JTAlert - 73 Badge

HamApps Support (VK3AMA)
 

On 17/04/2021 2:19 am, Craig wrote:
GM.  First, Congratulations on 2.5  Great implementation.  Do have a question - when the 73 decode badge window appears, was it intended that double-clicking would not enable TX?   Do not see the option on this.  Thanks again.

JTAlert doesn't control whether WSJT-X goes into TX in response to a double-click, it simply sends the appropriate command to WSJT-X to setup for the QSO, the choice to TX is decided by WSJT-X internally.

JTAlert doesn't make any checks of decode type when the Callsign is double-clicked, it ALWAYS sends the command to WSJT-X, regardless.

A quick test, what does WSJT-X do when you double-click a "73" decode within WSJT-X (ignore JTAlert for a moment), does it go into TX, it will not (based on my tests).

de Laurie VK3AMA


locked Re: Callsign window has some problems

Laurie, VK3AMA
 

On 17/04/2021 4:08 am, Joe Subich, W4TV wrote:

Well, you can always disable the callers list all together since the
callers are duplicated in the main display.  Click on the gear icon
or press F2, then select Callers and choose "Disabled" in the "Display
Position" box.

With your single line, you might also be able to choose Left or Right
and divide the long single line.

I use a tall and narrow Callsigns window since it fits my display real
estate better than a horizontal display so I have room to allow one
short line of "callers" at the bottom of the display.

73,

  ... Joe, W4TV
You beat me to my response, which essentially says the same, but not as clear in the detail.

de Laurie VK3AMA


locked Re: Callsign window has some problems

Laurie, VK3AMA
 



On 17/04/2021 1:59 am, WB5JJJ - George wrote:
Thanks for you suggestion Joe.  But I desire to use a minimalist single line display for this as with earlier versions.  I'll live with the pop UNDER for lower priority items to keep it to one line.  Don't need a 2nd line that will be mostly empty space occupying real estate.  Besides the calling me calls are duplicated in both lines anyway just wasting space.  

JTA filters all the chaff from the wheat for me, leaving just new LoTW callers and wanted DXCC, New Prefix and a couple other alert items.  A quick glance tells me all I really need to know in the moment, while WSJTx BA shows me the rest, if I'm interested.  
--
73's
George - WB5JJJ

If you want single line only, which will automatically show a vertical scroll bar when the number of callsigns exceeds the space available, you need to have the Callers display position set to either "Right" or "Left", NOT "Top" or "Bottom".

If you're not interested in seeing the Callers in a separate view of the Callsigns window (where they persists and don't clear at the end of a period) then set the Callers display position to "Disabled"

   

de Laurie VK3AMA
 


locked Re: JTAlert 2.50.0

Michael Black
 

What version of WSJTX or JTDX are you using?

Mike W9MDB




On Friday, April 16, 2021, 01:02:40 PM CDT, Angus G0UGO <angus.g0ugo@...> wrote:


That’s exactly what’s happening with me

 

Angus G0UGO

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Walter Reinert
Sent: 16 April 2021 16:15
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.50.0

 

When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: Callsign window has some problems

Joe Subich, W4TV
 

Well, you can always disable the callers list all together since the
callers are duplicated in the main display. Click on the gear icon
or press F2, then select Callers and choose "Disabled" in the "Display
Position" box.

With your single line, you might also be able to choose Left or Right
and divide the long single line.

I use a tall and narrow Callsigns window since it fits my display real
estate better than a horizontal display so I have room to allow one
short line of "callers" at the bottom of the display.

73,

... Joe, W4TV

On 2021-04-16 11:59 AM, WB5JJJ - George wrote:
Thanks for you suggestion Joe.  But I desire to use a minimalist single line display for this as with earlier versions.  I'll live with the pop UNDER for lower priority items to keep it to one line.  Don't need a 2nd line that will be mostly empty space occupying real estate.  Besides the calling me calls are duplicated in both lines anyway just wasting space.
JTA filters all the chaff from the wheat for me, leaving just new LoTW callers and wanted DXCC, New Prefix and a couple other alert items.  A quick glance tells me all I really need to know in the moment, while WSJTx BA shows me the rest, if I'm interested.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: JTAlert 2.50.0

Angus G0UGO
 

That’s exactly what’s happening with me

 

Angus G0UGO

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Walter Reinert
Sent: 16 April 2021 16:15
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.50.0

 

When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: JTAlert 2.50.0

Steve H.
 

I got the same issue. It happens when a variable is used but not declared first . 


On Fri, Apr 16, 2021, 11:15 Walter Reinert <nj8g@...> wrote:
When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: JTAlert - 73 Badge

Jim Cooper
 

On 16 Apr 2021 at 12:19, Craig wrote:

Do have a question - when the 73
decode badge window appears, was it
intended that double-clicking would
not enable TX? Do not see the
option on this.
my experience is that clicking on a call
showing the 73 badge SETS UP the
messages for that call in WSJT-X, but
does not enable the Enable Tx (which seems
reasonable, as the operator should decide
when to start calling a 'tail ender' call --
if you don't have the Tx freq locked, you
would start calling on top of the ending
part of the current QSO).

When you click on a call with the CQ badge,
it does enable Enable Tx because it's known
that you want to start calling right away.

2761 - 2780 of 36897