Hi, I'm looking for the commands and sub commands i can send towards the HRD server on 7809. Can someone provide? Links i found to the API on HRD are no longer working. 73 Pat ON4AMI / OO7P

Thanks, that did it! 73, -Steve WX2S

See the JTDX "Misc -> Accept UDP Reply messages" menu and set to "any messages". de Laurie VK3AMA

Hi, all, I notice that, if I left-click on a decode of a station calling CQ in JTAlert, JTDX will set the Rx frequency to that station and start calling them. But it doesn't do that if the station

It’s in the release notes 2.50.8 for further information. 73 Charlie G4EST www.g4est.me.uk Stay safe out there

I too have not seen this behavior with JTAlertV2.Manager.exe becoming non-responsive. It is just a console application with all the dedicated JTAlert services (as seen in the Help->About)

He installed on a separate computer and it all works fine there. So perhaps he needs to just do an OS reset. Going to try that. First time I've seen this behavior with all the people I've

Yes the "call signs" window will continue to stay open. Laurie, thank you for reminding me about Event viewer, I haven't used it for a long time. Here is the report on the JTAlert crash. Log Name:

All existing JTAlert settings and the B4 file are preserved across JTAlert version upgrades/downgrades. de Laurie VK3AMA

To understand why there is an Alert Database in JTAlert and why there is a need to periodically run the "Rebuild Alert Database" operation click the "Help -> Frequently Asked Questions

That is typically the problem. ACLog by design defaults to using unicast 1270.0.1 on port 2237 for the UDP Server settings regardless of the true setting in WSJTX. ACLog by doing this

Blinking Callsign = ATNO, Hover your mouse over a blinking callsign and examine the resulting tooltip and look for the "ATNO" label that is displayed to the right of one of the

Mike, Anything in the Windows Event Viewer logs? What happens if you rollback JTAlert to an earlier version do you still get this non-responsive condition? de

When you say "Call" window are you referring to the JTAlert "Callsigns" window or something else ? Does the Windows Event Viewer contain any entries relating to JTAlert.exe or

The symptoms are those of an incorrect version of dotNET 5.0.x ... Open PC Settings -> Apps -> Apps & Features ... scroll down to "Microsoft Windows Runtime" - does it say *EXACTLY* "Microsoft

Rename \Users\[username]\AppData\Local\HamApps Then start JTAlert and see if it behaves -- it will be a new configuration. Mike W9MDB

I have tried rolling back to the last 4 64bit versions listed on the web page, but no luck. Tyson

I downloaded the version via the link on the hamapps page. It says it is the desktop version.

Did you install the *DESKTOP* version of dotNET 5.0.x? It sounds as if you might have the "console" version with is incomplete and lacks several interfaces required by JT-Alert. 73, ... Joe,