Date   

locked Re: Eliminate all CQ State Alerts? #FT8

Michael Black
 

I assume you must mean you have worked the first level of WAS and have no interest in doing it by-band or by-mode.

Two things:

#1 Settings/Wanted State -- you should be able to turn off the checkbox on that one and stop all such alerts.
#2 Same place but you could change it to "any mode" and "any band" which would stop the alerts too.

#2 depends though on you having done "Scan Log and Rebuild" to update your QSL status.

What logger are you using?  Have you updated your logger with the LOTW QSLs?  And have you then done the "Scan Log and Rebuild"?

de Mike W9MDB




On Friday, September 14, 2018, 1:28:39 PM CDT, GLENN PACKARD <packardg@...> wrote:


I have worked WAS and want to turn off ALL CQs STATE alerts from WSJT-X FT8 .  I have found this impossible to do after trying many different approaches.  I would appreciate any help on this issue.

Tnx,

Glenn
K4ZOT


locked Re: Eliminate all CQ State Alerts? #FT8

Dave Garber
 

are you using jtalert?   with wsjtx?     try turning it off in jtalert
Dave Garber
VE3WEJ / VE3IE


On Fri, Sep 14, 2018 at 2:28 PM GLENN PACKARD <packardg@...> wrote:
I have worked WAS and want to turn off ALL CQs STATE alerts from WSJT-X FT8 .  I have found this impossible to do after trying many different approaches.  I would appreciate any help on this issue.

Tnx,

Glenn
K4ZOT


locked Eliminate all CQ State Alerts? #FT8

 

I have worked WAS and want to turn off ALL CQs STATE alerts from WSJT-X FT8 .  I have found this impossible to do after trying many different approaches.  I would appreciate any help on this issue.

Tnx,

Glenn
K4ZOT


locked Re: Support for FT8Call

James Shaver (N2ADV)
 

See the following from the group already:

https://hamapps.groups.io/g/Support/message/21406

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of hghinson@...
Sent: Thursday, September 13, 2018 3:42 PM
To: Support@HamApps.groups.io
Subject: [HamApps] Support for FT8Call

 

Are there any plans to support the new FT8Call program in JTalert? Am especially interested in logging to DXkeeper in DXlabs. Thanks. KI5WA


locked Support for FT8Call

Horace
 

Are there any plans to support the new FT8Call program in JTalert? Am especially interested in logging to DXkeeper in DXlabs. Thanks. KI5WA


locked Re: logging with DXKeeper

scot
 

Dave,

I found the error of my ways, there was another check box that I missed

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@ambersoft.com]
Sent: Wednesday, September 12, 2018 5:55 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] logging with DXKeeper

+ AA6YQ comments below

I notice that after an FT* contact is made and JT alert logs it, it does not set the QSL requested flag to R. Am I just missing a check mark that I dont find?

+ On the LoTW tab of DXKeeper's "QSL Configuration" window, check the "Initialize LoTW Sent to 'R' for each logged QSO or imported QSO" box.

73,

Dave, AA6YQ


locked Re: logging with DXKeeper

scot
 

Dave,

I have that checked, everything works fine for all other modes but the FT8. You have a great suite of programs!!!

Scott
N2SAB

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@ambersoft.com]
Sent: Wednesday, September 12, 2018 5:55 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] logging with DXKeeper

+ AA6YQ comments below

I notice that after an FT* contact is made and JT alert logs it, it does not set the QSL requested flag to R. Am I just missing a check mark that I dont find?

+ On the LoTW tab of DXKeeper's "QSL Configuration" window, check the "Initialize LoTW Sent to 'R' for each logged QSO or imported QSO" box.

73,

Dave, AA6YQ


locked Re: logging with DXKeeper

scot
 

Laurie,

 

I set that check box as instructed and did a complete reboot and still no “R” in the QSL field. Any ideas?

 

The program is great!!!!!!

 

Scott

N2SAB

 

From: HamApps Support (VK3AMA) [mailto:vk3ama.ham.apps@...]
Sent: Wednesday, September 12, 2018 5:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] logging with DXKeeper

 

On 13/09/2018 5:36 AM, scot wrote:

Hello,
I notice that after an FT* contact is made and JT alert logs it, it does not set the QSL requested flag to R.  Am I just missing a check mark that I dont find?

Scott
N2SAB

Scott,

Use the QSL checkbox in the Log fields area of JTAlert.
This is for card requests and has to be set on a per-QSO basis.
Visit the Settings, Logging section, and check the "Remember QSL Request..." option to have the option permanently enabled.
 
   

   

For LoTW and eQSL, they can be set on an all-QSO basis. Visit the settings, Logging section, and enable the appropriate option.

   

   
de Laurie VK3AMA


locked Re: #WARNING : Latest HamApps Callsign Database (2018.09.13) problems.

Alfred Reeves
 

Thanks for the heads up Laurie!

Al
W1JHU

On 9/13/2018 6:11 AM, HamApps Support (VK3AMA) wrote:
The latest database (2018.09.13) was created with an updated sqlite.dll file and it looks like it is not compatible with the current JTAlert 2.12.5 which uses an older sqlite.dll

If anyone is experiencing missing LoTW/eQSL flags and country names replaced with a "0" they will need to install an earlier version of the database. HamApps.com is now listing the previous version, 2018.08.27, which is compatible with the current and earlier JTAlert.

Let me know if that doesn't work for you.

de Laurie VK3AMA


locked Re: #WARNING : Latest HamApps Callsign Database (2018.09.13) problems.

Ed Wilson
 

Laurie,

The older version is working as expected.

Ed, K0KC

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


On Thursday, September 13, 2018, 6:11:37 AM EDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


The latest database (2018.09.13) was created with an updated sqlite.dll file and it looks like it is not compatible with the current JTAlert 2.12.5 which uses an older sqlite.dll

If anyone is experiencing missing LoTW/eQSL flags and country names replaced with a "0" they will need to install an earlier version of the database. HamApps.com is now listing the previous version, 2018.08.27, which is compatible with the current and earlier JTAlert.

Let me know if that doesn't work for you.

de Laurie VK3AMA

Virus-free. www.avast.com


locked #WARNING : Latest HamApps Callsign Database (2018.09.13) problems.

HamApps Support (VK3AMA)
 

The latest database (2018.09.13) was created with an updated sqlite.dll file and it looks like it is not compatible with the current JTAlert 2.12.5 which uses an older sqlite.dll

If anyone is experiencing missing LoTW/eQSL flags and country names replaced with a "0" they will need to install an earlier version of the database. HamApps.com is now listing the previous version, 2018.08.27, which is compatible with the current and earlier JTAlert.

Let me know if that doesn't work for you.

de Laurie VK3AMA


locked Re: logging with DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I notice that after an FT* contact is made and JT alert logs it, it does not set the QSL requested flag to R. Am I just missing a check mark that I dont find?

+ On the LoTW tab of DXKeeper's "QSL Configuration" window, check the "Initialize LoTW Sent to 'R' for each logged QSO or imported QSO" box.

73,

Dave, AA6YQ


locked Re: logging with DXKeeper

HamApps Support (VK3AMA)
 

On 13/09/2018 5:36 AM, scot wrote:
Hello,
I notice that after an FT* contact is made and JT alert logs it, it does not set the QSL requested flag to R.  Am I just missing a check mark that I dont find?

Scott
N2SAB
Scott,

Use the QSL checkbox in the Log fields area of JTAlert.
This is for card requests and has to be set on a per-QSO basis.
Visit the Settings, Logging section, and check the "Remember QSL Request..." option to have the option permanently enabled.
 
   

   

For LoTW and eQSL, they can be set on an all-QSO basis. Visit the settings, Logging section, and enable the appropriate option.

   

   
de Laurie VK3AMA


locked logging with DXKeeper

scot
 

Hello,
I notice that after an FT* contact is made and JT alert logs it, it does not set the QSL requested flag to R.  Am I just missing a check mark that I dont find?

Scott
N2SAB


locked Re: Changing my call results in a Error.

vdlaken@...
 

Thanks Laurie

Your guess was right. The problem I had was that although I chose a file as logfile, I forgot to go up to the "logging" item before I was able to save the configuration. It's up and running now.

73 de Wil, pe3t (pa0bwl)


locked Re: Need to find WSJT-X JTAlert-X setting

Jim - N4ST
 

I believe what you are looking for is when using the MSK144 mode you can offset your receive frequency to allow for rig calibration errors.

 

_____________

73,

Jim – N4ST

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of k6vib@q.com
Sent: Tuesday, September 11, 2018 13:13
To: Support@HamApps.groups.io
Subject: [HamApps] Need to find WSJT-X JTAlert-X setting

 

I ran across a setting in one of the "settings" of the subject matter that allowed me to set my received frequency +/- a certain number of Hz. I cannot find that again after going through several of the available pages to make changes in either program. Any help?


locked Re: Changing my call results in a Error.

HamApps Support (VK3AMA)
 

On 11/09/2018 5:14 AM, vdlaken@xs4all.nl wrote:
JTAlertX 2.12.5 After changing my call (in the startup directory) I get an error message about AdifImport.exe : Bad or missing command line parameters -  and than the filename and location: C: \Program Files\HamApps\JTAlert\plugins\AdifImport.exe followed by all that is missing (call out trace and lock)
I suppose I did something wrong but I cannot get it working again properly.
Any ideas?
OM,

Without seeing the error message, I can only guess as to the cause.

Most likely the error message is showing --in="". Is that the case? If so, it indicates that your adif file path set in JTAlert is empty. Which may happen if you changed your Callsign which then alters file paths were critical JTAlert files are stored.

de Laurie VK3AMA


locked Re: Changing my call results in a Error.

HamApps Support (VK3AMA)
 

On 11/09/2018 5:14:
TAlertX 2.12.5 After changing my call (in the startup directory) I get an error message about AdifImport.exe : Bad or missing command line parameters -  and than the filename and location: C: \Program Files\HamApps\JTAlert\plugins\AdifImport.exe followed by all that is missing (call out trace and lock)
I suppose I did something wrong but I cannot get it working again properly.
Any ideas?
OM,

What is the changed Callsign? Does it contain any non-standard characters?

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.

de Laurie VK3AMA


locked Changing my call results in a Error.

vdlaken@...
 

JTAlertX 2.12.5  After changing my call (in the startup directory) I get an error message about AdifImport.exe : Bad or missing command line parameters -  and than the filename and location: C: \Program Files\HamApps\JTAlert\plugins\AdifImport.exe followed by all that is missing (call out trace and lock)
I suppose I did something wrong but I cannot get it working again properly.
Any ideas?


locked Re: JTAlert and QRZ.com lookup

W
 

Laurie,

That was it, did not have the XML Log lookup set, once I did that, works perfectly.

Thanks again and apologize for taking your time with this.  I should have figured it out.

Wally

K5WLY

16921 - 16940 of 38543