Date   

locked Re: Any possibility for JTAlerts to work with MSHV?

Carl - WC4H
 

Thanks Laurie.
It does broadcast the qso via UDP.

I managed to send the data from MSHV to N1MM+ on the UDP port.  Then using the N1MM_DXLab_Gateway the qso goes to DXKeeper.

It's Just easier and more consistent to use JTAlerts accross the spectrum (WSJT-X, JTDX, and MSHV).

I always like testing out each of the 3 programs to see who has what.

73.
Carl - WC4H


locked Re: No callsigns showing when using JTAlert-X 2.12.7 with WSJT-X 2.0 RC4

HamApps Support (VK3AMA)
 

On 21/11/2018 7:58 am, groupsio via Groups.Io wrote:
After some troubleshooting I noticed I was still in Hound mode, once I changed that in WSJT-X, JTAlert started showing calls again.

-Jason.
Jason,

Thanks for that. I had totally forgotten about WSJT-X Hound Mode not reporting decodes.

While WSJT-X provides a Status update on several value changes (Callsigns, Frequency, DF, Sig, Grids, etc), it does not for changes in Fox/Hound/Contest operating mode status. WSJT-X can be queried at any time by JTAlert for the current state of WSJT-X, but again, Fox/Hound/Contest operating mode is not available.

If WSJT-X in the future provides the missing Status data JTAlert will be extended to test for these WSJT-X operating modes and provide some sort of warning or indicator to the user.

de Laurie VK3AMA


locked Re: No callsigns showing when using JTAlert-X 2.12.7 with WSJT-X 2.0 RC4

HamApps Support (VK3AMA)
 

On 21/11/2018 10:02 pm, Tom Ramberg via Groups.Io wrote:
Yeah, I'll check that tomorrow. It never ocurred to me that something like that could be the reason, so I never checked. It's a nuisance that RC4 doesn't remember the last settings so you have to recheck all settings every time you start the programme.
--
73 de Tom OH6VDA
Tom,

Was having Hound mode enabled in WSJT-X the cause of your no-callsigns in JTAlert problem?

de Laurie VK3AMA


locked Re: Any possibility for JTAlerts to work with MSHV?

HamApps Support (VK3AMA)
 

On 23/11/2018 5:47 am, Carl - WC4H via Groups.Io wrote:

Has any thought been given to integrating JTAlerts with MSHV (like WSJT-X and JTDX).

NOTE: I tried to post this question before but looks like it did not make it.  Sorry if it duplicates.

73.
Carl - WC4H

Carl,

Sorry, it is very unlikely that MSHV support will be added. The MSHV developers stripped out all the UDP reporting code of WSJT-X. There is no facility (that I could find) for MSHV to generate Decode or Status data that can be used by third party applications like JTAlert.

de Laurie VK3AMA


locked Re: V2.12.7 Crash

HamApps Support (VK3AMA)
 

On 22/11/2018 8:27 am, Mike Davies wrote:
Not sure if this has been reported before but I've now seen this crash 3 times.  Happy to provide further details if required.

Mike, G0KAD
Mike,

Unfortunately, this error has no fix. It has been rather elusive and not reproducible in testing. The root cause is unknown, I suspect a memory leak associated with the compiler used.

Common amongst some users experiencing this error is having the Decodes History enabled. Do you have it enabled?

de Laurie VK3AMA


locked Any possibility for JTAlerts to work with MSHV?

Carl - WC4H
 

Has any thought been given to integrating JTAlerts with MSHV (like WSJT-X and JTDX).

NOTE: I tried to post this question before but looks like it did not make it.  Sorry if it duplicates.

73.
Carl - WC4H


locked Re: JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

Stephen - K6SJT
 

I just received an email that HRD is currently running a Black Friday 30% off sale through midnight Monday – use code BLACKFRIDAY18 at checkout

 

Stephen – K6SJT

 


From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of WB5JJJ
Sent: Wednesday, November 21, 2018 3:23 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

 

You can update at any time even if your service subscription has expired.  You just won't get any new features or enhancements, but always fixes to the software.  Also check the HRD website, they have 20% - 30% off during the holidays.  Just pay the $50 or less price, no need for a full new purchase.
--
73's
George - WB5JJJ


locked Re: JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

WB5JJJ - George
 

You can update at any time even if your service subscription has expired.  You just won't get any new features or enhancements, but always fixes to the software.  Also check the HRD website, they have 20% - 30% off during the holidays.  Just pay the $50 or less price, no need for a full new purchase.
--
73's
George - WB5JJJ


locked V2.12.7 Crash

Mike Davies
 

Not sure if this has been reported before but I've now seen this crash 3 times.  Happy to provide further details if required.

Mike, G0KAD


locked Re: JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

n8mdp
 

Hi Ron,

Yes, I had that checked. I did a little bit of digging last night and found other posts (like you said, "standard question") that had similar issues. I didn't realize that The Grid Chase updates monthly or at least I'm behind the times!! Once I unchecked that and ran a scan to rebuild the database, everything started working again. Live an learn!

Oh, and regarding my HRD being old, or at leat version 6.3, it works just fine for me with JTAlertX and other software. I suppose I'll consider updating it next year at Hamvention.

Thanks for the guidance.
73
John, N8MDP


locked Re: JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

Ron W3RJW
 

I guess the standard question when this occurs is do you have "Enable 2018 ARRL Grid Chase" checked in the "wanted Grid" tab ?  It resets monthly ...

73
Ron, W3RJW


locked Re: JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

WB5JJJ - George
 

I noticed you are running a really old version of HRD.  There have been a lot of great updates, enhancements and fixes for old, nagging problems since your installed version was released in December 2016.  You did not mention your operating system and version.  Current version is 6.4.0.902 and is rock solid stable.  Read the release notes and make sure your system will support it. 
--
73's
George - WB5JJJ


locked Re: No callsigns showing when using JTAlert-X 2.12.7 with WSJT-X 2.0 RC4

Tom Ramberg, OH6VDA
 

Yeah, I'll check that tomorrow. It never ocurred to me that something like that could be the reason, so I never checked. It's a nuisance that RC4 doesn't remember the last settings so you have to recheck all settings every time you start the programme.
--
73 de Tom OH6VDA


locked Re: No callsigns showing when using JTAlert-X 2.12.7 with WSJT-X 2.0 RC4

groupsio@...
 

So something to check is the mode of WSJT-X. As I ran into this today.

  • JTAlert-X was tracking Band Changes
  • No Filtering was on
  • Still no calls appearing in JTAlert
After some troubleshooting I noticed I was still in Hound mode, once I changed that in WSJT-X, JTAlert started showing calls again.

-Jason.


locked JTAlertX 2.12.7 showing Grids that are needed but already worked #FT8

n8mdp
 

Hi.

This is my first post and I've reviewed a number of posts to see if I can determine why I'm having issues seeing grid squares needed when I know a grid has already been worked. Didn't find much so I'm writing this post. Here's what I'm seeing.

Software in use:
  • WSJT-X v1.8.0
  • JTAlertX 2.12.7
  • Ham Radio Deluxe v6.3.0.613
  • HRD Logbook v6.3.0.613
I have JTAlertX 2.1.7 set up to use HRD V5/V6 for Logging. I use the "Scan Log and Rebuild" to scan my HRD Logbook database. I have all scan types enabled and the Card, eQSL, and LoTW check boxes checked.  So I run the Scan All to scan my HRD log and everything looks like its working. Once everything is done, I restart the JTAlertX software to make sure that any changes are in. But now here's the dilemma.

As JTAlertX begins to decode alerts, I'm noticing that most of the alerts coming up are indicating Wanted Grids that I have already worked! I also noticed that when I look in the Wanted Grid => Individual Bands box for each band, the grids show that are not needed are nowhere near the number of grids I have already worked. For example, for FT8, Band 40m is showing only 5 grids out of 32400 Grid Squares NOT Needed. However, my logbook indicates I have worked and confirmed 130 grids. Why the difference? Why aren't the 130 grids no longer needed not even showing up in the box?

I built a web tool that I use to determine whether I have a confirmed grid square at http://www.n8mdp.com/arrl_igc2018.php
I can use this tool to make sure I don't try to go after a confirmed grid square but would prefer to to use JTAlertX to tell me this. Right now, I have Wanted Grid as the top priority in my alerts priority list.

I would appreciate advice and guidance on how to resolve this issue.
Thanks and 73.
John
N8MDP


locked Re: No callsigns showing when using JTAlert-X 2.12.7 with WSJT-X 2.0 RC4

Tom Ramberg, OH6VDA
 
Edited

1. The calsign database is installed. I've disabled that filter, because we'll work anyone regardless of their LoTW/eQsl status.
2. The communication between WSJT-X and JTAlert works. With WSJT-X 1.9.1 everything is normal.
3. The number of stations on each band using 77 bits here in Europe can be counted on one hand. So I I'm not able to test  RC4 and JTAlert in a decent manner right now. Just let it rest for the time being, I'll be back if the problem prevails.
--
73 de Tom OH6VDA


locked Re: My Decode History statistics for just under 3 months of monitoring and ~3.16 million decodes.

HamApps Support (VK3AMA)
 

On 18/11/2018 10:46 pm, Mark W2OR via Groups.Io wrote:
I've been looking for that same Statistics Database File here, but it seems to be hiding somewhere.


Mark W2OR
Mark,

That statistics view is part of the Statistics Window of the JTAlert V3 Decodes History.

As previously advised here in the forum, the V3 Decodes History is nearly ready for inclusion in the JTAlert V2 code. I am expecting the next JTAlert V2 public release (early January) will include the new V3 Decodes History component.

de Laurie VK3AMA


locked logging#how to

David Michael Gaytko // WD4KPD
 

I find the logging/tally sheet feature of hamapps the easiest to use for logging.!  how would one set the computer/another instance for using the application to only use the log tally section to track was/dxcc for other modes without bothering or breaking it's use with jtdx/wsjtx.  it would be nice to not need wsjtx to get the log running and then shutting it down.
it would also be nice to run the alert function with other programs/modes.
MOST importantly i don't want to mess up the functions with wsjtx/jtdx.

david/wd4kpd


locked Re: My Decode History statistics for just under 3 months of monitoring and ~3.16 million decodes.

Mark W2OR
 

Re the statistics - - Big congrats on those numbers.  All CQ Zones  : )    and all U.S. States !!   Even North Dakota !!   Ha.
I've been looking for that same Statistics Database File here, but it seems to be hiding somewhere.  

BTW, Laurie, here in the U.S. we're celebrating Thanksgiving Day next week.  I know Thanksgiving Day in Australia is in May, but I send along my Best Wishes now, anyway. I am very grateful for the JTAlert app, its diversity of functions and abilities, and its expected v.2 and v.3 renditions, in the works for next year.  Thank you very much.

Mark W2OR


locked Re: No callsigns showing when using JTAlert-X 2.12.7 with WSJT-X 2.0 RC4

HamApps Support (VK3AMA)
 

On 17/11/2018 9:09 pm, Tom Ramberg via Groups.Io wrote:
Yes, I see decodes in WSJT-X 2.0-RC4 that are not shown by JTAlert-X. (That's the reason for my initial question).
After I worked one station, he showed up as worked B4, all other decodes not shown in JTAlert. None of the sound warnings from JTAlert ever happened with RC4, however, I tested with 1.9.1 in between, and everything works fine with that. I tried to reinstall both WSJT-X RC4 and JTAlert-X, that changed nothing. That's the reason why I'm really bewildered. None of the UDP settings have been changed by me.

Alas, after that, an antenna issue developed, and I had to QRT. I can probably not be on air again until next week, when the antenna situation is resolved. 
--
73 de Tom OH6VDA
Tom,

As far as JTAlert is concerned, there is no difference between WSJT-X 1.9.1 and 2.0-rc4. Decode UDP packets from WSJT-X are identical.

If WSJT-X is showing decodes that are not shown in JTAlert, check that JTAlert is following WSJT-X band changes (see the JTAlert titlebar). If JTAlert is not following Band changes, than JTAlert is not receiving UDP packets from WSJT-X, in which case try restarting JTAlert.

If JTAlert is following WSJT-X band changes, than UDP communications between WSJT-X and JTAlert is working. In this case, then Callsigns not being displayed in JTAlert is likely due to them not passing Alert filtering. Do you have any Alert Filters applied? If so are any of them QSL filters (LoTW and/or eQSL)? QSL filters need the HamApps Callsigns database to be installed.

Are any Callsigns shown in JTAlert or is it ALWAYS empty?

de Laurie VK3AMA


14881 - 14900 of 37153