Date   

locked Re: Second Instance of JTAlert

HamApps Support (VK3AMA)
 

On 27/03/2019 10:14 pm, Ed Wilson via Groups.Io wrote:

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC
Grey-out Settings menu on instance #2 is expected behaviour. See the Help File, "Multiple Instances" topic.

Setting the unique UDP ports in WSJT-X is all that needs to be done, JTAlert automates the rest, just start JTAlert the required number of times.

de Laurie VK3AMA


locked Re: Second Instance of JTAlert

Michael Black
 

Nope...no limit.  Recommend higher port numbers though since lower ones have well known services.

de Mike W9MDB




On Wednesday, March 27, 2019, 9:42:37 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Well, that is convenient! :)

Are there any limitations on the port number that you use other than it cannot be in conflict with one already in use?

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, March 27, 2019, 10:29:43 AM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


You don't set the UDP port in JTAlert -- it finds it automagically from the WSJT-X instance.

Mike




On Wednesday, March 27, 2019, 9:26:00 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Mike,

Thanks for the input...I assumed that was the case.

Since the second instance of JTDX (or WSJT-X) requires a different UDP port number, is it not possible for that instance to communicate with JTAlert (instance #2) via UDP?

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, March 27, 2019, 9:42:38 AM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


Settings are only available on the 1st instance.  If you need to make changes it applies to all.

de Mike W9MDB




On Wednesday, March 27, 2019, 6:14:17 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: Title Bar

William "Brad" Rich <wbradrich@...>
 

I did not understand the special charactors, -, F, #, 1.

Brad


locked Re: Second Instance of JTAlert

Ed Wilson
 

Well, that is convenient! :)

Are there any limitations on the port number that you use other than it cannot be in conflict with one already in use?

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, March 27, 2019, 10:29:43 AM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


You don't set the UDP port in JTAlert -- it finds it automagically from the WSJT-X instance.

Mike




On Wednesday, March 27, 2019, 9:26:00 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Mike,

Thanks for the input...I assumed that was the case.

Since the second instance of JTDX (or WSJT-X) requires a different UDP port number, is it not possible for that instance to communicate with JTAlert (instance #2) via UDP?

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, March 27, 2019, 9:42:38 AM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


Settings are only available on the 1st instance.  If you need to make changes it applies to all.

de Mike W9MDB




On Wednesday, March 27, 2019, 6:14:17 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: Second Instance of JTAlert

Michael Black
 

You don't set the UDP port in JTAlert -- it finds it automagically from the WSJT-X instance.

Mike




On Wednesday, March 27, 2019, 9:26:00 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Mike,

Thanks for the input...I assumed that was the case.

Since the second instance of JTDX (or WSJT-X) requires a different UDP port number, is it not possible for that instance to communicate with JTAlert (instance #2) via UDP?

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, March 27, 2019, 9:42:38 AM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


Settings are only available on the 1st instance.  If you need to make changes it applies to all.

de Mike W9MDB




On Wednesday, March 27, 2019, 6:14:17 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: Second Instance of JTAlert

Ed Wilson
 

Mike,

Thanks for the input...I assumed that was the case.

Since the second instance of JTDX (or WSJT-X) requires a different UDP port number, is it not possible for that instance to communicate with JTAlert (instance #2) via UDP?

Ed, K0KC

k0kc@...
http://k0kc.us/


On Wednesday, March 27, 2019, 9:42:38 AM EDT, Michael Black via Groups.Io <mdblack98@...> wrote:


Settings are only available on the 1st instance.  If you need to make changes it applies to all.

de Mike W9MDB




On Wednesday, March 27, 2019, 6:14:17 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: Second Instance of JTAlert

 

Personally I don’t like the new one. The outline is not dark anymore and the window is hard to see. Also the – and X at the top right don’t work anymore.

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via Groups.Io
Sent: Wednesday, March 27, 2019 9:42 AM
To: Hamapps Groups Support <support@hamapps.groups.io>
Subject: Re: [HamApps] Second Instance of JTAlert

 

Settings are only available on the 1st instance.  If you need to make changes it applies to all.

 

de Mike W9MDB

 

 

 

 

On Wednesday, March 27, 2019, 6:14:17 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:

 

 

Laurie,

 

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

 

I bet that I am just missing something obvious here.

 

Thanks,

 


locked Re: Title Bar

Neil <n4fn.neil@...>
 

Well...I followed Michael's suggestion, but I can not check off the box . In fact I was unable to make any changes??
Neil   N4FN


locked Re: Second Instance of JTAlert

Michael Black
 

Settings are only available on the 1st instance.  If you need to make changes it applies to all.

de Mike W9MDB




On Wednesday, March 27, 2019, 6:14:17 AM CDT, Ed Wilson via Groups.Io <ed.wilson@...> wrote:


Laurie,

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: Title Bar

Neil Foster
 

Thanks Mike
Neil   N4FN


locked Second Instance of JTAlert

Ed Wilson
 

Laurie,

I have been using JTAlert for many years, but never have had the need to launch multiple instances until today. I am using two instances of JTDX and have changed the default UDP port number from 2237 in the first instance of JTDX to 2238 in the second instance of JTDX. The first instance of JTAlert shows #1 and the second instance of JTAlert shows #2 but the settings are greyed-out in the second instance. Is there a way to allow the first instance of JTDX to communicate with the first instance of JTAlert and the second instance of JTDX to communicate with the second instance of JTAlert? The two instances of JTDX have different rig names and in fact communicate with different rigs.

I bet that I am just missing something obvious here.

Thanks,

Ed, K0KC

k0kc@...
http://k0kc.us/


locked Re: Need Help with New DT Display Feature in 2.13.3

HamApps Support (VK3AMA)
 

On 27/03/2019 7:45 pm, fkemmerer@... wrote:
I've downloaded and installed V2.13.2 of JTAlert and I'd like to take advantage of the DT summary display feature. I am using JTDX and DXLab (both latest versions) with JTAltert but I don't seem to be getting the DT display. I'm not exactly sure where it would be displayed or if I need to set an option or change configuration to get this going. Can someone please help me to sort this out?

Thank you,
--
Fred, AB1OC

Did you read the release notes and view the help file as instructed?
The Help file has images showing where the DT is displayed.

From the Release Notes...
    - Decodes History now displays in the status bar (to the right of the clock)
       a median calculation of decode DT values. Initially no display until
       sufficient samples (25) are collected. If the median DT exceeds +-2 it is
       colored red, while DTs between +-1 and +-2 are colored yellow. A tooltip
       provides information about the sample count and time period. See the
       "Introduction" topic of the Decodes History Help.

The DT is available in the Status bar of the Decodes History.

de Laurie VK3AMA


locked Need Help with New DT Display Feature in 2.13.3

Fred Kemmerer
 

I've downloaded and installed V2.13.2 of JTAlert and I'd like to take advantage of the DT summary display feature. I am using JTDX and DXLab (both latest versions) with JTAltert but I don't seem to be getting the DT display. I'm not exactly sure where it would be displayed or if I need to set an option or change configuration to get this going. Can someone please help me to sort this out?

Thank you,
--
Fred, AB1OC

https://stationproject.blog
https://www.n1fd.org


locked Re: Error on Installing 2.13.2

Jim Cary
 

Thanks.  That did the trick.

73

jim


locked Re: Error on Installing 2.13.2

Brian (N2MLP)
 

Installed and running 100%

 

========================

         de N2MLP Brian

       Monroe County PA

 

 

========================

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Tuesday, March 26, 2019 11:23 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Error on Installing 2.13.2

 

That means something is still running.

 

Simply reboot and install before running anything.

 

de Mike W9MDB

 

 

 

 

On Tuesday, March 26, 2019, 10:19:23 AM CDT, Jim Cary <JimLCary@...> wrote:

 

 

I get the attached error message when trying to install 2.13.2.  I have tried several times, with the same result.  Running Windows 10

Jim
ZF2LC


locked Re: Error on Installing 2.13.2

Michael Black
 

That means something is still running.

Simply reboot and install before running anything.

de Mike W9MDB




On Tuesday, March 26, 2019, 10:19:23 AM CDT, Jim Cary <JimLCary@...> wrote:


I get the attached error message when trying to install 2.13.2.  I have tried several times, with the same result.  Running Windows 10

Jim
ZF2LC


locked Re: Title Bar

Michael Black
 

View/Show Log Fields

de Mike W9MDB




On Tuesday, March 26, 2019, 10:15:04 AM CDT, Neil <n4fn.neil@...> wrote:


Lawrie,
I only see the top half of the title bar. How does one display the section showing the F6 call and the other info on the bottom half?
Many thanks
Neil   N4FN


locked Error on Installing 2.13.2

Jim Cary
 

I get the attached error message when trying to install 2.13.2.  I have tried several times, with the same result.  Running Windows 10

Jim
ZF2LC


locked Re: Title Bar

Neil <n4fn.neil@...>
 

Lawrie,
I only see the top half of the title bar. How does one display the section showing the F6 call and the other info on the bottom half?
Many thanks
Neil   N4FN


locked New JTAlert 2.13.2 available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.13.2 is now available @ https://HamApps.com

The Release Notes...
  New Features:
    - Decodes History now displays in the status bar (to the right of the clock)
       a median calculation of decode DT values. Initially no display until
       sufficient samples (25) are collected. If the median DT exceeds +-2 it is
       colored red, while DTs bewteen +-1 and +-2 are colored yellow. A tooltip
       provides information about the sample count and time period. See the
       "Introduction" topic of the Decodes History Help.

  Changes:
    - Macedonia renamed to North Macedonia. This doesn't require any changes by
       the user as the logged DXCC number is unchanged and DXCC alerting is
       based on the DXCC number, not the Country name.

  Fixes:
    - Decodes History displaying DT values incorrectly for Windows users
       with a language that uses a period "." as a number group separator.
       eg "1.0" became "10", "1.6" became "16, "0.1" became "1", etc.
    - Scan Log failing to update Wanted lists for some Log entries.
       This affected a very small number of QSO records, those with
       State/Province data that contained a single quote.
    - Some Callsigns with two slashed suffixes not decoding due to failed
       callsign validation. eg AA1AA/2/P


de Laurie VK3AMA

13621 - 13640 of 37288