Date   

locked Re: JT Alert Main Window

HamApps Support (VK3AMA)
 

On 22/10/2020 1:11 am, John K9EL wrote:

Any plans to allow the main window to be re-sized?

 

I would love to be able to essentially rotate the window 90 degrees – in other words, have tall columns.   Instead of choices of 1-4 X 6-9, be able to do 6-9 X 1-4.

 

Thanks!

 

73, John K9EL

John,

Making the JTAlert window resizable, within the current V2 series is not likely.  Do do so would require significant layout changes as the Log Fields and Confirmed Bands displays would need to be reworked significantly or made separate windows.

The future JTAlertV3 has no such restrictions on window size (or number of displayed callsigns). Unfortunately, its release is still many months away. I have recently changed direction with how JTAlert is being coded that has further pushed out a possible release date.

But all is not lost, as part of that change I decided to start integrating parts of JTAlertV3 into the current V2 series, a hybridization. Most of that work to date has been in the background introducing new multi-threaded functionality.

The Test Team has been playing with new functionality where the Callsigns display is a separate resizable window. It is likely to be made part of V2 before Christmas.

To wet your appetite, here are some screen grabs of this new "Calls" window. These were taken of the same window resized and settings adjusted (show/hide country name, auto-adjust callsign display width) in real-time.



   

de Laurie VK3AMA





locked Re: JTALERT and Last version of HRD logbook ( 6.7.0.301 )

Roger- AC6BW
 

OK, you exported and imported the HRD-ADIF version. That is better than using a standard ADIF file.
However, as I said before, exporting an XML file, which is a true backup file for HRD, would have been better.
Anyway, glad you got it working.
Be sure to backup your HRD log to xml regularly.
--
73,
Roger
AC6BW


locked Re: No Decodes - Packets Seen with Wireshark

 
Edited

In my case I don't see band information, etc.  which is consistent with what Laurie describes.  It doesn't seem to be able to communicate with WSJT-X. 

BTW, I completely disabled my firewall.  Same result.

Tnx


locked Re: No Decodes - Packets Seen with Wireshark

Bob Willey K3RLW
 

I have been seeing similar, e,dept aclog 
Wsjt-x keeps decoding, but nothing in jtalert or decodes window. 
I just shutdown jtalert and restart

Bob Willey - bobwilley@...


On Wed, Oct 21, 2020, 7:46 AM Bob WB2NVR <wb2nvr@...> wrote:
I'm having the same problem. Started a day or two ago, possibly after a Windows update.

I have multicast set up.  After one or two QSOs, it looks like JTAlert stops responding. JTAlert 2.16.4 (also tried 2.16.13, same problem). WSJT-X 2.2.2, same problem with 2.3.0 rc1. DXKeeper 15.8.5. Looking at the DXKeeper Server Log, 
when JTAlert freezes, nothing is sent to DXKeeper port 12060. Restarting the port in DXKeeper doesn't resolve the issue.

Restarting JTAlert (and WSJT-X) seems to reset something, and the programs work for a few Qs.

I sent session files a day or two ago when this first started.

Would really appreciate some help with this.

TNX ES 73, Bob WB2NVR

Bob WB2NVR


locked Re: Callsign history?

HamApps Support (VK3AMA)
 

On 21/10/2020 6:02 am, kons wrote:
Is it possible at a QSO to see both callsigns if had a qso in the past or need it and not only the one
73
kons

It is not possible.

JTAlert will only alert (color) the callsign transmitting, not the callsign that is being called.

de Laurie VK3AMA


locked Re: No Decodes - Packets Seen with Wireshark

HamApps Support (VK3AMA)
 

On 21/10/2020 2:34 pm, Michael Black via groups.io wrote:
Second start...JTAlert sees band info...but no decodes

I don't know how that can be. If JTAlert is following Band changes it is receiving the UDP status messages OK. There should be no reason why the decodes messages are not being received.

PC Protection software interference maybe?

Please be aware that ALL UDP comms between JTAlert and WSJT-X, in both directions is handled by the JTAlertV2.Manager.exe process, not the JTAlert.exe process.

de Laurie VK3AMA


locked Re: JTALERT and Last version of HRD logbook ( 6.7.0.301 )

Daniele
 

Hi
 
the ADIF-HRD version includes all QSL info !

73


locked Re: JTALERT and Last version of HRD logbook ( 6.7.0.301 )

Tom Melvin
 

Hi

It _may_ be what you have set for conformation - worked, LOTW, etc.  

ADIF does not usually have the QSL info - HRD may have an extended export option that does include it - I would double check the ADIF has the info used by the confirmation type.

Tom

--
73

Tom
GM8MJV (IO85)





On 21 Oct 2020, at 14:21, Daniele <iw9grl@...> wrote:

Hi

probably I solved, creating a new DB in HRD from scratch and importo the ADIF exported before . 
Now with last version of HRD and last version of JTALERT no more crash .
Only a thing seems to be not solved, the Rebuild Alert Database seems don't work, JTAlert see the correct count of QSOs but didn't update the interal Alert DB of JTAlert . 
Really strange ...

anyway, thank you for all for all suggestions !

73
de IW9GRL/KD2PRQ


locked JT Alert Main Window

John K9EL
 

Any plans to allow the main window to be re-sized?

 

I would love to be able to essentially rotate the window 90 degrees – in other words, have tall columns.   Instead of choices of 1-4 X 6-9, be able to do 6-9 X 1-4.

 

Thanks!

 

73, John K9EL

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Daniele
Sent: Wednesday, October 21, 2020 8:22 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTALERT and Last version of HRD logbook ( 6.7.0.301 )

 

Hi

probably I solved, creating a new DB in HRD from scratch and importo the ADIF exported before . 
Now with last version of HRD and last version of JTALERT no more crash .
Only a thing seems to be not solved, the Rebuild Alert Database seems don't work, JTAlert see the correct count of QSOs but didn't update the interal Alert DB of JTAlert . 
Really strange ...

anyway, thank you for all for all suggestions !

73
de IW9GRL/KD2PRQ


locked Re: JTALERT and Last version of HRD logbook ( 6.7.0.301 )

Daniele
 

Hi

probably I solved, creating a new DB in HRD from scratch and importo the ADIF exported before . 
Now with last version of HRD and last version of JTALERT no more crash .
Only a thing seems to be not solved, the Rebuild Alert Database seems don't work, JTAlert see the correct count of QSOs but didn't update the interal Alert DB of JTAlert . 
Really strange ...

anyway, thank you for all for all suggestions !

73
de IW9GRL/KD2PRQ


locked Re: No Decodes - Packets Seen with Wireshark

Bob WB2NVR
 

I'm having the same problem. Started a day or two ago, possibly after a Windows update.

I have multicast set up.  After one or two QSOs, it looks like JTAlert stops responding. JTAlert 2.16.4 (also tried 2.16.13, same problem). WSJT-X 2.2.2, same problem with 2.3.0 rc1. DXKeeper 15.8.5. Looking at the DXKeeper Server Log, 
when JTAlert freezes, nothing is sent to DXKeeper port 12060. Restarting the port in DXKeeper doesn't resolve the issue.

Restarting JTAlert (and WSJT-X) seems to reset something, and the programs work for a few Qs.

I sent session files a day or two ago when this first started.

Would really appreciate some help with this.

TNX ES 73, Bob WB2NVR

Bob WB2NVR


locked Re: JTALERT and Last version of HRD logbook ( 6.7.0.301 )

Daniele
 

Hi 

first of all thank you for suggests . 
I contacted also the HRD team support and they didn't know about problems in the last revision ( 6.7.0.301 ) .
What I saw is that when all tools are up, HRD, logbook, WSJT-X and JTALERT, all of them work fine, but when I receive the first decode callsign, JTAlert stop to works and need to reboot, also after reboot the problem persist .
The workaround to have JTAlert works is to disable HRD logging in its settings .

What I did is  to downgrade HRD to 6.7.0.275 and now all works very well as before, without any crash of JTAlert !

I think that in HRD logbook have somethings different than before, some settings to do or something else, I don't know, the HRD support tell me that by their side all works well  .

This is the actual status
I hope someone of you is able to replicate the issue to find quickly the best solution .

Thank you so much
73 de Daniele IW9GRL/KD2PRQ


locked Re: No Decodes - Packets Seen with Wireshark

Michael Black
 

I'm seeing the same thing here on 2.3.0-rc1

FIrst start...JTAlert sees no packets at all...no band info or such in title bar
Second start...JTAlert sees band info...but no decodes
Third start...all is well.

I did have a wireless connection turned on which I turned off between 2nd and 3rd...but don't quite see how that should make any difference.

Mike




On Tuesday, October 20, 2020, 07:40:22 PM CDT, Greg Tilford <gregtilford@...> wrote:


Here's my Help -> About JTAlert

JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X - IC7300   v2.2.2   by K1JT, G4WJS, and K9AN
WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe" -r IC7300
WSJT-X   --rig-name   : IC7300
WSJT-X Config File    : C:\Users\gregt\AppData\Local\WSJT-X - IC7300\WSJT-X - IC7300.ini
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 59330 57529
JTAlertV2.Manager.exe : 58220 58221 
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Realtek(R) Audio)
[2] Line 1 (Virtual Audio Cable)
[3] Speakers (USB Audio CODEC )
[4] IC-7300 (3- USB Audio CODEC )
[5] Line 2 (Virtual Audio Cable)
 
 
==================================================
JTAlertV2.Manager (2.16.14.0) status
(2020-10-21 00:37:51 utc)
--------------------------------------------------
NET Framework    : .NET Framework 4.8.4250.0
CLR Version      : 4.0.30319.42000
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X - IC7300)
Audio            : Initialized : YES (5 output devices)
BandData         : Initialized : YES (started : 58)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (KM5GT)
HamQth Xml       : Initialized : YES 
QRZ Log          : Initialized : YES 
HamQth Log       : Initialized : YES 
ClubLog Log      : Initialized : YES 
Eqsl Log         : Initialized : YES 
HrdLog Log       : Initialized : YES 
DXLab DDE        : Initialized : YES
User Alert       : Initialized : YES
Updates Chk      : Initialized : YES
Maintenance      : Initialized : YES
 


locked Re: No Decodes - Packets Seen with Wireshark

 

Here's my Help -> About JTAlert

JTAlert Instance      : #1
JTAlert Start Params  : /wsjtx
WSJT-X Window Title   : WSJT-X - IC7300   v2.2.2   by K1JT, G4WJS, and K9AN
WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe" -r IC7300
WSJT-X   --rig-name   : IC7300
WSJT-X Config File    : C:\Users\gregt\AppData\Local\WSJT-X - IC7300\WSJT-X - IC7300.ini
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 59330 57529
JTAlertV2.Manager.exe : 58220 58221 
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (Realtek(R) Audio)
[2] Line 1 (Virtual Audio Cable)
[3] Speakers (USB Audio CODEC )
[4] IC-7300 (3- USB Audio CODEC )
[5] Line 2 (Virtual Audio Cable)
 
 
==================================================
JTAlertV2.Manager (2.16.14.0) status
(2020-10-21 00:37:51 utc)
--------------------------------------------------
NET Framework    : .NET Framework 4.8.4250.0
CLR Version      : 4.0.30319.42000
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X - IC7300)
Audio            : Initialized : YES (5 output devices)
BandData         : Initialized : YES (started : 58)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (KM5GT)
HamQth Xml       : Initialized : YES 
QRZ Log          : Initialized : YES 
HamQth Log       : Initialized : YES 
ClubLog Log      : Initialized : YES 
Eqsl Log         : Initialized : YES 
HrdLog Log       : Initialized : YES 
DXLab DDE        : Initialized : YES
User Alert       : Initialized : YES
Updates Chk      : Initialized : YES
Maintenance      : Initialized : YES
 


locked Re: No Decodes - Packets Seen with Wireshark

 

It looks like the broadcast is going out okay, but still the same result.  "Unable to communicate with the WSJT-X process"


locked Re: No Decodes - Packets Seen with Wireshark

HamApps Support (VK3AMA)
 

On 21/10/2020 9:22 am, Greg Tilford wrote:
Suggestions as to where to look next?

Thanks in advance,
73, Greg, KM5GT
Try setting wsjtx to use a multicast address for the UDP Server address. I suggest 239.255.0.0
After making the change restart both wsjtx & JTAlert

   

de Laurie VK3AMA


locked Re: No Decodes - Packets Seen with Wireshark

Michael Black
 

What does the Help/About show?  It shows all the JTAlert processes.

What antivirus are you running?

Mike W9MDB




On Tuesday, October 20, 2020, 05:22:45 PM CDT, Greg Tilford <gregtilford@...> wrote:


I'm a bit puzzled.  JTAlert stopped showing  any decodes.  I am getting the dreaded "Unable to communicate with the WSJT-X process" see below. I am running WSJT-X v2.2.2 0d9b96 with JTAlert version 2.16.14, Build 0000.


WSJT-X seems like it is still set up correctly.



I can see the packets on the loopback with Wireshark.



Suggestions as to where to look next?

Thanks in advance,
73, Greg, KM5GT


locked No Decodes - Packets Seen with Wireshark

 

I'm a bit puzzled.  JTAlert stopped showing  any decodes.  I am getting the dreaded "Unable to communicate with the WSJT-X process" see below. I am running WSJT-X v2.2.2 0d9b96 with JTAlert version 2.16.14, Build 0000.


WSJT-X seems like it is still set up correctly.



I can see the packets on the loopback with Wireshark.



Suggestions as to where to look next?

Thanks in advance,
73, Greg, KM5GT


locked Re: JTALert #FT8 Falling behind and then not working at all. #FT8

HamApps Support (VK3AMA)
 

On 21/10/2020 8:35 am, John Sokol wrote:
The program was working like a charm with WSJT-X. Then all of a sudden its starting to fall behind. Sometimes it doesn't show anything at all. I know its connected, because it reads the mode and band from WSJT-X. If I restart JT Alert, that works for a short period. I use it to connect to Amateur Contact Log. Worked great for days, now it just seems to be an issue. When it does work, it still logs properly. 

What version of WSJT-X?
What are your PC specs, cpu type, # cores, memory installed?

de Laurie VK3AMA


locked Re: Scan Log Missing

HamApps Support (VK3AMA)
 

On 21/10/2020 7:58 am, John K9EL wrote:
I was in that section, but I do not see anywhere to scan my existing ADIF log like the previous version

From the JTAlert window menu...


Within the Settings window...


de Laurie VK3AMA

5221 - 5240 of 36990