Date   

locked Re: Feature reqest

HamApps Support (VK3AMA)
 

On 12/02/2018 4:27 AM, Randy wrote:

Thanks, mike.   I have not checked that thread out yet...

Rather than 'set up a call' - can we just change RX frequency?   That's really all I'm looking for - an easy way to tune my RX without scrolling up through a mile long list of decodes to locate the frequency.   I have no problem manually setting up the call... a little help tuning RX would go a mile.

~Randy
K6RP


Randy,

JTAlert is already sending the correct UDP request to WSJT-X regardless of the decode type double-clicked. The filtering to only accept the UDP request for CQ only decodes is happening within WSJT-X. If WSJT-X is extended to allow non-CQ decode double-clicks than it will only require you to upgrade WSJT-X.

de Laurie VK3AMA
   


locked Re: Feature reqest

Randy
 

Thank you Laurie for explaining that.

How about we can display the RX frequency in the info bubble when hovering over a call?

Literally any help I can get finding the station in the waterfall will be very helpful.

---
~Randy
K6RP


On 02/11/2018 10:06 am, HamApps Support (VK3AMA) wrote:

On 12/02/2018 4:27 AM, Randy wrote:

Thanks, mike.   I have not checked that thread out yet...

Rather than 'set up a call' - can we just change RX frequency?   That's really all I'm looking for - an easy way to tune my RX without scrolling up through a mile long list of decodes to locate the frequency.   I have no problem manually setting up the call... a little help tuning RX would go a mile.

~Randy
K6RP


Randy,

JTAlert is already sending the correct UDP request to WSJT-X regardless of the decode type double-clicked. The filtering to only accept the UDP request for CQ only decodes is happening within WSJT-X. If WSJT-X is extended to allow non-CQ decode double-clicks than it will only require you to upgrade WSJT-X.

de Laurie VK3AMA
   


locked Re: WES logging

HamApps Support (VK3AMA)
 

On 12/02/2018 2:02 AM, Dave Godfrey wrote:
I am currently logging to HRD and want to also send log info to QRZ log. Can't find any settings for QRZ logging.

Dave NY5A
Dave,

If your running a version of HRD that doesn't support uploading to QRZ log, visit the JTAlert Settings, "Web Services -> Online Logbooks" section and setup the QRZ logging. Be aware that to use your QRZ logbook you need to have a QRZ xml subscription.

de Laurie VK3AMA
   


locked Re: Feature reqest

Jim Cooper
 

On 11 Feb 2018 at 9:27, Randy wrote:

That's really all I'm looking for - an easy
way to tune my RX without scrolling up through a
mile long list of decodes to locate the
frequency. I have no problem manually
setting up the call... a little help tuning RX
would go a mile.
I definitely agree !!


locked Re: Feature reqest

Randy
 

Thanks, mike.   I have not checked that thread out yet...

Rather than 'set up a call' - can we just change RX frequency?   That's really all I'm looking for - an easy way to tune my RX without scrolling up through a mile long list of decodes to locate the frequency.   I have no problem manually setting up the call... a little help tuning RX would go a mile.

~Randy
K6RP


On 02/11/2018 9:19 am, Michael Black via Groups.Io wrote:

That's a restriction in WSJTX and not Jtalert. This was just discussed on the WSJTX list as a possible change to allow this.   Question is the best way to avoid QRM needs to be determined. The easier we make things the more likely QRM. 

De Mike W9MDB 


On Sun, Feb 11, 2018 at 11:12 AM, Randy
<amps@...> wrote:
Hello Laurie,
 
Currently JTalert only responds to mouse clicks on CQ calls.  Often,
especially when the band is very crowded or there is a rare DXCC, the
station you are trying to call rarely ever calls CQ.  On top of that,
there are so many other stations on the freqency it's nearly impossible
to locate the desired station/frequency in WSJT-X before the next round
of calls decode.
 
I propose that double clicking a non-CQ call still set WSJT-X up for a
call, but not enable TX.  This way I can leave JTalert, and monitor the
QSO RX freq in WSJT-X (looking for the 73), and execute the call
manually.
 
Thanks for the awesome work Laurie...
 
~Randy
K6RP
 
 
 
 


locked Re: Feature reqest

Michael Black
 

That's a restriction in WSJTX and not Jtalert. This was just discussed on the WSJTX list as a possible change to allow this.   Question is the best way to avoid QRM needs to be determined. The easier we make things the more likely QRM. 

On Sun, Feb 11, 2018 at 11:12 AM, Randy
<amps@...> wrote:
Hello Laurie,

Currently JTalert only responds to mouse clicks on CQ calls.  Often,
especially when the band is very crowded or there is a rare DXCC, the
station you are trying to call rarely ever calls CQ.  On top of that,
there are so many other stations on the freqency it's nearly impossible
to locate the desired station/frequency in WSJT-X before the next round
of calls decode.

I propose that double clicking a non-CQ call still set WSJT-X up for a
call, but not enable TX.  This way I can leave JTalert, and monitor the
QSO RX freq in WSJT-X (looking for the 73), and execute the call
manually.

Thanks for the awesome work Laurie...

~Randy
K6RP





locked Re: WES logging

Brian (N2MLP)
 

IN LOGBOOK/CONFIGURE/QRZ.COM

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Brian (N2MLP)
Sent: Sunday, February 11, 2018 10:49 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] WES logging

 

It’s in HRD

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Dave Godfrey
Sent: Sunday, February 11, 2018 10:02 AM
To: Support@HamApps.groups.io
Subject: [HamApps] WES logging

 

I am currently logging to HRD and want to also send log info to QRZ log. Can't find any settings for QRZ logging.

 

Dave NY5A


locked Feature reqest

Randy
 

Hello Laurie,

Currently JTalert only responds to mouse clicks on CQ calls. Often, especially when the band is very crowded or there is a rare DXCC, the station you are trying to call rarely ever calls CQ. On top of that, there are so many other stations on the freqency it's nearly impossible to locate the desired station/frequency in WSJT-X before the next round of calls decode.

I propose that double clicking a non-CQ call still set WSJT-X up for a call, but not enable TX. This way I can leave JTalert, and monitor the QSO RX freq in WSJT-X (looking for the 73), and execute the call manually.

Thanks for the awesome work Laurie...

~Randy
K6RP


locked Re: Where does the data come from for the lookup?

Lawrence Godek
 

Brian, I'd think that as long as you updated your GRID locator in QRZ.com when you change locations, if the grid does indeed change, would be all you need to do.  My thoughts for correct grid logging since QRZ.com is where the data comes from.

Larry
W0OGH


On Sun, Feb 11, 2018 at 7:25 AM, Brian Kassel <briank7re@...> wrote:
Laurie Said:
"If you want JTAlert to provide accurate State alerts I can put in-place a Callsign override in the FCC Data import code so that each

time the Callsigns database is updated (as well as HamSpots,net) your State is recorded per your last request. I already do this for

6 other Callsigns, adding another is not a problem.

If you request an override, please be aware that the override is permanent until you request its removal. It is a manual process (not

onerous, 5 seconds to comment out the code). It is not automated based on date or some online service lookup change detection. You

simply request via email that the current override be removed or changed."

Apparently I had been dealing with all of the wrong sources in my quest to get the state changed.
I was not aware of the process in which state names are determined.

Your suggestion as to how to get an over ride for the state names was unknown to me, so
I ended up pursuing the wrong  sources.

I now understand the process, and I thank you for your direction.

Since my state changes and locations will change from week to week, I am not sure
that I should bother you with the constant updates that would be required.

Thanks again for the excellent reply, and for your time in supporting the applcation.

I will think on it a bit.

--
Sent by my Raspberry PI3
Brian K7RE



locked Re: WES logging

Brian (N2MLP)
 

It’s in HRD

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Dave Godfrey
Sent: Sunday, February 11, 2018 10:02 AM
To: Support@HamApps.groups.io
Subject: [HamApps] WES logging

 

I am currently logging to HRD and want to also send log info to QRZ log. Can't find any settings for QRZ logging.

 

Dave NY5A


locked WES logging

Dave Godfrey
 

I am currently logging to HRD and want to also send log info to QRZ log. Can't find any settings for QRZ logging.

Dave NY5A


locked Re: Where does the data come from for the lookup?

Brian Kassel K7RE
 

Laurie Said:
"If you want JTAlert to provide accurate State alerts I can put in-place a Callsign override in the FCC Data import code so that each

time the Callsigns database is updated (as well as HamSpots,net) your State is recorded per your last request. I already do this for

6 other Callsigns, adding another is not a problem.

If you request an override, please be aware that the override is permanent until you request its removal. It is a manual process (not

onerous, 5 seconds to comment out the code). It is not automated based on date or some online service lookup change detection. You

simply request via email that the current override be removed or changed."

Apparently I had been dealing with all of the wrong sources in my quest to get the state changed.
I was not aware of the process in which state names are determined.

Your suggestion as to how to get an over ride for the state names was unknown to me, so
I ended up pursuing the wrong  sources.

I now understand the process, and I thank you for your direction.

Since my state changes and locations will change from week to week, I am not sure
that I should bother you with the constant updates that would be required.

Thanks again for the excellent reply, and for your time in supporting the applcation.

I will think on it a bit.

--
Sent by my Raspberry PI3
Brian K7RE


locked Re: #FT8 #FT8

Michael Black
 

A java update should have nothing to do with JTAlert (or most any other ham program).

Sounds to me like you may have something corrupted.

So try renaming the config.sqlite file to config.sqlite.broke to start with a new config in this directory.

C:\Users\[username]\AppData\Local\HamApps\[callsign]\config\JTAlertX)

If that works you can try copying one of the backup configs (probably the most recent one to start with) until you find one that works.

-----------------------------------
Michael D. Black


On Saturday, February 10, 2018, 11:31:17 PM CST, Mike Shelby <mshelby@...> wrote:


JTAlertX 2.10.14, hangs on startup

 

Looks like this is an issue with latest Java runtime version 8 update 161. Problems started today, right after updated to latest Java runtime.


locked #FT8 #FT8

Mike Shelby
 

JTAlertX 2.10.14, hangs on startup

 

Looks like this is an issue with latest Java runtime version 8 update 161. Problems started today, right after updated to latest Java runtime.


locked Re: Log4om issue...Zone 5 default bug...

Tom WA9WSJ
 

Hi Jim,

Ahh better understanding now, thanks!

Interesting, I asked one gent about his zone and even though the map showed him in one zone, he actually was in an adjacent zone that the map didn't show. Sort of a bump in the line which captured him. 

So I have a couple more questions, if you know, :)

1. If I sign up for the xml service, will that update the zones in my logging program if I do an update? I would think so.
2. If so, will it update those guys who didn't add the zone info on their qrz lookup page?

thanks again,

Tom



From: Jim Preston <jpreston1@...>
To: Support@HamApps.groups.io
Sent: Saturday, February 10, 2018 6:57 PM
Subject: Re: [HamApps] Log4om issue...Zone 5 default bug...

Tom,

Many other countries will show correct zones, simply because the country
is only in one zone. Japan, zone 25, is just one example. The problem
shows up when a country can have more than one zone. The US is one
example, but there are others. Since ham calls in the US are not tied to
any one region, it isn't easy to know what the zone is, just from the
call. Even knowing the state doesn't always help, since some states are
in more than one zone, depending on where in the state you are.

73,

Jim N6VH


On 2/10/2018 5:22 PM, Tom WA9WSJ via Groups.Io wrote:
> Hi Jim,
>
> Thanks for the info, makes sense now. Funny how the zones outside of the
> US seem to be okay. That's what kind of threw me on this.
>
> 73 Tom
>
>
>
>
> ------------------------------------------------------------------------
> *From:* Jim Preston <jpreston1@...>
> *Sent:* Saturday, February 10, 2018 3:36 PM
> *Subject:* Re: [HamApps] Log4om issue...Zone 5 default bug...
>
> Tom,
>
> As per my answer on the Log4OM forum, if you aren't a paid subscriber to
> QRZ, the zones might not get updated in Log4OM.
>
> 73,
>
> Jim N6VH
>
>
> On 2/9/2018 6:50 PM, Tom WA9WSJ via Groups.Io wrote:
>  > Hi Jim,
>  >
>  > I was finally able to get back at this. i checked your questions in the
>  > forum and answered you as well as Laurie.
>  >
>  > Thank you both for helping with this!
>  >
>  > 73 Tom
>  >
>  >
>  > ------------------------------------------------------------------------
>  > *From:* Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io
>  > *Sent:* Sunday, February 4, 2018 10:18 PM
>  > *Subject:* Re: [HamApps] Log4om issue
>  >
>  > I just submitted a bug report with an example of this problem.
>  > I just had one entry logged as Zone 5 and there was a prior entry in my
>  > log with him in Zone 4 where he should be.  So hopefully Laurie can
>  > figure out what's going on.
>  >
>  > It got the ITU wrong too.
>  >
>  > de Mike W9MDB
>  >
>  > On Sunday, February 4, 2018, 11:06:57 PM CST, Jim Preston
>  > <jpreston1@... <mailto:jpreston1@...>> wrote:
>  >
>  >
>  > Tom,
>  >
>  > I'm surprised that you didn't get an answer on the Log4OM Forum. The
>  > support people there are usually pretty quick to help.
>  >
>  > I sent a reply on the Log4OM forum. Please check it out there. I don't
>  > know if I can help, but maybe the discussion over there will get some
> help.
>  >
>  > 73,
>  >
>  > Jim N6VH
>  >
>  >
>  > On 2/4/2018 8:11 PM, Tom WA9WSJ via Groups.Io wrote:
>  >  > Hello Gents,
>  >  >
>  >  > I'm posting here because I have not gotten any answers from the log4om
>  >  > reflector or their forum since I posted on Jan 15th.
>  >  >
>  >  > Maybe someone has an idea to this?
>  >  >
>  >  >
>  >  > I checked some log entries recently for the cq zone numbers and found
>  >  > many that are actually in zone 3 and 4, are listed as in zone 5. I
>  >  > believe that all continental US contacts are defaulting to zone 5.
>  >  >
>  >  > So I did some searching for anything related to this in the forum and
>  >  > found some discussion about it concerning that the original qrz entry
>  >  > could be wrong but I need to add the following because it may be
> another
>  >  > problem.
>  >  >
>  >  > I verified that QRZ has the right zone info for a couple of qso's
> and so
>  >  > I did an "update" for these qso's in log40m but the zone entry in the
>  >  > log didn't change to the correct number which was shown on qrz.
>  >  >
>  >  > I can understand that if QRZ didn't show any zone info for a
> particular
>  >  > call, that maybe it would default, but I verified that the correct
> info
>  >  > was listed.
>  >  >
>  >  > I'm using the current versions of all three: WSJT-X ft-8 program,
>  >  > JTAlert program and log4om.
>  >  >
>  >  > Any thought about this?
>  >  >
>  >  > Thanks, Tom
>  >  >
>  >
>  >
>  >
>  >
>  >
>  >
>
>
>
>
>
>






locked Re: Log4om issue...Zone 5 default bug...

Jim N6VH
 

Tom,

Many other countries will show correct zones, simply because the country is only in one zone. Japan, zone 25, is just one example. The problem shows up when a country can have more than one zone. The US is one example, but there are others. Since ham calls in the US are not tied to any one region, it isn't easy to know what the zone is, just from the call. Even knowing the state doesn't always help, since some states are in more than one zone, depending on where in the state you are.

73,

Jim N6VH

On 2/10/2018 5:22 PM, Tom WA9WSJ via Groups.Io wrote:
Hi Jim,
Thanks for the info, makes sense now. Funny how the zones outside of the US seem to be okay. That's what kind of threw me on this.
73 Tom
------------------------------------------------------------------------
*From:* Jim Preston <jpreston1@cox.net>
*To:* Support@HamApps.groups.io
*Sent:* Saturday, February 10, 2018 3:36 PM
*Subject:* Re: [HamApps] Log4om issue...Zone 5 default bug...
Tom,
As per my answer on the Log4OM forum, if you aren't a paid subscriber to
QRZ, the zones might not get updated in Log4OM.
73,
Jim N6VH
On 2/9/2018 6:50 PM, Tom WA9WSJ via Groups.Io wrote:
> Hi Jim,
>
> I was finally able to get back at this. i checked your questions in the
> forum and answered you as well as Laurie.
>
> Thank you both for helping with this!
>
> 73 Tom
>
>
> ------------------------------------------------------------------------
> *From:* Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io
<mailto:yahoo.com@groups.io>>
> *To:* Support@HamApps.groups.io <mailto:Support@HamApps.groups.io>
> *Sent:* Sunday, February 4, 2018 10:18 PM
> *Subject:* Re: [HamApps] Log4om issue
>
> I just submitted a bug report with an example of this problem.
> I just had one entry logged as Zone 5 and there was a prior entry in my
> log with him in Zone 4 where he should be.  So hopefully Laurie can
> figure out what's going on.
>
> It got the ITU wrong too.
>
> de Mike W9MDB
>
> On Sunday, February 4, 2018, 11:06:57 PM CST, Jim Preston
> <jpreston1@cox.net <mailto:jpreston1@cox.net>> wrote:
>
>
> Tom,
>
> I'm surprised that you didn't get an answer on the Log4OM Forum. The
> support people there are usually pretty quick to help.
>
> I sent a reply on the Log4OM forum. Please check it out there. I don't
> know if I can help, but maybe the discussion over there will get some
help.
>
> 73,
>
> Jim N6VH
>
>
> On 2/4/2018 8:11 PM, Tom WA9WSJ via Groups.Io wrote:
>  > Hello Gents,
>  >
>  > I'm posting here because I have not gotten any answers from the log4om
>  > reflector or their forum since I posted on Jan 15th.
>  >
>  > Maybe someone has an idea to this?
>  >
>  >
>  > I checked some log entries recently for the cq zone numbers and found
>  > many that are actually in zone 3 and 4, are listed as in zone 5. I
>  > believe that all continental US contacts are defaulting to zone 5.
>  >
>  > So I did some searching for anything related to this in the forum and
>  > found some discussion about it concerning that the original qrz entry
>  > could be wrong but I need to add the following because it may be
another
>  > problem.
>  >
>  > I verified that QRZ has the right zone info for a couple of qso's
and so
>  > I did an "update" for these qso's in log40m but the zone entry in the
>  > log didn't change to the correct number which was shown on qrz.
>  >
>  > I can understand that if QRZ didn't show any zone info for a
particular
>  > call, that maybe it would default, but I verified that the correct
info
>  > was listed.
>  >
>  > I'm using the current versions of all three: WSJT-X ft-8 program,
>  > JTAlert program and log4om.
>  >
>  > Any thought about this?
>  >
>  > Thanks, Tom
>  >
>
>
>
>
>
>


locked Re: Log4om issue...Zone 5 default bug...

Tom WA9WSJ
 

Hi Jim,

Thanks for the info, makes sense now. Funny how the zones outside of the US seem to be okay. That's what kind of threw me on this.

73 Tom





From: Jim Preston <jpreston1@...>
To: Support@HamApps.groups.io
Sent: Saturday, February 10, 2018 3:36 PM
Subject: Re: [HamApps] Log4om issue...Zone 5 default bug...

Tom,

As per my answer on the Log4OM forum, if you aren't a paid subscriber to
QRZ, the zones might not get updated in Log4OM.

73,

Jim N6VH


On 2/9/2018 6:50 PM, Tom WA9WSJ via Groups.Io wrote:
> Hi Jim,
>
> I was finally able to get back at this. i checked your questions in the
> forum and answered you as well as Laurie.
>
> Thank you both for helping with this!
>
> 73 Tom
>
>
> ------------------------------------------------------------------------
> *From:* Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io>
> *Sent:* Sunday, February 4, 2018 10:18 PM
> *Subject:* Re: [HamApps] Log4om issue
>
> I just submitted a bug report with an example of this problem.
> I just had one entry logged as Zone 5 and there was a prior entry in my
> log with him in Zone 4 where he should be.  So hopefully Laurie can
> figure out what's going on.
>
> It got the ITU wrong too.
>
> de Mike W9MDB
>
> On Sunday, February 4, 2018, 11:06:57 PM CST, Jim Preston
> <jpreston1@...> wrote:
>
>
> Tom,
>
> I'm surprised that you didn't get an answer on the Log4OM Forum. The
> support people there are usually pretty quick to help.
>
> I sent a reply on the Log4OM forum. Please check it out there. I don't
> know if I can help, but maybe the discussion over there will get some help.
>
> 73,
>
> Jim N6VH
>
>
> On 2/4/2018 8:11 PM, Tom WA9WSJ via Groups.Io wrote:
>  > Hello Gents,
>  >
>  > I'm posting here because I have not gotten any answers from the log4om
>  > reflector or their forum since I posted on Jan 15th.
>  >
>  > Maybe someone has an idea to this?
>  >
>  >
>  > I checked some log entries recently for the cq zone numbers and found
>  > many that are actually in zone 3 and 4, are listed as in zone 5. I
>  > believe that all continental US contacts are defaulting to zone 5.
>  >
>  > So I did some searching for anything related to this in the forum and
>  > found some discussion about it concerning that the original qrz entry
>  > could be wrong but I need to add the following because it may be another
>  > problem.
>  >
>  > I verified that QRZ has the right zone info for a couple of qso's and so
>  > I did an "update" for these qso's in log40m but the zone entry in the
>  > log didn't change to the correct number which was shown on qrz.
>  >
>  > I can understand that if QRZ didn't show any zone info for a particular
>  > call, that maybe it would default, but I verified that the correct info
>  > was listed.
>  >
>  > I'm using the current versions of all three: WSJT-X ft-8 program,
>  > JTAlert program and log4om.
>  >
>  > Any thought about this?
>  >
>  > Thanks, Tom
>  >
>
>
>
>
>
>






locked Re: jtalert/dxk/and clublog

Anthony W. DePrato
 

Laurie
thanks for the help you were correct i had clublog auto loading thanks
73 Tony WA4JQS



At 11:09 PM 2/9/2018, you wrote:
On 10/02/2018 11:51 AM, Anthony W. DePrato wrote:

is anyone else finding this problem ?
i am running dxlab.. wsjt-x jt alert.
if i run just wsjt-x and dxlab when i upload my logs to clublog then i
get
a message back saying i have x number of NEW qso's uploaded. BUT if i
have
jt alert running also and upload my qso's from dxkeeper to clublog i get
a
message back saying

NO NEW QSO'S WERE UPLOADED. i may very well have something set wrong But
what ?
thanks for any help

73 Tony
WA4JQS
Tony,

Sounds like you may have JTAlert set to auto-upload new QSOs to ClubLog and then when you upload them again from DXKeeper you get the "No New QSOs" message.

You can turn off JTAlert uploading. Visit the Settings, Web Services -> Online Logbooks section.

de Laurie VK3AMA
   

[]  Virus-free. www.avg.com

Anthony W.DePrato WA4JQS since 1962
CQ DX HALL OF FAME  # 35
DXCC HONOR ROLL
DXPEDITION OF THE YEAR 1992 VP8SSI
DXPEDITION OF THE YEAR 1993/1994 3Y0PI
VP8SSI 3Y0PI VP8BZL V31SS ZD8JQS
 WA4JQS/ZS1 WA4JQS/KC4 WA4JQS/4K1


locked Re: Log4om issue...Zone 5 default bug...

Jim N6VH
 

Tom,

As per my answer on the Log4OM forum, if you aren't a paid subscriber to QRZ, the zones might not get updated in Log4OM.

73,

Jim N6VH

On 2/9/2018 6:50 PM, Tom WA9WSJ via Groups.Io wrote:
Hi Jim,
I was finally able to get back at this. i checked your questions in the forum and answered you as well as Laurie.
Thank you both for helping with this!
73 Tom
------------------------------------------------------------------------
*From:* Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io>
*To:* Support@HamApps.groups.io
*Sent:* Sunday, February 4, 2018 10:18 PM
*Subject:* Re: [HamApps] Log4om issue
I just submitted a bug report with an example of this problem.
I just had one entry logged as Zone 5 and there was a prior entry in my log with him in Zone 4 where he should be.  So hopefully Laurie can figure out what's going on.
It got the ITU wrong too.
de Mike W9MDB
On Sunday, February 4, 2018, 11:06:57 PM CST, Jim Preston <jpreston1@cox.net> wrote:
Tom,
I'm surprised that you didn't get an answer on the Log4OM Forum. The
support people there are usually pretty quick to help.
I sent a reply on the Log4OM forum. Please check it out there. I don't
know if I can help, but maybe the discussion over there will get some help.
73,
Jim N6VH
On 2/4/2018 8:11 PM, Tom WA9WSJ via Groups.Io wrote:
> Hello Gents,
>
> I'm posting here because I have not gotten any answers from the log4om
> reflector or their forum since I posted on Jan 15th.
>
> Maybe someone has an idea to this?
>
>
> I checked some log entries recently for the cq zone numbers and found
> many that are actually in zone 3 and 4, are listed as in zone 5. I
> believe that all continental US contacts are defaulting to zone 5.
>
> So I did some searching for anything related to this in the forum and
> found some discussion about it concerning that the original qrz entry
> could be wrong but I need to add the following because it may be another
> problem.
>
> I verified that QRZ has the right zone info for a couple of qso's and so
> I did an "update" for these qso's in log40m but the zone entry in the
> log didn't change to the correct number which was shown on qrz.
>
> I can understand that if QRZ didn't show any zone info for a particular
> call, that maybe it would default, but I verified that the correct info
> was listed.
>
> I'm using the current versions of all three: WSJT-X ft-8 program,
> JTAlert program and log4om.
>
> Any thought about this?
>
> Thanks, Tom
>


locked Re: Randomly get this error msg and other

Morris WA4MIT
 
Edited

What you say makes sense Laurie I have had memory use problems I have to restart computer sometimes to keep from having problems. I do not have any vacant memory slots but do have 8GB plus put a USB stick to be used expressly for memory which added 4GB for what that is worth. I checked my Alert settings and yes I have the "CQ only" checked will run a test and see what happens but it seemed to be showing grid alerts for non-CQ stations last time I used it earlier today. If it is still doing this will send report. update added here I think what I was seeing on the CQ`s was due to filters I use within JTDX removing those filters showed the Alert filter to be working properly, JTDX was removing B4 CQ`s from screen I did not catch that at first my bad. Thank you my friend
73 wa4mit

18021 - 18040 of 36991