Date   

locked Re: Strange UI phenomenon

HamApps Support (VK3AMA)
 

On 22/10/2020 7:31 pm, Björn SM7IUN wrote:
From time to time I find the "Help" menu replaced by the name of a newly connected audio device.

Is this intentional? I assume not.

Also, JTAlert seems to suffer from the inability to handle UTF-8 in device names of which some are 
created by default in non-English Windows. The different effects of this have been reported previously.

Björn SM7IUN

image.png


No it is not intentional.
It is due to a code defect in the creation of additional sound device selection menus when a new audio device is detected. When this occurs, your only recourse is to restart JTAlert.

What is this "inability to handle UTF-8 in device names" problem? What is not working?

de Laurie VK3AMA


locked Re: Question

HamApps Support (VK3AMA)
 

On 23/10/2020 8:09 am, Neil wrote:
I have asked this before and apologize for asking again but I lost the reply, sorry about that.
In JT alert on 12m (it seems band specific) the alert box has a yellow background that carries over to WSJT-X spots. How do I remove the yellow from JT Alert. I know it is likely a filter but where to find it and turn it off??
Thanks
Neil   N4FN

If you're getting Callsign coloring it is because the Alert that corresponds to that color was triggered. You cannot remove specific colors except by disabling the associated Alert on the Band in question.

If you are still using the default colors, a yellow background indicates either a Dxcc or US State Alert, the text color identifies which (red = dxcc, black= state). You can see your current Alert color settings quickly via the "Alert Types Summary Window"
   

JTAlert is alerting you to something that is needed on 12m per your current requirements. If you don't want to see those alerts on 12m, turn off the 12m band for the Alert or adjust its Band Tracking to "Amy Band" and hopefully the reason for the Alert (say dxcc or State) has already been confirmed on another Band.

de Laurie VK3AMA


locked Question

Neil <n4fn.neil@...>
 

I have asked this before and apologize for asking again but I lost the reply, sorry about that.
In JT alert on 12m (it seems band specific) the alert box has a yellow background that carries over to WSJT-X spots. How do I remove the yellow from JT Alert. I know it is likely a filter but where to find it and turn it off??
Thanks
Neil   N4FN


locked Re: JTAlert Decodes Window

 

Thanks Laurie. I didn't, but I do now! Hi. Works fine. Just getting set up on a new computer and to much to remember at 80 yrs old. Hi

John   NA6Y


locked Re: #FT8/JTAlert

HamApps Support (VK3AMA)
 

On 23/10/2020 6:42 am, Wes Elton wrote:
Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.


de Laurie VK3AMA


locked Re: #FT8/JTAlert

Jim N6VH
 

On 10/22/2020 12:42 PM, Wes Elton wrote:
Hi All,
Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.
Wes,

Go to Settings/Window. Click Show db (DXCC Name)

73,

Jim N6VH


locked #FT8/JTAlert

Wes Elton
 

Hi All,
Can someone please advise where I can find the settings info that will enable received signal strength to appear beneath calls in the callsign display lines.
I've searched the help files but see anything relevant.

Cheers,

Wes.
GW3RIH.


locked Re: JTAlert Decodes Window

HamApps Support (VK3AMA)
 

On 23/10/2020 3:00 am, John wrote:
Win 10. FT4. When I use to double click on a call in the Decodes (2.16.14) window it would come up in the WSJT-x window and be sent.
I no longer can do that. The only way I can double click a call and have it come up in the xmitt window is when it shows in the WSJY-x  Band Activity window .
The same is true for the JTAlert window. I see a lot of calls but can not do anything about them until they pop-up in the Band Activity window. Any suggestions???

John   NA6Y

What version of WSJT-X?

Does the same non-response occur for FT8 decodes?

Do you have the "Accept UDP requests" setting enabled in WSJT-X?
   

BTW, there is no need for a double-click, just a single-click is needed.

de Laurie VK3AMA






locked Re: Audible Alerts

HamApps Support (VK3AMA)
 

On 23/10/2020 1:06 am, Norm Fasoletos wrote:
I am having a problem with an audible alert for my call sign. When I receive a call from another station, no alert. I have my call sign alert on, did a test from the software and it works, however, when another station calls me, I get so sound alert. My other alerts for new states, new grids, etc work just fine.

Your help is appreciated ...

73

Norm - K7NWF 

If JTAlert is showing the "Own Call" alert coloring but not producing the audio alert than likely you don't have the sound file set for the Alert. If the coloring is also not working than you likely don't have a Callsign set or an incorrect Callsign set for the Alert. See the Settings window, "Alerts -> Own Call" section.

de Laurie VK3AMA


locked Re: Audible Alerts

Jim N6VH
 

On 10/22/2020 7:06 AM, Norm Fasoletos wrote:
I am having a problem with an audible alert for my call sign. When I receive a call from another station, no alert. I have my call sign alert on, did a test from the software and it works, however, when another station calls me, I get so sound alert. My other alerts for new states, new grids, etc work just fine.

Your help is appreciated ...

73

Norm - K7NWF
Norm,

When you did a test from the software, did you test in the "Settings/Own Call" window, or did you test from the "Sound On/Test Sound Output" on the main JTAlert window? Two possibilities I can think of :

1 - In Settings/Own Call you don't have a wave file selected, or you  have the volume slider under that selection too far to the left.

2 - You don't have "Enable Own Call Alert" checked.

If the other alerts are working, then this one should also.

73,

Jim N6VH


locked Re: Corrupt JTA cfg data after un/reinstall causing QRZ UL to be ignored.

HamApps Support (VK3AMA)
 

On 22/10/2020 2:34 pm, TomK wrote:

I am always hopeful for resolutions to erratic errors such as I outlined.

Alas, my brother’s JT setup is for logging to QRZ so it’s had to hold one’s breath 😊

Also, our prob is due to config corruption as our last uninstall/reinstall seemed to corroborate,

… it is less likely another GA release will fix it.

We’re leaning toward blowing it all away right down to the folder level.

That’s why I was asking if there were other folders than standard two (Exe + AppData) trees.

Thanks for you input.

TomK 73


What erratic errors? What exactly is not working correctly?

What is the problem with QRZ logging? "hold one's breath" tells me nothing! Are the log uploads failing or is there a problem with the uploaded data? Please be precise in your fault description.

If you suspect you have a corrupt JTAlert config file, that can be easily checked by making a simple setting change, restarting JTAlert and checking if that change was remembered.  See the Help File, "Troubleshooting -> Setting Changes Not Remembered" topic which describes this simple check and how to recover an old config file.

de Laurie VK3AMA




locked Audible Alerts

Norm Fasoletos <norm.k7nwf@...>
 

I am having a problem with an audible alert for my call sign. When I receive a call from another station, no alert. I have my call sign alert on, did a test from the software and it works, however, when another station calls me, I get so sound alert. My other alerts for new states, new grids, etc work just fine.

Your help is appreciated ...

73

Norm - K7NWF 


locked JTAlert Decodes Window

 

Win 10. FT4. When I use to double click on a call in the Decodes (2.16.14) window it would come up in the WSJT-x window and be sent.
I no longer can do that. The only way I can double click a call and have it come up in the xmitt window is when it shows in the WSJY-x  Band Activity window .
The same is true for the JTAlert window. I see a lot of calls but can not do anything about them until they pop-up in the Band Activity window. Any suggestions???

John   NA6Y


locked Minimize Text Message Window if 'Offline'

Mike Flowers
 

I enjoy having the Text Message window open when I select a new callsign, and often have a nice text chat after a QSO.   I wonder if the Text Message window could be minimized when the other op is 'Offline'?  Just a thought ... - 73 and good DX de Mike, K6MKF


locked Strange UI phenomenon

Björn SM7IUN
 

From time to time I find the "Help" menu replaced by the name of a newly connected audio device.

Is this intentional? I assume not.

Also, JTAlert seems to suffer from the inability to handle UTF-8 in device names of which some are 
created by default in non-English Windows. The different effects of this have been reported previously.

Björn SM7IUN

image.png



locked Re: Issue re corruption causing QRZ UL 2be ignored when enabled & key verified

Michael Black
 

There's no "wipe out some stuff".  It's all or nothing.

3 folders contain everything.  The normal EXE, the AppData folder, and \ProgramData\HamApps

Mike W9MDB




On Wednesday, October 21, 2020, 10:27:46 PM CDT, TomK <qso@...> wrote:


Thanks for your input, Mike, but that wasn’t the question.

Your suggestion wipes out all HamApps info.

I am familiar with the basic data tree.

I was asking 2 things re a method to clear JTA config data only since it appears there is
some sticky malformed config data that is kept across a full Windows de-install/re-install.
So I was asking

  1. Is there was an easy way to wipe out the config data for JTA (not everything).
  2. If not, how to clear all data for just JTA, not all HamApps data (like Call info & other HamApps stuff).
  3. If I do complete un-install (Windows & Folders) are there any folders OTHER than the basic 2 (EXE + DATA)

That’s the gist of it.

It’s looking like the answer is NO and I’ll have to wipe out EVERYTHING.

If so, that leaves Q3. Are there any other folders beside the standard basic EXE + DATA trees

 

Thanks

TomK 73

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via groups.io
Sent: Monday, October 19, 2020 8:45 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issue after band change

 

The folder to delete is

 

\Users\[username]\AppData\Local\HamApps

 

Mike W9MDB

 

 

 

 

On Monday, October 19, 2020, 07:41:16 AM CDT, TomK <qso@...> wrote:

 

 

On a 2nd note, Laurie, did you see my msg about a JTA error popup and also
not sending to QRZ even though it is enabled?
Had also asked how to reset JTA config or how to do a complete folder level
uninstall (what folders that is to delete)
If you get a chance, scan for my msg from 1-2 days ago. Has more detail.
Thanks for your time and great coding!
TomK 73


-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of
Laurie, VK3AMA
Sent: Sunday, October 18, 2020 5:23 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issue after band change



On 19/10/2020 8:05 am, TomK wrote:
> But waterfall below shows absolutely no signal.
Are you sure?
F/MM was decoded at 2389Hz, but your waterfall image is limited to 1500Hz.

de Laurie VK3AMA













locked Re: Corrupt JTA cfg data after un/reinstall causing QRZ UL to be ignored.

TomK
 

Thanks for your input Uwe.

I am always hopeful for resolutions to erratic errors such as I outlined.

Alas, my brother’s JT setup is for logging to QRZ so it’s had to hold one’s breath 😊

Also, our prob is due to config corruption as our last uninstall/reinstall seemed to corroborate,

… it is less likely another GA release will fix it.

We’re leaning toward blowing it all away right down to the folder level.

That’s why I was asking if there were other folders than standard two (Exe + AppData) trees.

Thanks for you input.

TomK 73

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Uwe, DG2YCB
Sent: Monday, October 19, 2020 9:02 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issue after band change

 

I am already in contact with Bill, G4WJS. I shared with him details about the issue on band change and how I fixed it.

@ TomK: I don't think the problem you mentioned is caused by the same inconsistencies in the code. However, as far as I can remember, some other inconsistencies have already been identified that should be addressed for the GA release. So let's see what gets fixed and what doesn't.

73 de Uwe, DG2YCB


locked Re: No Decodes - Packets Seen with Wireshark

Michael Black
 

127.0.0.1 -- same port

Mike W9MDB




On Wednesday, October 21, 2020, 06:20:53 PM CDT, Bob WB2NVR <wb2nvr@...> wrote:


Hi Mike - Noticed the same thing. When JTAlert stops responding, it doesn't see band changes.  It also doesn't send anything to DXKeeper when I click on a call in WSJT-X.

What is the address and port for Local Host?  I'll try that next.

I changed to Muilticast to try Grid Tracker, but I'm not using it. Local Host should be OK.

Thanks!

Bob  WB2NVR


locked Re: Issue re corruption causing QRZ UL 2be ignored when enabled & key verified

TomK
 

Thanks for your input, Mike, but that wasn’t the question.

Your suggestion wipes out all HamApps info.

I am familiar with the basic data tree.

I was asking 2 things re a method to clear JTA config data only since it appears there is
some sticky malformed config data that is kept across a full Windows de-install/re-install.
So I was asking

  1. Is there was an easy way to wipe out the config data for JTA (not everything).
  2. If not, how to clear all data for just JTA, not all HamApps data (like Call info & other HamApps stuff).
  3. If I do complete un-install (Windows & Folders) are there any folders OTHER than the basic 2 (EXE + DATA)

That’s the gist of it.

It’s looking like the answer is NO and I’ll have to wipe out EVERYTHING.

If so, that leaves Q3. Are there any other folders beside the standard basic EXE + DATA trees

 

Thanks

TomK 73

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via groups.io
Sent: Monday, October 19, 2020 8:45 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issue after band change

 

The folder to delete is

 

\Users\[username]\AppData\Local\HamApps

 

Mike W9MDB

 

 

 

 

On Monday, October 19, 2020, 07:41:16 AM CDT, TomK <qso@...> wrote:

 

 

On a 2nd note, Laurie, did you see my msg about a JTA error popup and also
not sending to QRZ even though it is enabled?
Had also asked how to reset JTA config or how to do a complete folder level
uninstall (what folders that is to delete)
If you get a chance, scan for my msg from 1-2 days ago. Has more detail.
Thanks for your time and great coding!
TomK 73


-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of
Laurie, VK3AMA
Sent: Sunday, October 18, 2020 5:23 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issue after band change



On 19/10/2020 8:05 am, TomK wrote:
> But waterfall below shows absolutely no signal.
Are you sure?
F/MM was decoded at 2389Hz, but your waterfall image is limited to 1500Hz.

de Laurie VK3AMA













locked Re: No Decodes - Packets Seen with Wireshark

Michael Black
 

No change in protection software.  Been using Defender and Malwarebytes forever.
Yes on the Windows restart.

Didn't try multicast until somebody else said they had a problem and I started having problems too.  Packets are being sent from WSJT-X but JTAlert isn't seeing them.

I sent you a debug last time it stopped.  Been running most of today on localhost without a problem.  Going to let it run overnight and I'll switch back to multicast tomorrow and see what happens.

Mike





On Wednesday, October 21, 2020, 07:52:11 PM CDT, Laurie, VK3AMA <hamapps.support@...> wrote:




On 22/10/2020 7:52 am, Michael Black via groups.io wrote:
> I don't either...pretty odd...as though JTALert stopped receiving
> multicast.
> I've switched back to localhost now and seems the problem has at least
> temporarily gone away.
>
> Mike

Something has clearly changed within the last couple of days. A Windows
update perhaps? Changed Protection software behavior perhaps?

Have you performed a Windows restart?

At this time, I am at a loss as to what may be the cause. The UDP
handling code in recent versions is unaltered, it hasn't changed in over
2 months. For problems to surface now suggests an external influence.

de Laurie VK3AMA






1081 - 1100 of 32884