Date   

locked Re: Unable to Communicate

D. Scott MacKenzie
 

Thank you very much Laurie – I will make those changes.  I had it working then it stopped working.  I probably did something stupid

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, July 17, 2020 4:15 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Unable to Communicate

 

On 17/07/2020 11:35 am, D. Scott MacKenzie wrote:

I recently got this message after WSJT-X was being flaky communicating with DXLabs Commander:

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\kb0fh\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.2.2   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

What should the settings be?




Other possible cause of this error, WSJT-X is set to run as Administrator, either the wsjtx.exe file or the shortcut used to start WSJT-X is set to run elevated. There should be no need to run WSJT-X (or JTAlert elevated).

The port 2237 may be being used by some other application running on your PC. Try changing the port to 2238 and restart both WSJT-X and JTAlert.

de Laurie VK3AMA


locked Re: Unable to Communicate

HamApps Support (VK3AMA)
 

On 17/07/2020 11:35 am, D. Scott MacKenzie wrote:

I recently got this message after WSJT-X was being flaky communicating with DXLabs Commander:

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\kb0fh\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.2.2   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

What should the settings be?




Other possible cause of this error, WSJT-X is set to run as Administrator, either the wsjtx.exe file or the shortcut used to start WSJT-X is set to run elevated. There should be no need to run WSJT-X (or JTAlert elevated).

The port 2237 may be being used by some other application running on your PC. Try changing the port to 2238 and restart both WSJT-X and JTAlert.

de Laurie VK3AMA


locked Re: Grid Alerts: Preparing JTA Settings for CQ WW VHF Contest with Grids. #DXLAB

HamApps Support (VK3AMA)
 

On 18/07/2020 3:56 am, Mark W2OR via groups.io wrote:

~~ Start a new (empty) log for DXKeeper (DXLabs)
~~ Download the latest cty. database from HamApps.com into JTA
~~ Set 'enable' for JTA 'Wanted Grid' . 
~~ Probably turn 'OFF' most all of the other JTA alerts.
~~ Do a JTA Scan of (the empty DXKeeper) log for 'Wanted Grid'
~~ I'm forgetting something here ...  

That covers it, but you don't need to download the Callsign database as it doesn't contain any Grid data, only US State & online QSL membership (lotw & eqsl) data.

A new empty log is the way to go along with a new "Scan Log" operation after setting the new log to ensure that the internal list of not-needed grids is empty.

de Laurie VK3AMA


locked Grid Alerts: Preparing JTA Settings for CQ WW VHF Contest with Grids. #DXLAB

Mark W2OR
 

Preparing JTA Settings for CQ Worldwide VHF Contest with Grids.

This weekend's VHF contest will be a new one here, and am unsure on what JTA settings to adjust before hand, specifically, any related to needed grids.  Any advice would be appreciated.  Thanks.  I'm assuming the following steps are appropriate . . . but being a newbie, perhaps not.  // Mark.

~~ Start a new (empty) log for DXKeeper (DXLabs)
~~ Download the latest cty. database from HamApps.com into JTA
~~ Set 'enable' for JTA 'Wanted Grid' . 
~~ Probably turn 'OFF' most all of the other JTA alerts.
~~ Do a JTA Scan of (the empty DXKeeper) log for 'Wanted Grid'
~~ I'm forgetting something here ...  




locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

Richard Bertrand Larson
 

I use jtalert with LOTW and aclog. After a Scan Log and Rebuild I must use the apply function then save for an update to my wanted list.

Rick KD0XD

On 7/16/2020 4:46 PM, scubajosh77 via groups.io wrote:
I'm going to start off this with a disclaimer that I'm brand new to JTAlert as of yesterday so it may very well be that I don't understand something correctly.  I'm using it with JTDX.  I have an .adif log setup specifically for JTAlert.  When I log a QSO with a new state, it doesn't remove it from my wanted list.  Also I tried to 'Scan Log and Rebuild' the JTAlert .adif file thinking that was how to update the wanted lists against the log, but doing so reset all of my wanted settings.  Have I mis-configured something?  I thought the whole point of the wanted lists was to keep track of your completed QSO goals?


locked JTAlert Crashes/Freezes Often

William D'Agostino
 

Hi Everyone,

First, JTAlert 2.16.8 is a great program, and "Thanks" to everyone who helped write, update, and maintain the program.  I've already made 3,000+ FT8 QSOs using WSJT-X and JTAlert.

I've been experiencing some strange behavior.

When starting JTAlert after starting WSJT-X 2.2.2 and AC Log 6.6, I will often get the following JTAlert error messages:

"Line 22794 Error: Variable used without being declared."

Inline image

Or, this error:

"Line 1380 Error: Variable used without being declared."

Inline image

In addition, almost every time after clicking on "OK" when changing a JTAlert "Setting" such as an alert setting or after scanning/rebuilding my log, the JTAlert program will either quit or freeze.

Last but not least, about 1 in every 15 logged QSOs, JTAlert won't display a "Grayed Call Sign with B4" after logging the QSO successfully.  Scanning/rebuilding JTAlert log will only fix this issue about 50% of the time.  But, as mentioned above, the JTAlert with quit or freeze when clicking on OK, requiring me to restart the program.

I have restarted my laptop several times, but that doesn't seem to fix anything. I've also tried re-installing JTAlert, WSJT-X and AC Log with no change.

Has anyone else experienced anything like this?

I'm running:

Dell Latitude Laptop E6420; 64-bit; 8 GB; 2.80 GHz
Windows 7 with Service Pack 1
WSJT-X 2.2.2
AC Log 6.6
JTAlert 2.16.8
I'm not using CAT control for rig (i.e., rig is manually controlled)

Thanks,

Will
WB1DMK






locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

That was it Laurie!  Thank you so much!  Doesn't make a lick of sense but it works LOL!

73
Josh
KN4VDR


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

HamApps Support (VK3AMA)
 

On 17/07/2020 11:06 am, scubajosh77 via groups.io wrote:
Yes, I downloaded my LoTW QSL .adif.  There's something not working with the JTAlert confirmation as it ties into the Wanted Alerts.  I can see the actual LoTW confirmation data in my .adif file and JTAlert isn't recognizing it for some reason.

Josh, KN4VDR

If your using an LoTW sourced ADIF file you need to use the "Card" checkbox for the QSL confirmation type for the Scans.

LoTW adif files, DON"T use the standard adif <LOTW_QSL_RCVD> field despite the file containing Lotw confirmed QSOs, they use the <QSL_RCVD> field normally used to indicate card confirmations.

Open the adif file in a text editor and you will note there are NO <
LOTW_QSL_RCVD> fields in the data.

de Laurie VK3AMA


locked Unable to Communicate

D. Scott MacKenzie
 

I recently got this message after WSJT-X was being flaky communicating with DXLabs Commander:

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2237

  IP Address : 127.0.0.1

  Values read from WSJT-X config file...

    C:\Users\kb0fh\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.2.2   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

What should the settings be?


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

Yes, I downloaded my LoTW QSL .adif.  There's something not working with the JTAlert confirmation as it ties into the Wanted Alerts.  I can see the actual LoTW confirmation data in my .adif file and JTAlert isn't recognizing it for some reason.

Josh, KN4VDR


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

Larry Banks
 

Have you downloaded your LoTW confirmations and put them in your log, by whatever method your log requires?

73 -- Larry -- W1DYJ

 

Sent: Thursday, July 16, 2020 20:54
Subject: Re: [HamApps] Scan Log and Rebuild Kills my 'Wanted Settings'
 
Thank you, I think I understand partially now.  If I select the No QSL Confirmation in the Scan menu it reflects the QSOs I've worked.  What I don't understand is if I don't select it and have LoTW selected as a confirmation source, it doesn't accurately reflect my QSLs on LoTW.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

g4wjs
 

On 17/07/2020 02:00, scubajosh77 via groups.io wrote:
I merged my WSJT-X and LoTW .adif files using ADIFMerge.exe specifically for JTAlert use.  Then checked them for errors with ADIFMaster.
Josh,

I believe the LoTW ADIF export doesn't use the LoTW QSL confirmed field  to show a match, I believe it uses the field that is normally used to confirm a QSL by a paper card.



--
73
Bill
G4WJS.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

Larry Banks
 

Hi Scubajosh77 (name?  call?)
 
Are you responding to my earlier comment?  Without the thread I don’t know.
 
But if you are, once you have confirmed calls in the log you are using for the Scan and Update process, they will be recognized IF you have the proper attributes set in the Scan & Update fields.

73 -- Larry -- W1DYJ

 

Sent: Thursday, July 16, 2020 20:48
Subject: Re: [HamApps] Scan Log and Rebuild Kills my 'Wanted Settings'
 
So the Wanted Alerts are based on QSL, QSO?  And what method is used to confirm the contacts?  I only QSL via QRZ and LotW.  And my QSL/confirmed contacts in either database aren't reflected in my JTAlert Wanted Alerts?


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

I merged my WSJT-X and LoTW .adif files using ADIFMerge.exe specifically for JTAlert use.  Then checked them for errors with ADIFMaster.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

g4wjs
 

On 17/07/2020 01:54, scubajosh77 via groups.io wrote:
Thank you, I think I understand partially now.  If I select the No QSL Confirmation in the Scan menu it reflects the QSOs I've worked.  What I don't understand is if I don't select it and have LoTW selected as a confirmation source, it doesn't accurately reflect my QSLs on LoTW.
Josh,

what is the source of your ADIF log?



--
73
Bill
G4WJS.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

Thank you, I think I understand partially now.  If I select the No QSL Confirmation in the Scan menu it reflects the QSOs I've worked.  What I don't understand is if I don't select it and have LoTW selected as a confirmation source, it doesn't accurately reflect my QSLs on LoTW.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

g4wjs
 

On 17/07/2020 01:48, scubajosh77 via groups.io wrote:
So the Wanted Alerts are based on QSL, QSO?  And what method is used to confirm the contacts?  I only QSL via QRZ and LotW.  And my QSL/confirmed contacts in either database aren't reflected in my JTAlert Wanted Alerts?
Josh,

you set your own criteria for a confirmation in the "Scan Log and Rebuild" settings.



--
73
Bill
G4WJS.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

*based on QSL, not QSO?


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

So the Wanted Alerts are based on QSL, QSO?  And what method is used to confirm the contacts?  I only QSL via QRZ and LotW.  And my QSL/confirmed contacts in either database aren't reflected in my JTAlert Wanted Alerts?


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

Larry Banks
 

Not until it’s confirmed.

73 -- Larry -- W1DYJ

 

Sent: Thursday, July 16, 2020 20:37
Subject: Re: [HamApps] Scan Log and Rebuild Kills my 'Wanted Settings'
 
Thank you for the response.  But that does not explain how I can log a QSO with someone in New Mexico for example, and then run the Scan Log and Rebuild function, and New Mexico shows up on my Wanted List for the same band.  If I log a QSO with a State, DXCC, etc. shouldn't it be removed from my want alerts when I do the Scan and Rebuild?

Josh, KN4VDR

5401 - 5420 of 36207