Date   

locked JT Alert and HRD

Bob Davet
 

Not trying to get anything started here but why is this:

HRD V6 logging is no longer supported by JTAlert starting with version 2.9.0.

Went to up grade from 2.8.7 to 2.9.0 and saw that.

I understand that there were some issue going on with HRD and JT Alert.

With Rick leaving HRD I was hoping that those issues could be resolved.

Besides not being supporting HRD anymore what other upgrades does 2.9.0 have that would make me want to upgrade to it??

I use HRD and love the suite of programs. I can understand friction between the 2 entities.

If I do chose to upgrade, what will I net be getting from JT Alert and HRD no longer being supported??

Thanks

Bob
W8RID



locked Re: JTAlertX log update did not work

Laurie, VK3AMA <groups08@...>
 



On 28/01/2017 3:04 PM, 'Dan Malcolm' dmalcolm24@... [HamApps] wrote:

I should have mentioned it, but I did that this time.� I�ve had this happen previously, but before now the second attempt worked.� It did not this time.

_____________________________

Dan Malcolm CFI/II

K4SHQ

Thanks Dan,

That's disappointing, as the JTAlert version your running (the Azimuth patched version) contains some code changes to try and avoid these occasional Log4OM UDP logging failures.

de Laurie VK3AMA
���


locked Re: JTAlertX log update did not work

Laurie, VK3AMA <groups08@...>
 

On 28/01/2017 4:55 PM, Rory n6oil@... [HamApps] wrote:
Great work mate! Yeah know, I bet you hate it when a Yank tries to talk Aussie.
Doesn't bother me, but does sometimes make me cringe when it is "over the top" and I am left thinking this Guy has watched too many Paul Hogan movies (eg. Crocodile Dundee) :-)

de Laurie VK3AMA


locked Re: Comments & QSL Message text substitution

Laurie, VK3AMA <groups08@...>
 



On 28/01/2017 3:59 PM, David Potter dwaine_pipe@... [HamApps] wrote:

Hi Laurie,

Was wondering if it could be possible to add %Mode% to the current available above list?

Not a biggie and more than happy to wait for vers 3 if you�re busy :^)

Thank you for a great program.

David

VK7YUM

David,

It would be a trivial addition, but for what purpose?
The Mode is already set within the QSO record of you log, why the need to duplicate that information in the Comments or QSL message?

de Laurie VK3AMA
���


locked Re: logging 2.9 ADi and Import HRD 6.3 how to scan worke B4

Laurie, VK3AMA <groups08@...>
 

On 29/01/2017 12:30 AM, 'Jim - N4ST' newsgroup@... [HamApps] wrote:
Hopefully Laurie will chime in with the best answer.
When I went to Ver 2.9, I lost my +8,500 JT QSOs that had been used in the B4 check.
I exported my JT QSOs from HRD Logbook in ADIF format and added that to the new existing JTAlert ADIF Log
That seemed to report my B4 contacts correctly.
Subsequently, I wrote a VBA program which strips out the HRD "extra" ADIF information and reformats the HRD ADIF data to the one QSO per line format of JTAlert.
Don't know that it was necessary to do that, but is prettier.

__________
73,
Jim - N4ST
Jim,

JTAlert doesn't care about multi-line QSO records in the ADIF. Similarly, all the superfluous HRD clutter in the ADIF file is of no consequence, they are ignored. JTAlert will work with an unmodified HRD ADIF export.

de Laurie VK3AMA


locked Re: logging 2.9 ADi and Import HRD 6.3 how to scan worke B4

Laurie, VK3AMA <groups08@...>
 

Jacques,

You don't need to do anything. JTAlert automatically checks the B4 status of decodes against whatever log type JTAlert is configured to use, including an ADIF file.

de Laurie VK3AMA

On 28/01/2017 6:58 PM, f1vev@... [HamApps] wrote:

HI,

if- when changing to version 2.9 and save log as ADI I can import to HRD 6.3 etc simple enough.

What is best way to get the scan log to check the worked before status?

do I need to import HRD adi into new log created for JT alert ? any pointers would help me

thank you Jacques


locked Re: JTAlertX Alert Wanted Continent but only when CQ?

Laurie, VK3AMA <groups08@...>
 

Frank,

The Alert filters apply universally across all Alert types, they cannot be applied to individual Alerts.

My Suggestion is to turn OFF Continent alerts. They are not really needed as you will quickly get your Continents through normal QSO activity or by pursuing Dxcc's. You wont have to worry about missing "AN" as an example, as that will trigger a DXCC alert anyway. I can't imagine your chasing Continents without also chasing DXCC. In my opinion Wanted Continent alerts are not needed, but I have included them in JTAlert for the sake of "completeness".

The User Defined alert is not suitable for your purpose. It is primarily intended for when you want to be alerted (via email, sms, house alarm system going off, the actual alert is left to your own ingenuity and programming skill) when a rare one is decoded (like your last State on a particular Band) and you want to know about even when away from the shack.

de Laurie VK3AMA

On 29/01/2017 5:39 AM, n1gdo@... [HamApps] wrote:

Is there a way to trigger Wanted Continent but only when the station is calling CQ?

If I turn on Wanted CQ I get too many alerts for every station calling CQ.

If I turn on Wanted Continent I get the alert even when the station is already in a QSO...


I tried to read up on the User Defined Alert but it may be over my head...


Thanks for any assistance.


frank

N1GDO



locked JTAlertX Alert Wanted Continent but only when CQ?

Frank Ptzii
 

Is there a way to trigger Wanted Continent but only when the station is calling CQ?

If I turn on Wanted CQ I get too many alerts for every station calling CQ.

If I turn on Wanted Continent I get the alert even when the station is already in a QSO...


I tried to read up on the User Defined Alert but it may be over my head...


Thanks for any assistance.


frank

N1GDO


locked Thanks Much

William Wagaman <wwagaman@...>
 

Hello all Bill here N3GTY new to the group and JTalert. I thought I had problems in the past with my setup and JTalert and I have discovered that the problem was with the program I was using for JT65. I had one program for JT9 and another for JT65. WSJT-X  worked logged and did everything correctly. Now I use WSJT-X for both modes and I am one happy camper since it reads my ACLOG program and lets me know what I have worked before. All I can say is that JTalert ROCKS. Lets me know what stations I need and what bands are most active and after I started using my headphones for alerts even my wife is happy. Thanks much Laurie your software is a work of art 73 for now Bill N3GTY




locked Re: : RE: logging 2.9 ADi and Import HRD 6.3 how to scan worke B4

f1vev
 

OK James,

scratched all  and restarted   and all is ok now  and restored my B4 cells show up .

Thanks Jacques 


locked Re: : RE: logging 2.9 ADi and Import HRD 6.3 how to scan worke B4

f1vev
 


Thanks James 

well this is what I did but when I scan log it shows scanning 10K contacts but does not update anything and take  milli seconds to complete ... Strange ..

must  have missed something   will continue  to experiment 

when you say added  do you mean import  or rename to new JT alert tried both with no scanning succes 

Cheers Jacques  


locked Re: logging 2.9 ADi and Import HRD 6.3 how to scan worke B4

Jim - N4ST
 

Jacques,

Hopefully Laurie will chime in with the best answer.
When I went to Ver 2.9, I lost my +8,500 JT QSOs that had been used in the B4 check.
I exported my JT QSOs from HRD Logbook in ADIF format and added that to the new existing JTAlert ADIF Log
That seemed to report my B4 contacts correctly.
Subsequently, I wrote a VBA program which strips out the HRD "extra" ADIF information and reformats the HRD ADIF data to the one QSO per line format of JTAlert.
Don't know that it was necessary to do that, but is prettier.

__________
73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...]
Sent: Saturday, January 28, 2017 02:59
To: HamApps@...
Subject: [HamApps] logging 2.9 ADi and Import HRD 6.3 how to scan worke B4


HI,
if- when changing to version 2.9 and save log as ADI I can import to HRD 6.3 etc simple enough.
What is best way to get the scan log to check the worked before status?

do I need to import HRD adi into new log created for JT alert ? any pointers would help me
thank you Jacques

________________________________________
Posted by: f1vev@...
________________________________________


locked logging 2.9 ADi and Import HRD 6.3 how to scan worke B4

f1vev
 

HI,

if- when  changing to version 2.9  and save log as ADI I can import to HRD 6.3  etc simple enough. 

What is best way to get  the scan log  to check the worked before status?


do I need to import HRD adi into new log created for JT alert ? any pointers would help me 

thank you Jacques 


locked Re: JTAlertX log update did not work

N6OIL
 

Great work mate! Yeah know, I bet you hate it when a Yank tries to talk Aussie.



On Fri, Jan 27, 2017 at 8:01 PM, 'Laurie, VK3AMA' groups08@... [HamApps] <HamApps@...> wrote:
 



On 28/01/2017 2:34 PM, Rory n6oil@... [HamApps] wrote:
> Hey Laurie I have had the same thing happen a few times using your
> previous version did a second "log QSO" and it took but I haven't been
> worried about. It might be that UDP went to sleep and needs a tickle.
>
> Rory
> N6OIL
Hi Rory,

I was also thinking that UDP might be an issue. I have altered the
Log4OM UDP handling to explicitly close and reopen the UDP socket prior
to logging. A Test version with this change is currently being tested by
a user who was experiencing this behaviour on a consistent basis, every
few days.

de Laurie VK3AMA



locked Comments & QSL Message text substitution

Dwaine Pipe
 

Hi Laurie,

 

Was wondering if it could be possible to add %Mode% to the current available above list?

 

Not a biggie and more than happy to wait for vers 3 if you’re busy :^)

 

Thank you for a great program.

David

VK7YUM

 

 


locked Re: JTAlertX log update did not work

Dan Malcolm <dmalcolm24@...>
 

Laurie,

I should have mentioned it, but I did that this time.  I’ve had this happen previously, but before now the second attempt worked.  It did not this time.

 

_____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Friday, January 27, 2017 9:25 PM
To: HamApps@...
Subject: Re: [HamApps] JTAlertX log update did not work

 

 

Dan.

Next time this happens, before you play with Communicator, try a second time to log the QSO via JTAlert, that is use the WSJT-X "Log QSO" button a second time. Let me know if the second logging works (or not).

de Laurie VK3AMA
   

On 28/01/2017 12:28 PM, 'Dan Malcolm' dmalcolm24@... [HamApps] wrote:

Laurie,

I know there has been a discussion about JTAlertX having a logging failure lately.  It just happened to me, and I have sent you a “?->Contact Support” message.  I use Log4OM, and the failure seems to be connected to its Communicator app.  I had to cycle the “Start” “Stop” buttons twice before logging was accepted.  I do have “Auto Start” enabled.

 

I suspect JTAlertX is not the culprit here, but thought you would be interested.  I will relay this incident to the Log4OM Forum.

 

Thanks.

 

___________________________________________

Dan Malcolm

K4SHQ

 


locked Re: JTAlertX log update did not work

Laurie, VK3AMA <groups08@...>
 

On 28/01/2017 2:34 PM, Rory n6oil@... [HamApps] wrote:
Hey Laurie I have had the same thing happen a few times using your previous version did a second "log QSO" and it took but I haven't been worried about. It might be that UDP went to sleep and needs a tickle.

Rory
N6OIL
Hi Rory,

I was also thinking that UDP might be an issue. I have altered the Log4OM UDP handling to explicitly close and reopen the UDP socket prior to logging. A Test version with this change is currently being tested by a user who was experiencing this behaviour on a consistent basis, every few days.

de Laurie VK3AMA


locked Re: JTAlertX log update did not work

N6OIL
 

Hey Laurie I have had the same thing happen a few times using your previous version did a second "log QSO" and it took but I haven't been worried about. It might be that UDP went to sleep and needs a tickle.

Rory
N6OIL 

On Fri, Jan 27, 2017 at 7:25 PM, 'Laurie, VK3AMA' groups08@... [HamApps] <HamApps@...> wrote:
 

Dan.

Next time this happens, before you play with Communicator, try a second time to log the QSO via JTAlert, that is use the WSJT-X "Log QSO" button a second time. Let me know if the second logging works (or not).

de Laurie VK3AMA
   


On 28/01/2017 12:28 PM, 'Dan Malcolm' dmalcolm24@... [HamApps] wrote:

Laurie,

I know there has been a discussion about JTAlertX having a logging failure lately.  It just happened to me, and I have sent you a “?->Contact Support” message.  I use Log4OM, and the failure seems to be connected to its Communicator app.  I had to cycle the “Start” “Stop” buttons twice before logging was accepted.  I do have “Auto Start” enabled.

 

I suspect JTAlertX is not the culprit here, but thought you would be interested.  I will relay this incident to the Log4OM Forum.

 

Thanks.

 

___________________________________________

Dan Malcolm

K4SHQ




locked Re: JTAlertX log update did not work

Laurie, VK3AMA <groups08@...>
 

Dan.

Next time this happens, before you play with Communicator, try a second time to log the QSO via JTAlert, that is use the WSJT-X "Log QSO" button a second time. Let me know if the second logging works (or not).

de Laurie VK3AMA
���


On 28/01/2017 12:28 PM, 'Dan Malcolm' dmalcolm24@... [HamApps] wrote:

Laurie,

I know there has been a discussion about JTAlertX having a logging failure lately.� It just happened to me, and I have sent you a �?->Contact Support� message.� I use Log4OM, and the failure seems to be connected to its Communicator app.� I had to cycle the �Start� �Stop� buttons twice before logging was accepted.� I do have �Auto Start� enabled.

�

I suspect JTAlertX is not the culprit here, but thought you would be interested.� I will relay this incident to the Log4OM Forum.

�

Thanks.

�

___________________________________________

Dan Malcolm

K4SHQ



locked JTAlertX log update did not work

Dan Malcolm <dmalcolm24@...>
 

Laurie,

I know there has been a discussion about JTAlertX having a logging failure lately.  It just happened to me, and I have sent you a “?->Contact Support” message.  I use Log4OM, and the failure seems to be connected to its Communicator app.  I had to cycle the “Start” “Stop” buttons twice before logging was accepted.  I do have “Auto Start” enabled.

 

I suspect JTAlertX is not the culprit here, but thought you would be interested.  I will relay this incident to the Log4OM Forum.

 

Thanks.

 

___________________________________________

Dan Malcolm

K4SHQ


Politicians are people who, when they see light at the end
of the tunnel, go out and buy some more tunnel.