Date   

locked Re: [Ham-Apps] Re: HRD Logbook 5.24 and JT-Alert - South Africa Issue

Dave Wright <hfradiopro@...>
 


locked Re: [Ham-Apps] JT-Alert Window updating

hb9ari <hb9ari@...>
 

Hi Laurie,

Oh yes, thank you Laurie ! May be for my birthday (69 yo), the 14 August hi !
A very nice and useful present, specially when running multiple instances of JT65-HF.

Have a nice week-end.

My best 73,
Rudi, HB9ARI
 




On 28.07.2012 01:05, Laurie, VK3AMA wrote:
 

Hi Rudi,

An early Christmas present for you :-) ...
The next release of JT-Alert will detect and alert on any new JT65-HF decodes at any time in the minute. Doing a "Decode Again" will produce the necessary alerts if it produces decodes.

Regards
de Laurie, VK3AMA

On 27/07/2012 5:01 PM, hb9ari wrote:
Hi Laurie,

Thank you for your (always) quick reply.

I understand the "mechanism" you are using in your software
for JT65-HF's window polling and the reason to allow time for slow PC.

Happy to see that my "wish" is already in your to-do list.

Thank you also for the new locators contacted with the " Wanted Grid" alert !

My best 73,
Rudi, HB9ARI



locked Re: [Ham-Apps] JT-Alert Window updating

Laurie, VK3AMA <groups04@...>
 

Hi Rudi,

An early Christmas present for you :-) ...
The next release of JT-Alert will detect and alert on any new JT65-HF decodes at any time in the minute. Doing a "Decode Again" will produce the necessary alerts if it produces decodes.

Regards
de Laurie, VK3AMA

On 27/07/2012 5:01 PM, hb9ari wrote:
Hi Laurie,

Thank you for your (always) quick reply.

I understand the "mechanism" you are using in your software
for JT65-HF's window polling and the reason to allow time for slow PC.

Happy to see that my "wish" is already in your to-do list.

Thank you also for the new locators contacted with the " Wanted Grid" alert !

My best 73,
Rudi, HB9ARI


locked Re: [Ham-Apps] JT-Alert Window updating

hb9ari <hb9ari@...>
 

Hi Laurie,

Thank you for your (always) quick reply.

I understand the "mechanism" you are using in your software
for JT65-HF's window polling and the reason to allow time for slow PC.

Happy to see that my "wish" is already in your to-do list.

Thank you also for the new locators contacted with the " Wanted Grid" alert !

My best 73,
Rudi, HB9ARI



On 27.07.2012 03:42, Laurie, VK3AMA wrote:
 

Hi Rudi,

Currently JT-Alert only polls the JT65-HF window starting at the 49 sec tick of the current minute until 15 secs into the next minute (for those running multi-decode on slow PCs) looking for new decodes. Once new decodes are detected, JT-Alert stops polling JT65-HF until the next 49 sec tick, so will not detect if new decodes are generated as a result of the "Decode Again" button being used.

Detecting new decodes at any time within a minute is already on my todo list. If your lucky, it may be available in the next release.

Regards
Laurie, VK3AMA

On 26/07/2012 6:48 PM, hb9ari wrote:
Hi Laurie,

I move often between 2 or 3 instances of JT65-HF running at the same time;
the JT-Alert and JT-Macros windows "follow"  and lock on the last
selected instance 100% OK.

My question, is it possible to update the calls in the JT-Alert window
when" Decode Again", is activated in the "active" JT65-HF window?

My best 73 and thank you for your nice software.

Rudi, HB9ARI





locked Re: [Ham-Apps] JT-Alert Window updating

Laurie, VK3AMA <groups04@...>
 

Hi Rudi,

Currently JT-Alert only polls the JT65-HF window starting at the 49 sec tick of the current minute until 15 secs into the next minute (for those running multi-decode on slow PCs) looking for new decodes. Once new decodes are detected, JT-Alert stops polling JT65-HF until the next 49 sec tick, so will not detect if new decodes are generated as a result of the "Decode Again" button being used.

Detecting new decodes at any time within a minute is already on my todo list. If your lucky, it may be available in the next release.

Regards
Laurie, VK3AMA

On 26/07/2012 6:48 PM, hb9ari wrote:
Hi Laurie,

I move often between 2 or 3 instances of JT65-HF running at the same time;
the JT-Alert and JT-Macros windows "follow"  and lock on the last
selected instance 100% OK.

My question, is it possible to update the calls in the JT-Alert window
when" Decode Again", is activated in the "active" JT65-HF window?

My best 73 and thank you for your nice software.

Rudi, HB9ARI




locked Re: [Ham-Apps] Re: HRD Logbook 5.24 and JT-Alert - South Africa Issue

Thomas Schaefer <ny4i@...>
 

Rick, W4PC of HRD Software said it was a bug and is fixed in next release. 

Tom NY4I



On Jul 26, 2012, at 6:38 PM, "Laurie, VK3AMA" <groups04@...> wrote:

I would call that a critical design flaw in HRD Log if it is setting the DXCC code to zero, especially without seeking approval of the user through a confirmation dialogue popup. The act of opening a Log entry (say for QSL status changes) in HRD Log shouldn't be making any changes to existing data except for those initiated by the user. That's my view.

I will do some investigation on how best to mitigate this behaviour, but wont spend too much time until the HRD people release a stable and relatively bug-free version, especially since this is a new "feature" introduced since 5.24

de Laurie, VK3AMA

On 27/07/2012 5:46 AM, Jim wrote:
Unfortunately, when HRD nukes the cosmetic country name for a discrepancy, it also sets the DXCC country code for that log entry to zero.  An informative exercise for HRD users is to include the DXCC code in your logbook display and then sort on that column to see how many country codes you have set to zero.   




locked Re: [Ham-Apps] Re: HRD Logbook 5.24 and JT-Alert - South Africa Issue

Laurie, VK3AMA <groups04@...>
 

I would call that a critical design flaw in HRD Log if it is setting the DXCC code to zero, especially without seeking approval of the user through a confirmation dialogue popup. The act of opening a Log entry (say for QSL status changes) in HRD Log shouldn't be making any changes to existing data except for those initiated by the user. That's my view.

I will do some investigation on how best to mitigate this behaviour, but wont spend too much time until the HRD people release a stable and relatively bug-free version, especially since this is a new "feature" introduced since 5.24

de Laurie, VK3AMA

On 27/07/2012 5:46 AM, Jim wrote:
Unfortunately, when HRD nukes the cosmetic country name for a discrepancy, it also sets the DXCC country code for that log entry to zero.  An informative exercise for HRD users is to include the DXCC code in your logbook display and then sort on that column to see how many country codes you have set to zero.   




locked Re: HRD Logbook 5.24 and JT-Alert - South Africa Issue

Jim - N4ST
 

Unfortunately, when HRD nukes the cosmetic country name for a discrepancy, it also sets the DXCC country code for that log entry to zero. An informative exercise for HRD users is to include the DXCC code in your logbook display and then sort on that column to see how many country codes you have set to zero.


locked JT-Alert Window updating

hb9ari <hb9ari@...>
 

Sorry, i used a "reply" with false subject !

73, Rudi


locked Re: [Ham-Apps] CBA - DXKEEPER

hb9ari <hb9ari@...>
 

Hi Laurie,

I move often between 2 or 3 instances of JT65-HF running at the same time;
the JT-Alert and JT-Macros windows "follow" and lock on the last
selected instance 100% OK.

My question, is it possible to update the calls in the JT-Alert window
when" Decode Again", is activated in the "active" JT65-HF window?

My best 73 and thank you for your nice software.

Rudi, HB9ARI


locked Re: [Ham-Apps] CBA - DXKEEPER

Laurie, VK3AMA <groups04@...>
 

Hi John,

The Call Book Address is NOT something that JT-ALert sends to DXKeeper when a QSO is logged.
Sounds like a setting in DXKeeper has changed.

de Laurie, VK3AMA


On 26/07/2012 2:57 PM, jgmags2000 wrote:
Hello Laurie,
            Using JT-Alerts 1.6.0 with JT65-HF 1.09.3, DXKeeper and Pathfinder. Previously when clicking the LOG QSO button all the data including the CBA field in DXKeeper were populated. Now all the data except the CBA data is logged. Do I have something unchecked in the config set-up?

Thank you for this great program.
73, John, KJ1J



locked CBA

jgmags2000 <jgmags2000@...>
 

Hello Laurie,
Using JT-Alerts 1.6.0 with JT65-HF 1.09.3, DXKeeper and Pathfinder. Previously when clicking the LOG QSO button all the data including the CBA field in DXKeeper were populated. Now all the data except the CBA data is logged. Do I have something unchecked in the config set-up?

Thank you for this great program.
73, John, KJ1J


locked Re: [Ham-Apps] Re: HRD Logbook 5.24 and JT-Alert - South Africa Issue

Laurie, VK3AMA <groups04@...>
 

And the ARRL DXCC Entities document, April 2012 edition (http://www.arrl.org/files/file/DXCC/2012%20DXCC%20Current_G%281%29.pdf)
list ZS as "South Africa".

de Laurie, VK3AMA

On 24/07/2012 2:02 AM, Jim wrote:
FWIW, QRZ returns Republic of South Africa for a query on a ZS call.

Jim - N4ST




locked Re: [Ham-Apps] HRD Logbook 5.24 and JT-Alert - South Africa Issue

Laurie, VK3AMA <groups04@...>
 

Hi Jim,

I agree, this is a problem with HRD.

I view the Country name as a "Cosmetic" piece of data, the critical item in a QSO that correctly identifies the Country is the DXCC code. What the country is called is irrelevant. The DXCC code is what is used by eQSL & LoTW to determine Countries (actually DXCCs) confirmed.

de Laurie, VK3AMA

On 24/07/2012 1:47 AM, Jim wrote:
Just like with United States vs. United States of America.
JT-Alert and previous versions of HRD recorded ZS as South Africa.
Now HRD Logbook checks the spelling and wants Republic of South Africa.
If you open a ZS entry from JT-ALert or an older HRD version, the country name of South Africa will be blanked when you update the entry.
I posted this on HRD Forum, since it is their fix.  ARRL DX list shows South Africa, if that is the adjudication source.

Jim - N4ST



locked Re: HRD Logbook 5.24 and JT-Alert - South Africa Issue

Jim - N4ST
 

FWIW, QRZ returns Republic of South Africa for a query on a ZS call.

Jim - N4ST


locked HRD Logbook 5.24 and JT-Alert - South Africa Issue

Jim - N4ST
 

Just like with United States vs. United States of America.
JT-Alert and previous versions of HRD recorded ZS as South Africa.
Now HRD Logbook checks the spelling and wants Republic of South Africa.
If you open a ZS entry from JT-ALert or an older HRD version, the country name of South Africa will be blanked when you update the entry.
I posted this on HRD Forum, since it is their fix. ARRL DX list shows South Africa, if that is the adjudication source.

Jim - N4ST


locked Re: [Ham-Apps] JT-Alert Callsign Databases - New version, 12.07.21 (2012-Jul-21), available

Laurie, VK3AMA <groups04@...>
 

Hi Jim,

The US States list I produce from FCC data, the LoTW list is from a file maintained at http://www.hb9bza.net and the eQSL (AG) list comes direct from eQSL.

Cheers
de Laurie, VK3AMA

On 22/07/2012 10:49 AM, Jim Campbell wrote:
Laurie,

Yes. I didn't know the source for the database and had no way to check for myself. I use your flags a lot and wanted my info to be correct for others.

Thanks and 73,

Jim - W4BQP

On 7/21/2012 7:43 PM, Laurie, VK3AMA wrote:
 

Hi Jim,

W4BQP is in all 3 database files, eQSL, LoTW and US States (returns NC).
Is there are reason for the question?

de Laurie, VK3AMA


On 22/07/2012 1:43 AM, Jim Campbell wrote:
Laurie,

Thanks for the update to the database. I have a favour to ask of you. Can you please check to see if my call is listed as being registered with both LOTW and eQSL?

I would like to reiterate what a blessing JT-Alert is. Trying to do anything on JT65-HF without it would be very difficult. In fact, if you withdrew it I would almost certainly quit using JT65.

Regards,

Jim - W4BQP





locked Re: [Ham-Apps] LOG4OM

Laurie, VK3AMA <groups04@...>
 

Hi Arthur,

First I have heard of heard of LOG4OM.

I have added your request to my "To be Investigated and Tested for Potential Future Integration" List.

Regards
de Laurie, VK3AMA


On 23/07/2012 9:55 AM, afa1yy wrote:
You have provided logging for more than 1 logging program.  I wonder if you can add one more.  LOG4OM would require TCP linking to localhost port 8080, service name log4om. Their logs are kept, I believe in SQlite.

Arthur
K0AY




locked LOG4OM

afa1yy
 

You have provided logging for more than 1 logging program. I wonder if you can add one more. LOG4OM would require TCP linking to localhost port 8080, service name log4om. Their logs are kept, I believe in SQlite.

Arthur
K0AY


locked Re: [Ham-Apps] JT-Alert Callsign Databases - New version, 12.07.21 (2012-Jul-21), available

Jim Campbell <jim@...>
 

Laurie,

Yes. I didn't know the source for the database and had no way to check for myself. I use your flags a lot and wanted my info to be correct for others.

Thanks and 73,

Jim - W4BQP

On 7/21/2012 7:43 PM, Laurie, VK3AMA wrote:
 

Hi Jim,

W4BQP is in all 3 database files, eQSL, LoTW and US States (returns NC).
Is there are reason for the question?

de Laurie, VK3AMA


On 22/07/2012 1:43 AM, Jim Campbell wrote:
Laurie,

Thanks for the update to the database. I have a favour to ask of you. Can you please check to see if my call is listed as being registered with both LOTW and eQSL?

I would like to reiterate what a blessing JT-Alert is. Trying to do anything on JT65-HF without it would be very difficult. In fact, if you withdrew it I would almost certainly quit using JT65.

Regards,

Jim - W4BQP