Date   

locked Re: alerts set on Fields

Jim Brown
 

Yes, this is well worth doing.

On Sun, Aug 25, 2019 at 9:52 PM K6EU <wa4qvq@...> wrote:
Sorry a couple of typos.  Is there any way to get alerts ...    And CM is a field, CM97 is a grid. 


locked Re: Sudden burst in JT9 activity. Why?

Jim Brown
 

Is it possible that hams have RTFM and realized that it's greatly superior mode for weak signal work, especially at lower frequencies? I would LOVE to see it much more widely used on 160M for weak signal work. EU is very tough on 160M from NorCal; the 4 dB or so advantage of JT9 over FT8 would help a lot!

73, Jim K9YC

On Sun, Aug 25, 2019 at 12:43 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
I have noticed over the last 2 days, a significant increase in JT9 activity as shown in the JTAlert Band Activity popup and on HamSpots and PSKReporter. Is there a JT9 specific contest on at the moment?

As I type this message 19:30 utc, the daily peak in PSKReporter activity, the top 3 reported modes (last 2 hours) on PSKReporter are FT8, FT4, JT9.
   

Does anyone know the reason for the sudden increase?

de Laurie VK3AMA


locked Re: alerts set on Fields

K6EU
 

Sorry a couple of typos.  Is there any way to get alerts ...    And CM is a field, CM97 is a grid. 


locked alerts set on Fields

K6EU
 

Is there nay way to get alerts based on fields instead or  in additions to girds?  By fields I mean the first two characters of a four digit grid.  IE CM is a grid.  For the new Digi contest uses fields for multipliers.  I'd like to receive alerts for new fields. 

tnx

Tom K6EU. 


locked Re: path of where hamapps callsign database is installed?

wbr@...
 

Thank you Mike.  Very kind of you.  73, Bill

WBR_WF4R
wbr@...


-----Original Message-----
From: Michael Black via Groups.Io <mdblack98@...>
To: Support <Support@HamApps.groups.io>
Sent: Sun, Aug 25, 2019 8:07 am
Subject: Re: [HamApps] path of where hamapps callsign database is installed?

The callsign database is C:\ProgramData\HamApps\Databases\fcc_lotw_eqsl.sqlite

de Mike W9MDB




On Sunday, August 25, 2019, 06:48:55 AM CDT, neil_zampella <neilz@...> wrote:


I'm pretty sure its a Sqllite database and kept under your Users directory under Local/AppData/Hamapps.
 
neil, KN3ILZ


locked Re: QSO Not Logged! (Error message)

HamApps Support (VK3AMA)
 

On 26/08/2019 9:55 am, Jon Titus wrote:
Thanks for the added info.  Yes, I can save the information in the ACLog, but I must add the call.  It doesn't "come over" from the JTAlert.  I'll check the things you recommend.  Thank you.

Jon, KZ1G
John,

The WSJT-X -> JTAlert -> ACLog process is normally automatic if the TCP API is enabled in ACLog. Log the QSO in WSJT-X and JTAlert automatically detects that event, combines the WSJT-X QSO data with the additional data JTAlert gathers from XML or previous QSO lookup and sends it off to ACLog. If the QSO is not appearing in the log despite the error message, than it is very likley you have not enabled the ACLog TCP API.

One way to test, without logging a QSO is to simply put a Callsign into the DXCall field of WSJT-X. JTAlert will see that and put it into its log fields area and also sends that Callsign over to ACLog which will populate its QSO entry area.

de Laurie VK3AMA


locked Re: Need help with JTALERT 2.14.3

HamApps Support (VK3AMA)
 

On 26/08/2019 9:56 am, KR4LU wrote:
Laurie, This occurs both using the shortcut created by the setup, or by executing the  still present JTAlert.exe file.(1,748 KB)
I do use Spy Hunter and it will prevent setup from working but I have it locked out and rebooted, as I always do when doing an upgrade.
The first time I setup the new version it asked about paths. It does not do that now even though I removed all traces of JTAlert and
rebooted before trying to install again using the same setup app and a newly downloaded one.

de Dave KR4LU

Dave,

Your image confirms it is not a shortcut problem it is not the standard message thrown by Windows when the shortcut has incorrect paths and files.

That message looks like something is preventing the Windows OS from accessing the JTAlert executable. I personally have not see that specific error window before. That looks very much like your Virus/Malware protection is blocking access by adjusting permissions on the file.

   

Starting JTAlert directly without using a shortcut should show the following, a JTAlert generate message...

   

It all looks to me like Virus/Malware protection interference. What do the logs of that software shown?

de Laurie VK3AMA


locked Re: Need help with JTALERT 2.14.3

KR4LU
 

It was installed under my login. I have admin privileges.


locked Re: Need help with JTALERT 2.14.3

KR4LU
 

Laurie, This occurs both using the shortcut created by the setup, or by executing the  still present JTAlert.exe file.(1,748 KB)
I do use Spy Hunter and it will prevent setup from working but I have it locked out and rebooted, as I always do when doing an upgrade.
The first time I setup the new version it asked about paths. It does not do that now even though I removed all traces of JTAlert and
rebooted before trying to install again using the same setup app and a newly downloaded one.

de Dave KR4LU
image attached


locked Re: QSO Not Logged! (Error message)

Jon Titus, KZ1G
 

Thanks for the added info.  Yes, I can save the information in the ACLog, but I must add the call.  It doesn't "come over" from the JTAlert.  I'll check the things you recommend.  Thank you.

Jon, KZ1G

Jon Titus
14253 S Trailview Way
Herriman, UT 84096 USA
+1-801-446-8882
tituskz1g@...


locked Re: QSO Not Logged! (Error message)

HamApps Support (VK3AMA)
 

On 26/08/2019 8:59 am, HamApps Support (VK3AMA) via Groups.Io wrote:

Jon,

That message indicates that JTAlert was unable to confirm that the QSO got logged (by JTAlert) successfully to ACLog. JTAlert confirms the QSO was logged by directly querying the ACLog log database. A couple of possibilities...
  1. The QSO didn't get logged because ACLog is not running or the TCP API is not enabled in ACLog (both conditions need to be satisfied).
  2. The log file JTAlert tried to read was not found.
In a default installation, JTAlert automatically determines the correct log file by reading the ACLog settings file, so number 1. is the most likely problem.

Let us know how you get on with this.

If you still can't get this to work, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.


I neglected in the above response to ask the question "Does the QSO get logged to ACLog despite the error message?"

If the answer is yes, than look under the "Miscellaneous -> Performance" section of the JTAlert Settings window and increase the "Check QSO Log Record" time.

de Laurie VK3AMA


locked Re: QSO Not Logged! (Error message)

HamApps Support (VK3AMA)
 

On 26/08/2019 7:50 am, Jon Titus wrote:
Hello.  I have just installed JTAlert and the N3FJP Amateur Contact Log program (ver. 6.5).  I use WSJT-X in the FT-8 mode. When the WSJT-X pops up its own log window and I click to save the QSO info in the WSJT-X log I get the following message in a pop-up box:

FAILURE: QSO to N3FJP Amateur Contact Log

ERROR Message: : AC LOG File : Unable to confirm QSO logged

NOTE: The QSO is still saved to the WSJT-X Log File.

I looked in the FAQ area but did not find useful information.  What does this error message mean, what is the solution to get the log info into the ACL log?  Any help greatly appreciated.  Thank you.

Jon Titus, KZ1G

Jon,

That message indicates that JTAlert was unable to confirm that the QSO got logged (by JTAlert) successfully to ACLog. JTAlert confirms the QSO was logged by directly querying the ACLog log database. A couple of possibilities...
  1. The QSO didn't get logged because ACLog is not running or the TCP API is not enabled in ACLog (both conditions need to be satisfied).
  2. The log file JTAlert tried to read was not found.
In a default installation, JTAlert automatically determines the correct log file by reading the ACLog settings file, so number 1. is the most likely problem.

Let us know how you get on with this.

If you still can't get this to work, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis.

de Laurie VK3AMA




locked QSO Not Logged! (Error message)

Jon Titus, KZ1G
 

Hello.  I have just installed JTAlert and the N3FJP Amateur Contact Log program (ver. 6.5).  I use WSJT-X in the FT-8 mode. When the WSJT-X pops up its own log window and I click to save the QSO info in the WSJT-X log I get the following message in a pop-up box:

FAILURE: QSO to N3FJP Amateur Contact Log

ERROR Message: : AC LOG File : Unable to confirm QSO logged

NOTE: The QSO is still saved to the WSJT-X Log File.

I looked in the FAQ area but did not find useful information.  What does this error message mean, what is the solution to get the log info into the ACL log?  Any help greatly appreciated.  Thank you.

Jon Titus, KZ1G
Herriman, Utah


locked Re: Need help with JTALERT 2.14.3

Dave Garber
 

perhaps one of the applications is in elevated / administrator mode??


Dave Garber
VE3WEJ / VE3IE


On Sun, Aug 25, 2019 at 4:09 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 26/08/2019 4:07 am, KR4LU wrote:
Was working fine, but after a freeze and reinstall of both WSJT-X and JTALERT 2.14.3, WSJT-X starts and runs fine. When I start Jtalert, I get the message: Windows cannot access the specified device, path or file. You may not have appropriate permissions to access them. I suspect a path problem, but don't know how to correct it. BTW the Windows is 10 64bit.
Dave KR4LU

Dave,

Sounds like the shortcut your using to start JTAlert is referencing an incorrect path or file. Is this a user-created shortcut or one automatically created during the JTAlert install? If the later, than very likely you virus protection may have removed the JTAlert.exe file.

Please post an image of the offending error window (pse don't post your entire desktop, just the error window is needed).

de Laurie VK3AMA


locked Re: Apostrophe

HamApps Support (VK3AMA)
 

On 26/08/2019 7:07 am, Tony Dixon G4CJC wrote:
Not red, absolutely not red. For those of us who are chromatically challenged.
Tony, don't worry. I endeavour to have all colors in JTAlert user-settable.

In this case, coloring the updates indicator, it is very unlikely to be implemented. But if it is, the color will be user-settable.

A little know fact, I am personally color challenged in one eye only.

de Laurie VK3AMA


locked Re: Apostrophe

Tony Dixon G4CJC
 

Not red, absolutely not red. For those of us who are chromatically challenged.
T


locked Re: Unique Callsign display

HamApps Support (VK3AMA)
 

On 26/08/2019 6:30 am, WB8ASI Herb wrote:
I've been shrinking the band activity columns that I don't use, thus it's about half the size for just FT4&8. Would also like to cancel out the bands I can't use.


I don't know what your achieving by altering the column widths. The overall window size doesn't change so you end up with a lot of empty  window space without any net gain in available screen space, plus the widths are not remembered so you have to do that every time you start JTAlert.

Hiding user-selectable bands is already on the todo list.

de Laurie VK3AMA


locked Re: Unique Callsign display

WB8ASI Herb
 

I've been shrinking the band activity columns that I don't use, thus it's about half the size for just FT4&8. Would also like to cancel out the bands I can't use.


Sent from Xfinity Connect Application


-----Original Message-----

From: vk3ama.ham.apps@...
To: Support@HamApps.groups.io
Sent: 2019-08-25 3:47:50 PM
Subject: Re: [HamApps] Unique Callsign display

On 25/08/2019 9:33 am, Dennis wrote:
Is there a way to not show modes in which I am not interested? For example, if I'm running FT8, I have no real interest in say JT65. With the recent addition of the FT4 columns, the display is now using up a lot screen real estate - a very valuable commodity in my shack hihi.
Kind Regards,
Dennis W7DRW

Dennis,

It is on the todo list, added by myself when I first coded the F4 support as I knew the user request would be coming ;-)

Until it is implemented, I suggest you don't have the Band Activity window open and rely on a periodic mouse-hover over the Band Activity status to temporarily show the popup window.

de Laurie VK3AMA




locked Re: path of where hamapps callsign database is installed?

HamApps Support (VK3AMA)
 

On 25/08/2019 6:05 am, wbr via Groups.Io wrote:
Hello, I'm a beginner and would like to know where the hamapps callsign database is installed on my computer.
I've searched but am not able find.  I've also tried to catch the path while program was installing but little window
goes by too fast.
Is it important to know where the call sign database is installed? probably not, but I'd still like to know.  Thanks
73, WF4R
"C:\ProgramData\HamApps\Databases\fcc_lotw_eqsl.sqlite"

I advise against trying to modify the data in the file.
If there is an error in the data report it here so it can be corrected for all users.

de Laurie VK3AMA


locked Re: Not work scan Wanted Continent and Wanted Prefix

HamApps Support (VK3AMA)
 

On 24/08/2019 11:07 pm, Vladimir Doroshenko wrote:
Hello!

Please help, not work scan Wanted Continent and Wanted Prefix. In scan
results I see Continents Needed : 7 and Prefix Not Needed : 0 in all
bands and modes:

[Prefixes : FT8 Modes Only]
Band : ANY - Prefix Not Needed : 0 (Previous : 0)
Band : 160 - Prefix Not Needed : 0 (Previous : 0)
Band : 80 - Prefix Not Needed : 0 (Previous : 0)
Band : 60 - Prefix Not Needed : 0 (Previous : 0)
Band : 40 - Prefix Not Needed : 0 (Previous : 0)
Band : 30 - Prefix Not Needed : 0 (Previous : 0)
Band : 20 - Prefix Not Needed : 0 (Previous : 0)
Band : 17 - Prefix Not Needed : 0 (Previous : 0)
Band : 15 - Prefix Not Needed : 0 (Previous : 0)
Band : 12 - Prefix Not Needed : 0 (Previous : 0)
Band : 10 - Prefix Not Needed : 0 (Previous : 0)
Band : 6 - Prefix Not Needed : 0 (Previous : 0)
Band : 2 - Prefix Not Needed : 0 (Previous : 0)


Other scans work correctly. For example:

[Grids : FT8 Modes Only]
Band : ANY - Grids Not Needed : 893 (Previous : 893)
Band : 160 - Grids Not Needed : 157 (Previous : 157)
Band : 80 - Grids Not Needed : 534 (Previous : 534)
Band : 60 - Grids Not Needed : 0 (Previous : 0)
Band : 40 - Grids Not Needed : 387 (Previous : 387)
Band : 30 - Grids Not Needed : 545 (Previous : 545)
Band : 20 - Grids Not Needed : 421 (Previous : 421)
Band : 17 - Grids Not Needed : 223 (Previous : 223)
Band : 15 - Grids Not Needed : 142 (Previous : 142)
Band : 12 - Grids Not Needed : 58 (Previous : 58)
Band : 10 - Grids Not Needed : 71 (Previous : 71)
Band : 6 - Grids Not Needed : 0 (Previous : 0)
Band : 2 - Grids Not Needed : 5 (Previous : 5)

ADIF file from AAlog 3.9

Thank you!

73!
UW5EKD
Vladimir
Vladimir,

Very likely that for the scans affected your adif log file doesn't contain the required information. Does it contain the <CONT> and <PFX> fields?

Please send me direct (not via this group) a copy of your adif file.

de Laurie VK3AMA

13221 - 13240 of 38547