Date   

locked Re: [HapMap's] Application Auto-Start Issue

Wyndell - K5WJF
 

Ji/\m thanks!  Its  been a long time since I messed wit .bat files.  Forgot about echo!

 

Wyndell

Resistance is NOT futile, it's Voltage divided by Current

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jim N6VH
Sent: Sunday, March 7, 2021 16:13
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Application Auto-Start Issue

 

 

On 3/5/2021 3:50 PM, HamApps Support (VK3AMA) wrote:

On 6/03/2021 10:25 am, Jim N6VH wrote:

As an experiment, I tested my suggested method, and it doesn't work. I can point Win4Yaesu to the desired JTAlert shortcut, but Win4Yaesu then points to the location listed in the shortcut, instead of running the shortcut itself. Wyndell will need to use another method to do what he wants.

73,

Jim N6VH


RRR.

The easiest option to overcome deficiencies in these applications that don't support command-line parameters for starting other applications is to simply put the command that needs a param into a batch file and have the batch file started.

de Laurie VK3AMA
 

Laurie,

I wrote a very basic batch file that might help Wyndell. It has been a long time since I have worked with batch files, so it might not be perfect. It does work, however.

Wyndell, open Notepad. Then copy the following statements, and paste them into Notepad. Then save this as a .bat file. I called it Start JTAlet.bat.

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

It might be necessary to change the file location in the second line, depending on where JTAlert is installed. If you want to use JTDX instead, just change wsjtx in the third line to jtdx.

Then setup Win4Icom like this (see attached picture). Once again, change the location to wherever you saved the batch file.

Next, set JTAlert like this (see attached picture).

As I said, you might need to make adjustments to file locations, etc. This works on my computer. I hope it works for you.

Incidentally, I normally use Log4OM, but I did the test with AC Log since that was the log mentioned in the original post.

73,

Jim N6VH




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: WSJT-X Auto-Starts Later Than ACLog

Michael Black
 

Can you show a snapshot or your startup settings?

Mike W9MDB




On Monday, March 8, 2021, 10:08:48 AM CST, Patrick Hung <pathung@...> wrote:


Hi All,

I had described my problem of setting both WSJT-X and ACLog to auto-start (in this sequence) in another thread, but the subject had meandered there, so I'm starting a new thread here.

It was suggested that I lengthen the time (in milliseconds) for post-WSJT-X start, so that ACLog wouldn't start up before WSJT-X (and seemingly take the rig-communications port away from WSJT-X, causing WSJT-X's start to fail). 

I lengthened the time lapse to 6000 ms, and the results are as follow: upon first attempt, the process fails, as ACLog immediately launches after I click the JTAlert shortcut; WSJT-X takes its sweet time to start, and fails to connect to the rig (ACLog already hogs the port?). I close JTAlert (WSJT-X and ACLog also close as they are set to auto-close). I then try it again, and bingo, WSJT-X launches immediately, takes command of the rig, followed by the proper ACLog launch, and everything works.

This "second time's a charm" situation was my main problem prior to making the change to 6000 ms. 

Any thoughts/comments, anybody? Thanks.
--
73,

Patrick - W6AJR


locked WSJT-X Auto-Starts Later Than ACLog

Patrick Hung
 

Hi All,

I had described my problem of setting both WSJT-X and ACLog to auto-start (in this sequence) in another thread, but the subject had meandered there, so I'm starting a new thread here.

It was suggested that I lengthen the time (in milliseconds) for post-WSJT-X start, so that ACLog wouldn't start up before WSJT-X (and seemingly take the rig-communications port away from WSJT-X, causing WSJT-X's start to fail). 

I lengthened the time lapse to 6000 ms, and the results are as follow: upon first attempt, the process fails, as ACLog immediately launches after I click the JTAlert shortcut; WSJT-X takes its sweet time to start, and fails to connect to the rig (ACLog already hogs the port?). I close JTAlert (WSJT-X and ACLog also close as they are set to auto-close). I then try it again, and bingo, WSJT-X launches immediately, takes command of the rig, followed by the proper ACLog launch, and everything works.

This "second time's a charm" situation was my main problem prior to making the change to 6000 ms. 

Any thoughts/comments, anybody? Thanks.
--
73,

Patrick - W6AJR


locked Re: Worked B4 issue

Joe
 

Does anyone know if Laurie is okay?  I haven't heard a word in response since I sent the files he requested?

Joe/WQ6Q


locked Re: Application Auto-Start Issue

Jim N6VH
 


On 3/5/2021 3:50 PM, HamApps Support (VK3AMA) wrote:
On 6/03/2021 10:25 am, Jim N6VH wrote:

As an experiment, I tested my suggested method, and it doesn't work. I can point Win4Yaesu to the desired JTAlert shortcut, but Win4Yaesu then points to the location listed in the shortcut, instead of running the shortcut itself. Wyndell will need to use another method to do what he wants.

73,

Jim N6VH


RRR.

The easiest option to overcome deficiencies in these applications that don't support command-line parameters for starting other applications is to simply put the command that needs a param into a batch file and have the batch file started.

de Laurie VK3AMA
 

Laurie,

I wrote a very basic batch file that might help Wyndell. It has been a long time since I have worked with batch files, so it might not be perfect. It does work, however.

Wyndell, open Notepad. Then copy the following statements, and paste them into Notepad. Then save this as a .bat file. I called it Start JTAlet.bat.

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

It might be necessary to change the file location in the second line, depending on where JTAlert is installed. If you want to use JTDX instead, just change wsjtx in the third line to jtdx.

Then setup Win4Icom like this (see attached picture). Once again, change the location to wherever you saved the batch file.

Next, set JTAlert like this (see attached picture).

As I said, you might need to make adjustments to file locations, etc. This works on my computer. I hope it works for you.

Incidentally, I normally use Log4OM, but I did the test with AC Log since that was the log mentioned in the original post.

73,

Jim N6VH


locked Re: keep logging to HRD / #FT8

Laurie, VK3AMA
 

On 7/03/2021 7:19 am, Michael Black via groups.io wrote:
Maybe a check to ensure they aren't the same in the code?

Mike W9MDB
Already coded. The resend now gets disabled if the detected WSJT-X UDP Server port matches the resend port.

de Laurie VK3AMA


locked Re: keep logging to HRD / #FT8

Michael Black
 

Maybe a check to ensure they aren't the same in the code?

Mike W9MDB




On Saturday, March 6, 2021, 12:55:17 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 7/03/2021 5:34 am, Michael Black via groups.io wrote:
> Make sure you don't have the "Resend" option checked in JTAlert
>
> Mike W9MDB

To be clear, fundamentally having the Resend option enabled is not the
problem, but having it enabled and set to use the same UDP port as set
in WSJT-X (UDP Server) is the true problem.

There have been a number of this specific configuration problem (JTAlert
resend port set to match WSJT-X UDP port) in recent weeks. I suspect
this misinformation is being propagated on a Forum/User group somewhere
or perhaps a tutorial video.

de Laurie VK3AMA







locked Re: keep logging to HRD / #FT8

Lawrence AB6OJ
 

Thank you.
I did follow Michael, it works.
also followed HamApps support, It works too.
I appreciate.


locked Re: keep logging to HRD / #FT8

HamApps Support (VK3AMA)
 

On 7/03/2021 5:34 am, Michael Black via groups.io wrote:
Make sure you don't have the "Resend" option checked in JTAlert

Mike W9MDB
To be clear, fundamentally having the Resend option enabled is not the problem, but having it enabled and set to use the same UDP port as set in WSJT-X (UDP Server) is the true problem.

There have been a number of this specific configuration problem (JTAlert resend port set to match WSJT-X UDP port) in recent weeks. I suspect this misinformation is being propagated on a Forum/User group somewhere or perhaps a tutorial video.

de Laurie VK3AMA


locked Re: keep logging to HRD / #FT8

Michael Black
 

Make sure you don't have the "Resend" option checked in JTAlert

Inline image


Mike W9MDB

On Saturday, March 6, 2021, 12:31:57 PM CST, Lawrence AB6OJ <ab6ojll0365@...> wrote:


I installed 2.16.17.
This keep logging to HRD.
Pop up windows keep repeating.
I hade to terminate JT-alert and delete so many duplicatyed log from HRD Log.


locked keep logging to HRD / #FT8

Lawrence AB6OJ
 

I installed 2.16.17.
This keep logging to HRD.
Pop up windows keep repeating.
I hade to terminate JT-alert and delete so many duplicatyed log from HRD Log.


locked Re: Highlighting wanted dxcc in decodes (not only cq)?

Daniel <dko1@...>
 

Hi Laurie,

thanks for your hint. I have just run a "Rebuild Alert Database" and now all DXCC are in the wanted box!
Obviously there is no synchronisation with the "worked DXCC" database

I have "Standard ADIF Fille logging" enabled (not the WSJT-x path).
When I open die ADIF file with the W10 editor, I can see that all QSOs are logged.



Daniel


locked Re: Application Auto-Start Issue

HamApps Support (VK3AMA)
 

On 6/03/2021 10:25 am, Jim N6VH wrote:

As an experiment, I tested my suggested method, and it doesn't work. I can point Win4Yaesu to the desired JTAlert shortcut, but Win4Yaesu then points to the location listed in the shortcut, instead of running the shortcut itself. Wyndell will need to use another method to do what he wants.

73,

Jim N6VH


RRR.

The easiest option to overcome deficiencies in these applications that don't support command-line parameters for starting other applications is to simply put the command that needs a param into a batch file and have the batch file started.

de Laurie VK3AMA
 


locked Re: JTAlert makes PC slow

Laurie, VK3AMA
 

On 3/03/2021 3:26 pm, K0GU wrote:
I've been working on this a lot tonight, reading old posts, etc and I don't quite get it.

I'm running three instances of JTDX rc-155 (153 before that, etc). With each instance of JTAlert I start the typing into the PC gets slower and I think my FT8 decodes get slower. If I have only one instance of JTAlert running I can type character into W10 Notepad fairly smoothly but by the time I'm running three instances of JTAlert typing gets about five seconds behind. I first noticed this when typing messages into the Text Message Window.

I have some delay in my SDR/SDR program so I always use AutoSeq3 so I can have late decoding. But the delay has gotten pretty bad and is running two or more seconds into the xmit sequence. I have a fast computer and the load with three instances of JTDX/JTAlert only uses about 30% of the CPU and 50% if I turn SWL mode on to all JTDXs (I'm listening to dead bands ATM 6m &10m). So to me it doesn't seem to be a resource issue.

I'm guessing I don't have something setup quite right when it comes to JTDX/JTAlert communication and that is causing the delay??? Can someone post what my settings should look like please??? All three instances are working (displaying calls properly). BTW I have no logging program hooked up at all. I'm just using the stand along features in JTDX.

73,  Jay  K0GU
Try disabling hotkey support in JTAlert. A small number of users have experienced performance issues when hotkeys are enabled.
I believe it is tied to the 3rd party hotkey library used by JTAlert in conjunction with something else running on the users PC (what that is is unknown).

Settings Window -> "Miscellaneous -> Hot Keys" section, unckeck the "Enable all hotkeys" checkbox then restart JTAlert.

Let me know if this solves your problem.

de Laurie VK3AMA


locked Re: Highlighting wanted dxcc in decodes (not only cq)?

HamApps Support (VK3AMA)
 

On 6/03/2021 1:29 am, Daniel wrote:
However, there is a message saying "0 of 340 DXCC entities wanted", which I find strange.

That's your problem. The Alert database has no dxcc's set as needed. JTAlert thinks you have worked them all so there is nothing to alert/highlight.

It would appear that you have never run the
"Rebuild Alert Database". You have to periodically do this in order to have the database updated with your recent QSL confirmations in your log to remove entities from the database that are no longer needed. You only need to run the rebuild if you have updated your log with new QSL confirmations (eg. Card, Eqsl or Lotw).

de Laurie VK3AMA


locked Re: Application Auto-Start Issue

Jim N6VH
 


On 3/3/2021 4:28 PM, Jim N6VH wrote:
Laurie,

I use Win4Yaesu, which is probably similar to Win4Icom in this respect. While I don't have it auto-start anything, it looks like it could be set to start the appropriate JTAlert shortcut, which would then start JTAlet, of course. Then, JTAlert could start WSJT-X (or (JTDX). This might work for Wyndell. It might be worth a try for him

73,

Jim N6VH

_._,_._,_

Laurie,

As an experiment, I tested my suggested method, and it doesn't work. I can point Win4Yaesu to the desired JTAlert shortcut, but Win4Yaesu then points to the location listed in the shortcut, instead of running the shortcut itself. Wyndell will need to use another method to do what he wants.

73,

Jim N6VH


locked Re: Setting up GPS USB dongle

vk3fz
 

Yes I do I had to remove the driver in windows then se the com port manually as it was clashing

 

Sent from Mail for Windows 10

 

From: Richard Lawn
Sent: Saturday, 6 March 2021 8:36 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Setting up GPS USB dongle

 

I got a Glonass U-blox7 GPS GPS stick for my Pi 4b. Despite the tutorial I followed on the internet I have been unable to get it to work. For a while it did show a flashing green light on the dongle suggesting it was trying or actually synced to satellites but now there is nothing. the cat /dev/serial0 seems to show nothing. Does anyone use this GPS lock?

Rick, W2JAZ

 


locked Re: Highlighting wanted dxcc in decodes (not only cq)?

Ron W3RJW
 


--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.3.0, JTAlert 2.16.17, HRD Deluxe v6.7
FTdx-3000, SignaLink USB


locked Re: Highlighting wanted dxcc in decodes (not only cq)?

Ron W3RJW
 
Edited

That's exactly how it works ...  In fact that is a big advantage of using JTAlert ...  Check your settings ...




--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.3.0, JTAlert 2.16.17, HRD Deluxe v6.7
FTdx-3000, SignaLink USB


locked Setting up GPS USB dongle

Richard Lawn
 

I got a Glonass U-blox7 GPS GPS stick for my Pi 4b. Despite the tutorial I followed on the internet I have been unable to get it to work. For a while it did show a flashing green light on the dongle suggesting it was trying or actually synced to satellites but now there is nothing. the cat /dev/serial0 seems to show nothing. Does anyone use this GPS lock?

Rick, W2JAZ

4461 - 4480 of 37779