Date   

locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

I merged my WSJT-X and LoTW .adif files using ADIFMerge.exe specifically for JTAlert use.  Then checked them for errors with ADIFMaster.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

g4wjs
 

On 17/07/2020 01:54, scubajosh77 via groups.io wrote:
Thank you, I think I understand partially now.  If I select the No QSL Confirmation in the Scan menu it reflects the QSOs I've worked.  What I don't understand is if I don't select it and have LoTW selected as a confirmation source, it doesn't accurately reflect my QSLs on LoTW.
Josh,

what is the source of your ADIF log?



--
73
Bill
G4WJS.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

Thank you, I think I understand partially now.  If I select the No QSL Confirmation in the Scan menu it reflects the QSOs I've worked.  What I don't understand is if I don't select it and have LoTW selected as a confirmation source, it doesn't accurately reflect my QSLs on LoTW.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

g4wjs
 

On 17/07/2020 01:48, scubajosh77 via groups.io wrote:
So the Wanted Alerts are based on QSL, QSO?  And what method is used to confirm the contacts?  I only QSL via QRZ and LotW.  And my QSL/confirmed contacts in either database aren't reflected in my JTAlert Wanted Alerts?
Josh,

you set your own criteria for a confirmation in the "Scan Log and Rebuild" settings.



--
73
Bill
G4WJS.


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

*based on QSL, not QSO?


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

So the Wanted Alerts are based on QSL, QSO?  And what method is used to confirm the contacts?  I only QSL via QRZ and LotW.  And my QSL/confirmed contacts in either database aren't reflected in my JTAlert Wanted Alerts?


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

Larry Banks
 

Not until it’s confirmed.

73 -- Larry -- W1DYJ

 

Sent: Thursday, July 16, 2020 20:37
Subject: Re: [HamApps] Scan Log and Rebuild Kills my 'Wanted Settings'
 
Thank you for the response.  But that does not explain how I can log a QSO with someone in New Mexico for example, and then run the Scan Log and Rebuild function, and New Mexico shows up on my Wanted List for the same band.  If I log a QSO with a State, DXCC, etc. shouldn't it be removed from my want alerts when I do the Scan and Rebuild?

Josh, KN4VDR


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

Thank you for the response.  But that does not explain how I can log a QSO with someone in New Mexico for example, and then run the Scan Log and Rebuild function, and New Mexico shows up on my Wanted List for the same band.  If I log a QSO with a State, DXCC, etc. shouldn't it be removed from my want alerts when I do the Scan and Rebuild?

Josh, KN4VDR


locked Re: Scan Log and Rebuild Kills my 'Wanted Settings'

HamApps Support (VK3AMA)
 

On 17/07/2020 7:46 am, scubajosh77 via groups.io wrote:
I'm going to start off this with a disclaimer that I'm brand new to JTAlert as of yesterday so it may very well be that I don't understand something correctly.  I'm using it with JTDX.  I have an .adif log setup specifically for JTAlert.  When I log a QSO with a new state, it doesn't remove it from my wanted list.  Also I tried to 'Scan Log and Rebuild' the JTAlert .adif file thinking that was how to update the wanted lists against the log, but doing so reset all of my wanted settings.  Have I mis-configured something?  I thought the whole point of the wanted lists was to keep track of your completed QSO goals?

OM (Name?, Callsign?),

The Scan Log & Rebuild will rebuild your Wanted Alert lists based on the QSOs in your Log. It is not an update so any manual changes you have made will be lost due to the rebuild. There is no need to perform manual updates of the lists if your using JTAlert with a Log. Just hit the Scan, the process is automatic.

de Laurie VK3AMA


locked Scan Log and Rebuild Kills my 'Wanted Settings'

scubajosh77@...
 

I'm going to start off this with a disclaimer that I'm brand new to JTAlert as of yesterday so it may very well be that I don't understand something correctly.  I'm using it with JTDX.  I have an .adif log setup specifically for JTAlert.  When I log a QSO with a new state, it doesn't remove it from my wanted list.  Also I tried to 'Scan Log and Rebuild' the JTAlert .adif file thinking that was how to update the wanted lists against the log, but doing so reset all of my wanted settings.  Have I mis-configured something?  I thought the whole point of the wanted lists was to keep track of your completed QSO goals?


locked Re: display stopped

Joe
 

Not sure how they got changed but the filters were, indeed, messed up.  Sorry to be a bother!

thanks,

73,

Joe/WQ6Q


locked Re: Location alert by grid

asobel@...
 

Laurie

 

The JTAlert Wanted Grid Alert is tailored for the seekers of Work All Grids Awards such as eGrid by eQSL.

It does keep a list of all NOT needed grid squares and search for all other grid squares.

I am talking about an alert for a location, Say Rome, searching for one needed grid square.

You put the location grid of Rome and get a visual and voice alert when ever a station from Rome is online.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, July 16, 2020 11:13 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Location alert by grid

 

On 16/07/2020 4:21 pm, asobel@... wrote:

JTAlert does have a theoretical option of creating alert on location by grid.
Look at User Defined Alert.
You can use Wanted Grid as an Alert Trigger but if takes quite complicated programming to make a Wanted Grid act like Wanted Callsign.
Programmers, please provide us with a solution.
4X4MF


JTAlert already has a Wanted Grid Alert.

de Laurie VK3AMA


locked Re: Location alert by grid

HamApps Support (VK3AMA)
 

On 16/07/2020 4:21 pm, asobel@... wrote:
JTAlert does have a theoretical option of creating alert on location by grid.
Look at User Defined Alert.
You can use Wanted Grid as an Alert Trigger but if takes quite complicated programming to make a Wanted Grid act like Wanted Callsign.
Programmers, please provide us with a solution.
4X4MF

JTAlert already has a Wanted Grid Alert.

de Laurie VK3AMA


locked Re: display stopped

HamApps Support (VK3AMA)
 

On 17/07/2020 5:53 am, Joe wrote:
Things were working, for weeks, then suddenly no calls were being displayed in the JTAlert app main window.  WSJTX is decoding them, the JTAlert decode window shows them, but no callsigns are being displayed.

Ring a bell with anyone??

Joe/WQ6Q

Joe,

If the Decodes window is displaying decodes, than the main JTAlert processing is working.

The missing callsigns in the main display will be due to having one or more Alert filters set. JTAlert will be showing "Filter" in the titlebar status text. What filters do you have set under the "Alerts -> Filters" menu?

Are you sure that ALL decoded callsigns are non-displaying or do you randomly get some callsigns displayed like only CQs?

A couple of possibilities...
  • The "Show only callsigns generating Alerts" filter is set, but you don't have any Alert types enabled.

  • One of the QSL membership (lotw, eqsl) filters is set, but the Callsign database file (which contains the membership data) has been removed. A reinstall of JTAlert will reinstall the missing file.

de Laurie VK3AMA




locked display stopped

Joe
 

Things were working, for weeks, then suddenly no calls were being displayed in the JTAlert app main window.  WSJTX is decoding them, the JTAlert decode window shows them, but no callsigns are being displayed.

Ring a bell with anyone??

Joe/WQ6Q


locked Location alert by grid

asobel@...
 

JTAlert does have a theoretical option of creating alert on location by grid.
Look at User Defined Alert.
You can use Wanted Grid as an Alert Trigger but if takes quite complicated programming to make a Wanted Grid act like Wanted Callsign.
Programmers, please provide us with a solution.
4X4MF


locked Re: JTAlert screen stays small

BenFieke Meyer
 

Hi Mike,

Thanks for your suggestion and it did the trick!!! I have got my proper sized JTAlert screen back and can check the settings and it was so easy!!!

Very much appreciated!!

Kind Regards

Ben Meyer, ZL1CAH



On 16/07/2020 1:20 am, Michael Black via groups.io wrote:
On Wednesday, July 15, 2020, 08:17:33 AM CDT, BenFieke Meyer <benfieke@...> wrote:


Hi There,

For some reason I cannot get the oblong screen from JTAlert on top of my
WSJT-X screen anymore. If I move the mouse over the JTAlert Icon in the
taskbar I can see a miniature oblong JTAlert screen with the callsigns
in colours, but they are too small to read and not overlayed on the
WSJT-X screen. If I click on the JTAlert Icon, I only get the WSTJ-X
screen without the oblong JTAlert screen. I also cannot check any
settings anymore for JTAlert.

I run HRD ver. 6.5.0.207 ,  WSJT-X ver 2.2.2 and JTAlert ver 2.16.8  .

Has anybody an idea how to fix this?

Regards

Ben Meyer, ZL1CAH




locked Re: JTAlert screen stays small

Kenneth Dauma
 

I had the same problem. For some reason WSJT-X got resized and it covers up JTAlert.
I pulled down the top of the WSJT-X and moved it up until I got the JTAlert window.
All is good now.

Regards

Ken
WB0YBZ

On Wed, Jul 15, 2020 at 8:17 AM BenFieke Meyer <benfieke@...> wrote:
Hi There,

For some reason I cannot get the oblong screen from JTAlert on top of my
WSJT-X screen anymore. If I move the mouse over the JTAlert Icon in the
taskbar I can see a miniature oblong JTAlert screen with the callsigns
in colours, but they are too small to read and not overlayed on the
WSJT-X screen. If I click on the JTAlert Icon, I only get the WSTJ-X
screen without the oblong JTAlert screen. I also cannot check any
settings anymore for JTAlert.

I run HRD ver. 6.5.0.207 ,  WSJT-X ver 2.2.2 and JTAlert ver 2.16.8  .

Has anybody an idea how to fix this?

Regards

Ben Meyer, ZL1CAH





locked Re: JTAlert screen stays small

Michael Black
 

On Wednesday, July 15, 2020, 08:17:33 AM CDT, BenFieke Meyer <benfieke@...> wrote:


Hi There,

For some reason I cannot get the oblong screen from JTAlert on top of my
WSJT-X screen anymore. If I move the mouse over the JTAlert Icon in the
taskbar I can see a miniature oblong JTAlert screen with the callsigns
in colours, but they are too small to read and not overlayed on the
WSJT-X screen. If I click on the JTAlert Icon, I only get the WSTJ-X
screen without the oblong JTAlert screen. I also cannot check any
settings anymore for JTAlert.

I run HRD ver. 6.5.0.207 ,  WSJT-X ver 2.2.2 and JTAlert ver 2.16.8  .

Has anybody an idea how to fix this?

Regards

Ben Meyer, ZL1CAH




locked JTAlert screen stays small

BenFieke Meyer
 

Hi There,

For some reason I cannot get the oblong screen from JTAlert on top of my WSJT-X screen anymore. If I move the mouse over the JTAlert Icon in the taskbar I can see a miniature oblong JTAlert screen with the callsigns in colours, but they are too small to read and not overlayed on the WSJT-X screen. If I click on the JTAlert Icon, I only get the WSTJ-X screen without the oblong JTAlert screen. I also cannot check any settings anymore for JTAlert.

I run HRD ver. 6.5.0.207 ,  WSJT-X ver 2.2.2 and JTAlert ver 2.16.8  .

Has anybody an idea how to fix this?

Regards

Ben Meyer, ZL1CAH

4641 - 4660 of 35434