Date   

locked Re: New Feature Enable Fill In Circle for On Line Text Messages?

HamApps Support (VK3AMA)
 

On 20/11/2020 8:46 am, Hasan Schiers N0AN wrote:
New feature listed, but I can't find where to turn it on:
2.16.16
A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.
TIA, 73, N0AN

The full release notes entry reads...
    - Decodes Window Online Indicators: Callsigns that are online for text message
       receipt will be shown with an underline, the same as the main JTAlert
       Callsigns display. A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.

This applies to the Decodes Window only. You need to look in the Decodes Window Settings.


de Laurie VK3AMA



locked Re: does not work

Tom Melvin
 

Mark

Sorry the description you give - it’s not really too obvious what the problem is.

The current release of JTAlert is 2.16.16 - you mention jumping back 10 versions   to 2.16.6 - is that correct? - did you try any of the versions between 2.16.6 and 2.16.16

What version of WSJT-X are you running? - actually you don’t mention the version of JTAlert - what is  that?

Regards

Tom
GM8MJV


On 19 Nov 2020, at 21:46, Mark KB7N <mark.kb7n@...> wrote:

Does not work. Would not trans decoded call to WSJT-x.
 
Reloaded 2.16.6 to get back on the air.
 
M.
 
 
Sent from Mail for Windows 10
 


locked New Feature Enable Fill In Circle for On Line Text Messages?

Hasan Schiers N0AN
 

Apologies for sending prior post to wrong place, shoul dhave been more careful.

New feature listed, but I can't find where to turn it on:
2.16.16
A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.
TIA, 73, N0AN

Hasan


locked does not work

Mark KB7N
 

Does not work. Would not trans decoded call to WSJT-x.

 

Reloaded 2.16.6 to get back on the air.

 

M.

 

 

Sent from Mail for Windows 10

 


locked Re: RR73 73 PROBLEM

Tom Melvin
 


Are we talking about a sound alert or a visual one?


The release notes do mention this: 


WSJT-X Decode Highlighting: "73" or "RR73" decode highlighting no longer require the CQ Alert to be enabled. A dedicated setting is now available. See the "Applications -> WSJT-X / JTDX" section of the Settings window. 

Note: This and other color highlighting is not available for JTDX. 


If this is not the case you will need to be a little clearer as to what you mean. It also helps to provide which version you are using.

Tom
GM8MJV


On 19 Nov 2020, at 20:07, stevemm0sjh via groups.io <mm0sjh@...> wrote:

There seems a problem with the decodes of RR73 and 73 its comming with a stupid alert,where do you switch that off?


locked Re: RR73 73 PROBLEM

HamApps Support (VK3AMA)
 

On 20/11/2020 7:07 am, stevemm0sjh via groups.io wrote:
There seems a problem with the decodes of RR73 and 73 its comming with a stupid alert,where do you switch that off?

What does "stupid alert" mean? Describe what your experiencing that is unwanted.

de Laurie VK3AMA


locked Re: LOTW data is often wrong

neil_zampella
 

Lets keep the politics OFF THE LIST ...

 

Neil, KN3iLZ


locked Re: After updating WSJT-X to 2.3.0-rc2, it is not reflected in JTAlert

Koike Toshiya
 

JTAlert (and GridTracker) worked fine.
The setting is like this.
(WSJT-X 2.3.0-rc2 Settings Reporting Tab)

(JTAlert 2.16.16 Settings)
Resend UDP Port 2334

(Grid Tracker 1.20.0927 Settings)
Received UDP Port 2334
Multicast is OFF.


JL1JVT Toshiya


locked Re: ADIF file will not ..

Michael Black
 

If you can't find it then how are you uploading it to LOTW?




On Thursday, November 19, 2020, 06:19:12 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:


I am having further problem locating the audit file to upload. Just not my day

WA9JBQ 

On Wed, Nov 18, 2020 at 12:00 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Still no ADIF file.




On Wednesday, November 18, 2020, 10:43:39 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:


 

 

Sent from Mail for Windows 10

 

From: Michael Black via groups.io
Sent: Wednesday, November 18, 2020 9:29 AM
To: support@hamapps.groups.io; Support@HamApps.groups.io
Subject: Re: [HamApps] ADIF file will not ..

 

The file that you are uploading that you say doesn't work.

You need to attach the log.adi file to the email.

 

Mike W9MDB

 

 

 

 

On Wednesday, November 18, 2020, 06:44:15 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:

 

 

????

 

On Tue, Nov 17, 2020 at 5:55 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:

Please attach your ADIF file to an email.

 

Mike W9MDB

 

 

 

 

On Tuesday, November 17, 2020, 03:17:10 PM CST, Rick Wyrwas <rwyrwas48@...> wrote:

 

 

 

Sent from Mail for Windows 10

 

From: Michael Black via groups.io
Sent: Tuesday, November 17, 2020 11:53 AM
To: Support@HamApps.groups.io; Support@HamApps.groups.io
Subject: Re: [HamApps] ADIF file will not ..

 

I just created an  ADIF file from JTAlert and it uploaded with TQSL just fine and registered the QSO OK.

 

So if you're having problems maybe show us the ADIF file?

 

Mike W9MDB

 

 

 

 

On Tuesday, November 17, 2020, 10:45:47 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:

 

 

ADIF file will not decode nor upload to Tqsl

 

73

WA9JBQ

 

Sent from Mail for Windows 10

 

 

--

Rick Wyrwas

 

--
Rick Wyrwas


locked Re: ADIF file will not ..

Rick Wyrwas
 

I am having further problem locating the audit file to upload. Just not my day

WA9JBQ 

On Wed, Nov 18, 2020 at 12:00 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Still no ADIF file.




On Wednesday, November 18, 2020, 10:43:39 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:


 

 

Sent from Mail for Windows 10

 

From: Michael Black via groups.io
Sent: Wednesday, November 18, 2020 9:29 AM
To: support@hamapps.groups.io; Support@HamApps.groups.io
Subject: Re: [HamApps] ADIF file will not ..

 

The file that you are uploading that you say doesn't work.

You need to attach the log.adi file to the email.

 

Mike W9MDB

 

 

 

 

On Wednesday, November 18, 2020, 06:44:15 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:

 

 

????

 

On Tue, Nov 17, 2020 at 5:55 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:

Please attach your ADIF file to an email.

 

Mike W9MDB

 

 

 

 

On Tuesday, November 17, 2020, 03:17:10 PM CST, Rick Wyrwas <rwyrwas48@...> wrote:

 

 

 

Sent from Mail for Windows 10

 

From: Michael Black via groups.io
Sent: Tuesday, November 17, 2020 11:53 AM
To: Support@HamApps.groups.io; Support@HamApps.groups.io
Subject: Re: [HamApps] ADIF file will not ..

 

I just created an  ADIF file from JTAlert and it uploaded with TQSL just fine and registered the QSO OK.

 

So if you're having problems maybe show us the ADIF file?

 

Mike W9MDB

 

 

 

 

On Tuesday, November 17, 2020, 10:45:47 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:

 

 

ADIF file will not decode nor upload to Tqsl

 

73

WA9JBQ

 

Sent from Mail for Windows 10

 

 

--

Rick Wyrwas

 

--
Rick Wyrwas


locked Re: LOTW data is often wrong

n3nz Noel
 




On Nov 18, 2020, at 6:13 PM, Gordon Brown <mr.hot.saab@...> wrote:

On Thu, Nov 19, 2020 at 08:27 AM, HamApps Support (VK3AMA) wrote:
Claiming errors without providing any supporting evidence is worthless.
SOunds like the situation with the USA at the moment, Hi Hi


locked Re: LOTW data is often wrong

Russ Ravella
 

:-) !!!!!!


On Nov 18, 2020, at 4:13 PM, Gordon Brown <mr.hot.saab@...> wrote:

On Thu, Nov 19, 2020 at 08:27 AM, HamApps Support (VK3AMA) wrote:
Claiming errors without providing any supporting evidence is worthless.
SOunds like the situation with the USA at the moment, Hi Hi


locked Re: LOTW data is often wrong

Gordon Brown
 

On Thu, Nov 19, 2020 at 08:27 AM, HamApps Support (VK3AMA) wrote:
Claiming errors without providing any supporting evidence is worthless.
SOunds like the situation with the USA at the moment, Hi Hi


locked Re: Multiple Instances JT Alert

HamApps Support (VK3AMA)
 

On 17/11/2020 10:43 pm, SV8JNL SV8JNL wrote:
Hello i would like to know if there is a way to have 2 jtdx apps with 2 jt alert at the same pc same time.
I can have 2 jtdx but  i cant have 2 jt alert to run for each jtdx...Any help?
Thank you.

Simple,

Start your 2 JTDX instances, then start JTAlert twice.

de Laurie VK3AMA


locked Re: unsuccessful contacts with 7q7ru

HamApps Support (VK3AMA)
 

On 17/11/2020 8:46 pm, Tom Melvin wrote:
Does any of this have anything to do with JTAlert?  

Since it seems to be 100% related to wsjt-x would it not be better moving this over to the WSJTX mailing list.

Tom
GM8MJV

I agree, thread is now locked.

de Laurie VK3AMA


locked Re: Greyed menus

HamApps Support (VK3AMA)
 

On 18/11/2020 7:12 pm, Paul F6EXV wrote:
Hi all
Thanks to various people (VK3AMA, MM0HVU, W9MDB) I have managed to configure 2 sessions of Log4OM + JTDX + JTalert to work simultaneously.
These two sessions are for different callsigns, on one single rig (Flex 6500).
So I can have both open at the same time, and go from one callsign to the other in no time at all, which is what I wanted to obtain.

The only thing that still does not work properly is that, on the second JTAlert that I launch, most of the setting menus are greyed out.
It is always the second one launched that has this problem.
I have created the shortcuts in accordance with the manual.

Any idea if this can be solved ?
Thanks + 73
Paul F6EXV

Sorry,

Can't be resolved. What your experiencing is due to limitations in the multi-instance support of JTAlert. All setting changes need to be made from instance #1 only.

See the Help file, "Multiple Instances" topic for more detail, especially the sections headed "Actions restricted to first instance" and "Important".

de Laurie VK3AMA


locked Re: Text message window

HamApps Support (VK3AMA)
 

On 18/11/2020 4:25 am, Guy G4DWV 4X1LT wrote:
That option is greyed out when the "Receive text Messages from other JTAlert users" is not selected, as indeed are all the options. I had assumed that that meant all the options were set to the state as if the box were unticked. I do not recall ever having to enable an item to un-grey out an option so I could change it. OTOH, my chemo may be pickling my brain.
--
73 de Guy G4DWV 4X1LT

Just a defect in the logic.

Simple fix, temporarily enable the "receipt" checkbox, uncheck the "restore" check box, uncheck the "receipt" checkbox.

de Laurie VK3AMA


locked JTAlert 2.16.16 is available #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.16 is now available @ https://hamapps.com/JTAlert/

Please review the release notes at the end of this message, in particular the wsjtx 2.3.0-rc2 requirements.

de Laurie VK3AMA

Release Notes.

2.16.16 (18-Nov-2020)

*****************************************************************************
  *** IMPORTANT: WSJT-X Multicast UDP Server setting requirement
  ***
  *** For WSJT-X 2.3.0-rc2 and future versions when using a multicast
  *** address for the UDP Server the "Outgoing Interfaces" selector needs
  *** to have the Loopback interface enabled.
*****************************************************************************

  *** Includes Callsign database file version 2020-11-18 (2020-Nov-18)

  New Features:

    - Decodes Window Online Indicators: Callsigns that are online for text message
       receipt will be shown with an underline, the same as the main JTAlert
       Callsigns display. A new online indicator, a filled circle, can be shown
       in the top-right corner of the Callsign display cell.

    - Text Messages: Can now be initiated via the Callsign right-click context menu
       of the Decodes Window.

  Changes:

    - Callsign QSL Indicators: Striped QSL indicators have been removed.
       Only flag style indicators are used. The position of the indicators is
       now fixed, Lotw in the top-left corner and Eqsl in the bottom-right corner
       of the Callsign display. This change is for both the main JTAlert window
       and the Decodes window.

    - WSJT-X Decode Highlighting: "73" or "RR73" decode highlighting no longer
       require the CQ Alert to be enabled. A dedicated setting is now available.
       See the "Applications -> WSJT-X / JTDX" section of the Settings window.
       Note: This and other color highlighting is not available for JTDX.

  Fixes:

    - Decodes Window: Showing 6 character grids instead of 4 characters for
       compound callsigns (typicaly seen for portable and special event calls)
       when a log entry for the callsign exists with a 6 character grid.

    - Grid Alert: If the Grid alert is enabled a 6 character grid would be
       alerted despite its 4 character grid being set as not needed after the
       Alert database rebuild was run.

    - Popup Notifications: Popups like "Logging Confirmation" and "Text Message
       Reciept" not displaying if the main JTAlert window was mimimized (hidden)
       at the time the popop was shown.

    - TX PWR: Value change not remembered when set to no value (empty string).


locked Re: LOTW data is often wrong

HamApps Support (VK3AMA)
 

On 19/11/2020 7:07 am, Torsten - DL9GTB wrote:
Stations with LOTW membership are often marked even though they are not registered with LOTW, or vice versa.

73 de Torsten - DL9GTB
Examples? Even just one Callsign is enough to start an investigation.

Claiming errors without providing any supporting evidence is worthless.

de Laurie VK3AMA


locked Re: LOTW data is often wrong

Dave AA6YQ
 

+ AA6YQ comments below

Stations with LOTW membership are often marked even though they are not registered with LOTW, or vice versa. I see this repeatedly and have been doing so for a long time. Now I noticed that in particular because I was running the grid tracker at the same time and can quickly recognize the different data. I will continue to observe this and note a few examples.

+ The ARRL provides an API that returns a list of LoTW users with "date of last upload" for each. Since it first became available, I've not seen an example nor received a report of it being inaccurate.

<https://lotw.arrl.org/lotw-help/developer-query-lotw-users/>

+ If you know of a callsign that erroneously appears (or doesn’t' appear) on this list, please send it my way, and I will engage with the appropriate ARRL personnel.

73,

Dave, AA6YQ

3241 - 3260 of 35447