Date   

locked Re: : Re: Wanted Prefix Alert

John Singler
 

Thank you.
I'm having fun with the program. I'll just have to keep my cheat sheet handy


locked Azimuth

Dan Malcolm <dmalcolm24@...>
 

Laurie,

 

I am using WSJT-X 1.7.0 and JTAlert-X 2.9.0.  When I was using HRD Logbook, my QSO partners azimuth from my QTH was calculated (as an HRD LB function) when the QSO was logged.  Now that I am using Log4OM, that feature is missing.  In talking to the Log4OM guys on their forum, I am told that there is no API and logs get written directly, so azimuth would be hard for them to calculate. 

 

Azimuth is displayed on the WSJT-X window just above the “Lookup” button.  Between the two apps can something be arranged to upload the azimuth to Log4OM?

 

If for some reason that’s not feasible I will figure out a work around.  The reason for not doing it could be that I am the only one recording that data.

 

Thanks for your consideration.

 

___________________________________________

Dan Malcolm

K4SHQ


Politicians are people who, when they see light at the end
of the tunnel, go out and buy some more tunnel.

 


locked Re: JTAlert

Laurie, VK3AMA <groups08@...>
 

On 26/01/2017 11:01 AM, Robert rit001@yahoo.com [HamApps] wrote:
Where can we find the users manual.

73
WA6MBL bob
Bob,

There is a help file that is installed with JTAlert. Unfortunately, it is a "work in progress" and is incomplete. Most settings are explained within the JTAlert Settings window with enough detail that no further help is needed, these are typically the topics in the help file that are "under construction". Complex settings that require explanation are typically covered in the help file and have direct links from the applicable section of the Settings Window

You can always ask here on the group if your having difficulty understanding a setting or an operational question.

de Laurie VK3AMA


locked Re: Retain logging information in ACLOG

Laurie, VK3AMA <groups08@...>
 

On 26/01/2017 11:18 AM, William Wagaman wwagaman@hotmail.com [HamApps] wrote:

Hello Bill here N3GTY the HB9HQX version is 4.3 When the log window appears it does not show the signal report but does show the Mode Time Date Band and that it has been successfully logged. Also the version of JTAlert is 2.9.0 and ACLog is 5.8.2 which I think is a beta version. Auto-Start is starting HB9HQX with no issues. I just thought of something from getting my Auto-Start up and running and Started ACLog Running as Administrator and it did Log correctly all but comments as in WSJT-X which gives the Mode and Report in comments field. As it stands I am happy with the addition of getting all but the comments field which may be the way it is designed to be.

I will attempt to send the report as soon as I make another contact Thanks in advance Bill N3GTY
Bill,

If HB9HQX is not displaying signal reports in its Log QSO window, then those missing values are not logged to the HB9HQX adi log file. It is that adi file that JTAlert reads to get the newest QSO for sending on to ACLog. The problem is with HB9HQX, not JTAlert.

There should be no need to start ACLog as Administrator, Running any of the applications as Administrator will likely cause security level permission mismatches between the applications producing unpredictable results, depending on which application is running with elevated privileges.

I'm not following you description of Comments not being logged. Which applications Comments are not getting logged by JTAlert?

de Laurie VK3AMA


locked Re: : Logging failure

Seb
 

I have one computer with an SDR that runs the latest versions of WSJT-X and JTAlertX. This PC is never shut off, runs on a UPS and for the most part has been up for months.

I have yet to see any lockups or crashes on either program.

73 de Sebastian, W4AS

On Jan 25, 2017, at 5:04 PM, 'Joe Subich, W4TV' lists@subich.com [HamApps] <hamapps@yahoogroups.com.au> wrote:


Laurie,

If I knew definitively which version started exhibiting this
behaviour I might be able to identify a probable cause.
Unfortunately, I did not note when the behavior began as I assumed
it was being generated by issues with the beta and RC versions of
WSJT-X 1.7.0 that I was using.

Sorry, unless I identify a definitive cause of the hangs, they are
likely go unresolved.
I have sent you session logs that followed a crash that occurred while
I was away during the mid portion of today. As typically happens,
JTAlertX stopped responding to anything other than the window controls
while I was away and the only course of action was to close the
Window [X] and then use Task Manager to end the remaining background
task (Audio & Visual Alerts for WSJT-x and JT65-HF).


73,

... Joe, W4TV


On 1/25/2017 4:33 PM, 'Laurie, VK3AMA' groups08@vkdxer.com [HamApps] wrote:


On 26/01/2017 12:13 AM, 'Joe Subich, W4TV' lists@subich.com [HamApps] wrote:
I find that JTAlert (the last two or three versions) will hang if left
running 24 x 7. Often after the computer has been idle (monitoring)
for several hours. When I notice the hang, it becomes necessary to
use Task Manager to end task and restart JTAlert.

73,

... Joe, W4TV
Joe,

This is the first I have heard of this consistent hanging behaviour.
Hard to guess the root cause if it has been happening for the last few
versions. If I knew definitively which version started exhibiting this
behaviour I might be able to identify a probable cause.

There are several high-use JTAlert users running multiple instances 24x7
that are not reporting this sort of consistent hang.

There has been some problematic behaviours creeping into JTAlert over
the last year or so. The only consistency with the reports is that the
behaviours are random, affecting different parts of JTAlert operation,
different Windows versions, often erroneous non-declared variable errors
or code line numbers, only affecting a small number of users and
non-reproducable in a test environment.

I have long suspected the Compiler used for JTAlert is the root-cause. I
am pushing its limits and the number of hacks and workarounds to
overcome many if its limitations (single-threaded, non-object oriented
constructs, no support for async functions, uses old pre Win8 API calls)
has been increasing. This is why I am currently working on JTAlert V3, a
total rewrite of the code using a modern object-orientated
language/development environment.

Sorry, unless I identify a definitive cause of the hangs, they are
likely go unresolved.

de Laurie VK3AMA


locked Re: Retain logging information in ACLOG

William Wagaman <wwagaman@...>
 

Hello Bill here N3GTY the HB9HQX version is 4.3 When the log window appears it does not show the signal report but does show the Mode Time Date Band and that it has been successfully logged. Also the version of JTAlert is 2.9.0 and ACLog is 5.8.2 which I think is a beta version. Auto-Start is starting HB9HQX with no issues. I just thought of something from getting my Auto-Start up and running and Started ACLog Running as Administrator and it did Log correctly all but comments as in WSJT-X which gives the Mode and Report in comments field. As it stands I am happy with the addition of getting all but the comments field which may be the way it is designed to be.

I will attempt to send the report as soon as  I make another contact Thanks in advance Bill N3GTY


On 1/25/2017 6:21 PM, 'Laurie, VK3AMA' groups08@... [HamApps] wrote:
 



On 26/01/2017 9:45 AM, William Wagaman wwagaman@... [HamApps] wrote:
> Hello all Bill here N3GTY new to JTalert and to the group. I setup
> JTalert and ACLOG with HB9HQX all are working as they should ACLOG
> populates all information from HB9HQX and JTalert, after logging the QSO
> with HB9HQX it logs and retains only the callsign of the contact,
> date, band and frequency. I need to enter the signal report name county.
> I have WSJT-X working no issued it populates ACLOG with all data needed.
> Thanks in advance for any assistance 73 for now Bill N3GTY
Bill,

What version of HB9HQX?

Does the "Log QSO" window of HB9HQX correctly show the signal reports?

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to
send me your Configuration and Session files for analysis. Include a
note of the Callsign and the UTC time when you performed a logging
action and the reports didn't make it into the ACLog log.

de Laurie VK3AMA



locked JTAlert

Robert
 

Where can we find the users manual.


73
WA6MBL bob


Sent from my iPad


locked Re: Retain logging information in ACLOG

Laurie, VK3AMA <groups08@...>
 

On 26/01/2017 9:45 AM, William Wagaman wwagaman@hotmail.com [HamApps] wrote:
Hello all Bill here N3GTY new to JTalert and to the group. I setup
JTalert and ACLOG with HB9HQX all are working as they should ACLOG
populates all information from HB9HQX and JTalert, after logging the QSO
with HB9HQX it logs and retains only the callsign of the contact,
date, band and frequency. I need to enter the signal report name county.
I have WSJT-X working no issued it populates ACLOG with all data needed.
Thanks in advance for any assistance 73 for now Bill N3GTY
Bill,

What version of HB9HQX?

Does the "Log QSO" window of HB9HQX correctly show the signal reports?

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Include a note of the Callsign and the UTC time when you performed a logging action and the reports didn't make it into the ACLog log.

de Laurie VK3AMA


locked Retain logging information in ACLOG

William Wagaman <wwagaman@...>
 

Hello all Bill here N3GTY new to JTalert and to the group. I setup
JTalert and ACLOG with HB9HQX all are working as they should ACLOG
populates all information from HB9HQX and JTalert, after logging the QSO
with HB9HQX it logs and retains only the callsign of the contact,
date, band and frequency. I need to enter the signal report name county.
I have WSJT-X working no issued it populates ACLOG with all data needed.
Thanks in advance for any assistance 73 for now Bill N3GTY


locked Re: : Logging failure

Joe Subich, W4TV
 

Laurie,

If I knew definitively which version started exhibiting this
behaviour I might be able to identify a probable cause.
Unfortunately, I did not note when the behavior began as I assumed
it was being generated by issues with the beta and RC versions of
WSJT-X 1.7.0 that I was using.

Sorry, unless I identify a definitive cause of the hangs, they are
likely go unresolved.
I have sent you session logs that followed a crash that occurred while
I was away during the mid portion of today. As typically happens,
JTAlertX stopped responding to anything other than the window controls
while I was away and the only course of action was to close the
Window [X] and then use Task Manager to end the remaining background
task (Audio & Visual Alerts for WSJT-x and JT65-HF).


73,

... Joe, W4TV


On 1/25/2017 4:33 PM, 'Laurie, VK3AMA' groups08@vkdxer.com [HamApps] wrote:


On 26/01/2017 12:13 AM, 'Joe Subich, W4TV' lists@subich.com [HamApps] wrote:
I find that JTAlert (the last two or three versions) will hang if left
running 24 x 7. Often after the computer has been idle (monitoring)
for several hours. When I notice the hang, it becomes necessary to
use Task Manager to end task and restart JTAlert.

73,

... Joe, W4TV
Joe,

This is the first I have heard of this consistent hanging behaviour.
Hard to guess the root cause if it has been happening for the last few
versions. If I knew definitively which version started exhibiting this
behaviour I might be able to identify a probable cause.

There are several high-use JTAlert users running multiple instances 24x7
that are not reporting this sort of consistent hang.

There has been some problematic behaviours creeping into JTAlert over
the last year or so. The only consistency with the reports is that the
behaviours are random, affecting different parts of JTAlert operation,
different Windows versions, often erroneous non-declared variable errors
or code line numbers, only affecting a small number of users and
non-reproducable in a test environment.

I have long suspected the Compiler used for JTAlert is the root-cause. I
am pushing its limits and the number of hacks and workarounds to
overcome many if its limitations (single-threaded, non-object oriented
constructs, no support for async functions, uses old pre Win8 API calls)
has been increasing. This is why I am currently working on JTAlert V3, a
total rewrite of the code using a modern object-orientated
language/development environment.

Sorry, unless I identify a definitive cause of the hangs, they are
likely go unresolved.

de Laurie VK3AMA



------------------------------------
Posted by: "Laurie, VK3AMA" <groups08@vkdxer.com>
------------------------------------


------------------------------------

Yahoo7 Groups Links




locked Re: Wanted Prefix Alert

Laurie, VK3AMA <groups08@...>
 

John,

Being overwhelmed by multiple alert types is the curse of the new JTMode/JTAlert operator ;-)

When first starting out, it is best to try and avoid having all alerts types enabled (or set a CQ only filter) to avoid the visual/audio overload from JTAlert where every decode seems to produce one or more alerts. After a few weeks of activity, they will reduce as you start to see more Worked B4 decodes.
 

You could try changing the Alert priority of the Wanted Prefix alert so that other Alert types will take precedence.

As the number of unique prefixes is very large, I suggest you may want to disable the PFX alerts and
focus on the alert types for a few weeks (or more depending on your activity level) you will be accumulating many new Prefixes through chasing other alert types. Once the number of alerts start to reduce and the B4's increase, turn the PFX alerts back on, setting their Tracking to "Any Mode" and "Any Band" to help keep the number down. Then at some point in the future, as the number of alerts has reduced again, you may want to change the Tracking to "By Mode" and "By Band" depending on your ultimate PFX goal.

de Laurie VK3AMA
   


On 26/01/2017 3:36 AM, jes148@... [HamApps] wrote:

Is there a way to alert on only a few wanted prefixes? I only have about 2800 log entries so if I turn Wanted Prefix on my display is mostly alerts. I though of using Wanted Call Sign but it doesn't seem to take wildcards.

Thanks
73
John, KA5BJC


locked Re: : Logging failure

Laurie, VK3AMA <groups08@...>
 

On 26/01/2017 12:13 AM, 'Joe Subich, W4TV' lists@subich.com [HamApps] wrote:
I find that JTAlert (the last two or three versions) will hang if left
running 24 x 7. Often after the computer has been idle (monitoring)
for several hours. When I notice the hang, it becomes necessary to
use Task Manager to end task and restart JTAlert.

73,

... Joe, W4TV
Joe,

This is the first I have heard of this consistent hanging behaviour. Hard to guess the root cause if it has been happening for the last few versions. If I knew definitively which version started exhibiting this behaviour I might be able to identify a probable cause.

There are several high-use JTAlert users running multiple instances 24x7 that are not reporting this sort of consistent hang.

There has been some problematic behaviours creeping into JTAlert over the last year or so. The only consistency with the reports is that the behaviours are random, affecting different parts of JTAlert operation, different Windows versions, often erroneous non-declared variable errors or code line numbers, only affecting a small number of users and non-reproducable in a test environment.

I have long suspected the Compiler used for JTAlert is the root-cause. I am pushing its limits and the number of hacks and workarounds to overcome many if its limitations (single-threaded, non-object oriented constructs, no support for async functions, uses old pre Win8 API calls) has been increasing. This is why I am currently working on JTAlert V3, a total rewrite of the code using a modern object-orientated language/development environment.

Sorry, unless I identify a definitive cause of the hangs, they are likely go unresolved.

de Laurie VK3AMA


locked Re: Help needed setting up new log book program

Dave AA6YQ
 

AA6YQ comments belo-w
-----Original Message-----
From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Wednesday, January 25, 2017 8:43 AM
To: HamApps@yahoogroups.com.au
Subject: RE: [HamApps] Help needed setting up new log book program

Sorry Dave. I made an assumption and of course it was wrong. My bad.

No problem, Dan.
73,

Dave, AA6YQ


locked Wanted Prefix Alert

John Singler
 

Is there a way to alert on only a few wanted prefixes? I only have about 2800 log entries so if I turn Wanted Prefix on my display is mostly alerts. I though of using Wanted Call Sign but it doesn't seem to take wildcards.
Thanks
73
John, KA5BJC



locked Re: Help needed setting up new log book program

Dan Malcolm <dmalcolm24@...>
 

Sorry Dave.  I made an assumption and of course it was wrong.  My bad.

 

_____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Tuesday, January 24, 2017 11:27 PM
To: HamApps@...
Subject: RE: [HamApps] Help needed setting up new log book program

 

 

>>>AA6YQ comments below

-----Original Message-----
From: HamApps@... [mailto:HamApps@...]
Sent: Tuesday, January 24, 2017 10:56 PM
To: HamApps@...
Subject: RE: [HamApps] Help needed setting up new log book program

I just went through a similar change. I have tried DX Keeper, ACLog, and Log4OM. So far Log4OM seems to suit me best. I don’t use FLdigi, but I do use DM-780, WSJT-X and JTAlertX. ACLog offers a 45 day trial, but then you have to pay for it. The other 2 are free, but ask for donations. Not unreasonable in my opinion.

>>>I have never requested or accepted donations for DXLab.

73,

Dave, AA6YQ


locked Re: : Logging failure

Michael Black
 

If you get a hang send in your session files via ?/Contact Support after you restart.
I would think if this was common would've seen it mentioned on the list

de Mike W9MDB
 



From: "'Joe Subich, W4TV' lists@... [HamApps]"
To: HamApps@...
Sent: Wednesday, January 25, 2017 7:13 AM
Subject: Re: [HamApps] Re:: Logging failure

 

> It's definitely not Log4OM's problem and this problem should show up
> on other loggers too.

I have never seen the problem with JTAlert and DXKeeper.

> I keep mine running 24x7.

I find that JTAlert (the last two or three versions) will hang if left
running 24 x 7. Often after the computer has been idle (monitoring)
for several hours. When I notice the hang, it becomes necessary to
use Task Manager to end task and restart JTAlert.

73,

... Joe, W4TV

On 1/25/2017 8:03 AM, Black Michael mdblack98@... [HamApps] wrote:
> Nope...not a communicator problem....not 100% sure but seems to happen after being on overnight and 1st QSO of day.I've tracked down some possible problems and am testing a potential fix from Laurie now but may take a week or so before I'd call it "fixed" since it doesn't happen very often.
> It's definitely not Log4OM's problem and this problem should show up on other loggers too. But if you are the kind of operator that restart things every day you may not see the behavior. I keep mine running 24x7.
> de Mike W9MDB
>
> From: "ralfvoepel@... [HamApps]"
> To: HamApps@...
> Sent: Tuesday, January 24, 2017 5:43 PM
> Subject: [HamApps] Re:: Logging failure
>
> Hi Mike,
> I have the same setup and had the same problem. For some reason the communicator from Log4OM did not autostart. I always make sure it is running. Sometimes I have to stop and restart the communicator if it "misbehaves".
> That fixed my problem.
>
> 73,
> de KF5WGB - Ralf



locked Re: : Logging failure

Joe Subich, W4TV
 

It's definitely not Log4OM's problem and this problem should show up
on other loggers too.
I have never seen the problem with JTAlert and DXKeeper.

I keep mine running 24x7.
I find that JTAlert (the last two or three versions) will hang if left
running 24 x 7. Often after the computer has been idle (monitoring)
for several hours. When I notice the hang, it becomes necessary to
use Task Manager to end task and restart JTAlert.

73,

... Joe, W4TV


On 1/25/2017 8:03 AM, Black Michael mdblack98@yahoo.com [HamApps] wrote:
Nope...not a communicator problem....not 100% sure but seems to happen after being on overnight and 1st QSO of day.I've tracked down some possible problems and am testing a potential fix from Laurie now but may take a week or so before I'd call it "fixed" since it doesn't happen very often.
It's definitely not Log4OM's problem and this problem should show up on other loggers too. But if you are the kind of operator that restart things every day you may not see the behavior. I keep mine running 24x7.
de Mike W9MDB

From: "ralfvoepel@gmail.com [HamApps]" <HamApps@yahoogroups.com.au>
To: HamApps@yahoogroups.com.au
Sent: Tuesday, January 24, 2017 5:43 PM
Subject: [HamApps] Re:: Logging failure

Hi Mike,
I have the same setup and had the same problem. For some reason the communicator from Log4OM did not autostart. I always make sure it is running. Sometimes I have to stop and restart the communicator if it "misbehaves".
That fixed my problem.

73,
de KF5WGB - Ralf


locked Re: : Logging failure

Michael Black
 

Nope...not a communicator problem....not 100% sure but seems to happen after being on overnight and 1st QSO of day.
I've tracked down some possible problems and am testing a potential fix from Laurie now but may take a week or so before I'd call it "fixed" since it doesn't happen very often.

It's definitely not Log4OM's problem and this problem should show up on other loggers too.  But if you are the kind of operator that restart things every day you may not see the behavior.  I keep mine running 24x7.

de Mike W9MDB



From: "ralfvoepel@... [HamApps]"
To: HamApps@...
Sent: Tuesday, January 24, 2017 5:43 PM
Subject: [HamApps] Re:: Logging failure

 
Hi Mike,
I have the same setup and had the same problem. For some reason the communicator from Log4OM did not autostart. I always make sure it is running. Sometimes I have to stop and restart the communicator if it "misbehaves".
That fixed my problem.

73,
de KF5WGB - Ralf



locked Re: : Logging failure

NA4MM Paul St John
 

Mike I was using the same setup and the problem is with the communicator.  I used Log4OM for years and loved it but I just changed over to ACLog by N3FJP and it logs every time.
Wish you well.

73 de NA4MM  Paul


locked Re: Newby JT^% etc with HRD JTA 2.8.7 WSJT 1.6.0

Michael Black
 

You're most likely culprit is time sync.
Next is audio level.  You should really be asking on the WSJT-X yahoo group as this isn't a HamApps problem.

Yyou don't say what OS or rig or sound path that you have...so I'll assume Windows for your OS.

Check your time here:

You'll want to use something like Meinberg NTP or Dimension 4 to sync your time.

Your audio should be set so that the receive slider bar is in the middle...and adjust your rig & soundcard levels so the you see about 30dB with the slider at that middle level.

de Mike W9MDB




From: "4dbw6gkxkjjuwmzofoxf7hgaktsw2bkos5krwbgf@... [HamApps]"
To: HamApps@...
Sent: Wednesday, January 25, 2017 4:02 AM
Subject: [HamApps] Newby JT^% etc with HRD JTA 2.8.7 WSJT 1.6.0

 
Hi all I cannot get a green light on Radio Settings Test PT? also I am receiving signals but no band activity being received on WSJT-X?
I know there is a problem with JTA and HRD but I have only just renewed subscription and it suits my purpose. Can anyone help with advice?
Derek