Date   

locked Re: 2nd instance Callsign window not following JTAlert main window on minimize - Defect Confirmed.

HamApps Support (VK3AMA)
 

On 14/04/2021 5:45 am, Gary Yarbrough via groups.io wrote:
>From the settings window in the Callsign window I have ticked the box for the Callsign window to follow the JTAlert main window and it works on the 1st instance.  On the 2nd instance I also ticked the box  but the Callsign window does not minimize when I minimize the JTAlert main window. Anyone else having this issue ?

Gary / KE5TD

Gary,

Thanks for the report. I can confirm this is a defect.

I'll correct it for the next release.

de Laurie VK3AMA


locked Re: Ver 2.50.0 issues

HamApps Support (VK3AMA)
 

On 13/04/2021 9:59 pm, Bill Barrett wrote:
Hello Laurie-

Switched over to Multicast but no help. Notice the band and mode are still not found.
Any other suggestions?
Thanks;
Bill W2PKY

On Mon, Apr 12, 2021 at 10:54 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 13/04/2021 10:40 am, Bill Barrett wrote:

1.) Running 8 instances of WSJT-X and JTAlert. Receiving UDP Comm Failure on instance 8.
Each instance of WSJT-X has a unique UDP Port number.

2.) Instance #1 does not always display the Band and Mode.

3.) If all 8 instances of WSJT-X are up and starting JTAlert instances, JTAlert sometimes misses an instance of WSJT-X. Best to start one instance of WSJT-X along with JTAlert and go on until all 8 instances are up.

The new call window is very flexible.

Thanks;
Bill W2PKY

Bill,

I suggest you move over to using UDP multicast for the WSJT-X UDP Server settings. With multicast there is no need for unique ports, all instances can use the same port.

As for auto-starting WSJT-X, you could try adding in an additional delay for each startup entry. Alternatively, setup a batch file to start WSJT-X then JTAlert followed by a pause and repeat that for the additional instance pairs.

de Laurie VK3AMA




Likely its the port 2333 you're trying to use. That should not be a problem, but I have seen many users set to use 2333 and things stop working because they also have the WSJT-X secondary server enabled and it is set to 2333.
   

Make sure it is turned off. Also check that you don't have JTAlert set to rebroadcast UDP messages on the same port (under the "Applications -> WSJT-X /JTDX" section of the main JTAlert Settings window).

If you still have problems, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA



locked Re: the .NET 5 Desktop Runtime 64bit (x64)

Russ - KA1ERL
 

Running windows 10 64bit version.

Attached is the log generated by the error.

Thanks.

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Tuesday, April 13, 2021 19:59
To: Support@HamApps.groups.io
Subject: Re: [HamApps] the .NET 5 Desktop Runtime 64bit (x64)

 

On 14/04/2021 5:15 am, Russ - KA1ERL wrote:

When I try to install the above, I receive and error 0x80070570.
How do I fix this error.  I scanned my drive and no file errors.
Thank you


Please post an image of the error message.

Are you sure you're running a 64bit version of Windows?

What Windows version are running, Win7, 8.1 or 10?

de Laurie VK3AMA


locked Re: the .NET 5 Desktop Runtime 64bit (x64)

HamApps Support (VK3AMA)
 

On 14/04/2021 5:15 am, Russ - KA1ERL wrote:
When I try to install the above, I receive and error 0x80070570.
How do I fix this error.  I scanned my drive and no file errors.
Thank you

Please post an image of the error message.

Are you sure you're running a 64bit version of Windows?

What Windows version are running, Win7, 8.1 or 10?

de Laurie VK3AMA


locked Re: 2.50 Like It

HamApps Support (VK3AMA)
 

On 13/04/2021 2:38 pm, G. E. Janssens - K5WW wrote:
Many fantastic, and welcomed improvements and new features!

Including the very last one on the list, which has been a pain in my lower back for years. I know, minor gripe (which I never reported - mea culpa)

Erik - K5WW
What list are you referring too, and what is the last one on that list? I am curious.

de Laurie VK3AMA


locked Re: 2.50 Like It

HamApps Support (VK3AMA)
 

On 13/04/2021 1:43 pm, Jon KM8V wrote:
Personally, I'd love to ditch the "main" window for the callsigns window, if there was a way to get to the menu from there.

That's coming. Not immediately, the remaining components of the main JTAlert window, Logging fields, the Confirmed Bands/Mode display as well as some miscellaneous popups need to be migrated over to the new code base.

Eventually, there will be no main JTAlert window, just an icon in the Windows notification area or perhaps a small floating toolbar. I haven't decided yet, but I am leaning towards a small toolbar, or perhaps a choice between the two. I'm big on allowing user choice, hi.

de Laurie VK3AMA


locked Re: 2.50 Like It - NET 5 - QSLpath indicators

HamApps Support (VK3AMA)
 

On 14/04/2021 5:19 am, Willi Passmann wrote:
I can also confirm that the .NET 5 runtime and JTAlert 2.50 are running fine with my Win7 Prof. SP1, without paid updates.

I like the new version, for example the indication of the desired continent for directed calls is very informative, much better than the solution used in 2.16.
I wonder if the triangles for EQSL and LotW could also replaced by one letter (E / L) in the according corners in the entries of the callsign window? Then one would not have to remember which corner stands for which QSL route.

vy 73,
Willi, DJ6JZ

Willi,

Good news about Win7 SP1, I wonder how long that will last?

As for the QSL flag changes, I have some changes in mind for those. I'll run some tests and see how the Test Team feel.

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

HamApps Support (VK3AMA)
 

On 14/04/2021 6:51 am, David - AK2L wrote:
Note: I did try to have JTAlert send (UDP) the QSO to HRD, but HRD was not picking up the submode from a MFSK/FT4 QSO whereas it picked it up from WSJT-X just fine.

Likely you haven't set the "Log FT4 as ADIF 3.1.0 ..." setting under the Logging Options (you will need to scroll the window down to find the setting).



de Laurie VK3AMA


locked Re: Transmit frequency

HamApps Support (VK3AMA)
 

On 14/04/2021 6:19 am, Ernie Barnhart wrote:

Using JTAlert v2.50.0, with Callsigns Window set for single click using ctrl-click does not change transmit frequency to receive frequency as I thought previous versions did. Comment?

I do like the new version with separate windows, and all the flexibility!

73,
Ernie, N8DVE


JTAlert has no control over how or if WSJT-X changes frequency in response to the Callsign click in JTAlert. The WSJT-X interface doesn't support frequency changes in the message sent from JTAlert. It is likely a setting in WSJT-X, perhaps it is influenced by the "Hold  Tx Freq" checkbox.

de Laurie VK3AMA


locked Re: Version 2.50.0 request

HamApps Support (VK3AMA)
 

On 14/04/2021 9:20 am, John, DK9JC / AK9JC wrote:
On Tue, Apr 13, 2021 at 11:59 PM, John C wrote:
could it be made larger please, currently, it is quite hard to see.

I agree. Right now it seems, that you can zoom only everything together. BTW: I see you now -13 into Germany:

 


Have your tried adjust the Flag size? The online indicator is controlled by that selector.



Whatever position you have the indicator, top-left or top-right, it will only ever be that indicator in that position.

de Laurie VK3AMA



locked Re: A quick Question....

HamApps Support (VK3AMA)
 

On 14/04/2021 9:02 am, Tom Job wrote:

 

Just a quick one….in the callsign window, when I mouse over any call, I can see their eQSL and/or LoTW status.  The date in brackets for LoTW….is that date when they joined LoTW or when they last uploaded their log?  I’ve seen some going back to 2015!  I hope its join and not upload, good grief!

Cheers….Tom VE3II


The LoTW date shown is the last time they uploaded to LoTW.
Note: this date is correct at the last time the JTAlert Callsigns database was updated.

If you want to avoid these slow-qsl'ers, set the LoTW date  filter under the "Alerts -> LoTW / eQSL(AG) Flags" section of the OLD Settings window.

   

de Laurie VK3AMA



locked Re: Thank You!!

HamApps Support (VK3AMA)
 

On 14/04/2021 8:10 am, Charlie - K5EY wrote:
Thank you for making this awesome upgrade available to the ham community. JTAlert ver. 2.50.0 is truly amazing. No problems with installation or setup. Very intuitive and all the controls are right where one would expect them to be. All of the enhancements are super, but three stand out for me:
  1. Ability to zoom individual windows with a simple ctrl+mouse wheel.
  2. Badges and other information on the callsigns.
  3. Improved messaging.
Thanks again. The ham world is in your debt.
--
Charlie -- K5EY

#1 is my favorite feature.

de Laurie VK3AMA


locked Re: Version 2.50.0 request

HamApps Support (VK3AMA)
 

On 14/04/2021 8:03 am, John C wrote:

I am an idiot...  sorry,  I meant the Top Left Hand corner.. duhhhhhhh

John
Top-Right is also valid. The positioning of the online indicator is dependent on what position you have the new badges. It will always display on the opposite side to the badges.

As for the sizing, see this message... https://hamapps.groups.io/g/Support/message/34055 <https://hamapps.groups.io/g/Support/message/34055>

BTW, the indicator image is a star, not a dot.

de Laurie VK3AMA


locked Re: A quick Question....

Joe Subich, W4TV
 

On 2021-04-13 7:02 PM, Tom Job wrote:
The date in brackets for LoTW..is that date when they joined LoTW or
when they last uploaded their log?
Last upload date.

73,

... Joe, W4TV


On 2021-04-13 7:02 PM, Tom Job wrote:
Hi Laurie.
Again, a solid program for me cuz I know how to read J
Just a quick one..in the callsign window, when I mouse over any call, I can
see their eQSL and/or LoTW status. The date in brackets for LoTW..is that
date when they joined LoTW or when they last uploaded their log? I've seen
some going back to 2015! I hope its join and not upload, good grief!
Thanks and I'll leave you alone for more important, already documented
questions.
Cheers..Tom VE3II


locked Re: Version 2.50.0 request

John, DK9JC / AK9JC
 

On Tue, Apr 13, 2021 at 11:59 PM, John C wrote:
could it be made larger please, currently, it is quite hard to see.

I agree. Right now it seems, that you can zoom only everything together. BTW: I see you now -13 into Germany:

 


locked Re: A quick Question....

Tom Job
 

Excellent, John.  Thanks for that.  I searched the Help file but didn’t find that. 

 

73, Tom

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of John, DK9JC / AK9JC
Sent: April 13, 2021 19:12
To: Support@HamApps.groups.io
Subject: Re: [HamApps] A quick Question....

 

On Wed, Apr 14, 2021 at 01:02 AM, Tom Job wrote:

cuz I know how to read

sure?

The date in brackets for LoTW….is that date when they joined LoTW or when they last uploaded their log?

Just look in JTAlert under Help --> Open Help File:

Where does the LoTW and eQSL data come from?

 

LoTW data, Callsign plus last upload date, comes from an official list provided by the ARRL.     eQSL data, AG Callsigns only, comes from an official list provided by eQSL.

I’ve seen some going back to 2015!  I hope its join and not upload, good grief!

You can always login on LOTW and go to "Find call" in the top menu. Then you see the last log upload.
https://lotw.arrl.org/lotwuser/act?awg_id=&ac_acct=

 




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: A quick Question....

John, DK9JC / AK9JC
 

On Wed, Apr 14, 2021 at 01:02 AM, Tom Job wrote:
cuz I know how to read
sure?

The date in brackets for LoTW….is that date when they joined LoTW or when they last uploaded their log?

Just look in JTAlert under Help --> Open Help File:

Where does the LoTW and eQSL data come from?

 
LoTW data, Callsign plus last upload date, comes from an official list provided by the ARRL.     eQSL data, AG Callsigns only, comes from an official list provided by eQSL.

I’ve seen some going back to 2015!  I hope its join and not upload, good grief!

You can always login on LOTW and go to "Find call" in the top menu. Then you see the last log upload.
https://lotw.arrl.org/lotwuser/act?awg_id=&ac_acct=

 


locked A quick Question....

Tom Job
 

Hi Laurie…

 

Again, a solid program for me cuz I know how to read J 

 

Just a quick one….in the callsign window, when I mouse over any call, I can see their eQSL and/or LoTW status.  The date in brackets for LoTW….is that date when they joined LoTW or when they last uploaded their log?  I’ve seen some going back to 2015!  I hope its join and not upload, good grief!

 

Thanks and I’ll leave you alone for more important, already documented questions.

 

Cheers….Tom VE3II

 




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: JTAlert 2.50.0 Upgrade help needed

Bill Rogers
 

Thanks for the reply! JTAlert is fantastic operationally. 

I did successfully downgrade to 2.16.17



On Apr 13, 2021, at 2:36 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 14/04/2021 1:10 am, Bill Rogers wrote:
I upgraded JTAlert to 2.50.0 from 2.16.10 (I think) for use with WSJT-X.  After the install the Callsign Window and others like "About" don't come up when selected. I am also getting an Unable to communicate with the WSJT-X process: UDP Port 2237 IP Address 127.0.0.1. 

I did not modify my setup after the installation and it appears WSJT-X is still set up to use port 2237.

Is there a remedy or something to try?

Is there a way to go back to the older version safely?

Thanks,
Bill K2TER

All those symptoms indicate that the JTAlertV2.Manager.exe process is not running.

That process requires the .NET 5 Desktop Runtime to be installed. Make sure it is installed and of the correct architecture  (32bit or 64bit), The Runtime needs to match your Windows architecture.

If your running Windows 64bit install the X64 runtime, if 32bit install the X86 runtime.

de Laurie VK3AMA


locked Thank You!!

Charlie - K5EY
 

Thank you for making this awesome upgrade available to the ham community. JTAlert ver. 2.50.0 is truly amazing. No problems with installation or setup. Very intuitive and all the controls are right where one would expect them to be. All of the enhancements are super, but three stand out for me:
  1. Ability to zoom individual windows with a simple ctrl+mouse wheel.
  2. Badges and other information on the callsigns.
  3. Improved messaging.
Thanks again. The ham world is in your debt.
--
Charlie -- K5EY

3421 - 3440 of 37288