Date   

locked Re: MixW logging will no longer be available Announcement

Dave Cole
 

Alas, another logging program leaves... I will miss it, as I used MixW as well.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Technical Specialist
ARRL Volunteer Examiner
ARRL Asst. Director, NW Division, Technical Resources

On 7/20/19 1:30 AM, Murf wrote:
Bummer that mixwlogging be available


locked Re: MixW logging will no longer be available Announcement

Murf <n7uvh01@...>
 

Bummer that mixwlogging be available


locked Re: update of the callsign

f8nhf
 

     Hello
Everything's fine now.

Thank you very much for your help. 

73 Denis F8NHF


locked Re: JTALERT/WSJT Shutdown

HamApps Support (VK3AMA)
 

On 20/07/2019 12:05 pm, Steven Radoff wrote:

The alternate 2.13.10 version solved the closer highlighting issue. It would be nice if the title is black as shown on the Web page. Closing WSJT from JTALert still remains.

I was running this exact version with Win 7.

Sorry for the missing info.
Regards..Steve
Steve,

To what webpage are you referring? I don't see any JTAlert image with a black title on the offical download page on HamApps.com

"Closing WSJT from JTAlert still remains", what does this mean? Are you saying that WSJT-X is not closing when JTAlert is closed? If so, that will only happen if JTAlert was used to start WSJT-X using one of the JTAlert auto-start entries and the "close" checkbox is enabled. Do you satisfy both those requirements?

de Laurie VK3AMA


locked Re: JTALERT/WSJT Shutdown

Steven Radoff
 

Name: Steven Radoff
Call Sign: K4SKR

JTALERT version: 2.13.8

The alternate 2.13.10 version solved the closer highlighting issue. It would be nice if the title is black as shown on the Web page. Closing WSJT from JTALert still remains.

I was running this exact version with Win 7.

Sorry for the missing info.
Regards..Steve


On Jul 19, 2019, at 4:48 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 20/07/2019 4:48 am, sradoff1942@... wrote:
I updated Win 7 to win 10. With win 7 I am able to close WSJT from the JTALERT closer. This does not happen with win 10. Further the closer turns red with WSJT closer, but not JTALert on win 10.

OM (name, callsign??)

What version of JTAlert?

From the 2.13.8 release notes...
  Fixes:
    - Non-responsive Minimize and Close buttons (traditional JTAlert) after
       Win10 v1903 update. Note, these buttons still don't display the normal
       color changes when the mouse pointer is hovered over the buttons, but
       are now responding to mouse-clicks.

If you still have problems, install the "Alternate Layout" build of JTAlert.

de Laurie VK3AMA


locked #Announcement : JT65-HF & JT65-HB9HQX support is being dropped with the next release of JTAlert (2.14.0) #Announcement

HamApps Support (VK3AMA)
 

JTAlert users of the long-abandoned JT65-HF and JT65-HB9HQX programs, please take note that with the next release of JTAlert (2.14.0) there will be no support for these two legacy JT65 only applications.

de Laurie VK3AMA


locked Re: MixW logging will be dropped with the next release of JTAlert (2.14.0)

richard stanley
 

Shame I still use mixw myself :(


Richard G7OED

On 19/07/2019 00:29, HamApps Support (VK3AMA) wrote:
MixW users of JTAlert (are there any?), please take note that with the next release of JTAlert (2.14.0), MixW logging will no longer be available.

de Laurie VK3AMA


Virus-free. www.avast.com


locked Re: JTALERT/WSJT Shutdown

HamApps Support (VK3AMA)
 

On 20/07/2019 4:48 am, sradoff1942@... wrote:
I updated Win 7 to win 10. With win 7 I am able to close WSJT from the JTALERT closer. This does not happen with win 10. Further the closer turns red with WSJT closer, but not JTALert on win 10.

OM (name, callsign??)

What version of JTAlert?

From the 2.13.8 release notes...
  Fixes:
    - Non-responsive Minimize and Close buttons (traditional JTAlert) after
       Win10 v1903 update. Note, these buttons still don't display the normal
       color changes when the mouse pointer is hovered over the buttons, but
       are now responding to mouse-clicks.

If you still have problems, install the "Alternate Layout" build of JTAlert.

de Laurie VK3AMA


locked Re: update of the callsign

HamApps Support (VK3AMA)
 

On 20/07/2019 4:10 am, f8nhf wrote:
Due to PC problems I had to re-install JTDX / JTALERT / HRD...... in haste I was wrong when I entered my callsign in the WEB Services / Station Callsing tab   
Ican't make the change as indicated on the change key  
thank you 
73 Denis F8NHF
Denis,

You need to click the "Change" button which will produce a popup message with instructions.

   

My Windows 10 Start Menu...
   

de Laurie VK3AMA


locked JTALERT/WSJT Shutdown

Steven Radoff
 

I updated Win 7 to win 10. With win 7 I am able to close WSJT from the JTALERT closer. This does not happen with win 10. Further the closer turns red with WSJT closer, but not JTALert on win 10.


locked update of the callsign

f8nhf
 

 hello

Due to PC problems I had to re-install JTDX / JTALERT / HRD...... in haste I was wrong when I entered my callsign in the WEB Services / Station Callsing tab   
Ican't make the change as indicated on the change key  
thank you 
73 Denis F8NHF


locked Re: JTAlert Auto-log

 
Edited

I found what my problem was. It now auto-logs to DxKeeper. The option to do so is found in the WSJT-x app. Go to SETTINGS-REPORTING and under logging check the box that says PROMPT ME TO LOG QSO. That's the only box. When you complete a QSO a box pops up saying "Click OK to confirm the following QSO". When you OK it it says "Success, QSO logged". If something went wrong it will tell you it failed. I also use QRZ.com and it sends it there also but you have to manually do a little work.


locked MixW logging will no longer be available Announcement

John - AI4FR
 

I read the below announcement and thought I'd chime in. I still use MixW2 ver. 2.19 here. JTAlertX has worked perfectly in conjunction with WSJT-X to log more than 30k QSO's. I am sad to see the support being dropped but I do understand. When it comes to MixW2 logging I use the .log file and not the .csv file as recommended by JTAlertX and so far all has been fine. Maybe I'll get lucky and version 2.14.0 of JTAlert will still work with the .log file... Either way, a huge thank you to Laurie VK3AMA for creating this software that has made amateur radio better for all of us out here. Thanks Laurie!!
 
73,
John / AI4FR
 
2a.           #Announcement : MixW logging will be dropped with the next release of JTAlert (2.14.0) #Announcement
From: HamApps Support (VK3AMA)
Date: Thu, 18 Jul 2019 16:29:09 PDT
 
MixW users of JTAlert (are there any?), please take note that with the next release of JTAlert (2.14.0), MixW logging will no longer be available.
 
de Laurie VK3AMA


locked Re: JTAlert Auto-log

Michael Black
 

Only under FT4 contesting can WSJT-X log automatically.

Is that what you're remembering?  It never autologged any other mode.  JTDX might have done such a thing though....not sure....

de Mike W9MDB





On Friday, July 19, 2019, 07:25:12 AM CDT, John Scheuer <na6y@...> wrote:


I am using JTAlert 2.13.10. I had it set up to show me a window when the contact was completed. It  would also let me know whether the QSO was logged successfully or if it failed. This know longer happens. I do get that window if I click on "Log QSO" in the WSJT-X app but I never had to do that before. I am puzzled as to why this no longer takes place automatically.
de NA6Y


locked JTAlert Auto-log

 

I am using JTAlert 2.13.10. I had it set up to show me a window when the contact was completed. It  would also let me know whether the QSO was logged successfully or if it failed. This know longer happens. I do get that window if I click on "Log QSO" in the WSJT-X app but I never had to do that before. I am puzzled as to why this no longer takes place automatically.
de NA6Y


locked Re: JTAlert scheduling WSJT-X with different parameters??

Michael Black
 

Just add the switch like this in the parameters box.  I use this for a different config setup.

Inline image

de Mike W9MDB


On Thursday, July 18, 2019, 10:16:04 PM CDT, Darrell Gordon <dargordo@...> wrote:


Howdy all.  I have two shortcuts designed to run WSJT-X on 1) my FT-847 for V/UHF, and 2) IC-7410.  The only difference in the two shortcut string is the rigname which points to a config file. Example:
C:\WSJT\wsjtx\bin\wsjtx.exe --rig-name=FT847    and  just plain     C:\WSJT\wsjtx\bin\wsjtx.exe

I'm trying  to find out if I can do the same for JTAlert so that it will pass the same string ("--rig-name=FT847) to WSJT-X when it launches.  I swear I've been all over the documentation, but my tired old eyes are not picking it up.  Any help very appreciated.

73 de W4CX  Darrell


locked JTAlert scheduling WSJT-X with different parameters??

Darrell Gordon <dargordo@...>
 

Howdy all.  I have two shortcuts designed to run WSJT-X on 1) my FT-847 for V/UHF, and 2) IC-7410.  The only difference in the two shortcut string is the rigname which points to a config file. Example:
C:\WSJT\wsjtx\bin\wsjtx.exe --rig-name=FT847    and  just plain     C:\WSJT\wsjtx\bin\wsjtx.exe

I'm trying  to find out if I can do the same for JTAlert so that it will pass the same string ("--rig-name=FT847) to WSJT-X when it launches.  I swear I've been all over the documentation, but my tired old eyes are not picking it up.  Any help very appreciated.

73 de W4CX  Darrell


locked Re: Tracking 60 meters?

HamApps Support (VK3AMA)
 

On 19/07/2019 11:17 am, Al Bailey (K8SIX) wrote:

I know 60 meters is not included in DXCC so therefore will not get alerts when a new one shows up I/We don’t have.. Would it be possible to add that as an optional band in the DXCC Alerts? Something a user could turn on/off?

 

73 de Al, K8SIX

Already available (has been for several years).

   

JTAlert doesn't restrict the Alerts to the specific requirements of popular awards. Its alerting is generic in nature, consistent across all the alert types, supporting Band/Mode tracking regardless of the alert type. 60m DXCC Alerts are available.

de Laurie VK3AMA


locked Re: Decodes History v3 (v0.1.10) and FT4 Reporting

Gene, K5PA
 

Laurie, I found the solution in your Release Notes. This did bring the version up to Database Version 0.3.1 and now the FT4 contacts are being displayed correctly on the WIN7 computer with Decode History display. 
Thanks for you help, this was a great end to a problem. 
Gene

*** Using Windows File Explorer delete "decodes.sqlite" and "lookup.sqlite"
  *** which are located at %localappdata%\HamApps\JTAlert\YOUR_CALLSIGN\Decode\


locked Re: Decodes History v3 (v0.1.10) and FT4 Reporting

HamApps Support (VK3AMA)
 

On 19/07/2019 11:24 am, Gene, K5PA wrote:
Of course I meant to write update the Win7 computer's version to Database Version 0.3.1 
Gene

Using Windows File Explorer delete "decodes.sqlite" and "lookup.sqlite"
which are located at %localappdata%\HamApps\JTAlert\YOUR_CALLSIGN\Decode\
These two files will be auto-created when you next run the Decodes History.

let me know if that corrects the problem.

de Laurie VK3AMA