1. Support@HamApps.groups.io
  2. Messages
   Date   
locked Re: Grid not passed correctly from WSJTX-> JTA > DXK #FT8

Jim Cooper
 

On 16 Nov 2021 at 18:22, Rich - K1HTV wrote:

If I understand it correctly, the QSO data is passed from WSJT-X
through JT Alert to the DX Keeper log. If that is the case, is the
incorrect grid being introduced by JTAlert?
Do you have the JTalert DECODES window open?
If so, what grid does it show there for the /MM ?

That is most likely what JTalert will send for the log ...
if it is EMPTY, then that might explain why an old
grid is being found and used.

From what I have seen operating, most /MM FT8 stations
do not send their current grid square very often, if at all.

Just some thoughts ...

w2jc
locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

Jim Cooper
 

On 16 Nov 2021 at 16:11, A. Mark Gillespie (VK3BU) wrote:

1. I've only just returned to the
hobby and I am still in the process of
setting things up so the only
logging that I'm doing is in WSJT-X
and then up loading that .ADI file
to QRZ.COM.
Mark ... you're doing that the HARD WAY!!

I also use the QRZ logbook and LotW ... but
I use JTalert to upload my QSOs as they are
made DIRECTLY to QRZ.com (you do need to
have the QRZ XML subscription). It is super
simple and super easy.

Then at the end of the day, three mouse clicks
in QRZ logbook and all my new entries are sent
up to LotW magically !!

Jim w2jc
locked Grid not passed correctly from WSJTX-> JTA > DXK #FT8

Rich - K1HTV
 

In the past, when I completed an FT8 QSO with a /MM maritime mobile station in a new water grid, the grid in the WSJT-X "DX Grid" field was entered in the llog box which opened after the 73 message was received. The grid along with the rest of the QSO data was passed through JTAlert to DX Keeper and logged. However, I have noticed that after a QSO is logged, the Grid logged in DX Keeper for that QSO is a grid from an older QSO. I can't seem to find any option or checkbox in either WSJT-X, JT Alert or DX Keeper which might be related to correcting this problem.
 
I wrote to DX Lab Suite and Dave, AA6YQ suggested doing some diagnostics. I sent him the error log file with the results. It indicated that the incorrect grid was being sent to DX Keeper and not the grid that was in the WSJT-X log box. I checked the wsjtx.log file and it had the correct grid that was in the WSJT-X log box which came up after the QSO.
 
If I understand it correctly, the QSO data is passed from WSJT-X through JT Alert to the DX Keeper log. If that is the case, is the incorrect grid being introduced by JTAlert?
 
73,
Rich - K1HTV
locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

A. Mark Gillespie (VK3BU)
 

Hi Laurie,
1. I've only just returned to the hobby and I am still in the process of setting things up so the only logging that I'm doing is in WSJT-X and then up loading that .ADI file to QRZ.COM.
I followed the procedure in JTAlert for the initial once only import of the WSJT-X .ADI file into JTAlert. JTAlert seems to know about all my worked B4 contacts as I make them, they just aren't identified ONLY in the "Show QSO's History Popup". All my worked B4 stations have a grey background in WSJT-X and a grey box in JTAlert as I make them. The worked B4 identification is working perfectly to identify all stations as worked before, it's just the details of the previous conversations aren't included in the "Show QSO's History Popup".
2.With the setup described above, do I need to set up an additional log file somewhere?
3. I turned off Malwarebytes and Norton and it made no difference.
4. I can confirm that there are two 3D2USU entries in the WSJT-X .ADI log. The logging of new contacts into JTAlet seems to be working fine since the do get a grey background. This problem is happening with all my worked B4 contacts.
Thanks for your comments.
Cheers, Mark VK3BU
locked Re: Text in DX window

Jim Cooper
 

On 16 Nov 2021 at 14:15, Bob wrote:

now here is the dilemma my call isnTMt showing in
the window no text¦????
what window? always good idea to include a
screen shot of what you are talking about so
folks here don't have to guess, or ask a bunch
of questions to get the details.
locked Re: Text in DX window

Dave Garber
 

rx window?  in wsjt?     what version jtalert and wsjtx ( or jtdx) are you using

Dave Garber
VE3WEJ / VE3IE


On Tue, Nov 16, 2021 at 9:15 AM Bob <bobl4655@...> wrote:

 

First let me say I love JT alert . That being said. I have problem in RX frequency window. I call cq all meters say I’m putting signal out. Even get response , now here is the dilemma my call isn’t showing in the window no text…???? If you need more info please contact me I have audio that signal is going out but no text in window I read and read and didn’t find any info, one said needed to allow dx activity ticked that box nuffin, I am at a loss  kb1yxn thanking you in advance

Sent from Mail for Windows

 
locked Re: error message that randomly appears

Roger A. Corbin
 

I will watch to see when this problem next occurs and let you know. 
Roger ZF1RC
locked Text in DX window

Bob
 

 

First let me say I love JT alert . That being said. I have problem in RX frequency window. I call cq all meters say I’m putting signal out. Even get response , now here is the dilemma my call isn’t showing in the window no text…???? If you need more info please contact me I have audio that signal is going out but no text in window I read and read and didn’t find any info, one said needed to allow dx activity ticked that box nuffin, I am at a loss  kb1yxn thanking you in advance

Sent from Mail for Windows

 
locked Re: error message that randomly appears

JTAlert Support (VK3AMA)
 

On 16/11/2021 1:22 pm, Roger A. Corbin wrote:
I have noticed that from time to time the attached message appears on the screen. It is not repeatable to so I have to wait for it to occur.
Do I just continue to click OK and continue or does it need to be fixed?

Windows 10 with current updates, wsjt-x v2.5.1. JTAlert 2.50.7 HRD current version

73 Roger ZF1RC

Roger,

I would fix this if I could isolate the cause. Unfortunately, the error line numbers are typically grossly inaccurate.

Does this occur during very busy band periods?

Check your email, I have sent you a link to the latest JTAlert beta build please give it a try and let me know if it appears to resolve the issue.

de Laurie VK3AMA

locked error message that randomly appears

Roger A. Corbin
 

I have noticed that from time to time the attached message appears on the screen. It is not repeatable to so I have to wait for it to occur.
Do I just continue to click OK and continue or does it need to be fixed?

Windows 10 with current updates, wsjt-x v2.5.1. JTAlert 2.50.7 HRD current version

73 Roger ZF1RC
locked Re: JT ALERT stopped communicating with wsjt-x

JTAlert Support (VK3AMA)
 

On 16/11/2021 9:07 am, afa1yy wrote:
No QSOs are showing. any help welcome.
SJT-X UDP ID          :
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 127.0.0.1
WSJT-X UDP MCast on LB : False
WSJT-X UDP Max Schema  :

You're missing most of the WSJT-X diagnostic information included in the JTAlert "Help -> About".

Is this loss of comms with WSJT-X a recent problem or has it always done this? If recent, what software changes/updates have you made recently?

If you haven't done so already, a Windows Restart is worth a try especially if changed behavior has only just occurred.

I note that you're using unicast UDP for the WSJT-X UDP Server settings. Perhaps some other application is taking exclusive control of the UDP port and locking JTAlert out of the UDP comms.  I suggest setting WSJT-X to use Multicast UDP and setting any other applications that interoperate with WSJTX, like JTAlert, to use multicast UDP. See the JTAlert Help file "WSJT-X UDP Setup" topic, it has simple instructions for setting up multicast UDP.

de Laurie VK3AMA

locked Re: JT ALERT stopped communicating with wsjt-x

Joe Subich, W4TV
 

Are you running another logging program or something like GridTracker
that also requires UDP support from WSJTX?

Since you are not using multicast UDP, the "third program" may be
preventing JTAlert access to the UDP broadcasts from WSJTX.

73,

... Joe, W4TV

On 2021-11-15 5:07 PM, afa1yy wrote:
No QSOs are showing. any help welcome.
SJT-X UDP ID :
WSJT-X UDP Port : 2237
WSJT-X UDP Server : 127.0.0.1
WSJT-X UDP MCast on LB : False
WSJT-X UDP Max Schema :
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe : 61063 62667
JTAlertV2.Manager.exe : 53928 53929 53930
JTAlertV2.Decodes.exe : 53936
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (USB Audio CODEC )
[2] Speakers (High Definition Audio Device)
==================================================
JTAlertV2.Manager (2.50.7.0) status
(2021-11-15 22:03:06 utc)
--------------------------------------------------
CLR Version : 5.0.12
NET Framework : .NET 5.0.12
Architecture : x64 64bit
--------------------------------------------------
UDP Router : Initialized : YES (WSJT-X)
Audio : Initialized : YES (2 output devices)
Activity Service : Initialized : YES (started : 58)
Messaging Service : Initialized : YES (started : 17)
HamSpots Service : Initialized : YES
QRZ Xml : Initialized : YES
HamQth Xml : Initialized : YES
QRZ Log : Initialized : YES
HamQth Log : Initialized : YES
ClubLog Log : Initialized : YES (K0AY)
Eqsl Log : Initialized : YES
HrdLog Log : Initialized : YES
DXLab DDE : Initialized : YES
User Alert : Initialized : YES
Updates Check : Initialized : YES (started : 3600)
Environment Check : Initialized : YES (started : 3600)
Maintenance : Initialized : YES (started : 3600)
--------------------------------------------------
locked JT ALERT stopped communicating with wsjt-x

afa1yy
 

No QSOs are showing. any help welcome.
SJT-X UDP ID          :
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 127.0.0.1
WSJT-X UDP MCast on LB : False
WSJT-X UDP Max Schema  :

==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 61063 62667
JTAlertV2.Manager.exe : 53928 53929 53930
JTAlertV2.Decodes.exe : 53936


==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (USB Audio CODEC )
[2] Speakers (High Definition Audio Device)


==================================================
JTAlertV2.Manager (2.50.7.0) status
(2021-11-15 22:03:06 utc)
--------------------------------------------------
CLR Version       : 5.0.12
NET Framework     : .NET 5.0.12
Architecture      : x64 64bit
--------------------------------------------------
UDP Router        : Initialized : YES (WSJT-X)
Audio             : Initialized : YES (2 output devices)
Activity Service  : Initialized : YES (started : 58)
Messaging Service : Initialized : YES (started : 17)
HamSpots Service  : Initialized : YES
QRZ Xml           : Initialized : YES
HamQth Xml        : Initialized : YES
QRZ Log           : Initialized : YES
HamQth Log        : Initialized : YES
ClubLog Log       : Initialized : YES (K0AY)
Eqsl Log          : Initialized : YES
HrdLog Log        : Initialized : YES
DXLab DDE         : Initialized : YES
User Alert        : Initialized : YES
Updates Check     : Initialized : YES (started : 3600)
Environment Check : Initialized : YES (started : 3600)
Maintenance       : Initialized : YES (started : 3600)
--------------------------------------------------

--
Art  K0AY
locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

JTAlert Support (VK3AMA)
 

On 15/11/2021 7:54 am, A. Mark Gillespie (VK3BU) wrote:
Sorry, clicked on the wrong 3D2 station.

Here's what happens with 3D2USU.
_._,_._,_


There can be a number of reasons why the QSO History is not displaying results.
  • Not having a logger enabled in JTAlert.
  • JTAlert is looking at the wrong or empty log file.
  • Protection software interference preventing JTAlert from reading the log file.
  • In your example there are no FT8 QSOs with 3D2USU in your log.

What logger do you have enabled in JTAlert

Assuming you are using a log with JTAlert, are there any 3D2USU QSOs in that log recorded? If there are, for what mode?

de Laurie VK3AMA
locked Re: Wanted filter for other bands

Pawel Stobinski
 

Thanks, Laurie. Keeping fingers crossed :D

Paul, sq5nry
locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

A. Mark Gillespie (VK3BU)
 

Sorry, clicked on the wrong 3D2 station.

Here's what happens with 3D2USU.
locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

Joe Subich, W4TV
 

Worked B4 Operating Incorrectly In JTAlert
This is correct. Although you have worked 3D2USU, you apparently
have not worked 3D2TS.

73,

... Joe, W4TV


On 2021-11-14 2:25 AM, A. Mark Gillespie (VK3BU) wrote:
Hi All,
I've recently rediscovered the hobby and have just set up WSJT-X and JTAlert over the last couple of days. I'm currently only using QRZ.com for a log.
Everything seems to be working as it should, except for one aspect of JTAlert's worked B4 functionality.
I have worked 3D2USU once on two different bands. I'm getting grey a background on worked before stations in both WSJT-X and JTAlert, however when I right click on the worked B4 station in JTAlert and click on "Show QSO's History Popup", the popup states that it's not a worked B4 station.
It's all very odd since JTAlert does know that stations are worked before, but the "Show QSO's History Popup" alone doesn't seem to know about the worked B4 station.
Any ideas on how I can rectify the situation?
Thank you.
73 Mark
Worked B4 Operating Correctly In WSJT-X
Worked B4 Operating Correctly In JTAlert
Worked B4 Operating Incorrectly In JTAlert
locked Re: JTAlert misses some decodes from JTDX

JTAlert Support (VK3AMA)
 

On 12/11/2021 11:11 pm, Dwight Bosselman wrote:
As you said "If the original decode associated with a JTAlert callsign is no longer shown in JTDX than the callsign click event is ignored by JTDX."

FYI, this is also how WSJTX behaves.

de Laurie VK3AMA

locked Re: WSJTX & JTDX with JTAlert

JTAlert Support (VK3AMA)
 

On 14/11/2021 1:50 am, Pawel Stobinski wrote:

I wanted to have two WSJTXs + one JTDX instance running each with its JTAlert. I can get WSJTXs+JTAlerts alone working but then trying to start JTAlert for JTDX fails, as if it's not identifying the JTDX. And vice versa, JTAlert+JTDX started first work okay but then adding WSJTx is not successful. Is there a way to get such a set working well?

Best regards, Paul, sq5nry


Sorry, That's not possible.

I did some searching and found this note in the 2.10.0 release notes...
  Changes:

    - The multi-instance support has also been changed. Running multiple copies
       of JTAlert against both WSJT-X and JTDX simultaneously is not supported.
       You can run multiple instances of JTAlert against either WSJT-X OR JTDX
       only. Both types of applications can be running simultaneously on the PC,
       but only one JTAlert operating mode (against WSJT-X or JTDX) is allowed.

The above notes have been added to the JTAlert Help file, "Multiple Instances" topic for the next JTAlert release.

de Laurie VK3AMA

locked Re: JTAlert Chrome segfault

JTAlert Support (VK3AMA)
 

On 15/11/2021 4:36 am, Michael Black via groups.io wrote:
JTAlert seg faults with his Chrome browser when clicking the Q button.
I don't see any information in the debug logs that helps.
Changing his default browser to Edge fixes it....back to Chrome still seg faults.

Did the same on my system and Chrome (same version as his) works OK.

Can we maybe get some debug to find out what's going on?

Mike W9MDB

Nothing I can do. JTAlert doesn't know which browser is the Windows default. The code executed by JTAlert is identical for all browsers...
    If $call <> "" Then
        ShellExecute("http://www.qrz.com/db/" & $call)
    Else
        ShellExecute("http://www.qrz.com/")
    EndIf

The ShellExecute is an inbuilt AutoIT function, there is no facility for additional debugging.

de Laurie VK3AMA

2841 - 2860 of 40371