Date   

locked Re: JTAlert talking to WSJT and JTDX

Dave Garber
 

Aclog uses the api on port 1100.   And jtalert should be set to that port and correct log file..   I did try it using the multicast.    Cant remember if it worked


On Wed., May 19, 2021, 12:01 a.m. Bill Gillenwater, <k3sv@...> wrote:

Mike,

That seems to have fixed things. I will work a little more tonight to verify that it's working on both JTDX and WSJT, with my logger and with JTAlert running.

Help very much appreciated.

73 Bill K3SV

On 5/18/2021 11:22 PM, Michael Black via groups.io wrote:
It sounds like you have your logger listening on the same port as JTAlert.
So whichever starts first wins.

You probably want to set up JTAlert to forward the packets and set your logger to receive on port 2334 (the default you see below)

Inline image

Mike W9MDB



On Tuesday, May 18, 2021, 10:17:20 PM CDT, Bill Gillenwater <k3sv@...> wrote:


More info.
If I start WSJT and then JTAlert without starting a logging program, I get the JTAlert screen that alerts me to callers and needed calls, etc.

If I then start a logger and try to log a contact, it does not work.

If I start the logger first and then WSJT and JTAlert, I can do the logging with not problem, but I get messages that JTAlert is not talking to WSJT.

Need assist on this. It's probably simple, it's just eluding me.

73 Bill K3SV


locked Re: JTAlert talking to WSJT and JTDX

Bill Gillenwater
 

Mike,

That seems to have fixed things. I will work a little more tonight to verify that it's working on both JTDX and WSJT, with my logger and with JTAlert running.

Help very much appreciated.

73 Bill K3SV

On 5/18/2021 11:22 PM, Michael Black via groups.io wrote:
It sounds like you have your logger listening on the same port as JTAlert.
So whichever starts first wins.

You probably want to set up JTAlert to forward the packets and set your logger to receive on port 2334 (the default you see below)



Mike W9MDB



On Tuesday, May 18, 2021, 10:17:20 PM CDT, Bill Gillenwater <k3sv@...> wrote:


More info.
If I start WSJT and then JTAlert without starting a logging program, I get the JTAlert screen that alerts me to callers and needed calls, etc.

If I then start a logger and try to log a contact, it does not work.

If I start the logger first and then WSJT and JTAlert, I can do the logging with not problem, but I get messages that JTAlert is not talking to WSJT.

Need assist on this. It's probably simple, it's just eluding me.

73 Bill K3SV


locked Re: JTAlert talking to WSJT and JTDX

Michael Black
 

It sounds like you have your logger listening on the same port as JTAlert.
So whichever starts first wins.

You probably want to set up JTAlert to forward the packets and set your logger to receive on port 2334 (the default you see below)

Inline image

Mike W9MDB



On Tuesday, May 18, 2021, 10:17:20 PM CDT, Bill Gillenwater <k3sv@...> wrote:


More info.
If I start WSJT and then JTAlert without starting a logging program, I get the JTAlert screen that alerts me to callers and needed calls, etc.

If I then start a logger and try to log a contact, it does not work.

If I start the logger first and then WSJT and JTAlert, I can do the logging with not problem, but I get messages that JTAlert is not talking to WSJT.

Need assist on this. It's probably simple, it's just eluding me.

73 Bill K3SV


locked Re: JTAlert talking to WSJT and JTDX

Bill Gillenwater
 

More info.
If I start WSJT and then JTAlert without starting a logging program, I get the JTAlert screen that alerts me to callers and needed calls, etc.

If I then start a logger and try to log a contact, it does not work.

If I start the logger first and then WSJT and JTAlert, I can do the logging with not problem, but I get messages that JTAlert is not talking to WSJT.

Need assist on this. It's probably simple, it's just eluding me.

73 Bill K3SV


locked JTAlert talking to WSJT and JTDX

Bill Gillenwater
 

I cannot get JTAlert to talk to either WSJT or JTDX.

I am using the 127.0.0.1     2237     UDP port to do logging in N3FJP logger.

How do I set up another avenue to talk to JTAlert?

Thanks,  73 Bill K3SV


locked Re: Question On Logging Config Items

Paul N3PS
 

Laurie,

Ham Radio Deluxe is recommending to use their UDP Broadcast set up (as opposed to TCP) to take in the QSO and let HRD Logbook do the address lookups.   If I were to follow their recommendations, what functionality would I be loosing within JT Alert?
--
Paul / N3PS


locked Re: Question On Logging Config Items

HamApps Support (VK3AMA)
 

On 18/05/2021 1:05 am, n3ps via groups.io wrote:
Within Logging settings, I am trying to understand the difference between two config items "Log Full QTH Returned From XML Lookups" and  "Log Address Returned From An XML Or Previous QSO Lookup".  It would seem they both control the same function.  Help me get my head around this . . .

--
Paul / N3PS

The QTH and Address are two different items in most logging programs, including the ADIF standard. The Address is typically the address to which QSLs are sent. Some users want that additional data recorded with each QSO, but many don't (myself included) so it is an option. The QTH logged can be either the full QTH returned from an XML data feed or a shortened version where JTAlert attempt to extract a Town/City name from the xml data which can often not contain a dedicated QTH field so the address field is used to try and get the QTH.

de Laurie VK3AMA


locked Re: JTAlert 2.50.1 running with WSJT-X v2.3.1 #FT8

Laurie, VK3AMA
 

On 18/05/2021 9:10 am, Grouch wrote:
Windows 10 Pro on ACPI x64-based desktop Intel Core 05-6400 @2.70GHz.  I downloaded and upgraded to JTAlert 2.50.1.  for use with WSJT-X v2.3.1 and JTDX v.2.2.156When I call the program the correct windows open and it interacts correctly and functions with WSJT-X showing the activity and filters.  However,  the main "Alerts Settings View Sound Help"  window just disappears within 2 minutes and the other windows freeze.  In Task Manager the following are listed "Audio & Visual Alerts for WSTX-32bit Decodes, JTAlert V2 Manager - GPU 0-3D.  When I check each is shown as "Disabled. This occurs each time the main drops from view on the screen and taskbar. This happens if it is running with HRD for rig control or independently.  The same same occurs with JTDX v2.2.156 with JTAlert for JTDX.  Each time the same Autoit Error appears "Line 10382 (file "C:\Program Files ((X86)HamApps\JTAlert\JTAlert.exe): Error: Variable used without being declared.  I have done clean re-installs of all these software packages and checked the "permissions" in the system. I have even run the install as Current User" I am the administrator and "run as Adminstrator." NOTE: I had no problem with the previous version 2.16.6   I am about to pull out what hair I have left.
OM (Name?, Callsign?)

I can understand JTAlert.exe showing as disabled if there has been an AutoIT error, but not JTAlertV2.Manager.exe. Sounds like your Protection software is interfering.

Another possibility is something unusual with your old version JTAlert config file, but that will not cause the Manager process to become disabled. Worth trying is starting JTAlert without a config file. Try shutting down JTAlert, deleting (or relocating) the config.sqlite file, then starting JTAlert without a config file (a new one will automatically be created). The config file, config.sqlite can be found at %localappdata%\HamApps\<YOUR_CALLSIGN>\config\JTAlertX\

Let me know your results.

de Laurie VK3AMA


locked JTAlert 2.50.1 running with WSJT-X v2.3.1 #FT8

Grouch
 

Windows 10 Pro on ACPI x64-based desktop Intel Core 05-6400 @2.70GHz.  I downloaded and upgraded to JTAlert 2.50.1.  for use with WSJT-X v2.3.1 and JTDX v.2.2.156When I call the program the correct windows open and it interacts correctly and functions with WSJT-X showing the activity and filters.  However,  the main "Alerts Settings View Sound Help"  window just disappears within 2 minutes and the other windows freeze.  In Task Manager the following are listed "Audio & Visual Alerts for WSTX-32bit Decodes, JTAlert V2 Manager - GPU 0-3D.  When I check each is shown as "Disabled. This occurs each time the main drops from view on the screen and taskbar. This happens if it is running with HRD for rig control or independently.  The same same occurs with JTDX v2.2.156 with JTAlert for JTDX.  Each time the same Autoit Error appears "Line 10382 (file "C:\Program Files ((X86)HamApps\JTAlert\JTAlert.exe): Error: Variable used without being declared.  I have done clean re-installs of all these software packages and checked the "permissions" in the system. I have even run the install as Current User" I am the administrator and "run as Adminstrator." NOTE: I had no problem with the previous version 2.16.6   I am about to pull out what hair I have left.


locked Re: Single/double click within callsigns window not working

Steve Masticola
 

> The WSJT-X API needs to be extended to set TX enabled on non-CQ decodes in response to a UDP Reply command (# 4) from external applications.

OK, in that case, would you mind filing either a bug fix or a feature request against WSJT-X? I could do it, but I know zero about the WSJT-X API.

73, -Steve WX2S


locked Re: How Does JT Alert Update HRD Logbook?

HamApps Support (VK3AMA)
 

On 18/05/2021 1:13 am, g4wjs wrote:
I believe mechanism for the current version of HRD is that JTAlert uses the HRD TCP/IP server API to enter QSOs. That means that the internal logic of HRD to derive fields is used. I also believe worked before queries are made by direct read-only access to the HRD logbook database tables, this probably because HRD logbook doesn't provide any mechanism to look up arbitrary QSO details.

Before the HRD logbook TCP/IP API worked properly (pre v6) I believe the only way for JTAlert to enter new QSOs was to directly insert records into he HRD logbook database tables.

-- 
73
Bill
G4WJS.

All that is correct. Tnx Bill.

de Laurie VK3AMA


locked Re: Single/double click within callsigns window not working

HamApps Support (VK3AMA)
 

On 18/05/2021 3:39 am, Michael Black via groups.io wrote:
I guess that got changed...good to know...


Not in my tests, WSJT-X (2.3.1) is not going into TX on non-CQ Callsigns clicked in JTAlert.

de Laurie VK3AMA


locked Re: Single/double click within callsigns window not working

HamApps Support (VK3AMA)
 

On 18/05/2021 3:34 am, Steve Masticola wrote:
Not correct. I just double-clicked a random station not calling CQ in WSJT-X and it enabled TX.

73, -Steve WX2S

That's because you double-clicked the decode in WSJT-X, NOT JTAlert. If you performed the click action on a non-CQ Callsign in JTAlert, WSJT-X does not got into TX. I just now repeated that test with WSJT-X 2.3.1

The decision to go into TX is controlled by WSJT-X, there is nothing in the command sent from JTAlert that can instruct WSJT-X to go into TX.

The WSJT-X API needs to be extended to set TX enabled on non-CQ decodes in response to a UDP Reply command
(# 4) from external applications.

de Laurie VK3AMA




locked Re: Single/double click within callsigns window not working

Michael Black
 

I guess that got changed...good to know...




On Monday, May 17, 2021, 12:37:27 PM CDT, Steve Masticola <wx2s@...> wrote:


[Edited Message Follows]

Michael,

Not correct. I just double-clicked a random station not calling CQ in WSJT-X and it enabled TX. (You have to have "Double-click on call sets TX enable" set in WSJT-X.)




73, -Steve WX2S


locked Re: Single/double click within callsigns window not working

Steve Masticola
 
Edited

Michael,

Not correct. I just double-clicked a random station not calling CQ in WSJT-X and it enabled TX. (You have to have "Double-click on call sets TX enable" set in WSJT-X.)



73, -Steve WX2S


locked Re: Single/double click within callsigns window not working

Michael Black
 

WSJT-X will only enable TX on CQ calls.  JTAlert does not control that.

JTDX will do it though.

Mike W9MDB




On Monday, May 17, 2021, 12:20:23 PM CDT, Steve Masticola <wx2s@...> wrote:


[Edited Message Follows]

Hi, Laurie,

I'm having the same problem. Clicking on a callsign in the Callsigns window will only set Enable TX in WSJT-X if the station is calling CQ. This appears to be the same with single or double click set.


I did enable single click in the callsign options.

73, -Steve WX2S


locked Re: Single/double click within callsigns window not working

Steve Masticola
 
Edited

Hi, Laurie,

I'm having the same problem. Clicking on a callsign in the Callsigns window will only set Enable TX in WSJT-X if the station is calling CQ. This appears to be the same with single or double click set.

I did enable single click in the callsign options.

73, -Steve WX2S


locked Re: How Does JT Alert Update HRD Logbook?

g4wjs
 

On 17/05/2021 15:56, n3ps via groups.io wrote:
Via what "mechanism" does JT Alert update QSOs into HRD Logbook.  Is it using a UDP, updating the DB directly or how?

To be clear, I'm not asking for configuration instructions, I'm just trying to under the mechanics of how it updates . . .
--
Paul / N3PS
Hi Paul,

I believe mechanism for the current version of HRD is that JTAlert uses the HRD TCP/IP server API to enter QSOs. That means that the internal logic of HRD to derive fields is used. I also believe worked before queries are made by direct read-only access to the HRD logbook database tables, this probably because HRD logbook doesn't provide any mechanism to look up arbitrary QSO details.

Before the HRD logbook TCP/IP API worked properly (pre v6) I believe the only way for JTAlert to enter new QSOs was to directly insert records into he HRD logbook database tables.



--
73
Bill
G4WJS.


locked Re: Closing JTAlert On Windows 10 Pro 64 Bit

Ronald Ford
 

Thanks for the explanation Laurie...almost 70 years old and still learning...take care...
--
73
Ronald, W4RJF


locked Question On Logging Config Items

Paul N3PS
 

Within Logging settings, I am trying to understand the difference between two config items "Log Full QTH Returned From XML Lookups" and  "Log Address Returned From An XML Or Previous QSO Lookup".  It would seem they both control the same function.  Help me get my head around this . . .

--
Paul / N3PS

2441 - 2460 of 37312