Date   

locked Re: duplicate grid alerts

Rick
 

Mike, just started to download qsls from LoTW and Eqsl to the ACL that is used solely for FT8.  started with 1/1/2018 contacts thru today.  Haven't seen any previously worked stations yet so don't know if this was the problem but have noticed not all unworked stations calling CQ are alerted.    ACL is connecting with JT alert and am using the newest version.  In the grid chase, it looks like each band shows a wanted grid alert even if it was worked on another band.

Most of the previously worked stations are showing B4 so I think it is working properly most of the time.  I'll keep watching and see if this shows up any more.....  Thanks, Mike really appreciate your help..  73 Rick K9EXY


On 1/13/2018 3:59 PM, Michael Black via Groups.Io wrote:
Do you have ACL connected to JTAlert?  JTAlert can scan the ACL database to get confirmations.
Are you dowloading QSLs from LOTW through ACL?

And if you have worked a call sign it should be marked as B4 and if you have B4's turned off you won't see them again (unless a different band if you have band tracking on.

Mike


On Saturday, January 13, 2018, 3:33:55 PM CST, Rick <jrickj@...> wrote:


Mike, The confirmation might be the problem.  I take the  the log and import it into another log for updating at LoTW and Eqsl. I use N3FJP as the master so maybe I need to change my procedure??  None of the exported QSOs are marked as  sent/received on the FT8 computer.  However, I Don't get some alerts for stations that I've worked B4.. Wondered if the stations that alert were not signed up for Lotw or eqsl when they were first worked.???   anyway thanks for your help and I'll try your recommedations

------ Original Message ------
From: "Michael Black via Groups.Io" <mdblack98@...>
Sent: 1/13/2018 2:14:51 PM
Subject: Re: [HamApps] duplicate grid alerts

If you're using 2.9.10 then submit a bug report (with explicit examples in the notes) via ?/Contact Support

If you're using a prior version upgrade and see if you still have the problem.

Also...have the grids you've "worked" been confirmed?  I believe it will keep alerting until they are though it should note the B4 for the same callsign.

de Mike W9MDB

On Saturday, January 13, 2018, 2:03:43 PM CST, <jrickj@...> wrote:


I've set the alerts for the grid chase and find that I'm getting some alerts for stations previously worked on the band when they have been worked on the same band after Jan. 1   These alerts don't happen with each previously worked station but just on some occasions.  also I do not get some alerts for stations not previously worked and with a new grid.  Have I set up something wrong for the chase?   This program of yours has to be the best thing since FT8 was published!!!  thanks for your help,  Rick


locked Re: Using Logic9 with JT-Alert

James C. Hall, MD WB4YDL
 

Hi Tom:

You bet ! I would love to see LOGic9 interfaced with JTAlert for auto-logging. Been using LOGic since the LOGic3 days !

If this is the way to do feature requests, great ! Count me in. If there is a specific area / method for feature requests, please point me in that direction.

73, Jamie
WB4YDL


locked Re: duplicate grid alerts

Michael Black
 

Do you have ACL connected to JTAlert?  JTAlert can scan the ACL database to get confirmations.
Are you dowloading QSLs from LOTW through ACL?

And if you have worked a call sign it should be marked as B4 and if you have B4's turned off you won't see them again (unless a different band if you have band tracking on.

Mike


On Saturday, January 13, 2018, 3:33:55 PM CST, Rick <jrickj@...> wrote:


Mike, The confirmation might be the problem.  I take the  the log and import it into another log for updating at LoTW and Eqsl. I use N3FJP as the master so maybe I need to change my procedure??  None of the exported QSOs are marked as  sent/received on the FT8 computer.  However, I Don't get some alerts for stations that I've worked B4.. Wondered if the stations that alert were not signed up for Lotw or eqsl when they were first worked.???   anyway thanks for your help and I'll try your recommedations

------ Original Message ------
From: "Michael Black via Groups.Io" <mdblack98@...>
Sent: 1/13/2018 2:14:51 PM
Subject: Re: [HamApps] duplicate grid alerts

If you're using 2.9.10 then submit a bug report (with explicit examples in the notes) via ?/Contact Support

If you're using a prior version upgrade and see if you still have the problem.

Also...have the grids you've "worked" been confirmed?  I believe it will keep alerting until they are though it should note the B4 for the same callsign.

de Mike W9MDB

On Saturday, January 13, 2018, 2:03:43 PM CST, <jrickj@...> wrote:


I've set the alerts for the grid chase and find that I'm getting some alerts for stations previously worked on the band when they have been worked on the same band after Jan. 1   These alerts don't happen with each previously worked station but just on some occasions.  also I do not get some alerts for stations not previously worked and with a new grid.  Have I set up something wrong for the chase?   This program of yours has to be the best thing since FT8 was published!!!  thanks for your help,  Rick


locked Re: duplicate grid alerts

Rick
 

Mike, The confirmation might be the problem.  I take the  the log and import it into another log for updating at LoTW and Eqsl. I use N3FJP as the master so maybe I need to change my procedure??  None of the exported QSOs are marked as  sent/received on the FT8 computer.  However, I Don't get some alerts for stations that I've worked B4.. Wondered if the stations that alert were not signed up for Lotw or eqsl when they were first worked.???   anyway thanks for your help and I'll try your recommedations

------ Original Message ------
From: "Michael Black via Groups.Io" <mdblack98@...>
Sent: 1/13/2018 2:14:51 PM
Subject: Re: [HamApps] duplicate grid alerts

If you're using 2.9.10 then submit a bug report (with explicit examples in the notes) via ?/Contact Support

If you're using a prior version upgrade and see if you still have the problem.

Also...have the grids you've "worked" been confirmed?  I believe it will keep alerting until they are though it should note the B4 for the same callsign.

de Mike W9MDB

On Saturday, January 13, 2018, 2:03:43 PM CST, <jrickj@...> wrote:


I've set the alerts for the grid chase and find that I'm getting some alerts for stations previously worked on the band when they have been worked on the same band after Jan. 1   These alerts don't happen with each previously worked station but just on some occasions.  also I do not get some alerts for stations not previously worked and with a new grid.  Have I set up something wrong for the chase?   This program of yours has to be the best thing since FT8 was published!!!  thanks for your help,  Rick


locked Re: duplicate grid alerts

Michael Black
 

If you're using 2.9.10 then submit a bug report (with explicit examples in the notes) via ?/Contact Support

If you're using a prior version upgrade and see if you still have the problem.

Also...have the grids you've "worked" been confirmed?  I believe it will keep alerting until they are though it should note the B4 for the same callsign.

de Mike W9MDB


On Saturday, January 13, 2018, 2:03:43 PM CST, <jrickj@...> wrote:


I've set the alerts for the grid chase and find that I'm getting some alerts for stations previously worked on the band when they have been worked on the same band after Jan. 1   These alerts don't happen with each previously worked station but just on some occasions.  also I do not get some alerts for stations not previously worked and with a new grid.  Have I set up something wrong for the chase?   This program of yours has to be the best thing since FT8 was published!!!  thanks for your help,  Rick


locked duplicate grid alerts

Rick
 

I've set the alerts for the grid chase and find that I'm getting some alerts for stations previously worked on the band when they have been worked on the same band after Jan. 1   These alerts don't happen with each previously worked station but just on some occasions.  also I do not get some alerts for stations not previously worked and with a new grid.  Have I set up something wrong for the chase?   This program of yours has to be the best thing since FT8 was published!!!  thanks for your help,  Rick


locked Error when logging plus request

Morris WA4MIT
 
Edited

Since installing version 2.10.9 twice I have received this error msg when trying to log qso to HRD V6 I am using JTDX .65  logging to HRD .787 latest version system is W10 this only started with 10.9. I guess this msg is from JTAlert it really does not state where it is from?. I clear out call reinsert call then it logs OK this has happened twice out of maybe 60 log events. Also if possible in a future release could you make the grid box a little wider it cuts off the last letter if the last letter is a "m" or "w" it is just not wide enough. As always Laurie thanks for a great piece of software I use it every day. 73 Morris WA4MIT HNY


locked Grid Chase - small query

Phil Cooper
 

Hi Laurie and the group,

 

I am playing at the Grid Chase, and have followed the settings in the help file. Putting Wanted Grid at the top of the list is OK, but I note that I am getting new grid alerts even for those calls that are not LoTW users.

I do have the grid chase set to LoTW only.

 

Is it possible that I have missed something?

 

73 de Phil GU0SUP

 


locked Re: Mainwindow.ui for jtalert

HamApps Support (VK3AMA)
 

On 13/01/2018 9:36 PM, f1dsz@... wrote:
What I'm looking for ...
Can you send me the source target of JTalert v; 09
((src mainwindow. ui)) because I would like to change colors with "QTcréator"

JTAlert is closed source.

Also, JTAlert does not use the QT Framework. There is no mainwindow.ui

de Laurie VK3AMA
   


locked Mainwindow.ui for jtalert

Jean-Claude F1DSZ
 

Thank you for your reply

But I may be badly explain ...
What I'm looking for ...
Can you send me the source target of JTalert v; 09
((src mainwindow. ui)) because I would like to change colors with "QTcréator"


locked SRC Maindow.ui for JTalert

Jean-Claude F1DSZ
 

 
 
 
 
 
 
 
Hello everyone
I am looking for the source JTalert (v:2.10.9) "src maindow.ui" to rebuild JTalert in color, could you give me the way to follow.

Thank you 73 'Jean-Claude F1DSZ


locked New JTAlert 2.10.9 Available. #NewRelease #Announcement

HamApps Support (VK3AMA)
 

New JTAlert 2.10.9 is available for download. *** Please review the Release Notes ***

IMPORTANT: ARRL 2018 Grid Chase participants need to use this version.
See the Help File, "Tutorials -> ARRL International Grid Chase 2018" topic for Grid Chase setup.

Visit HamApps.com for the download link and upgrade instructions.

Release Notes for 2.10.9
  New Features:
    - Works with new 5.3.1 version of JT65-HF HB9HQX Edition.
       (Important Note: Only JT65-Log, the default, is supported)

  Changes:
    - Log4OM Settings, MySQL port field extended to accept 5 digits.
    - QSOs will not be logged and an error window will be shown if the Callsign
       to be logged doesn't match the Callsign of your current QSO partner.
       This occurs when double-clicking a new decode before completeing the
       logging of the previous QSO.

  Fixes:
    - With Grid Chase enabled, some Callsigns may not be detected as a B4,
       resulting in possible inappropriate alerting.
    - Manually changed Wanted States not being remembered with the needed count
       not updating. Affecting WAS alerts, on 20m and when mode tracking is set
       to "Any WSJT-X Mode (JT9 or JT65 or FT8)". (2.10.0 defect)
    - ADIF Scan Log not finding States when an LoTW ADIF export file is used.
    - Decodes History statistics not updated, decodes not restored after
       JTAlert restart and exports/backups non-functional.
       (affecting a very small number of users).
    - No B4 detection for those running with Logging disabled. (2.10.8 defect)
    - Scan Log ignoring ACLog records that were missing QSO frequencies.

de Laurie VK3AMA


locked Re: To upgrade from 2.10.7 to 2.10.8, must I first uninstall 2.10.7?

HamApps Support (VK3AMA)
 

On 13/01/2018 11:39 AM, WH wrote:

To upgrade from 2.10.7 to 2.10.8, must I first uninstall 2.10.7?

 

The instructions on the website refer to 2.7.7 and below.

 

Thanks

Bill, N9CDX

No need to uninstall first, but no harm is done if you do.

The 2.7.7 instructions apply to 2.7.7 and earlier only.

de Laurie VK3AMA
   


locked To upgrade from 2.10.7 to 2.10.8, must I first uninstall 2.10.7?

cqdx@...
 

I may have sent this too soon on my previous attempt.

 

To upgrade from 2.10.7 to 2.10.8, must I first uninstall 2.10.7?

 

The instructions on the website refer to 2.7.7 and below.

 

Thanks

Bill, N9CDX

 


locked Re: How to get to the tutorial

HamApps Support (VK3AMA)
 

On 13/01/2018 5:43 AM, WI4T wrote:
Well, yesterday I could find a post with the location of the tutorial but I was not near my "ham" computer and now can't find the information.  I believe it was by pressing a "F" key.  I have spent 30 minutes searching for the location of the tutorial but I can't find a post telling me.

Sorry as I am sure this is redundant.  But thank you in advance.

Greg - WI4T

Look in the Help File.

JTAlert "?->Open Help File" titlebar menu.

de Laurie VK3AMA
   


locked How to get to the tutorial

WI4T <wi4t@...>
 

Well, yesterday I could find a post with the location of the tutorial but I was not near my "ham" computer and now can't find the information.  I believe it was by pressing a "F" key.  I have spent 30 minutes searching for the location of the tutorial but I can't find a post telling me.

Sorry as I am sure this is redundant.  But thank you in advance.

Greg - WI4T


locked Re: JtAlert Hamradio delux and worked B4

Robert De Forge
 

What software did you update ? What stopped JT alert or the auto logging to HRD ?
Bobby

Sent from my iPod

On Jan 12, 2018, at 6:28 AM, johnscobb@... wrote:

Hello
Worked B4 working ok all the sudden after  updating software. I have HRD 6.3 and  have logs on HRD etc please help. Therefor would like to automatically log to HRD and  alert me of Worked B4


Regards
John


locked JtAlert Hamradio delux and worked B4

johnscobb@...
 

Hello
Worked B4 working ok all the sudden after  updating software. I have HRD 6.3 and  have logs on HRD etc please help. Therefor would like to automatically log to HRD and  alert me of Worked B4


Regards
John


locked Re: JTAlert / ACLog

HamApps Support (VK3AMA)
 

On 12/01/2018 1:14 PM, Arthur Petteway wrote:

When trying to establish AC Log as my external logging system,  JTAlert fails to automatically find the ACL configuration file which would contain the path directions to the current AC Log database file.

 

My AC Log system is located in an area of my files system which is not the usual situation.  I think that is the source of the problem.  Unfortunately, the problem may arise from some deleted and redirected user accounts which Win10 Home edition gives little help in unscrambling without reloading the OS.

 

Is there a way to manually designate in the JTAlert system-  where the AC Log configuration info is to be found, since the "automatic" process cannot figure it out?

 
73,
Art WB4MNK

Art,

Yes.

JTAlert Settings, Logging -> ACLog section. Choose the "Remote Networked PC" install location. Enter 127.0.0.1 and 1100 for the IP Address and Port. You will be able to select the the location of the ACLog log file. Restart JTAlert after making this change.

de Laurie VK3AMA
   


locked JTAlert / ACLog

Arthur Petteway <wb4mnk@...>
 

When trying to establish AC Log as my external logging system,  JTAlert fails to automatically find the ACL configuration file which would contain the path directions to the current AC Log database file.

 

My AC Log system is located in an area of my files system which is not the usual situation.  I think that is the source of the problem.  Unfortunately, the problem may arise from some deleted and redirected user accounts which Win10 Home edition gives little help in unscrambling without reloading the OS.

 

Is there a way to manually designate in the JTAlert system-  where the AC Log configuration info is to be found, since the "automatic" process cannot figure it out?

 
73,
Art WB4MNK

19381 - 19400 of 37715