Date   

locked 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


locked 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


locked 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/


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

Pete Ritter K5CPR
 

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. 


locked 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


locked 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.


locked 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


locked 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


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

WU9D <mike@...>
 

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


locked 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


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

HamApps Support (VK3AMA)
 

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


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

WU9D <mike@...>
 

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.


locked Re: callsign window in black modus #TIP

peter nn
 

Thanks... That will serve well 73 Peter. PC1Y 


locked Re: Missing dll file on install #HamSpots #FT8 #JTDX

Ron Schunk
 

HI..thanks for the tip... I went out and downloaded the C++ and got a good install (I think), but I'm still getting the error message...the download file was
vc-redist(x64) 14.0.24123 ...reloaded the C++ and also reloaded JTAlert....still no joy in W8 land...
Ron 
WA8KQF


locked Bug report

Steve Weeks AA8SW
 

The LoTW Last Upload Filtering function is not working properly.  I have it set at 1 year with the flag turned on.

Today the software flagged N1UL as an LoTW member, which should have meant that he had uploaded within the last year.  However, when I called him, AC Log showed that his last upload was in 2015.  Of course I had to finish the contact to avoid being rude, even though it is unlikely that he will ever confirm so it was probably wasted time and QRM.  Later I went to the LoTW website to confirm that AC Log was correct and the last upload by that callsign was in fact in 2015.  His QRZ page says that he does not use LoTW.

I have noticed the same thing in prior versions of the software but decided to report it this time since it was not fixed in 2.50 -- which is otherwise great.  Thank you for the considerable effort that must have been needed to make those major changes.

73, Steve AA8SW


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

Stewart Wilkinson
 

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.


locked Re: .NET5 issues

Phil Cooper
 

Hi Laurie,

Last night I just installed JTAlert 2.50.0 but didn't actually try it, as I had been out at our club, and consumed a glass (or two!) of a nice Merlot, so I didn't want to have to think too much, so I left it.
Got up this morning, itching to see if it all worked....

And YES, everything seems to work just fine! I even went on 30m to ensure contacts were logged OK, and they were. Made a few QSO's with the new version, all EU, with reports around the -09 to -12 region, which were logged into DXKeeper just fine. Just as I was about to close JTAlert, I was called by a VK3 with a report of +12!!!

So, a big thankyou to you for this new version....

I cannot work out why FrameworkCheck was telling me .NET5 was not installed, but hey ho, some things are sent to confuse us!

Very best 73

Phil GU0SUP


locked Re: callsign window in black modus #TIP

Laurie, VK3AMA
 



On 24/04/2021 2:51 pm, Peter van IJperen wrote:
Love the new version 2.50 but I loved it more as the callsign window can be set in a black mode....this gives more contrast.....  is this possible in next release?

73 Peter PC1Y

While not offering a single "Dark Mode" setting, the next release has color customization of the major UI elements of each of the new 2.50.0 windows.

Here's a sample of my Callsigns window.

   

de Laurie VK3AMA


locked callsign window in black modus #TIP

Peter van IJperen
 

Love the new version 2.50 but I loved it more as the callsign window can be set in a black mode....this gives more contrast.....  is this possible in next release?

73 Peter PC1Y


locked Re: Call Signs Window-Version 2.50 – How Do You Make the Font Bigger so I Can See It on My Notebook?

Robert K3RRR
 

Got it, Laurie… This is great! Thanks for all you do, my friend… You definitely add SIGNIFICANTLY to the ham radio hobby…
 
 -.- ...-- .-. .-. .-.
73 de Robert   K3RRR
Twitter:    @K3TripleR
YouTube.com/K3RRR
Website: K3RRR.com
-.- ...-- .-. .-. .-.   

2481 - 2500 of 36897