Date   

locked CQ for stations not CQing

Steve
 

I am not sure where the call info comes from that say CQ with JTAlert 2.50.0.  I am using JTDX v2.2.0-rc152 with JTAlert.

I keep getting CQ with call signs that don't show in JTDX.  I can't click on them in JTAlert to make a contact.  Where is the CQ contact info coming from that is used in JTAlert?

Thanks.

Steve NA6G


locked Re: JTAlert Issue

HamApps Support (VK3AMA)
 

On 12/05/2021 11:52 am, rob neff via groups.io wrote:
Okay, I tried running the shortcut on the desktop as Admin and it runs now. I will make that permanent. 

Sorry for the trouble. 

Rob KW2E

NO! There should be no need to run JTAlert elevated if installed correctly.

On the affected Windows account, did you install JTAlert or are you relying on the JTAlert install under the other (working) account. If the later, that explains why you need to elevate JTAlert as it is trying to access the %localappdata% area of another Windows account which is normally prevented due to Windows security permissions

For each Windows account you need to install JTAlert.

If your reason for using a secondary Windows account is so that you can use a different Callsign with JTAlert. That is easily accomplished by creating a new JTAlert shortcut with an appropriate callsign command parameter. See the "Station Callsign" section of the Settings window.

   

de Laurie VK3AMA


locked Re: JTAlert Autostart

Craig
 

Hi Jim - decided to make the new changes and all works just fine using JTAlert (launch / close) only. The only window that does not close automatically is the Google Earth Pro window.  That window was not closing when terminating apps using Launcher. Not sure how that is managed.  Best, C

On Fri, May 14, 2021 at 3:41 PM Craig Willison <nz4cwcraig@...> wrote:
Hi Jim - thanks much for your thoughts on shutdown options.  I understand your thinking / approach and how it would work not using the bat file.  Some thoughts on operating implications:

1 - If I am going to run digital, everything (launching / terminating) is then controlled by launching / stopping JTAlert
2 - If I am going to mostly run a different mode, I can launch / terminate DXLab apps via the Launcher (as designed) without WSJT-X / JTAlert running.  Issue would be then starting JTAlert and having the DXLab apps launched again - likely easier to terminate with Launcher and restart via JTAlert.
3 - For mixed mode, option 1 still works fine.

So maybe it's best to always run option 1  given the issue noted under 2. I wonder if there are implications for operating/logging with JTAlert starting before the DXLab apps?  

Could work Jim.  Appreciate you noodling on this for me.  I will swing back to you and let you know what I experience.

73, Craig


On Fri, May 14, 2021 at 2:26 PM Jim N6VH <N6VH@...> wrote:


On 5/13/2021 5:58 PM, Craig wrote:
Hello Jim - thanks so much for taking the time to put together the coding and the description of the process.  All works just great making the entire startup process a single click!  

Question, as Launcher takes care of starting and terminating the DXLab applications and other applications that start direct (before or after the DXLab apps), is there a way to have Launcher terminate the apps started using the above process that you put together for me?  Not a big item but would take care of everything at shutdown.  Thanks again Jim.

73, Craig

Craig,

I'm glad my solution worked fro you.

I don't see any easy way of shutting down JTAlert form DXLab Launcher. It has been many years since I worked with batch files, so I am pretty rusty with them. Here's a thought about a different approach. Would it work for you to have JTAlert autostart DXLab, and NOT use the batch file?  In JTAlert settings, under Auto-Start, set DXLab Launcher to Start after JTAlert, and then Close when JTAlert is closed.

In DXLab Launcher configuration, select the DXLab Apps you want to start, and at the top, check Auto Start. Also, check Terminate On Shutdown. See if that works for you.

Ignore any of the ACLog autostart you see in my JTAlert example. It is just there for testing (as is DXLab Launcher).

73,

Jim N6VH


locked Re: JTAlert Autostart

HamApps Support (VK3AMA)
 

On 15/05/2021 5:41 am, Craig wrote:
I wonder if there are implications for operating/logging with JTAlert starting before the DXLab apps?

There is no problems starting JTAlert before the DXLab programs. JTAlert will not finish its startup until its auto-start entries have started. So there is no trying to log a QSO if DXKeeper has not started.

My recommendation is to NOT autostart DXLab applications from JTAlert. There can be startup delays in starting the suite of DXLab programs, which you will need anticipate  and account for in setting delays in the JTAlert auto-starts. Also, if for some reason you need to restart JTAlert and or WSJT-X you will be forced to shutdown DXLab and restart them also due to their auto-start entries in JTAlert. I would keep the DXLab startups and JTAlert startup separate. Start DXLab first and wait for it to complete then start JTAlert which can be set to auto-start/close WSJT-X.

If you go with JTAlert startling everything, make sure that WSJT-X is started after DXLab commander and that you have given Commander sufficient time to complete its startup before starting WSJT-X.

I personally run the full DXLab suite. It gets started first, independent of JTAlert, then JTAlert/WSJT-X are started. When I want to switch to a non WSJT-X mode operation, I simply close JTAlert/WSJT-X, DXLab is still running for my non-JT modes.

de Laurie VK3AMA


locked Re: UDP defect in both 2.50.0 and 2.50.1

HamApps Support (VK3AMA)
 

On 15/05/2021 1:26 am, Todd (N3PKJ) wrote:
Another thing I noticed is that C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe fails to stays running. Seems like this file tries to start and fails repeatedly about every 5 seconds, can see this in Task Manager.
JTAlertV2.Manager not starting correctly is the cause for your UDP errors. All UDP traffic from WSJT-X to JTAlert comes via the Manager process.


Under view I see this. Note "Show Log Fields" is grayed out and can enable show confirmed bands.
The log fields display menu is grayed is normal behavior for when you don't have a logger enabled in JTAlert. Both your images of the affected Windows account show that you don't have logging enabled. "NO Log" in the main JTAlert title-bar and "Logging Disabled" in the Settings window titlebar.


Now isn't the main JTAlert window suppose to look like this?


Yes, BUT only if you have a log enabled, which is ADIF in this image, unlike your "NO Log" image. There is no point displaying the log fields if logging is disabled and there is no log to interrogate to fill in the Bands  confirmed display



And finally on the secondary Windows user eventually get this error.


This UDP error is due to the Manager process not running.

What do the "*.ERROR" files under the affected Windows account show?
They can be found at %localappdata%\HamApps\debug\

If you can't find the files, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.


de Laurie VK3AMA


locked Re: JTAlert Autostart

Craig
 

Hi Jim - thanks much for your thoughts on shutdown options.  I understand your thinking / approach and how it would work not using the bat file.  Some thoughts on operating implications:

1 - If I am going to run digital, everything (launching / terminating) is then controlled by launching / stopping JTAlert
2 - If I am going to mostly run a different mode, I can launch / terminate DXLab apps via the Launcher (as designed) without WSJT-X / JTAlert running.  Issue would be then starting JTAlert and having the DXLab apps launched again - likely easier to terminate with Launcher and restart via JTAlert.
3 - For mixed mode, option 1 still works fine.

So maybe it's best to always run option 1  given the issue noted under 2. I wonder if there are implications for operating/logging with JTAlert starting before the DXLab apps?  

Could work Jim.  Appreciate you noodling on this for me.  I will swing back to you and let you know what I experience.

73, Craig


On Fri, May 14, 2021 at 2:26 PM Jim N6VH <N6VH@...> wrote:


On 5/13/2021 5:58 PM, Craig wrote:
Hello Jim - thanks so much for taking the time to put together the coding and the description of the process.  All works just great making the entire startup process a single click!  

Question, as Launcher takes care of starting and terminating the DXLab applications and other applications that start direct (before or after the DXLab apps), is there a way to have Launcher terminate the apps started using the above process that you put together for me?  Not a big item but would take care of everything at shutdown.  Thanks again Jim.

73, Craig

Craig,

I'm glad my solution worked fro you.

I don't see any easy way of shutting down JTAlert form DXLab Launcher. It has been many years since I worked with batch files, so I am pretty rusty with them. Here's a thought about a different approach. Would it work for you to have JTAlert autostart DXLab, and NOT use the batch file?  In JTAlert settings, under Auto-Start, set DXLab Launcher to Start after JTAlert, and then Close when JTAlert is closed.

In DXLab Launcher configuration, select the DXLab Apps you want to start, and at the top, check Auto Start. Also, check Terminate On Shutdown. See if that works for you.

Ignore any of the ACLog autostart you see in my JTAlert example. It is just there for testing (as is DXLab Launcher).

73,

Jim N6VH


locked Re: JTAlert Autostart

Jim N6VH
 


On 5/13/2021 5:58 PM, Craig wrote:
Hello Jim - thanks so much for taking the time to put together the coding and the description of the process.  All works just great making the entire startup process a single click!  

Question, as Launcher takes care of starting and terminating the DXLab applications and other applications that start direct (before or after the DXLab apps), is there a way to have Launcher terminate the apps started using the above process that you put together for me?  Not a big item but would take care of everything at shutdown.  Thanks again Jim.

73, Craig

Craig,

I'm glad my solution worked fro you.

I don't see any easy way of shutting down JTAlert form DXLab Launcher. It has been many years since I worked with batch files, so I am pretty rusty with them. Here's a thought about a different approach. Would it work for you to have JTAlert autostart DXLab, and NOT use the batch file?  In JTAlert settings, under Auto-Start, set DXLab Launcher to Start after JTAlert, and then Close when JTAlert is closed.

In DXLab Launcher configuration, select the DXLab Apps you want to start, and at the top, check Auto Start. Also, check Terminate On Shutdown. See if that works for you.

Ignore any of the ACLog autostart you see in my JTAlert example. It is just there for testing (as is DXLab Launcher).

73,

Jim N6VH


locked UDP defect in both 2.50.0 and 2.50.1

 
Edited

Anyone besides me noticed that is your trying to setup both 2.50.0 and 2.50.1 on a secondary Windows account JTAlert fails to operate? I've tried both UDP server IP of 127.0.0.1 and 239.255.0.0 in WSJT-X. Another thing I noticed is that C:\Program Files (x86)\HamApps\JTAlert\pluginsX\JTAlertV2.Manager.exe fails to stays running. Seems like this file tries to start and fails repeatedly about every 5 seconds, can see this in Task Manager. I personally have seen this behavior on two different PCs. One being my own and the other a friend's of mine. Things I have tried; Shut off both antivirus software and Windows Firewall. Go back to the main User Account in Windows and everything is fine, JTAlert works without a hitch. Other behavior I've seen JTAlert version 2.16.17 works fine on either Windows Account using either UDP server IP. And before anyone asks only logged into one Windows User at a time here, so there should be no conflicts.

I also have tried a total reinstall & reconfig of JTAlert nothing solves this issue. During the reconfig JTAlert only opens a such. Is this normal behavior?


Next thing I was to know if this normal behavior is this....Under view I see this. Note "Show Log Fields" is grayed out and can enable show confirmed bands. so..... go to settings from here.

Enable "Show Log Fields".

Then go back to view. Now can enable "Show Confirmed Bands" yet "Show Log Fields" still grayed out.

Now isn't the main JTAlert window suppose to look like this?

And finally on the secondary Windows user eventually get this error.

Any thoughts in how to make this work?

 


locked Re: JTAlert 2.50.1 does not receive from WSJT-X - Callsigns, Activity and Band heat windows don't open

Frode Igland
 

I am sorry for my slow response in a very busy period. I now reply to Laurie's reply in Digest #1460 dated 3 May 2021.

The only thing I did to have v2.50.0 and v2.50.1 installed at the same time, was to install v.2.50.1 in a folder under Program Files, whilst v2.50.0 was installed under Program Files (x86). When opening v2.50.1 I had to select to use  JTAlert with WSJT-X, with JTDX as the alternative. When I first installed v2.50.1, I made a standard installation with default settings, installing it in the Program Files (x86)/Hamapps folder, so the double installation was a very special case just to see if I could notice any differences between the versions, which I didn't.

I followed Laurie's advice to uninstall both versions. All files were deleted by the uninstall, but some folders stuck, so I deleted the remaining folders, as well, leaving no trace of Hamapps or JTALert in the Program Files or the Program Files (x86) folders. The settings under Localappdata were kept. I then made a new installation of JTAlert v2.50.1 with default settings, opened JTAlert v2.50.1,  scanned the logbook to have everything updated. 

The Callsigns window and the Decodes window opened, but regrettably they were just as chaotic as before.

I attach an example with 7 decodes in the WSJT-X Band Activity window, whilst the Callsigns window produced 75 call signs in no particular order, some of which are repetitions from the latest decoded period, whilst others are decoded call signs from random previous periods (identified by different SNR for the same call sign). The Decodes window shows the same lack of order and system, listing old and new decodes in no particlular order.

However, what is listed last in the Callsigns window is listed on the top of the Decodes list, so between the windows the call sign sequence is identical, but it is not linked to the sequence in what has been received form WSJT-X.

The lack of consistency between the latest WSJT-X decodes and JTAlert 2.50.1 makes the Callsigns and Decodes windows useless for selecting calls to work, as the stations.

Everything worked without problems with JTAlert 2.50.0. The problem appeared when I installed v2.50.1, and going back to v2.50.0 did not correct the issue.

The configuration and latest session files have been sent by separate e-mail.

Frode, LA6VQ


locked Re: Log deleted by accident

Tom Melvin
 

Randy

Want to expand further - ‘wont recognise’ is a bit vague - does aclog not recognise it? Wsjt_x?

If it is an adi file and put in correct location it will work (pretty sure eqsl/lotw generate adi files as well)

I suspect one of your steps is wrong or you have named the file wrong - windows has habit of hiding file ext and you may end up with wsjtx_log.adi.txt

Can you try the aclog export again (check contents are OK - use notepad), then let the group know what steps you then use.

Not all is lost

Tom
GM8MJV

On 14 May 2021, at 02:28, randybuckner via groups.io <randybuckner=aol.com@groups.io> wrote:

Tried the ACLog, but it won't recognize the file/


locked Re: Log deleted by accident

Joe - W9RF
 

I accidentally deleted an entire directory and restored it with very little effort.



Choose the:

Restoring files from previous versions


Read the directions fully before starting (always a good idea) and be sure you are in the correct directory..

It's a restore point for files in a directory..


Worked for me...



73,

W9RF - Joe




On Thursday, May 13, 2021, 3:20:50 PM CDT, randybuckner via groups.io <randybuckner@...> wrote:


Senior moment -- wsjt_log.adi is history. Now everything shows up in the band activity window as needed. No worked before. JT Alert still shows worked b4.

I have an adi files of my logbook on QRZ, eQSL, LOTW, as well as my logging program, ACLog. But I can't seem to get any of these logs to work in WSJT.

Any advice, other than I should have backed up my WJST log?


locked Re: Log deleted by accident

randybuckner
 

Tried the ACLog, but it won't recognize the file/


locked Re: Log deleted by accident

randybuckner
 

Not there. :-(


locked Re: JTAlert Autostart

Craig
 

Hello Jim - thanks so much for taking the time to put together the coding and the description of the process.  All works just great making the entire startup process a single click!  

Question, as Launcher takes care of starting and terminating the DXLab applications and other applications that start direct (before or after the DXLab apps), is there a way to have Launcher terminate the apps started using the above process that you put together for me?  Not a big item but would take care of everything at shutdown.  Thanks again Jim.

73, Craig

On Thu, May 13, 2021 at 7:44 PM Jim N6VH <N6VH@...> wrote:


On 5/13/2021 6:06 AM, Craig wrote:
GM.  JTAlert has an internal feature (Under Applications) to auto-start other applications, for example starting WSJTX.exe    I would like to autostart JTAlert from DXLabs Launcher but the URL for JTAlert requires a WSJTX version reference.  The toolbar noted target is:
 "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx but when copied does not work from Launcher.  Pop-up window notes version reference is not present.  Can I get some guidance on this?  Is there a work-around?

73, Craig


locked Re: Log deleted by accident

John VA3BOF
 

If you are using MS Windows or MacOS the file may still be in your deleted folder. Did you look in there? The files in the directory will delete from the deleted when space is need or about 30 days.

Regards,
Johnny’s


locked Re: Log deleted by accident

Dave Garber
 

if you export the ft8/ft4 entries from aclog, to an ADI file.  I think you can copy that adi file into the correct folder.     did you do a new install?  perhaps there are more than one directory, and you are currently in the wrong ( new ) one , not your old one..

just a thought

Dave Garber
VE3WEJ / VE3IE


On Thu, May 13, 2021 at 4:20 PM randybuckner via groups.io <randybuckner=aol.com@groups.io> wrote:
Senior moment -- wsjt_log.adi is history. Now everything shows up in the band activity window as needed. No worked before. JT Alert still shows worked b4.

I have an adi files of my logbook on QRZ, eQSL, LOTW, as well as my logging program, ACLog. But I can't seem to get any of these logs to work in WSJT.

Any advice, other than I should have backed up my WJST log?


locked Re: JTAlert Autostart

Jim N6VH
 

On 5/13/2021 4:44 PM, Jim N6VH wrote:

Craig,

Copy and paste the following into a text editor (Notepad, for example).

@ECHO OFF
CD C:\Program Files (x86)\HamApps\JTAlert
START JTAlert.exe /wsjtx
EXIT

Then save it as a .bat file. Name it something like Run JTAlert.bat. Make certain it as saved as a .bat file, not .txt. Then, in DXLab Launcher, in the Config section, in the "Apps Started Before" or "Apps Started After DXLabs Apps" (whichever works for you), point the program path to that bat file and click enable. In the DXLab Apps tab, make sure that you only have the DXLab Apps enabled that you want to start. Then, in the DXLab Launcher main screen, click the Start button. That should run JTAlert, as well as the DXLab apps you have enabled. See if this works for you.

73,

Jim N6VH
Craig,

Even though it is probably obvious, I should have added that the second line needs to be pointed to wherever the JTAlert exe file is. In my case, it is in the location I show above. I do know, however, that some do have it installed elsewhere.

73,

Jim N6VH


locked Re: JTAlert Autostart

Jim N6VH
 


On 5/13/2021 6:06 AM, Craig wrote:
GM.  JTAlert has an internal feature (Under Applications) to auto-start other applications, for example starting WSJTX.exe    I would like to autostart JTAlert from DXLabs Launcher but the URL for JTAlert requires a WSJTX version reference.  The toolbar noted target is:
 "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx but when copied does not work from Launcher.  Pop-up window notes version reference is not present.  Can I get some guidance on this?  Is there a work-around?

73, Craig
_._,_._,_


Craig,

Copy and paste the following into a text editor (Notepad, for example).

@ECHO OFF
CD C:\Program Files (x86)\HamApps\JTAlert
START JTAlert.exe /wsjtx
EXIT

Then save it as a .bat file. Name it something like Run JTAlert.bat. Make certain it as saved as a .bat file, not .txt. Then, in DXLab Launcher, in the Config section, in the "Apps Started Before" or "Apps Started After DXLabs Apps" (whichever works for you), point the program path to that bat file and click enable. In the DXLab Apps tab, make sure that you only have the DXLab Apps enabled that you want to start. Then, in the DXLab Launcher main screen, click the Start button. That should run JTAlert, as well as the DXLab apps you have enabled. See if this works for you.

73,

Jim N6VH



locked Log deleted by accident

randybuckner
 

Senior moment -- wsjt_log.adi is history. Now everything shows up in the band activity window as needed. No worked before. JT Alert still shows worked b4.

I have an adi files of my logbook on QRZ, eQSL, LOTW, as well as my logging program, ACLog. But I can't seem to get any of these logs to work in WSJT.

Any advice, other than I should have backed up my WJST log?


locked Re: automatic start of JTDX #JTDX

Roger- AC6BW
 

I also use Win4Yaesu.
I autostart HRD Logbook, but I don't autostart WSJT-X (or JTDX), nor JTAlert.
Do the programs get autostarted in the same sequence as shown in the list? Is there a delay between each of the autostarts?
I ask, because the logging program must be started before WSJT-X (or JTDX), and WSJT-X (or JTDX) must be started before JTAlert.

This may be a good question for Tom, VA2FSQ, the developer of Win4Yaesu.
He is very responsive.
His email is: support at va2fsq.com
--
73,
Roger
AC6BW

2081 - 2100 of 36903