Date   

locked Name, qth...

Albert Müller <100almu@...>
 

Hi,
I have sometimes seen the names and contact details of my correspondent in the background of JTAlert.



I myself don't appear but how to have my contact information appear here?

Can you help me ?

Albert ON5AM


locked Re: New JTAlert (2.10.1) But Still Issues with DKKeeper/Pathfinder

Joe WB9SBD
 

Hi Dave,

I found that area, but there are like 8 choices, what do you choose?

Joe WB9SBD

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

On 8/8/2017 10:39 AM, David Chema wrote:

Did you go in to settings and choose your Pathfinder look up options?  It's not automatic.  You need to go in to settings and choose your options.  I did it last night and it works flawlessly.  

73,
Dave, KC8V

On Aug 8, 2017, at 11:14 AM, kkinderen@... wrote:

Hi:

I just installed JTAlertX 2.10.1. Something doesn't seem to be working. Double-clicking a call in JTAlertX does not filter DXKeeper and still doesn't update Pathfinder. I checked the log settings in JTAlert and restarted all DXLabs apps, JTAlertX and JTDX. Still no response from DXKeeper or Pathfinder. The version I just replaced didn't update Pathfinder but it did filter DXKeeper.

The actual act of logging seems to work OK. 



DXLab PathFinder not performing Callsign lookup if no previous QSOs in DXKeeper log.

--
73,
Kev K4VD


locked Re: New JTAlert (2.10.1) But Still Issues with DKKeeper/Pathfinder

kkinderen@...
 

Nice! I missed these options. I guess they are new in this version or were they there before and became unset with the upgrade.

Thanks much Dave... a quick test shows all works as expected.

--
73,
Kev K4VD


locked Re: New JTAlert (2.10.1) But Still Issues with DKKeeper/Pathfinder

David Chema
 

Hi Ken,

Click on Settings, Manage Settings, Applications, DXLab Suite.  In the center of that screen, attached below, you will see Pathfinder and DXView.  Set your options there.

Good luck!

73,
Dave, KC8V


Inline image 1

On Tue, Aug 8, 2017 at 11:48 AM, <kkinderen@...> wrote:
Hi David. It worked before and I made no changes to the settings after upgrading to 2.10.1. Can you tell me what settings you checked?

--
73,
Kev K4VD



locked Re: New JTAlert (2.10.1) But Still Issues with DKKeeper/Pathfinder

kkinderen@...
 

Hi David. It worked before and I made no changes to the settings after upgrading to 2.10.1. Can you tell me what settings you checked?

--
73,
Kev K4VD


locked Re: New JTAlert (2.10.1) But Still Issues with DKKeeper/Pathfinder

David Chema
 


Did you go in to settings and choose your Pathfinder look up options?  It's not automatic.  You need to go in to settings and choose your options.  I did it last night and it works flawlessly.  

73,
Dave, KC8V

On Aug 8, 2017, at 11:14 AM, kkinderen@... wrote:

Hi:

I just installed JTAlertX 2.10.1. Something doesn't seem to be working. Double-clicking a call in JTAlertX does not filter DXKeeper and still doesn't update Pathfinder. I checked the log settings in JTAlert and restarted all DXLabs apps, JTAlertX and JTDX. Still no response from DXKeeper or Pathfinder. The version I just replaced didn't update Pathfinder but it did filter DXKeeper.

The actual act of logging seems to work OK. 



DXLab PathFinder not performing Callsign lookup if no previous QSOs in DXKeeper log.

--
73,
Kev K4VD


locked New JTAlert (2.10.1) But Still Issues with DKKeeper/Pathfinder

kkinderen@...
 

Hi:

I just installed JTAlertX 2.10.1. Something doesn't seem to be working. Double-clicking a call in JTAlertX does not filter DXKeeper and still doesn't update Pathfinder. I checked the log settings in JTAlert and restarted all DXLabs apps, JTAlertX and JTDX. Still no response from DXKeeper or Pathfinder. The version I just replaced didn't update Pathfinder but it did filter DXKeeper.

The actual act of logging seems to work OK. 



DXLab PathFinder not performing Callsign lookup if no previous QSOs in DXKeeper log.

--
73,
Kev K4VD


locked Re: New 2.10.1 software feature. FYI

Michael Black
 

Did you install the callsign database?  I think it does the state automagically as long as that's installed and you have Wanted States enabled.

de Mike W9MDB


From: Joe WB9SBD <nss@...>
To: Support@HamApps.groups.io
Sent: Tuesday, August 8, 2017 8:43 AM
Subject: Re: [HamApps] New 2.10.1 software feature. FYI

Big Learning Curve on this software.
any way to have it tell me what state someone is in?


locked Re: New 2.10.1 software feature. FYI

Joe WB9SBD
 

Big Learning Curve on this software.
any way to have it tell me what state someone is in?

Joe WB9SBD

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

On 8/8/2017 8:38 AM, Mike Anderson wrote:
Thanks Laurie for the additional  filters for the newest release of JTAlert.      I can now set the  out of shack filter with no B4s   to  10Km   and on  the  FT8 mode I am no longer going nuts watching all of the calls stream by as it now ignores all of the US.   I can just wait for the siren to go off and then focus on WSJTX.     Setting it to 5Km  lets me pick up South America and the fringes of the US  from my location.

Mike  K5NAN









locked New 2.10.1 software feature. FYI

Mike Anderson
 

Thanks Laurie for the additional filters for the newest release of JTAlert. I can now set the out of shack filter with no B4s to 10Km and on the FT8 mode I am no longer going nuts watching all of the calls stream by as it now ignores all of the US. I can just wait for the siren to go off and then focus on WSJTX. Setting it to 5Km lets me pick up South America and the fringes of the US from my location.

Mike K5NAN


locked Re: Updates 2.10.1 shows I need update.

Mike Anderson
 

I'm familiar with that option Mike.  Here is a snapshot.   Must be me.   I reinstalled also and still says update   the   about  menu shows I have  2.110.1  and the menu bar is correct.   Weird.


locked Re: Updates 2.10.1 shows I need update.

Joe WB9SBD
 

I have the same situation here, and when going into the settings area I do not see a program up-date choice.

Joe WB9SBD

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

On 8/8/2017 7:55 AM, Michael Black via Groups.Io wrote:
Go to Settings/Program Updates and will tell you what you need-- you probably need to update Callsigns.
 
de Mike W9MDB



From: Mike Anderson <mike@...>
To: Support@HamApps.groups.io
Sent: Tuesday, August 8, 2017 7:52 AM
Subject: [HamApps] Updates 2.10.1 shows I need update.

I installed the latest  software twice now  but the  menu bar keeps saying Updates!.   It says I have  2.10.0  installed when I dont.    Even   the  about says I have   2.10.1
Not a huge issue.
Mike K5NAN




locked Re: Updates 2.10.1 shows I need update.

Michael Black
 

Go to Settings/Program Updates and will tell you what you need-- you probably need to update Callsigns.
 
de Mike W9MDB



From: Mike Anderson <mike@...>
To: Support@HamApps.groups.io
Sent: Tuesday, August 8, 2017 7:52 AM
Subject: [HamApps] Updates 2.10.1 shows I need update.

I installed the latest  software twice now  but the  menu bar keeps saying Updates!.   It says I have  2.10.0  installed when I dont.    Even   the  about says I have   2.10.1
Not a huge issue.
Mike K5NAN



locked Updates 2.10.1 shows I need update.

Mike Anderson
 

I installed the latest  software twice now  but the  menu bar keeps saying Updates!.   It says I have  2.10.0  installed when I dont.    Even   the  about says I have   2.10.1

Not a huge issue.

Mike K5NAN


locked Callsign/Sound database file versions 2.10.1

Don Hill AA5AU
 

Callsign databases and Sound Files still showing "Not Installed" for
Installed Version. Is there something we need to do in order to access the
file with the information?

The file versions do show when "Run as Administrator" as before. Running
Windows 10 Home in a standard account.

Thanks,
Don AA5AU


locked Re: Ham Radio Deluxe (HRD) API for 3rd party QSO integration

g4wjs
 

Hi Mike,

well this is a pleasant turn of events, let's hope that some burned bridges can be rebuilt!

As one of the WSJT development team I have a request, possibly related to your post. We have used the IP server in HRD for proxy rig control for those users of HRD that require HRD to control the rig's CAT interface. This has been in use from long before your involvement in HRD and despite some issues has worked well for us. My concern is that the last time we attempted to report an issue with the implementation of this facility for a particular rig (IC-7300) the response from HRD LLC was less than helpful, claiming that no such TCP/IP interface existed so we must be wrong!

My request is that you try and avoid breaking this interface for rig control unless there is going to be a major re-factoring in which case please let us know in advance?

--
73
Bill
G4WJS.


locked Ham Radio Deluxe (HRD) API for 3rd party QSO integration

Michael Carper
 

With the current version of JT-Alert supporting the API for sending QSO data to HRD Logbook, it's given us our first chance to see this in action since Rick left at the end of 2016.

First and foremost - any comments that have been made by me or our team at HRD Software were clearly a fact-less parroting of what we had all been told in the past.  We can now see that there is clearly some problems with our API.  We're working with several of our testers and customers to sort it all out.

Though it's news to me - it seems like we've got TWO different APIs.  One that is a command-line interface (CLI) that is a 2-way dialog between HRD Logbook and 3rd party programs.  And the other is a UDP broadcast interface.  Until recently, I had no idea which one was being used by JT-Alert.

But the point of this message is that I've heard the feedback from many users of JT-Alert and HRD and it has helped us understand the problem and its setting.  We now have resources focused on finding and correcting the problems.

Mike, WA9PIE


locked Re: Moving from Tracking By Individual Band "By Individual Mode" to "Any WSJT-X Mode"

HamApps Support (VK3AMA)
 

On 8/08/2017 3:12 PM, Graham Alston wrote:
Hi,

Is there any way of doing this without having to redo the Not Wanted/Wanted selections all over again?

Many thanks,
73 Graham VK3GA

Graham,

The Scan Log function creates/maintains all the different tracking (Band and mode) combinations for each Alert type, so it is just a matter of switching the tracking.

If your not performing a Scan Log because your not using a logger with JTAlert, then you have to maintain the lists manually.

Are you using a computer log, if so which one?

de Laurie VK3AMA
   


locked Moving from Tracking By Individual Band "By Individual Mode" to "Any WSJT-X Mode"

Graham Alston
 

Hi,

Is there any way of doing this without having to redo the Not Wanted/Wanted selections all over again?

Many thanks,
73 Graham VK3GA


locked New JTAlert 2.10.1 Available - Fixes, Changes, New Features, HRD v6 logging is enabled. : #Announcement #NewRelease #HRD

HamApps Support (VK3AMA)
 

New JTAlert 2.10.1 is available for download.

Please review the Release Notes.

  **** Important HRD V6 Logging Information.
  **** HRD V6 logging is again supported by JTAlert.
  **** The HRD V6 logging support in this release is a one-time event.
  **** Releases after 2.10.1 will again no longer have HRD V6 support.

  **** Important Contact Support changes.
  **** Due to Server security changes the Contact Support feature of JTAlert
  **** will no longer work for old JTAlert versions. Only versions 2.10.1 and
  **** later will be able to submit a support request via the HamApps Server.

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

If you want to report an issue with this version, please start a new message thread, don't reply to this message.

Release Notes for 2.10.1
  New Features:
    - Wildcard support for the Wanted Callsign Alert. Matching against the start
       of a Callsign only. Multiple wildcards can be defined. The wildcard is
       only supported as the last character in the Callsign.
       eg "VK3%" is valid, "VK%AMA" and "VK%A%A" are invalid.
    - Single option to initiate simultaneous DXKeeper log filter, Pathfinder
       and DXView lookups when your QSO partner Callsign changes. See the
       "Applications -> DXLab Suite" section of the Settings.
    - Option to not lookup previous qso data from logbook. Band/Mode/Worked/Cfm
       QSO data from the logbook are still used, but Name, QTH, Grid, DXCC, Cont,
       State and Zones are ignored. Location data (DXCC, Zones, etc) are derived
       from a simple cty.dat lookup when this option is enabled.
       (Default: OFF, Settings Section: Logging).
    - Out of Shack option Alert trigger based on Distance to decoded call (not B4).
       (Default: OFF, Window: Settings, Section: Alerts, Misc Alerts, Out of Shack).
    - Maximum number of JTAlert instances increased from 10 to 15.

  Changes:
    - Auto-start entries are now independent when running against WSJT-X & JTDX.
       It is now possible, for example, to have WSJT-X auto-start or have JTDX
       auto-start, depending on which shortcut is used to start JTAlertX.
    - Changes to DXLab specific lookups (DXKeeper, DXView, Pathfinder). See the
       "Applications -> DXLab Suite" section of the Settings and enable the
       required lookups to perform on a DX Call change.
    - FT8 spots upload to HamSpots changed from every 15sec to once per minute.
       (only one occurrence of a Callsign in this one minute period is spotted)
    - HamApps installed applications version data now stored in a disk-based
       file. The Registry is still used as a fallback if versions file missing.

  Fixes:
    - Band Activity Bar band colors not reflecting the FT8 counts when
       they exceeded the JT65/JT9 counts (2.10.0 defect).
    - End TX/RX Alert ignoring WSJT-X TX Enabled setting (2.10.0 defect).
    - Wanted Callsign alert not obeying any set filters.
    - Intermittent non-delivery of spots to HamSpots.net
    - DXLab PathFinder not performing Callsign lookup if no previous QSOs
       in DXKeeper log.
    - Non-delivery of Support emails when containing a very large attachment.
de Laurie VK3AMA