Date   

locked Re: Alert with JTDX

Tom Melvin
 

Dave

MSHV and JTAlert - how did you manage that? - I was under the belief that JTAlert does not support MSHV due to MSHV not being standard on the UDP messages.

Tom
GM8MJV


On 5 Feb 2021, at 15:52, Dave Tucker Nu4N <dwtucker19@...> wrote:

Kinda strange but while its trying to load it say my DXLAB logbook is running?  I have a qrp stn that I use MSHV on with version of Alert 2.11.5. Works perfectly.
I am using MSHV  on my qro stn and get the error While trying to load the latest version which is my Windows 7 laptop.

--
DAVE NU4N


locked Re: Alert with JTDX

 

Got it running somehow. Thanks for the help.
--
DAVE NU4N


locked Re: More CQ Marathon info

Jim N6VH
 


On 2/5/2021 6:16 AM, Phil Cooper via groups.io wrote:

Hi Steve,

 

For that call, it was a Marathon alert first and foremost.I have new Marathon entities set to a specific colour, and that is what it showed, and said.

 

Given that this call was previously worked on another band, it should not have given me a new Marathon alert.

 

I already have ZA worked, confirmed and verified on 30m, it should not have alerted me for a Wanted Prefix or DXCC, and that was not the alert type. I don't have grids set as an alert, so it won't have been that.

 

73 de Phil GU0SUP


Phil,

The Auto Clear is permanent.

You might have already done this, but you might want to make certain that none of the relevant settings have changed. IOW, Auto Clear is still checked, no QSL for Marathon, Any Band, Any Mode. They shouldn't have changed, but it might be worth a check.

Also, go to Settings - CQ Marathon, and see if Albania is listed in the "Not Wanted" or "Wanted" listing.

Even if you have already done thes, it is sometimes a good idea to a double, or even triple check.

73,

Jim N6VH



locked Re: Alert with JTDX

 

Kinda strange but while its trying to load it say my DXLAB logbook is running?  I have a qrp stn that I use MSHV on with version of Alert 2.11.5. Works perfectly.
I am using MSHV  on my qro stn and get the error While trying to load the latest version which is my Windows 7 laptop.

--
DAVE NU4N


locked Re: Alert with JTDX

 

Yes Dave I am. I deleted the first try and then reinstalled same problem. And  its the blue icon.
Thanks for ur reply 73
--
DAVE NU4N


locked Re: Transverter support #FT8

Michael Black
 

Seems to me WSJT-X should be reporting the correct frequency since it knows what's going on.

Mike W9MDB




On Friday, February 5, 2021, 08:58:20 AM CST, Tom Melvin <tom@...> wrote:


All

Not sure if this can be fixed/worked around - will depend I suspect on UDP message content

Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the rig to.

JTAlert reports the freq the rig is set to - is there a way to get JTAlert to report rig + offset?

2320 - offset (of  -2174) gives IF of 146 - JTAlert report 2m - which is correct for the rig but not to operating freq

Tom
GM8MJV


locked Transverter support #FT8

Tom Melvin
 

All

Not sure if this can be fixed/worked around - will depend I suspect on UDP message content

Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the rig to.

JTAlert reports the freq the rig is set to - is there a way to get JTAlert to report rig + offset?

2320 - offset (of  -2174) gives IF of 146 - JTAlert report 2m - which is correct for the rig but not to operating freq

Tom
GM8MJV


locked Re: Alert with JTDX

Dave Garber
 

Are you using the correct coloured jtalert shortcut?


On Fri., Feb. 5, 2021, 3:46 a.m. Dave Tucker Nu4N, <dwtucker19@...> wrote:
Cant load alert to JTDX even tho JTDX is up and running.
Thanks
--
DAVE NU4N


locked Re: More CQ Marathon info

Phil Cooper
 

Hi Steve,

 

For that call, it was a Marathon alert first and foremost.I have new Marathon entities set to a specific colour, and that is what it showed, and said.

 

Given that this call was previously worked on another band, it should not have given me a new Marathon alert.

 

I already have ZA worked, confirmed and verified on 30m, it should not have alerted me for a Wanted Prefix or DXCC, and that was not the alert type. I don't have grids set as an alert, so it won't have been that.

 

73 de Phil GU0SUP

 

 

 

-----Original Message-----
From: "Steve, N3SL" <n3sl@...>
Sent: Friday, 5 February, 2021 12:07
To: Support@hamapps.groups.io
Subject: Re: [HamApps] More CQ Marathon info

Phil,
When the alert fires, what "reason" is JTAlert telling you?  (put your mouse pointer over the alerted call in the JTA window - a popup will tell you what triggered the alert - plus other info)
Sounds to me like ZA on 30 may have fired for a reason other than Marathon.

On Fri, Feb 5, 2021 at 5:04 AM Phil Cooper via groups.io <pcooper=suremail.gg@groups.io> wrote:

Laurie and the group,

 

I have checked the "Auto clear triggered Alert entry after logging", but I am still getting alerts for an entity that was logged on another band.

 

As an example, I worked ZA/IN3PPH on 40m FT8 yesterday (4th), but JTAlert is giving me an alert today when he was on 30m FT8.

 

The only way I can prevent this is to do a rebuild of my log, which was what I had to do before.

 

So, does the Auto clear only work for the same band/mode in the same session?

 

73 de Phil GU0SUP


locked Re: More CQ Marathon info

Steve, N3SL
 

Phil,

When the alert fires, what "reason" is JTAlert telling you?  (put your mouse pointer over the alerted call in the JTA window - a popup will tell you what triggered the alert - plus other info)
Sounds to me like ZA on 30 may have fired for a reason other than Marathon.

On Fri, Feb 5, 2021 at 5:04 AM Phil Cooper via groups.io <pcooper=suremail.gg@groups.io> wrote:

Laurie and the group,

 

I have checked the "Auto clear triggered Alert entry after logging", but I am still getting alerts for an entity that was logged on another band.

 

As an example, I worked ZA/IN3PPH on 40m FT8 yesterday (4th), but JTAlert is giving me an alert today when he was on 30m FT8.

 

The only way I can prevent this is to do a rebuild of my log, which was what I had to do before.

 

So, does the Auto clear only work for the same band/mode in the same session?

 

73 de Phil GU0SUP


locked More CQ Marathon info

Phil Cooper
 

Laurie and the group,

 

I have checked the "Auto clear triggered Alert entry after logging", but I am still getting alerts for an entity that was logged on another band.

 

As an example, I worked ZA/IN3PPH on 40m FT8 yesterday (4th), but JTAlert is giving me an alert today when he was on 30m FT8.

 

The only way I can prevent this is to do a rebuild of my log, which was what I had to do before.

 

So, does the Auto clear only work for the same band/mode in the same session?

 

73 de Phil GU0SUP


locked Re: About worked b4 #HRD

Dave Garber
 

those highlights look like they are from jtalert, so check you alert settings.  you may have another alert type  selected to activate before the 'B4' alert.   the order can be changed

Dave Garber
VE3WEJ / VE3IE


On Fri, Feb 5, 2021 at 4:39 AM jorge garcia via groups.io <ea8tl=yahoo.com@groups.io> wrote:
Hello

I have a problem with worked b4, see picture:


ALERT > CLEAR B4 CACHE was clicked multiple times , JTAlert was restart mutiple times, "Do not check or report logging success/failure" not enabled.
Im using Ham Radio Deluxe 6.
In general the worked b4 works fine, but with some callsign I have this problem.

Any idea?
Thank you....
JORGE G.
EA8TL


locked About worked b4 #HRD

Jorge EA8TL
 

Hello

I have a problem with worked b4, see picture:


ALERT > CLEAR B4 CACHE was clicked multiple times , JTAlert was restart mutiple times, "Do not check or report logging success/failure" not enabled.
Im using Ham Radio Deluxe 6.
In general the worked b4 works fine, but with some callsign I have this problem.

Any idea?
Thank you....
JORGE G.
EA8TL


locked Alert with JTDX

 

Cant load alert to JTDX even tho JTDX is up and running.
Thanks
--
DAVE NU4N


locked Re: JTAlert--->DXKeeper problem

HamApps Support (VK3AMA)
 

On 5/02/2021 10:16 am, Jim Monroe wrote:
Thanks for your reply and I thought you solved my problem as I didnt have those checkmarked, I have only been hitting the Logging button and down to the DXLab DXKeeper tab without double hitting the Logging button. So now when I log a qso it filles the name and qth window in DXKeeper but not the address square unless I manually hit the CBA button than it fills with name and complete address. So close....In JTAlert I do have check marked "log full qth from xml lookups" I assume that should include the complete address. 
Jim, n7esu

I don't know what you mean by double hitting the Log button. There should only be one Log button clicked. That is the "OK" button on the WSJT-X "Log QSO" window only. Once you click that JTAlert automatically picks up the new QSO data, combines it with what ever data it has retrieved from the XML lookup (which can be seen in the Log fields area of JTAlert), formats the necessary command and sends to DXKeeper.

If you don't hit the "OK" button, than JTAlert will never log anything, that operation is mandatory and is how it has always worked, otherwise JTAlert will have no knowledge of what you want to log.

The XML data JTAlert downloads is not populated in DXKeeper prior to logging, only the DX Call callsign is sent to DXKeeper prior to logging. You should not be trying to log from within DXKeeper, I suspect that is what your doing. Let JTAlert do its thing in passing the WSJT-X QSO data with the XML data onto to DXKeeper.

de Laurie VK3AMA


locked Re: JTAlert--->DXKeeper problem

Jim Monroe
 

Ron,
Thanks for your reply and I thought you solved my problem as I didnt have those checkmarked, I have only been hitting the Logging button and down to the DXLab DXKeeper tab without double hitting the Logging button. So now when I log a qso it filles the name and qth window in DXKeeper but not the address square unless I manually hit the CBA button than it fills with name and complete address. So close....In JTAlert I do have check marked "log full qth from xml lookups" I assume that should include the complete address. 
Jim, n7esu

On Thu, Feb 4, 2021 at 8:17 AM Ron W3RJW via groups.io <w3rjw=verizon.net@groups.io> wrote:
Perhaps checks missing?


--
73
Ron, W3RJW


locked Re: CQ Marathon query

Phil Cooper
 

Hi Laurie,

 

Wow, many thanks for clearing that up!

I was feeling very confused, and will re-set that tomorrow.

It was not set, partly because I wasn’t clear about the meaning, although it did seem to be the answer given by Jim N6VH. However, when you sent your reply, I was starting to think that it would mean I would no longer get alerts for new band-slots.

 

Thanks again for all your support with JTAlert. I could not live without it now.

 

73 de Phil GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: 04 February 2021 18:56
To: Support@HamApps.groups.io
Subject: Re: [HamApps] CQ Marathon query

 

On 4/02/2021 11:25 pm, Phil Cooper via groups.io wrote:

Ah, so you are saying that if this box is checked, and I work (for example) P5XXX on 20m FT8, I will NOT get an alert when he pops up on another band?

 

I only want to stop alerts for any given country worked in the current year for CQ Marathon, as countries only count once, regardless of band/mode.

 

For now, i have unchecked that box again, as I don't wish to miss new DXCC slots.

 

73 de Phil GU0SUP

Rereading my response I can understand your confusion. The relevant part "This option is available for all the Alert types" could have been reworded. "This option is available for all the Alert types on a per Alert basis" may be better wording.

In a nut-shell, each Alert type has multiple options, each being independent of the same options in another Alert type. So you could set the Marathon Alert to track by any band and any mode while at the same time have the DXCC Alert track individual Bands and Modes. The same applies for the "Auto clear triggered Alert entity after logging" option. You can safely apply that option for the Marathon Alert without affecting your DXCC Alerts which you could have set for individual Bands and Modes and require a QSL confirmation (eg LoTW confirmed) for an Entity to be no longer Alerted.

de Laurie VK3AMA


locked Re: CQ Marathon query

HamApps Support (VK3AMA)
 

On 4/02/2021 11:25 pm, Phil Cooper via groups.io wrote:

Ah, so you are saying that if this box is checked, and I work (for example) P5XXX on 20m FT8, I will NOT get an alert when he pops up on another band?

 

I only want to stop alerts for any given country worked in the current year for CQ Marathon, as countries only count once, regardless of band/mode.

 

For now, i have unchecked that box again, as I don't wish to miss new DXCC slots.

 

73 de Phil GU0SUP

Rereading my response I can understand your confusion. The relevant part "This option is available for all the Alert types" could have been reworded. "This option is available for all the Alert types on a per Alert basis" may be better wording.

In a nut-shell, each Alert type has multiple options, each being independent of the same options in another Alert type. So you could set the Marathon Alert to track by any band and any mode while at the same time have the DXCC Alert track individual Bands and Modes. The same applies for the "Auto clear triggered Alert entity after logging" option. You can safely apply that option for the Marathon Alert without affecting your DXCC Alerts which you could have set for individual Bands and Modes and require a QSL confirmation (eg LoTW confirmed) for an Entity to be no longer Alerted.

de Laurie VK3AMA


locked Re: JTAlert--->DXKeeper problem

Ron W3RJW
 

Perhaps checks missing?


--
73
Ron, W3RJW


locked Re: CQ Marathon query

Steve, N3SL
 

Phil,
The checkbox is on "every" alert/award page, so each is individually configurable.  

On Thu, Feb 4, 2021 at 6:25 AM Phil Cooper via groups.io <pcooper=suremail.gg@groups.io> wrote:

Hi Laurie,

 

Ah, so you are saying that if this box is checked, and I work (for example) P5XXX on 20m FT8, I will NOT get an alert when he pops up on another band?

 

I only want to stop alerts for any given country worked in the current year for CQ Marathon, as countries only count once, regardless of band/mode.

 

For now, i have unchecked that box again, as I don't wish to miss new DXCC slots.

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Laurie, VK3AMA" <hamapps.support@...>
Sent: Thursday, 4 February, 2021 01:35
To: Support@HamApps.groups.io
Subject: Re: [HamApps] CQ Marathon query



On 4/02/2021 3:28 am, Jim N6VH wrote:

Go to Settings - Alerts - Wanted CQ Marathon.

Check "Auto clear triggered Alert entity after logging".


That will be the answer.

That setting causes an Entity to be automatically marked as no-longer needed in the Alert database. This option is available for all the Alert types, useful for those users who don't require a QSL confirmation to have an Entity set as no-longer need (so will not alert), that is they are happy for just working the Entity. Prior to this option being introduced, there was no automatic flagging of worked Entities, thus requiring the "Rebuild Alert Database" operation (previously called the Log Scan) to update the Alert database. For Entities that require just a worked status (like the Marathon) it is a simple set and forget option. Of course if you require a QSL confirmation (like LoTW for DXCC) donot enable that option.

Note: When I use the word "Entity", I am not referring to DXCC Entities, but using it to describe all the Alert type entities (DXCC, State, Zones, Grids, etc).

de Laurie VK3AMA

3221 - 3240 of 36203