Date   

locked Re: JTAlert Win10 Not Responding or Slow?

Charles Jessee
 
Edited

After all current updates are installed and rebooting my desktop:

Win10 Pro
Processor:  AMD FX-8150 8-Core 3.60 GHz
Installed RAM:  32 GB

Resource Monitor reports:
After reboot:  CPU Usage bounces 3-5% with max at 12%; 15% Used Physical Memory
With WSJT-X, JTAlert, HRD Logbook running CPU spikes up to 30% briefly when WSJT-X decodes

The countdown still runs very slow.
Might there be some clash between settings somewhere?

I'll add that I tried a QSO with HRD Logbook closed and still saw JTAlert lags and Not Responding. Upping priority of JTAlerts to High or Real-Time doesn't seem to help.

Bret/N4SRN


locked N3FJP

Don Farrar
 

Some time ago there were instructions on getting JTAlert-X to work with other N3FJP logging programs besides ACL
I cant seem to find them at this time.
Could any one fill me in?

Thanks,

73,

Don, VA3ZV


locked R: [HamApps] No longer logging automatically to DXKeeper

Carlo - IK2RPE
 

Laurie,

 

Many thanks.

I realized that I missed a couple of settings in WSJT-X (lost in the v. 2.0 vs. the previous one) i.e. set “reporting/Log automatically” and everything is now as I used with my great joy.

 

Best regards

 

 

Carlo  IK2RPE

 

 

 

Da: Support@HamApps.groups.io <Support@HamApps.groups.io> Per conto di HamApps Support (VK3AMA)
Inviato: venerdì 18 gennaio 2019 19:41
A: Support@HamApps.groups.io
Oggetto: Re: [HamApps] No longer logging automatically to DXKeeper

 

On 19/01/2019 5:30 am, Carlo - IK2RPE wrote:

I'm no longer logging automatically to DXKeeper, anymore, as I used to be .

 

I understood (from a past message of yours) that:

 

“Once DXKeeper logging is enabled in JTAlert, "DXK" will be displayed in the titlebar. If so, then automatic logging will occur, there is nothing else to set”

 

DXK  **IS** in my titlebar  

 Did I miss something else?

 

Thanks in advance

 

 

 

Carlo  IK2RPE

Carlo,

If you have "DXK" showing in the titlebar, than all is set correctly.
The only thing left to do is actually log a QSO in WSJT-X.

de Laurie VK3AMA


Mail priva di virus. www.avg.com


locked Re: Call sign display size

borant@...
 

I meant if you can consider enhancement in future versions. Filter does not work as is today, today I've seen whole Japan gang raping Panama station, 30-35 calls in pileup. There is no way to filter it.
73,
Boris KJ7G


locked Re: JTAlert Request

g4wjs
 

On 18/01/2019 22:19, HamApps Support (VK3AMA) wrote:
On 19/01/2019 8:50 am, g4wjs wrote:
Hi Mike,

that's not quite the full story. Any application can send UDP datagrams to a multicast group address, no special coding is needed. The server end(s) is where the multicast group has to be joined and that does require extra coding over a basic unicast UDP server. It is not a language limitation although the support libraries for a language may not include joining multicast groups out of the box, but writing the required code is quite feasible if the underlying system network supports it (Windows does).

73
Bill
G4WJS.
Bill,

What is the Multi-cast group address used by WSJT-X. I expect it is somewhere within the standard 224.0.0.0 through 239.255.255.255 range.

de Laurie VK3AMA

Hi Laurie,

it is whatever is set in the configuration, it would replace the unicast local loopback address (127.0.0.1) most are using currently. There isn't really a sensible default although a scoped site-local IPv4 group address like 239.255.0.0 is my usual choice for testing (I also use ff15:: when testing IPv6). As far as WSJT-X is concerned it just sends UDP datagrams to a port at an address. It doesn't care, nor does it need to, whether that is a unicast or multicast address.

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: JTAlert Request

HamApps Support (VK3AMA)
 

On 19/01/2019 8:50 am, g4wjs wrote:
Hi Mike,

that's not quite the full story. Any application can send UDP datagrams to a multicast group address, no special coding is needed. The server end(s) is where the multicast group has to be joined and that does require extra coding over a basic unicast UDP server. It is not a language limitation although the support libraries for a language may not include joining multicast groups out of the box, but writing the required code is quite feasible if the underlying system network supports it (Windows does).

73
Bill
G4WJS.
Bill,

What is the Multi-cast group address used by WSJT-X. I expect it is somewhere within the standard 224.0.0.0 through 239.255.255.255 range.

de Laurie VK3AMA


locked Re: Worked B-4 status

HamApps Support (VK3AMA)
 

On 19/01/2019 8:17 am, Rick wrote:

Is there some documentation on JTAlert? I read the description of Worked B-4 in the JTAlert options, and if that is true, I might have a in house problem because I have not seen anything other than signal reports. I even changed my date to 2018 on the “ignore before” date and still nothing on stations that I KNOW I have worked. Probably just a tic somewhere but I don’t know where!!!!

 

Rick, W5FKW

B4 checks are done against the logger you have set within JTAlert. If JTAlert is not showing B4's then likely you have JTAlert pointing at the wrong log file. Depending on the Logger, JTAlert will automatically determine the log file location, but other Loggers require that you set the path to the log file.

What Logger do you have set in JTAlert

de Laurie VK3AMA


locked Re: Call sign display size

HamApps Support (VK3AMA)
 

On 19/01/2019 9:02 am, borant@... wrote:
Is it possible to make display configurable bigger than 4x9?
The current 4x9 is frequently overloaded
OM,

4x9 is the limit.
I suggest you apply some filtering to remove unwanted Callsigns, say filter out B4's. See the Alerts -> Filters menu.

de Laurie VK3AMA



locked Call sign display size

borant@...
 

Is it possible to make display configurable bigger than 4x9?
The current 4x9 is frequently overloaded


locked Re: JTAlert Request

g4wjs
 

On 18/01/2019 21:17, Michael Black via Groups.Io wrote:
WSJT-X can do multicast....JTAlert cannot
Hi Mike,

that's not quite the full story. Any application can send UDP datagrams to a multicast group address, no special coding is needed. The server end(s) is where the multicast group has to be joined and that does require extra coding over a basic unicast UDP server. It is not a language limitation although the support libraries for a language may not include joining multicast groups out of the box, but writing the required code is quite feasible if the underlying system network supports it (Windows does).

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Worked B-4 does not show in rx window#Important

Rick Wines
 


I am not showing the B-4 tag next to a station in the Band Activity window that I know I have worked, even changing the date in the "ignore" option. 

Rick Wines, W5FKW


locked Worked B-4 status

Rick Wines
 

Is there some documentation on JTAlert? I read the description of Worked B-4 in the JTAlert options, and if that is true, I might have a in house problem because I have not seen anything other than signal reports. I even changed my date to 2018 on the “ignore before” date and still nothing on stations that I KNOW I have worked. Probably just a tic somewhere but I don’t know where!!!!

 

Rick, W5FKW

Round Rock, TX

 

Sent from Mail for Windows 10

 


locked Re: JTAlert Request

Michael Black
 

WSJT-X can do multicast....JTAlert cannot (limit of the language) but rebroadcast is already in JTAlert.


Under Applications/WSJT-X

Inline image

de Mike W9MDB







On Friday, January 18, 2019, 12:17:49 PM CST, markholbrook <markholbrook@...> wrote:


Hello all,

I am in the process of writing a unique logging program for Flex Radio users.   One of the many requests I've had it to integrate with WSJT-X and automate logging.

I am finding that when JTAlert is run and working with WSJT-X that the UDP broadcast sent by WSJT-X on port 2237 is swallowed.  I don't think this is a fault of JTAlert but I believe the broadcast is not multicast so the first subscriber tends to get all of the data.

I would like to request that a rebroadcast feature be added to JTAlert on a different port.  So when JTAlert receives the data from WSJT-X it then rebroadcasts the exact same data on the rebroadcast port.   I think this rebroadcast option should be off by default but allowed to be enabled in the settings dialog of JTAlert.

That would allow a program such as the one I am writing to also receive the full data broadcast from WSJT-X.   I have requested that Joe Taylor change to a multicast but I have not received any response.

The vast majority of my users love the features of JTAlert and do not want to lose them.  So their ideal setup would be WSJT-X, JTAlert and my logging program all working together.

When my program is a little further along I will try to work with JTAlert to have it added as one of the log program options.

Thanks for the consideration!  Please feel free to email me if you have any questions.

--
  Mark R. Holbrook
  markholbrook@...



locked Re: No longer logging automatically to DXKeeper

HamApps Support (VK3AMA)
 

On 19/01/2019 5:30 am, Carlo - IK2RPE wrote:

I'm no longer logging automatically to DXKeeper, anymore, as I used to be .

 

I understood (from a past message of yours) that:

 

“Once DXKeeper logging is enabled in JTAlert, "DXK" will be displayed in the titlebar. If so, then automatic logging will occur, there is nothing else to set”

 

DXK  **IS** in my titlebar  

 Did I miss something else?

 

Thanks in advance

 

 

 

Carlo  IK2RPE

Carlo,

If you have "DXK" showing in the titlebar, than all is set correctly.
The only thing left to do is actually log a QSO in WSJT-X.

de Laurie VK3AMA


locked No longer logging automatically to DXKeeper

Carlo - IK2RPE
 

Hi Laurie,

 

I'm no longer logging automatically to DXKeeper, anymore, as I used to be .

 

I understood (from a past message of yours) that:

 

“Once DXKeeper logging is enabled in JTAlert, "DXK" will be displayed in the titlebar. If so, then automatic logging will occur, there is nothing else to set”

 

DXK  **IS** in my titlebar  

 Did I miss something else?

 

Thanks in advance

 

 

 

Carlo  IK2RPE


locked Re: JTAlert Request

HamApps Support (VK3AMA)
 

On 19/01/2019 3:29 am, markholbrook wrote:
Hello all,

I am in the process of writing a unique logging program for Flex Radio users.   One of the many requests I've had it to integrate with WSJT-X and automate logging.

I am finding that when JTAlert is run and working with WSJT-X that the UDP broadcast sent by WSJT-X on port 2237 is swallowed.  I don't think this is a fault of JTAlert but I believe the broadcast is not multicast so the first subscriber tends to get all of the data.

I would like to request that a rebroadcast feature be added to JTAlert on a different port.  So when JTAlert receives the data from WSJT-X it then rebroadcasts the exact same data on the rebroadcast port.   I think this rebroadcast option should be off by default but allowed to be enabled in the settings dialog of JTAlert.

That would allow a program such as the one I am writing to also receive the full data broadcast from WSJT-X.   I have requested that Joe Taylor change to a multicast but I have not received any response.

The vast majority of my users love the features of JTAlert and do not want to lose them.  So their ideal setup would be WSJT-X, JTAlert and my logging program all working together.

When my program is a little further along I will try to work with JTAlert to have it added as one of the log program options.

Thanks for the consideration!  Please feel free to email me if you have any questions.

--
  Mark R. Holbrook
Mark,

A UDP rebroadcast is already available.
See the Settings, Applications -> WSJT-X section.

   

de Laurie VK3AMA


locked JTAlert Request

markholbrook
 

Hello all,

I am in the process of writing a unique logging program for Flex Radio users.   One of the many requests I've had it to integrate with WSJT-X and automate logging.

I am finding that when JTAlert is run and working with WSJT-X that the UDP broadcast sent by WSJT-X on port 2237 is swallowed.  I don't think this is a fault of JTAlert but I believe the broadcast is not multicast so the first subscriber tends to get all of the data.

I would like to request that a rebroadcast feature be added to JTAlert on a different port.  So when JTAlert receives the data from WSJT-X it then rebroadcasts the exact same data on the rebroadcast port.   I think this rebroadcast option should be off by default but allowed to be enabled in the settings dialog of JTAlert.

That would allow a program such as the one I am writing to also receive the full data broadcast from WSJT-X.   I have requested that Joe Taylor change to a multicast but I have not received any response.

The vast majority of my users love the features of JTAlert and do not want to lose them.  So their ideal setup would be WSJT-X, JTAlert and my logging program all working together.

When my program is a little further along I will try to work with JTAlert to have it added as one of the log program options.

Thanks for the consideration!  Please feel free to email me if you have any questions.

--
  Mark R. Holbrook
  markholbrook@...



locked Re: JTAlert 2.12.10 not responding

 

Laurie,

Apparently I outwaited whatever gremlin was at work.  JTAlert is now up and running.  Thanks.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Dan Malcolm
Sent: Friday, January 18, 2019 6:57 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

Tried waiting longer Laurie.  The this popped up:

 

Looking at the WSJT-X Setting -> Reporting page shows the correct UPD ip address (127.0.0.1) and UDP Port (2237).  The check boxes adjacent to those settings are all checked.  I’m going to continue to let it set, but it has been running about 10 minutes at this point.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, January 18, 2019 12:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

On 18/01/2019 4:36 pm, Dan Malcolm wrote:

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

__________

Dan – K4SHQ

Dan,

When this occurs, ignore it and wait a couple of minutes. Does JTAlert eventually startup?

de Laurie VK3AMA


--
Dan - K4SHQ


--
Dan - K4SHQ


locked Re: Spots from Jtalert to spotcollector

Ron W3RJW
 

On Wed, Jan 16, 2019 at 08:05 PM, HamApps Support (VK3AMA) wrote:
Auto posting every received decode to the DX Cluster is a very bad idea. I can not envisage a use-case where this would be desirable and accepted by the wider DX Community. What would be the reason for posting thousands of decodes to the DX Cluster? There are already far too many people posting their TU's for each FT8 QSO. The DX Cluster is not some sort of on-line log for posting each QSO (ego spots I call them), nor is it suitable for posting thousands of SWL spots (PSKReporter and HamSpots are available for that).
AMEN and well said !
 
--
73
Ron, W3RJW


locked Re: JTAlert 2.12.10 not responding

Michael Black
 

Sounds like either your firewall is blocking it or WSJT-X is corrupted.

#1 Turn off your firewall to test
#2 Run wsjt-x from a cmd line with a new config "wsjtx -r test", set your rig, audio, and turn on the reporting, restart both WSJT-X and JTAlert.

de Mike W9MDB




On Friday, January 18, 2019, 6:57:27 AM CST, Dan Malcolm <K4SHQ@...> wrote:


Tried waiting longer Laurie.  The this popped up:

 

Looking at the WSJT-X Setting -> Reporting page shows the correct UPD ip address (127.0.0.1) and UDP Port (2237).  The check boxes adjacent to those settings are all checked.  I’m going to continue to let it set, but it has been running about 10 minutes at this point.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, January 18, 2019 12:27 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.12.10 not responding

 

On 18/01/2019 4:36 pm, Dan Malcolm wrote:

Laurie,

I’m having trouble getting JTAlert to start successfully.  It starts up, I the “Reading Settings Data Standby” notice and a little while later I “Not Responding” in the title bar.  I have tried a warm reboot of the computer (Win10 x64) and a power off reboot, without success.  I have also tried reinstalling.  When I kill the process, it leaves behind  “JTAlert Plugins Helper”.  That may be normal since JTAlert was not shut down normally.  I can shut it down via the red ‘x’ in the upper right corner.

Now I’m wondering if there is an INI file that’s corrupted.  What do you recommend?

__________

Dan – K4SHQ

Dan,

When this occurs, ignore it and wait a couple of minutes. Does JTAlert eventually startup?

de Laurie VK3AMA


--
Dan - K4SHQ

14601 - 14620 of 37715