Date   

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

Ed K0iL
 

Looked at File Insight; 

Startup Item = No  (cannot change this)

User Trusted was Don't Trust.  (I changed this to Trust Checked) 

Developers = Not Available (this may be a problem in trust since it is so brand new time wise) 

Few Users = Fewer than 100 users

73, de ed -K0iL


locked Re: Callsign window has some problems

Joe Subich, W4TV
 

Increase the *HEIGHT* of your callsigns display to display a
second row.

Notice in Screen 1, 3 and 4 there is a gray line at the *TOP*
of the callsigns display. In Screen 2 that line is at the
*BOTTOM* of the callsigns display.

That gray line separates the "calling me" section of the window
and the "alerts" section. You need at least two rows in the
callsigns window otherwise the "calling me" section will overlay
the "alerts" (general callsigns) area.

73,

... Joe, W4TV

On 2021-04-16 10:19 AM, WB5JJJ - George wrote:
Caught it happening.
Screen 1 is the calling me on top of 2 announced wanted prefix callsigns.
Screen 2 is after I clicked the "x" and it shows what was hidden.
Screen 3 same as 1 with different stations.
Screen 4 same as 2 with different stations.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Issues after moving to a new Win10 PC

Phil Cooper
 

Hi all,

 

I've just set up a new Win10 Pro 64bit PC in the shack, and I am having issues with WSJTx.

 

When I start WSJTx, I'm told there is an issue with rig control, and that I need to have HamLib installed.

Well, I have downloaded that, but it fails to install on Win10, so now I am stuck...

 

Any pointers to getting this all working please?

 

73 de Phil GU0SUP


locked Another Callsign Window Issue

Tom Job
 

Good morning, all...

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


locked Re: Callsign window has some problems

WB5JJJ - George
 

Caught it happening.  

Screen 1 is the calling me on top of 2 announced wanted prefix callsigns.
Screen 2 is after I clicked the "x" and it shows what was hidden.
Screen 3 same as 1 with different stations.
Screen 4 same as 2 with different stations.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: Callsign window has some problems

WB5JJJ - George
 

The 1,2,3 are positions from the left side of the Callsign Window.  

I sent you a support request so you will have my settings and such to check.  

--
73's
George - WB5JJJ
Hamshack Holine #4969


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

Ed K0iL
 

Laurie, 
I just checked and I did load the 32 bit because it's (x86) which is was my other ham apps are installed at.  

So why isn't the JTAlertV2.Manager Application running as installed?  Hmmm.

73, de ed -K0iL


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

Ed K0iL
 

Tnx Laurie for responding. 

JTAlertV2.Manager Application is installed in the pluginsX folder, but it is not running per Task Manager.  

The only JT app running is "Audio & Visual Alerts for WSJT-X. (32 bit) which is odd since I thought I selected 64 bit like I do for most other apps.  But maybe not.  

My Norton 360 did alert me asking if it was okay to install JT Alert and I gave it approval so that allowed the installation without problems.  

I'll try reinstalling it again, and this time select 32 bit if there's an option for that.  

Thanks,
73, de ed -K0iL


locked Re: JTAlert - 73 Badge

Michael Black
 

I'm using single click and it's working on 73 badged call slots.  Lots easier on the carpal tunnel to use single click.
Mike W9MDB

Inline image





On Friday, April 16, 2021, 07:41:48 AM CDT, Craig <nz4cwcraig@...> 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 option on this.  Thanks again.


locked Re: System Crash...

Gilles beaulieu
 

Thanks Mike once again...

Will do that..

Gilles VE3NPI

On 4/16/2021 8:40 AM, Michael Black via groups.io wrote:
Uninstall all your USB audio devices (click on View/Show hidden devices to see everything) and make sure to uninstall everything listed.

Microsoft messed with the USB stuff on a recent update.

Mike W9MDB




On Friday, April 16, 2021, 07:20:13 AM CDT, Gilles beaulieu <ve3npi@...> wrote:


Good morning Laurie

I've got 1 problem which for the life of me I can't figure out.

I've got a FTDX-1200, SCU-17, WJST-X and JTAlert, all are latest version
of software. On receive everything works as it should. On transmit, it
worked flawlessly for 1 day. After that 1 day of operation I shut down
the radio. The next day I turn on the radio and software and on receive
it's running ok but on transmit I get error message of audio problem and
rig control.

I checked and recheck all settings and nothing has change, so why is it
behaving like that?

Any help would be appreciated.

Gilles VE3NPI








--


Gilles - VE3NPI

Prescott-Russell Amateur Radio Club

www.prarc.ca




locked JTAlert - 73 Badge

Craig
 

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 option on this.  Thanks again.


locked Re: System Crash...

Michael Black
 

Uninstall all your USB audio devices (click on View/Show hidden devices to see everything) and make sure to uninstall everything listed.

Microsoft messed with the USB stuff on a recent update.

Mike W9MDB




On Friday, April 16, 2021, 07:20:13 AM CDT, Gilles beaulieu <ve3npi@...> wrote:


Good morning Laurie

I've got 1 problem which for the life of me I can't figure out.

I've got a FTDX-1200, SCU-17, WJST-X and JTAlert, all are latest version
of software. On receive everything works as it should. On transmit, it
worked flawlessly for 1 day. After that 1 day of operation I shut down
the radio. The next day I turn on the radio and software and on receive
it's running ok but on transmit I get error message of audio problem and
rig control.

I checked and recheck all settings and nothing has change, so why is it
behaving like that?

Any help would be appreciated.

Gilles VE3NPI









locked System Crash...

Gilles beaulieu
 

Good morning Laurie

I've got 1 problem which for the life of me I can't figure out.

I've got a FTDX-1200, SCU-17, WJST-X and JTAlert, all are latest version of software. On receive everything works as it should. On transmit, it worked flawlessly for 1 day. After that 1 day of operation I shut down the radio. The next day I turn on the radio and software and on receive it's running ok but on transmit I get error message of audio problem and rig control.

I checked and recheck all settings and nothing has change, so why is it behaving like that?

Any help would be appreciated.

Gilles VE3NPI


locked Re: .DotNet

 

Thanks for replying Laurie,
Was using the supplied URL on the website & whatever popped up with .dotnet checker. I happened to check back later on & the page seem to work must have been something going on with the Microsoft site itself. Because seems to be fine late last night & now this morning as I type this response.

73,
N3PKJ


locked Re: JTAlert 2.50.0 upgrade Callsign Window

OM Marlon, DW3CWM
 

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


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Friday, April 16, 2021 5:25:27 PM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] JTAlert 2.50.0 upgrade Callsign Window
 
On 16/04/2021 6:07 pm, OM Marlon via groups.io wrote:
I am running JtAlert 2.16.17 / Log4OM2 2.12.0.0 and JTDX 2.2.0 rc152 on a modest Win10Pro64 ver 20h2 machine  simultaneously with no problems. Upgraded to JTAlert 2.50.0 smoothly after installing runtime 5.0.5 64. It was a plain straight upgrade, no tinkering whatsoever.  Had to look for the callsign window after as the main windows was just a simple bar after upgrade.

I Liked the way the callsign windows works now, especially the callers option, that is a great pile up reminder. if only I can trigger TX  via single or double click of the caller callsign, That wouild have been a lazy operators pile up handler, hihi. For now It help me manage the short pile ups. Thanks Laurie. Is there a way to do this?

73 de Marlon DW3CWM

Good to hear all went smoothly.

If JTDX is not responding to a single-click or double-click in the Callsigns window, it is likely that the JTDX "Accept UDP Requests" is not enabled. There are two places in JTDX you need to visit in order to have it respond to Callsign click events from JTAlert.
  • JTDX Main window, "Misc -> Accept UDP Reply Messages" menu.
  • JTDX Settings window, "Accept UDP Requests" checkbox on the "Reporting" tab.
You may want to adjust what click type, single or double JTAlert will use. See the Callsigns window Options, click the gear icon
   

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 upgrade Callsign Window

HamApps Support (VK3AMA)
 

On 16/04/2021 6:07 pm, OM Marlon via groups.io wrote:
I am running JtAlert 2.16.17 / Log4OM2 2.12.0.0 and JTDX 2.2.0 rc152 on a modest Win10Pro64 ver 20h2 machine  simultaneously with no problems. Upgraded to JTAlert 2.50.0 smoothly after installing runtime 5.0.5 64. It was a plain straight upgrade, no tinkering whatsoever.  Had to look for the callsign window after as the main windows was just a simple bar after upgrade.

I Liked the way the callsign windows works now, especially the callers option, that is a great pile up reminder. if only I can trigger TX  via single or double click of the caller callsign, That wouild have been a lazy operators pile up handler, hihi. For now It help me manage the short pile ups. Thanks Laurie. Is there a way to do this?

73 de Marlon DW3CWM

Good to hear all went smoothly.

If JTDX is not responding to a single-click or double-click in the Callsigns window, it is likely that the JTDX "Accept UDP Requests" is not enabled. There are two places in JTDX you need to visit in order to have it respond to Callsign click events from JTAlert.
  • JTDX Main window, "Misc -> Accept UDP Reply Messages" menu.
  • JTDX Settings window, "Accept UDP Requests" checkbox on the "Reporting" tab.
You may want to adjust what click type, single or double JTAlert will use. See the Callsigns window Options, click the gear icon
   

de Laurie VK3AMA


locked JTAlert 2.50.0 upgrade Callsign Window

OM Marlon, DW3CWM
 

I am running JtAlert 2.16.17 / Log4OM2 2.12.0.0 and JTDX 2.2.0 rc152 on a modest Win10Pro64 ver 20h2 machine  simultaneously with no problems. Upgraded to JTAlert 2.50.0 smoothly after installing runtime 5.0.5 64. It was a plain straight upgrade, no tinkering whatsoever.  Had to look for the callsign window after as the main windows was just a simple bar after upgrade.

I Liked the way the callsign windows works now, especially the callers option, that is a great pile up reminder. if only I can trigger TX  via single or double click of the caller callsign, That wouild have been a lazy operators pile up handler, hihi. For now It help me manage the short pile ups. Thanks Laurie. Is there a way to do this?

73 de Marlon DW3CWM


locked Re: JTAlert 2.50.0 Upgrade help needed

HamApps Support (VK3AMA)
 

On 16/04/2021 6:13 am, N2TK, Tony via groups.io wrote:
I installed .Net, 64 bit. At the end of the installation, "download and install" am I supposed to do anything else in NET?
I have had no luck with "dotnet" at a command prompt. I get an alarm that "Windows cannot find dotnet".
Any ideas?
Tnx
N2TK, Tony. 

What version of Windows, 7, 8.1 or 10? Is it 64bit or 32bit?

There is nothing you need to do after installing the .NET 5 Desktop Runtime. You might try restarting your PC, but personally I have never needed after many installs and uninstalls of the runtime during my testing.

If the command "dotnet" in a command  prompt window is throwing a cannot find dotnet error, that suggests that it is not installed correctly. Check control panel to see if it is listed. Try running the .NET installer again.

If the runtime is installed correctly you should get similar results in response to a "dotnet" and "dotnet --info" command...
   

de Laurie VK3AMA


locked Re: Callsign window has some problems

HamApps Support (VK3AMA)
 

On 16/04/2021 11:58 am, WB5JJJ - George wrote:
I have a very strict selection process in JTAlert.  I only see stations that I've not worked before that are LoTW users.  This would include any other alerts as well.  So I don't see B4 and non-LoTW users as they are shown already in WSJTx Band Activity, so no need to duplicate.  So, I've been watching the Callsign window carefully and noticed the following.

If a station is calling me, I hear the "Calling You" announcement and I see them in position 1, 2 or 3 (whatever the number calling).  Then I hear "New Prefix" and it pops UNDER the 1st position on the left.  If I click on any "X" in the calling me boxes, they spread out and the new prefix is shown after the calling me callsigns.  This also happens with "Wanted DX".  

If the prefix or DXCC is in the first decode, it gets covered by any new "Calling You" alerts that arrive after.  

--
73's
George - WB5JJJ

Sorry, I am not following what you're describing. What is position 1, 2 or 3 referring to? Try posting some screen-captures of the relevant windows when the undersirable displays are present.

de Laurie VK3AMA


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

Laurie, VK3AMA
 



On 16/04/2021 12:27 pm, Ed K0iL wrote:
UDP Comm Failure error message states unable to communicate with WSJT-X process. Says see JT Alert Help for correct WSJT-X UDP Setup. That help page now recommends new UDP multicast addressing. So verified that. It still doesn't work.

I have all setting same as recommended on Troubleshooting help page for WSJT-X UDP Setup.  
Then JT Alert Help suggests using JTAlert's "Help->About", but doesn't work either.  Nothing on v2.50.0 works at all.  
 
Anyone else having this problem with JTAlert's new version 2.50.0?  

73, de ed -K0iL

All UDP comms, Sound output and opening of the new 2.50.0 windows, like the new Help->About window are controlled by the JTAlertV2.Manager.exe process located in the pluginsX sub-directory of your JTAlert installation directory. It sounds to me like that process is either not running or is being interfered with by your Protection software. Is the process running, check using taskmanager.

de Laurie VK3AMA

2881 - 2900 of 36991