Date   

locked Re: Logging failures do not update worked before information

HamApps Support (VK3AMA)
 

On 10/05/2020 6:22 am, g4wjs wrote:
Hi Laurie,

it seems that when JTAlert cannot confirm logging of a QSO in the configured logging application it does not update its internal worked before database. Often these logging failures are due to slow updates to the logging application even though the log is eventually updated. Restarting JTAlert does sort it out but until then it is easy to mistakenly work the same station twice.



-- 
73
Bill
G4WJS.
Hi Bill,

Your correct, the internal B4 cache (held in memory) does not get updated if JTAlert is unable to confirm a QSO was logged.

What Logger are you using that is experiencing the delays?

If your logger is consistently slow in writing the QSO to the log file/database and your happy that QSOs are reliably getting logged, there is the option is to turn on the "Do not check or report logging success/failure" serring, under the Logging section of the Settings (scroll the checkbox display down). With that set, JTAlert will set the B4 status regardless and not perform any code-blocking checks.

There is the option to increase the QSO check time, but that can be problematic, especially with the short period FT4, as the delay QSO check delay, which is blocking the UI thread, can extend into the new decode period and JTAlert may miss the period. The main JTAlert code is single-threaded and synchronous (no async functionality) so any additional delay added to the QSO logged check function blocks there entire code.

Rather than restarting JTAlert you can use the "Alerts -> Clear B4 cache" menu (2nd from the top).

de Laurie VK3AMA


locked Re: Multiple instance JTAlert configuration.

HamApps Support (VK3AMA)
 

On 10/05/2020 5:19 am, asobel@... wrote:

Multiple  JTAlert instances are using common configuration. Sometimes I need to have it with separate configurations but I could not find a way to do it.

Is there a way of doing it?

Is this is not possible with the current software version, please consider adding it soon.

 

Amos 4X4MF

Sorry, separate configurations per JTAlert instance is not possible with the V2 series of JTAlert, it would require a significant code rewrite which will not happen. The V2 code is near EOL (End Of Life) and there will not be any further significant code changes, defect fixes and minor enhancements only. My focus is on getting JTAlertV3 finished any released, but that is still several months away unfortunately.

de Laurie VK3AMA


locked Re: I miss the old layout

HamApps Support (VK3AMA)
 

On 11/05/2020 12:33 am, Uwe wrote:
What if JTAlert makes it as Firefox has it? Right-hand click on the window title bar gives an option to show / hide the menus.

Or, alternatively, show the menu only when the mouse pointer hovers over the window title bar?

Could that be a way?
No, that wont be possible. It was the menus in the titlebar and the mouse position/click detection management that were the problem. The code for placing the menus (and the Band Activity display) in the titlebar was very complex due to limitations with the AutoIT compiler.

I have decided to abandon any further attempts at trying to correct the missing/misplaced menus defect experienced by some users (I was never able to reproduce the defect in testing). Maintaining two code bases was time consuming and error-prone.

Then there was the non-code issue with the seemingly endless support requests (on average 3 or 4 requests per week) from affected users who were either unwilling or unable to read the prominent display on the JTAlert download page advising of the use of the "Alt Layout" version to correct the missing menus problem.

If you wish to continue to have the Traditional Layout experience, your only option is to stay with 2.16.4. Similar to how JT65-HF, HB9HQX and MixW users are limited to 2.13.10 and XP users to 2.11.5.

There comes a point in time where old functionality is no longer available and that point has been reached with the Traditional Layout code.

de Laurie VK3AMA


locked Re: JTAlert 2.16.5 is available: Missing fields?

HamApps Support (VK3AMA)
 

On 11/05/2020 2:08 am, Richard Mead wrote:
I've not seen a mention so maybe it's just my install.
I no longer see the fields Continent or Country in the popup when I mouse over any call.
I reverted to 2.16.4 and they returned. Not a big deal but thought I'd mention...
73
Richard WB6NGC
Richard,

Tnx for the report. I can confirm this is a defect.
It has been corrected for the next release.

Sorry for the inconvenience.
de Laurie VK3AMA


locked Re: Zones Problem

HamApps Support (VK3AMA)
 

On 10/05/2020 12:58 pm, Dave Garber wrote:
I suspect an issue with adi from jtalert
It is not a JTAlert problem. If JTAlert shows zones in the log fields area, that is what gets sent in the ADIF packet to Log4OM.

If a zone is unknown than there will be no zone data in the adif packet sent. JTAlert deliberately does not send any Zone numbers if the value is NOT greater than zero. Similarly any data fields that are empty the corresponding adif field is simply not included in the adif packet. That is JTAlert only includes adif fields for non-empty and non-zero (> 1) data fields.

The problem is clearly with Log4OM V2.

de Laurie VK3AMA


locked Re: Welcome Back Laurie

HamApps Support (VK3AMA)
 

On 9/05/2020 7:53 am, WB8ASI Herb wrote:
Can't imagine your backlog.  Hope you had a good getaway.  Bet you're ready to start your next vacation.  73 Herb WB8ASI
Thanks Herb.

I was not officially back. I was in transit from my non-Internet QTH, spending some time at a family members house and wanted to check the unread messages and couldn't resist reply to some.

I am now back home and online again.

de Laurie VK3AMA


locked Re: JTAlert 2.16.5 Download

Jim N6VH
 

On 5/10/2020 10:15 AM, Robert T wrote:

Has anyone been able to download and successfully install ver 2.16.5 without their virus scan deleting the install saying it has a virus?

Bob, K2RET
_._,_._,_


Yes. Using Norton 360. I did get the message from Norton saying this is new, and not may users (or words to that effect), but all I had to do was click "Trust" and no problem.  This is a pretty standard message from Norton regarding JTAlert, but never a mention of a virus.

73,

Jim N6VH


locked Re: Issues working Special event calls

g4wjs
 

Hi Phil,

you can open a local copy from the WSJT-X "Help" menu.

73
Bill
G4WJS.

On 10/05/2020 19:26, Phil Cooper via groups.io wrote:

Hi Bill,

 

If I could actually get to the site, I would check again. All I am getting at the moment is a message that the connection has timed out.

I did scan through it last week, but couldn’t see the wood for the trees. I may have a local copy here on my shack PC, so I will check that out.

 

Thanks for the reply…

 

73 de Philo GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of g4wjs
Sent: 10 May 2020 16:16
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issues working Special event calls

 

On 10/05/2020 16:07, Phil Cooper via groups.io wrote:

Hi all,

 

I am currently running SES GU75LIB along with other club members (each operating from home!) and I have noted a small quirk when working SES calls, and other non-standard calls.

 

When being called by one of the SES calls with (say) a long suffix, or an ordinary stations signing /P, /M, or /QRP, my exchange ONLY sends the callsigns.

To make it work, I have had to lose the /x or truncate the SES call, which only serves to cause confusion.

 

Is this something that is known about? Or have I stumbled on an issue?

 

73 de Phil GU0SUP

Hi Phil,

please note the last sentence of the third paragraph here in the WSJT-X User Guide:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.2.html#COMP-CALL

73
Bill
G4WJS.


--
73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Issues working Special event calls

Phil Cooper
 

Hi Bill,

 

If I could actually get to the site, I would check again. All I am getting at the moment is a message that the connection has timed out.

I did scan through it last week, but couldn’t see the wood for the trees. I may have a local copy here on my shack PC, so I will check that out.

 

Thanks for the reply…

 

73 de Philo GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of g4wjs
Sent: 10 May 2020 16:16
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issues working Special event calls

 

On 10/05/2020 16:07, Phil Cooper via groups.io wrote:

Hi all,

 

I am currently running SES GU75LIB along with other club members (each operating from home!) and I have noted a small quirk when working SES calls, and other non-standard calls.

 

When being called by one of the SES calls with (say) a long suffix, or an ordinary stations signing /P, /M, or /QRP, my exchange ONLY sends the callsigns.

To make it work, I have had to lose the /x or truncate the SES call, which only serves to cause confusion.

 

Is this something that is known about? Or have I stumbled on an issue?

 

73 de Phil GU0SUP

Hi Phil,

please note the last sentence of the third paragraph here in the WSJT-X User Guide:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.2.html#COMP-CALL

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: JTAlert 2.16.5 and eSET now fixed

 

Good to know Graham.  Did you send off a sample?  I did, but haven’t heard back.

 

__________

Dan – K4SHQ

CFI/II

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Graham Alston
Sent: Saturday, May 9, 2020 7:11 PM
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.16.5 and eSET now fixed

 

eSET have updated their virus definitions and JTAlert download and installation now works fine.

Graham VK3GA


--
Dan - K4SHQ


locked Re: JTAlert 2.16.5 Download

Daniel VE3NI
 

Yes, usual download and install.

 

No problem

 

AV is Webroot.

 

Cheers es 73,

Daniel VE3NI / NI2D

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Robert T
Sent: Sunday, May 10, 2020 1:15 PM
To: support@hamapps.groups.io
Subject: [HamApps] JTAlert 2.16.5 Download

 

 

Has anyone been able to download and successfully install ver 2.16.5 without their virus scan deleting the install saying it has a virus?

 

Bob, K2RET


locked Re: JTAlert 2.16.5 Download

Jacques Corbu
 

Yes all downloaded and installled without a hitch 

most likely a false postive  I  have JTAlert excluded in my antivirus etc .

73 Jacques F1VEV  Win 10 Pro  Avast 


locked JTAlert 2.16.5 Download

Robert T
 


Has anyone been able to download and successfully install ver 2.16.5 without their virus scan deleting the install saying it has a virus?

Bob, K2RET


locked JTAlert 2.16.5 not highlighting Wanted Callsigns consistently?

Jim Reisert AD1C
 

Laurie, thanks for updating JTAlert in anticipation of the new RC of WSJT-X.

It seems that 2.16.5 may not be highlighting Wanted Callsigns
consistently. Example: KM4MQC is calling CQ on 10 meter FT8. I
right-clicked and added the call to my Wanted Callsigns list. The
next time he called CQ, JTAlert still showed a light-blue background
instead of a purple background.

Earlier to test this, I reverted to 2.16.4, and I did the same thing
for K1DG when he was calling CQ on 17m. His Wanted Callsign
highlighted as expected.

Has anyone else noticed this?

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us


locked Re: JTAlert 2.16.5 is available: Missing fields?

Ernie Barnhart
 

Same here.
73
Ernie N8DVE


locked Re: JTAlert 2.16.5 is available: Missing fields?

Richard Mead WB6NGC
 

I've not seen a mention so maybe it's just my install.
I no longer see the fields Continent or Country in the popup when I mouse over any call.
I reverted to 2.16.4 and they returned. Not a big deal but thought I'd mention...
73
Richard WB6NGC


locked Re: Issues working Special event calls

g4wjs
 

On 10/05/2020 16:07, Phil Cooper via groups.io wrote:

Hi all,

 

I am currently running SES GU75LIB along with other club members (each operating from home!) and I have noted a small quirk when working SES calls, and other non-standard calls.

 

When being called by one of the SES calls with (say) a long suffix, or an ordinary stations signing /P, /M, or /QRP, my exchange ONLY sends the callsigns.

To make it work, I have had to lose the /x or truncate the SES call, which only serves to cause confusion.

 

Is this something that is known about? Or have I stumbled on an issue?

 

73 de Phil GU0SUP

Hi Phil,

please note the last sentence of the third paragraph here in the WSJT-X User Guide:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.2.html#COMP-CALL

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Issues working Special event calls

Phil Cooper
 

Hi all,

 

I am currently running SES GU75LIB along with other club members (each operating from home!) and I have noted a small quirk when working SES calls, and other non-standard calls.

 

When being called by one of the SES calls with (say) a long suffix, or an ordinary stations signing /P, /M, or /QRP, my exchange ONLY sends the callsigns.

To make it work, I have had to lose the /x or truncate the SES call, which only serves to cause confusion.

 

Is this something that is known about? Or have I stumbled on an issue?

 

73 de Phil GU0SUP

 

 


locked Re: I miss the old layout

Uwe, DG2YCB
 

What if JTAlert makes it as Firefox has it? Right-hand click on the window title bar gives an option to show / hide the menus.

Or, alternatively, show the menu only when the mouse pointer hovers over the window title bar?

Could that be a way?

73 de Uwe, DG2YCB

Btw. As I need more vertical space, I've programed a couple of WSJT-X versions with a slightly different UI. Among them: A widescreen version optimized for laptops and a version with an alternative layout, both of which offer a larger Band Activity window! If someone else would like to use them: https://sourceforge.net/projects/wsjt-x-improved/.


locked Re: Zones Problem

Jim N6VH
 

Dave,

See my reply to Herb. As a test, I logged N3BNA from WSJT-X / JTAlert to Log4OM. Without using lookups, the zones were logged correctly. When I turned on lookups from QRZ, the QSO was logged with wrong zones since N3BNA doesn't have zones listed on QRZ. As i mentioned to Herb, this is A Log4OM problem, not WSJT-X or JTAlert.

73,

Jim N6VH

On 5/9/2020 7:58 PM, Dave Garber wrote:
Again, I say I had the same issue, and tried to report it on the log4om forum.  never saw an answer yet.  I suspect an issue with adi from jtalert, as to how they are handling it, cause jtalert shows correct info ( per qrz anyway), but it is not the info logged.

perhaps if more add to the forum complaint THEY will look into it, please then I will return to the software

Dave Garber
VE3WEJ / VE3IE



5381 - 5400 of 34798