Date   

Re: Missing .dll file #FT8 #JTDX #TIP

HamApps Support (VK3AMA)
 

On 26/04/2021 3:00 am, Ron Schunk wrote:
Been having problems getting JTAlert to work with JTDX....got that message about the missing .dll file api-ms-win-crt-runtime-l1-1-0.dll ....reloaded JTAlert after downloading and installing the C++ MS file and .NET 5.0 Runtime as suggested...still didn't work, so I went out and did a duckduckgo.com search and found a page that directed me to Microsoft for a download of Windows 8.1 KB2999226-x64 (using Windows 8.1 64 bit op sys)...installed that and rebooted and everything is working fine now...
Thanks for all the suggestions..
Ron
WA8KQF

Thanks for the tip.

de Laurie VK3AMA


Re: JTAlert 2.50

Laurie, VK3AMA
 



On 26/04/2021 2:44 am, WD8AJD wrote:

Which user’s group can tell me the meaning of the little black corners on the “license plate” call sign displays, as well as the meaning of the little star on the upper left corner of some of the calls?

 

Respectfully,

John Crist – WD8AJD


Bottom-Left = Lotw member
Bottom-Right = Eqsl (AG) member
Star = Callsign has JTAlert Text Messaging enabled.

de Laurie VK3AMA


Re: Seeking help

Laurie, VK3AMA
 

On 26/04/2021 12:57 am, deni wrote:
I have jtalert 2.5.0 working very smoothly with wsjtx and I love it. Especially, the one click to transmit from the callsign panel. Unfortunately this is not the case with JTDX.  All of the icons seem to appear correctly but clicking on any of them provides no response from jtdx.  I might also add that hovering over a callsign window does provide the correct information.  Am I missing some change I need to make when chaining back and forth from wsjtx amd jtdx?
Thanks to all.
73 - deni
WBØTAX
If JTDX is not responding to clicks in JTAlert it will be due to settings within jtdx.

The "Accept UDP requests" setting, jtdx Settings window reporting Tab, needs to be ticked.
Also check the the "Misc -> Accept UDP Reply Messages" menu of the main jtdx window and ensure it is set to the type of decodes you want to have respond to the click event.

de Laurie VK3AMA


Re: FT4 Logging

Laurie, VK3AMA
 



On 25/04/2021 10:42 pm, Ed Wilson via groups.io wrote:
I have been using JTAlert and the old HRD v 5.24 for many years. When FT4 was introduced, I was able to get contacts with this mode show up as FT4 in my log although I realize that by definition, FT4 is actually a sub mode of MFSK. After upgrading to JTAlert 2.50.0, FT4 contacts now are logged as MFSK. It appears that contacts are uploaded and are displayed as FT4 by LOTW and HRDLog. eQSL displays them as MFSK (FT8). Currently I am manually changing MFSK to FT4 in my log but would like them to automatically appear as FT4 as previously if possible.

Any ideas would be appreciated!

Ed, K0KC

Do you have the "Log FT4 as ADIF 3.1.0 ..." setting ticked? If so, that's the cause. It needs to be unticked. Visit the "Logging" section of the Settings window of the main JTAlert window. Scroll the options to bring the checkbox into view.

   

de Laurie VK3AMA


JTAlert 2.50

WD8AJD
 

Which user’s group can tell me the meaning of the little black corners on the “license plate” call sign displays, as well as the meaning of the little star on the upper left corner of some of the calls?

 

Respectfully,

John Crist – WD8AJD

 

Sent from Mail for Windows 10

 


Missing .dll file #FT8 #JTDX #TIP

Ron Schunk
 

Been having problems getting JTAlert to work with JTDX....got that message about the missing .dll file api-ms-win-crt-runtime-l1-1-0.dll ....reloaded JTAlert after downloading and installing the C++ MS file and .NET 5.0 Runtime as suggested...still didn't work, so I went out and did a duckduckgo.com search and found a page that directed me to Microsoft for a download of Windows 8.1 KB2999226-x64 (using Windows 8.1 64 bit op sys)...installed that and rebooted and everything is working fine now...
Thanks for all the suggestions..
Ron
WA8KQF


Re: 2.50.0 (64 bit) appears to stop WSJT-X Auto Seq

Stewart Wilkinson
 

Pete,
I use a desktop PC with a USB Mouse, so it is not that.

I was almost convinced that 2.50.0 was causing it and went back to 2.16.17 but I will try 2.50.0 again.


Allow filter overrides for needed DX, states, etc. #FT8

Pat N6PAT
 

I'm using the JTAlert filters for NA and eQSL so I don't expect DX call signs to appear in the call sign window. However I am still getting the wanted DX audio alerts but the DX call sign in WSJT-X window in not being assigned the specified wanted DX color . I'm not sure if this is by design or accident but I do like still getting wanted DX alerts even when I filter the call sign window for NA only.

So I'd like to suggest that the filter feature be modified to have override options that the op could select to allow continued audio and visual alerts for wanted DX, States, etc. even when they are not included in a given filter.  I don't want to miss a needed DX just because I have the filter set for NA while I'm county hunting. This would allow me to still limit listed calls to just NA except when a needed station is spotted.


Seeking help

deni
 

Hi Everyone,
I have jtalert 2.5.0 working very smoothly with wsjtx and I love it.  Especially, the one click to transmit from the callsign panel. Unfortunately this is not the case with JTDX.  All of the icons seem to appear correctly but clicking on any of them provides no response from jtdx.  I might also add that hovering over a callsign window does provide the correct information.  Am I missing some change I need to make when chaining back and forth from wsjtx amd jtdx?
Thanks to all.
73 - deni
WBØTAX


Re: FT4 Logging

Joe Subich, W4TV
 

On 2021-04-25 8:42 AM, Ed Wilson via groups.io wrote:
Currently I am manually changing MFSK to FT4 in my log but would like
them to automatically appear as FT4 as previously if possible.
That is no longer possible. See the Release notes on 2.50.0 Build 0004

- FT4 logging: The option to log FT4 QSOs as Mode=FT4 rather than the adif compliant specification has been removed. This affects
all Logs except ACLog.
- FT4, Q65 & FST4 logging: FT4, Q65, & FST4 mode QSOs are now logged using the official adif specifications (3.1.2) of
Mode=MFSK & Submode=Q65, FST4 & FT4 respecitvely.
Laurie would need to write special code to support HRD V5/6.2 which are
long out of date and no longer supported by the developers of that
software.

73,

... Joe, W4TV


On 2021-04-25 8:42 AM, Ed Wilson via groups.io wrote:
I have been using JTAlert and the old HRD v 5.24 for many years. When FT4 was introduced, I was able to get contacts with this mode show up as FT4 in my log although I realize that by definition, FT4 is actually a sub mode of MFSK. After upgrading to JTAlert 2.50.0, FT4 contacts now are logged as MFSK. It appears that contacts are uploaded and are displayed as FT4 by LOTW and HRDLog. eQSL displays them as MFSK (FT8). Currently I am manually changing MFSK to FT4 in my log but would like them to automatically appear as FT4 as previously if possible.
Any ideas would be appreciated!
Ed, K0KC
k0kc@arrl.net
http://k0kc.us/


Re: FT4 Logging

Paul F6EXV
 

FT4 must be logged as mode MFSK and submode FT4
73

Le 25/04/2021 à 15:44, Ed Wilson via groups.io a écrit :
I should have mentioned that I have only tested for this issue with JTDX, if that makes any difference.

Ed, K0KC


Garanti sans virus. www.avast.com


Re: FT4 Logging

Ed Wilson
 

I should have mentioned that I have only tested for this issue with JTDX, if that makes any difference.

Ed, K0KC


FT4 Logging

Ed Wilson
 

I have been using JTAlert and the old HRD v 5.24 for many years. When FT4 was introduced, I was able to get contacts with this mode show up as FT4 in my log although I realize that by definition, FT4 is actually a sub mode of MFSK. After upgrading to JTAlert 2.50.0, FT4 contacts now are logged as MFSK. It appears that contacts are uploaded and are displayed as FT4 by LOTW and HRDLog. eQSL displays them as MFSK (FT8). Currently I am manually changing MFSK to FT4 in my log but would like them to automatically appear as FT4 as previously if possible.

Any ideas would be appreciated!

Ed, K0KC

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


Re: 2.50.0 (64 bit) appears to stop WSJT-X Auto Seq

Pete Ritter
 

I have noticed that unless I am careful when I drag my finger across my notebook computer's touch pad to position the pointer, occassionly "Enable Tx", "Hold Tx Freq", etc change state.  I'm sure it's because I inadvertently put too much pressure on the pad at just the right (wrong) place.  I wonder if this might be the cause of the mysterious behavior you report. There is a touchpad sensitivity setting in Settings->Touchpad. 


2.5.00 Error in combination with HRDLog.net and HRDLog

Stefan Braun
 
Edited

I am running HamRadioDeluxe Logbook connected to HRDLog.net.
All was fine with JTAlert 2.1.6.17 .
QSOs where logged in HRD Logbook and also in HRDLog.net . There where no doublle loggings.

After installing the new version  logging on HRDLog.net appears always with 2 same records.
In the HRD Logbook it seems to be all ok.
After downgrading all is fine again.
Looks to me there is abug in the new version. 2.5.0.0
Installed Software:
HRD 6.7.0.323
JTDX V 2.2.0-rc155
JTAlert (now back to 2.1.6.17)

73 de Stefan HB9GFX


Re: 2.50.0 (64 bit) appears to stop WSJT-X Auto Seq

Stewart Wilkinson
 

I don't think the TX Watchdog had run out. 

I will have to check a bit more closely if it happens again.


Mouse Pointer jumping to top left corner of Window when JTAlert is focus window

KT7AZ
 

I use a small GPD brand Windows 10 PC for doing QRP work in the field.  To view the selected screens a little better I use the Magnifier feature in native Windows (Windows Key and Plus sign) to activate.

I have found a peculiar problem that occurs when the JTAlert App window is selected.  The mouse cursor will jump to top left of Windows monitor and then when trying to move it back to any other position it move a little and jumps right back to top left corner of monitor.

I have found a fix for this.  Go to the small app window that will appear when Magnifier mode is enabled, choose the Gear to go to the settings, scroll down to the "Have Magnifier follow:" section and check Mouse pointer, and uncheck the Keyboard focus, Text cursor and Narrator cursor.

This seems to do the trick.

Gary
--
KT7AZ


Re: 2.50.0 (64 bit) appears to stop WSJT-X Auto Seq

Jim N6VH
 


On 4/24/2021 11:57 AM, HamApps Support (VK3AMA) wrote:
On 24/04/2021 10:20 pm, Stewart Wilkinson via groups.io wrote:
I have noticed (twice) whilst JTALeryt 2.50.0 was ruuning and I was calling CQ on 6m FT8 (with Auto-Sqe and Call 1st enabeld) that WSJT-X 2.3.1 failed to answer someone that answered my CQ call in fact it stopped calling - 'Enable Tx' in WSJT-X became disabled. I stopped JTAlert then allowed WSJT-X to call CQ again and WSJT-X worked normally.

JTAlert can not affect the "Enable Tx" setting in WSJT-X. There is no facility to perform that action in the WSJT-X UDP interface which JTAlert uses exclusively to interact with WSJT-X.

If "Enable Tx" is becoming unchecked, it is likely to how you're using WSJT-X. You're best to ask the WSJT-X people why "Enable Tx" is becoming unchecked.

de Laurie VK3AMA

_._,_._,_


Just a thought here. It is possible that the TX watchdog timer in WSJT-X had expired just at the time that the other station answered the CQ. Just one possibility.

73,

Jim N6VH


Re: JTAlert cannot log to a HRD Access logbook unless it is open

WU9D
 

Thank you for clarifying Laurie. I was running HRD in conjunction with WSJT-X and JTAlert before, so the logbook was open. No problem, all I must do is run the logbook on its own. It complains about not having the HRD server running but I can ignore that.

 

73,

Mike WU9D

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA) via groups.io
Sent: Saturday, April 24, 2021 1:53 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert cannot log to a HRD Access logbook unless it is open

 

On 25/04/2021 1:58 am, WU9D wrote:

I keep getting error messages when trying to log to my HRD logbook. If the logging program is open then I can log to the Access database. But not if the logbook program is closed.

 

I haven’t had this problem before but I do now for some reason. I checked all the parameters and they are correct according to a previous post regarding the matter. I’m guessing the fix is something easy but I can’t find it.

 

I don’t have the error message so don’t ask for it. The version of the HRD Logbook is the current 6.7.0.323.


HRDLogbook needs to be running. This is highlighted in the Help file. It has always been the case, it is not new.

Logging is done via the TCP interface of HRDLogbook, if HRDLogbook is not running there is nothing listening on the TCP port to accept the logging instruction. The only exception is with HRD5 & HRD6.2 (and earlier) where logging is done via direct writes to the log database file as there is no TCP interface available with those very old versions.

de Laurie VK3AMA


Re: 2.50.0 (64 bit) appears to stop WSJT-X Auto Seq

HamApps Support (VK3AMA)
 

On 24/04/2021 10:20 pm, Stewart Wilkinson via groups.io wrote:
I have noticed (twice) whilst JTALeryt 2.50.0 was ruuning and I was calling CQ on 6m FT8 (with Auto-Sqe and Call 1st enabeld) that WSJT-X 2.3.1 failed to answer someone that answered my CQ call in fact it stopped calling - 'Enable Tx' in WSJT-X became disabled. I stopped JTAlert then allowed WSJT-X to call CQ again and WSJT-X worked normally.

JTAlert can not affect the "Enable Tx" setting in WSJT-X. There is no facility to perform that action in the WSJT-X UDP interface which JTAlert uses exclusively to interact with WSJT-X.

If "Enable Tx" is becoming unchecked, it is likely to how you're using WSJT-X. You're best to ask the WSJT-X people why "Enable Tx" is becoming unchecked.

de Laurie VK3AMA

441 - 460 of 34867