Date   

locked Re: JTAlert LOg

HamApps Support (VK3AMA)
 

On 4/02/2018 11:43 PM, Rick Arzadon via Groups.Io wrote:

Now that I downloaded the Callsign Database and have the colors the way I want them on the  Callsign Display.

What is necessary to populate the Name, QTH & Grid fields?

Thanks

Rick - N8XI

Rick,

The Callsign database doesn't provide Name, QTH & Grid data. Its use is to provide LoTW/eQSL(AG) membership data and US State data (need for the Wanted State alert).

There are 3 ways for the log fields area can be populated.
  1. Manual input from you using whatever source of data you have, typically from a Browser lookup.
  2. Automatically from a previous QSO in your log that has the data recorded.
  3. Automatically from an online XML lookup against one of the supported XML providers.

Option 3. is probably what you want. See the JTAlert Settings, "Web Services -> Online XML Callbooks" section.

de Laurie VK3AMA
   


locked Re: UDP set up #FT8

Robert Lorenzini
 

Well that's a pretty safe assumption at any time.

Bob - wd6dod

On 2/4/2018 10:30 AM, Michael Black via Groups.Io wrote:
I've heard there is a bug in HRD causing problems and they have a  beta version in test right now.


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


On Sunday, February 4, 2018, 11:56:23 AM CST, Vince Loschiavo <vince320@...> wrote:


Mike,

I think I can use your help.  Seems that I had everything working (moved to new computer)...didn't have uSoft office installed, and managed to get HRD Log to record the QSO in the logbook..
then Updated to 2.10.14 AND Loaded uSoft Office
Now cant seem to get the qso logged into HRD..
very sad..PIA..
drop me an email at n2aie at arrl dot net, and I'll get back to u...would like to sort this out this morning..
thanks
Vince


locked Grid Scan with ACLog

Ernie Barnhart
 

Using JTAlertX v2.10.14 and ACLog v6.1. When doing a “Scan Log and Rebuild” for “Wanted Grid” only a small number of grids are returned. ACLog stores most grids as 6 characters. The ones that are currently stored as 4 characters appear to be the ones found with the grid scan. ACLog logging is enabled. Under “Logging” “Apply standard format to all logged Grids” is checked. Initially tried with it unchecked. Please advise. Thank you.


locked JTAlert LOg

Rick Arzadon - N8XI
 

Now that I downloaded the Callsign Database and have the colors the way I want them on the  Callsign Display.

What is necessary to populate the Name, QTH & Grid fields?

Thanks

Rick - N8XI


locked Re: UDP set up #FT8

Michael Black
 

I've heard there is a bug in HRD causing problems and they have a  beta version in test right now.


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


On Sunday, February 4, 2018, 11:56:23 AM CST, Vince Loschiavo <vince320@...> wrote:


Mike,

I think I can use your help.  Seems that I had everything working (moved to new computer)...didn't have uSoft office installed, and managed to get HRD Log to record the QSO in the logbook..
then Updated to 2.10.14 AND Loaded uSoft Office
Now cant seem to get the qso logged into HRD..
very sad..PIA..
drop me an email at n2aie at arrl dot net, and I'll get back to u...would like to sort this out this morning..
thanks
Vince


locked Re: UDP set up #FT8

Vince Loschiavo
 

Mike,

I think I can use your help.  Seems that I had everything working (moved to new computer)...didn't have uSoft office installed, and managed to get HRD Log to record the QSO in the logbook..
then Updated to 2.10.14 AND Loaded uSoft Office
Now cant seem to get the qso logged into HRD..
very sad..PIA..
drop me an email at n2aie at arrl dot net, and I'll get back to u...would like to sort this out this morning..
thanks
Vince


locked Re: Mouse clicks

Jim Cooper
 

On 3 Feb 2018 at 17:45, jon6889@verizon.net wrote:

I'm new to JTALERT. In fact just started
today, I also am experiencing the same problem
with Mouse clicks not working at different
times. Is it something I'm doing??  de Jon AA2CC
Because it is intermittent, it might well be the
CPU is overly busy and doesn't get to the mouse click
right away ... I have seen that here, as I am using only
a dual-core cpu and with all the database processing
etc that Alert has to do, it sometimes seems to ignore
the mouse request ... or at least delays it.


locked Re: possible enhancement ?

David Michael Gaytko // WD4KPD
 

RRR Laurie....

have been trying, but just can't seem to get it right yet !

david/wd4kpd



On 2/3/2018 8:37 PM, HamApps Support (VK3AMA) wrote:
On 4/02/2018 12:07 PM, David Michael Gaytko // WD4KPD wrote:

for the designers of wsjtx/jtdx/jtalert........


i have set up my apps to ++only++ show needed dx spots/states in jtalert.


after noting the spot in alert, i got to go and find out where in the decoded windows the dx is in frequency and whether or not the spot is in qso or not, then try and make the click to get the qso started.  this almost always fails in ft8 especially on 20m when the band is crowded.


just wondering if it may be possible to have the three concerned programs possibly coordinate the color coding for the various type of spots/alerts.


thank you and very frustrated


david/wd4kpd

JTAlert offers complete customisation of the font color and background color for all the alert types. WSJT-X offers background color customisation for the color alerting it provides. Why not, for the alert types they have in common, Own Call, CQ, DXCC, set WSJT-X and JTAlert to use the same color combinations.

de Laurie VK3AMA
   


locked Re: Questions about JTDX JTAlert

Buzz Loeschman <ni5dx@...>
 

Hi Laurie,

 

After posting the message about my difficulties I decided to start WSJT-X and JTAlert-X.

Low and behold, the fields in JTAlert began populating.  I was very anxious to see if the logging to HRD worked and it took me quite a while to finally make

a contact (I try to work only DX).  When I did make a contact it was great to hear the alert chime when my CQ DX was answered.  Upon completion of the

QSO it was really sweet to see the message saying the QSO had been logged correctly.  I quickly checked HRD’s Logbook and saw the Q was there.

I was a happy camper. 

 

I did then shut down the 2 programs and started JTDX and the alert program for it.  No population or anything so I know there is something not checked

that should be.  I may investigate this or I may continue to just use WSJT-X as that is the program I began FT8 with.

 

Thanks for the reply.  Sorry to see that there was another incident of a similar nature.  Hopefully, this will be resolved soon unless it is “operator error” which

is a distinct possibility in my case.

 

73,

 

Buzz

NI5DX

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, February 3, 2018 5:36 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Questions about JTDX JTAlert

 

On 4/02/2018 12:29 AM, Buzz Loeschman wrote:

Hello,

 

I have been using JTDX for a while now and have been trying to get the auto-log function to work to log my contacts to Ham Radio Deluxe’s Logbook.

However, I (not very technical) and a friend (VERY technical and running the same combination) have not been able to get the link to work.

Here is the process I am trying:

I open Ham Radio Deluxe and its Logbook.  I then open JTDX (select FT8 as the mode) and then open JTDX-JTAlert.

I am able to make contacts with other stations using this process.  However, there are a couple of things that do not work.

 

First, we cannot get the gray fields in JTAlert to populate.  Nothing ever shows in the fields whenever stations fill the left pane of JTDX.

Whenever I move the mouse over the band numbers at the top of JTAlert, the Unique Callsingns TX/RX per band shows different numbers like it is receiving that data.

Also, the Callsign, country name, time, CQ, ITU, and continent fields all fill PROPERLY.  However, nothing ever fills the top two gray lines of JTAlert.

 

Whenever I finish a QSO and push the “Log QSO” button I get this error message:

 

QSO not logged:

The QSO was not logged.

There was a callsign mismatch.  The callsign to be logged did not match your current QSO partner.

Callsign (DX Call)

 

Log Callsign = PA2KPZ

QSO Partner = (this was blank)

I get this mismatch error even though the callsign I am attempting to log matches EXACTLY.

Any help with my problems would be greatly appreciated.  I am really enjoying JTDX and JTALert but it would be so much better if I did not have to manually log each completed QSO.

Thanks, and 73,

Buzz

NI5DX

Buzz,

What version of JTAlert? What version (including step number) of JTDX?

As a diagnostic step, try using WSJT-X rather than JTDX. Does JTAlert populate the Callsign boxes and log the QSO without error when using WSJT-X?

There has been one other report of this type of behaviour with respect to JTDX. I have not been able to identify what the cause is at this time. JTDX is a significant moving target with the frequent changes that I am not able to test all its releases.

There may be something in the JTAlert session files. While running JTAlert against JTDX with, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.

de Laurie VK3AMA
   


locked Re: Mouse clicks

Jon
 

Thank you I'll give that a try.   de jon  AA2CC


locked Re: Mouse clicks

Brian (N2MLP)
 

RF  in shack ??

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of jon6889@...
Sent: Saturday, February 3, 2018 8:46 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Mouse clicks

 

I'm new to JTALERT. In fact just started today, I also am experiencing the same problem with Mouse clicks not working at different times. Is it something I'm doing??  de Jon AA2CC


locked Re: Mouse clicks

HamApps Support (VK3AMA)
 

On 4/02/2018 12:45 PM, jon6889@... wrote:
I'm new to JTALERT. In fact just started today, I also am experiencing the same problem with Mouse clicks not working at different times. Is it something I'm doing??  de Jon AA2CC
Jon,

Double-clicking a Callsign in JTAlert will only setup WSJT-X to start the QSO (you will still need to enable Tx in WSJT-X) when the Callsign corresponds to a CQ decode. Double-clicking a Callsign in JTAlert for a non-CQ decode will be ignored by WSJT-X, you need to make that action within WSJT-X itself.

de Laurie VK3AMA
   


locked Re: Mouse clicks

Jon
 

I'm new to JTALERT. In fact just started today, I also am experiencing the same problem with Mouse clicks not working at different times. Is it something I'm doing??  de Jon AA2CC


locked Re: possible enhancement ?

HamApps Support (VK3AMA)
 

On 4/02/2018 12:07 PM, David Michael Gaytko // WD4KPD wrote:

for the designers of wsjtx/jtdx/jtalert........


i have set up my apps to ++only++ show needed dx spots/states in jtalert.


after noting the spot in alert, i got to go and find out where in the decoded windows the dx is in frequency and whether or not the spot is in qso or not, then try and make the click to get the qso started.  this almost always fails in ft8 especially on 20m when the band is crowded.


just wondering if it may be possible to have the three concerned programs possibly coordinate the color coding for the various type of spots/alerts.


thank you and very frustrated


david/wd4kpd

JTAlert offers complete customisation of the font color and background color for all the alert types. WSJT-X offers background color customisation for the color alerting it provides. Why not, for the alert types they have in common, Own Call, CQ, DXCC, set WSJT-X and JTAlert to use the same color combinations.

de Laurie VK3AMA
   


locked possible enhancement ?

David Michael Gaytko // WD4KPD
 

for the designers of wsjtx/jtdx/jtalert........


i have set up my apps to ++only++ show needed dx spots/states in jtalert.


after noting the spot in alert, i got to go and find out where in the decoded windows the dx is in frequency and whether or not the spot is in qso or not, then try and make the click to get the qso started.  this almost always fails in ft8 especially on 20m when the band is crowded.


just wondering if it may be possible to have the three concerned programs possibly coordinate the color coding for the various type of spots/alerts.


thank you and very frustrated


david/wd4kpd



locked Re: Questions about JTDX JTAlert

HamApps Support (VK3AMA)
 

On 4/02/2018 12:29 AM, Buzz Loeschman wrote:

Hello,

 

I have been using JTDX for a while now and have been trying to get the auto-log function to work to log my contacts to Ham Radio Deluxe’s Logbook.

However, I (not very technical) and a friend (VERY technical and running the same combination) have not been able to get the link to work.

Here is the process I am trying:

I open Ham Radio Deluxe and its Logbook.  I then open JTDX (select FT8 as the mode) and then open JTDX-JTAlert.

I am able to make contacts with other stations using this process.  However, there are a couple of things that do not work.

 

First, we cannot get the gray fields in JTAlert to populate.  Nothing ever shows in the fields whenever stations fill the left pane of JTDX.

Whenever I move the mouse over the band numbers at the top of JTAlert, the Unique Callsingns TX/RX per band shows different numbers like it is receiving that data.

Also, the Callsign, country name, time, CQ, ITU, and continent fields all fill PROPERLY.  However, nothing ever fills the top two gray lines of JTAlert.

 

Whenever I finish a QSO and push the “Log QSO” button I get this error message:

 

QSO not logged:

The QSO was not logged.

There was a callsign mismatch.  The callsign to be logged did not match your current QSO partner.

Callsign (DX Call)

 

Log Callsign = PA2KPZ

QSO Partner = (this was blank)

I get this mismatch error even though the callsign I am attempting to log matches EXACTLY.

Any help with my problems would be greatly appreciated.  I am really enjoying JTDX and JTALert but it would be so much better if I did not have to manually log each completed QSO.

Thanks, and 73,

Buzz

NI5DX

Buzz,

What version of JTAlert? What version (including step number) of JTDX?

As a diagnostic step, try using WSJT-X rather than JTDX. Does JTAlert populate the Callsign boxes and log the QSO without error when using WSJT-X?

There has been one other report of this type of behaviour with respect to JTDX. I have not been able to identify what the cause is at this time. JTDX is a significant moving target with the frequent changes that I am not able to test all its releases.

There may be something in the JTAlert session files. While running JTAlert against JTDX with, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.

de Laurie VK3AMA
   


locked Re: Jt-alert HRD Integration

Warren Greenberg
 

 Thanks for the help, had some free time today, did your config, and then successfully log to HRD. 
This HRD logging with JT-Alert logging to eQSL & QRZ is a great time saver, and also cuts down on typos. All I have to do is the upload to LOTW at the end if the day.
Warren - AE4WG


locked Re: #HRD Log file selection #HRD

HamApps Support (VK3AMA)
 

On 4/02/2018 12:07 AM, William W1WAB wrote:
I have several logs, all set up in Dropbox and all based on MS Access, using HRD 5.2893.  The different logs are use for regular QSOs, Field Day, etc... Mainly to keep the worked before status working. 

How can I select the log I wish by file name?

Thanks, Bill W1WAB 
Bill,

Short answer, you can't. JTAlert expects an ODBC DSN has been configured for each HRD Log. HRD should be automatically creating the necessary DSN when you create the log. You can create the DSN yourself (Google how to do that), just be sure to use the 32bit ODBC Manger and not the default 64bit manager found in Windows Control Panel.

de Laurie VK3AMA
   


locked Re: JTAlert 2.10.12 Does Not Auto Close JTDX

Bob
 

It appears there maybe an issue with the latest JTDX not communicating with JTDX-Alert.  Something to do with the UDP communications protocol.  Laurie, VK3AMA is looking into it.

 

I switched to WSJT-X and everything is working.

 

In JTDX-Alert have you specified what to use for logging? It’s in the settings, logging section.  You specify HRD V6.3 or V5 or pre 6.3.  You also have to have the logbook name correct.

 

73,

Bob

WK2Y

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, January 26, 2018 9:21 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.10.12 Does Not Auto Close JTDX

 

On 27/01/2018 1:01 PM, JohnB wrote:

JTAlert 2.10.12 after auto starting JTDX seems to have lost the ability to close JTDX after both programs are run for awhile. 

If I start JTAlert and it auto starts JTDX, and I then immediately close JTAlert, JTDX also closes.  But if I allow both programs to run for several minutes, closing JTAlert no longer auto closes JTDX.

. . . John (WA3CAS)

John,

What JTDX version and step number?
Has it always done this or only with a recent JTDX build?

From you description, it appears that JTDX is either changing its PID (Program Identifier which is created when a process is started), or JTDX is not obeying the Window Close signal (standard Windows message) sent by JTAlert. The PID is recorded by JTAlert and it is the Window Handle belonging to this PID that is sent the close signal. It is unlikely the PID is changing, so my bet is on JTDX not obeying the close signal.

JTAlert does gather some data when the apps are started and closed so there may be something in your session file. Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis.
  
de Laurie VK3AMA
   


locked Questions about JTDX JTAlert

Buzz Loeschman <ni5dx@...>
 

Hello,

 

I have been using JTDX for a while now and have been trying to get the auto-log function to work to log my contacts to Ham Radio Deluxe’s Logbook.

However, I (not very technical) and a friend (VERY technical and running the same combination) have not been able to get the link to work.

Here is the process I am trying:

I open Ham Radio Deluxe and its Logbook.  I then open JTDX (select FT8 as the mode) and then open JTDX-JTAlert.

I am able to make contacts with other stations using this process.  However, there are a couple of things that do not work.

 

First, we cannot get the gray fields in JTAlert to populate.  Nothing ever shows in the fields whenever stations fill the left pane of JTDX.

Whenever I move the mouse over the band numbers at the top of JTAlert, the Unique Callsingns TX/RX per band shows different numbers like it is receiving that data.

Also, the Callsign, country name, time, CQ, ITU, and continent fields all fill PROPERLY.  However, nothing ever fills the top two gray lines of JTAlert.

 

Whenever I finish a QSO and push the “Log QSO” button I get this error message:

 

QSO not logged:

The QSO was not logged.

There was a callsign mismatch.  The callsign to be logged did not match your current QSO partner.

Callsign (DX Call)

 

Log Callsign = PA2KPZ

QSO Partner = (this was blank)

 

I get this mismatch error even though the callsign I am attempting to log matches EXACTLY.

 

 

Any help with my problems would be greatly appreciated.  I am really enjoying JTDX and JTALert but it would be so much better if I did not have to manually log each completed QSO.

 

Thanks, and 73,

 

Buzz

NI5DX

 

18841 - 18860 of 37662