Support@HamApps.groups.io

kd6hq

					Laurie

Thank you for the commits about timing.  I am using D4 but I did not realize it needed to be updated as often as that.  I had it set for 1 hour.  I will change the setting and use the 1 minute setting and see if it helps.

At this point I only know that MixW can log to it.  I will get in touch with Howard, W6HN and find out for sure.  It may take a few days I think he is out of town right now.

Don, kd6hq

Re: [Ham-Apps] Thanks and ..........

Laurie, VK3AMA <groups03@...>

#763

Hi Don,

Timing is everything in JT65 and is the main cause for signals not being decoded. Either your time or the transmitting stations time may be off. Many operators sync their time using third party applications like D4 or Meinberg, windows time update is insufficient and often inaccurate. I personally sync my time every minute.

I had a brief look at CommCat, but couldn't find anything on the website or within the application help file regarding 3rd party application logging to CommCat. Is it able to accept commands from programs like JT-Alert to log a QSO? If so can you point me to the necessary information.

Regards
Laurie, VK3AMA

On 02-March-2012 03:40, kd6hq wrote:

Show quoted text

Good Day Laurie

I have been using JT-Alert and JT-Macros for about 2 weeks now and every thing seems to be going along fine.  My computer talks to me now which is a good thing because with the time JT65 takes my mind starts to wonder.

I have noticed that sometimes JT65 seems to copy signals that it does not decode.  Sometimes there will be 3 or 4 signals on the scope but only 2 will be decoded.  That is a curiosity to me and I was just wondering if this is a common occurrence?

Would you consider adding another logging program to your list?
The name of the program is CommCat.  It is written by a local fellow here in Northern California.
I can tell you that it already accepts information from MixW but I'm not sure if it is a CSV or not.
I can find out any information you need as I'm a beta tester for it.

Thank you for taking the time to write your enhancement programs Laurie.  They make JT65-HF much more enjoyable.

73's

Don, kd6hq

Re: [Ham-Apps] Unable to load jt

Laurie, VK3AMA <groups03@...>

#762

Hi Rayn,

You would be best to post this question to the JT65-HF support group http://groups.google.com/group/jt65-hf?hl=en

I haven't seen this problem before. Maybe there are others on this group who will respond, but the Google group is your best option.

de Laurie, VK3AMA

On 01-March-2012 20:36, Rayn wrote:

Show quoted text

I get an error message (HRD interface 0015 missing) JT56 won't load.  I have the newest version of HRD yet 0015 is missing.  Is there something I have to do in HRD to form the file?

Re: HRD logging

AB9QU

#761

					Ok thanks I will do that

Bill ab9qu

Thanks and ..........

kd6hq

#760

					Good Day Laurie

I have been using JT-Alert and JT-Macros for about 2 weeks now and every thing seems to be going along fine.  My computer talks to me now which is a good thing because with the time JT65 takes my mind starts to wonder.

I have noticed that sometimes JT65 seems to copy signals that it does not decode.  Sometimes there will be 3 or 4 signals on the scope but only 2 will be decoded.  That is a curiosity to me and I was just wondering if this is a common occurrence?

Would you consider adding another logging program to your list?
The name of the program is CommCat.  It is written by a local fellow here in Northern California.
I can tell you that it already accepts information from MixW but I'm not sure if it is a CSV or not.
I can find out any information you need as I'm a beta tester for it.

Thank you for taking the time to write your enhancement programs Laurie.  They make JT65-HF much more enjoyable.

73's

Don, kd6hq

Unable to load jt

Rayn <computernt41@...>

#759

					I get an error message (HRD interface 0015 missing) JT56 won't load.  I have the newest version of HRD yet 0015 is missing.  Is there something I have to do in HRD to form the file?
				

Re: [Ham-Apps] Up-Date

Bill Duffy

#758

Hi Laurie! Works great! Thanks for the help and great software………….

73

Bill

KA0VXK

Show quoted text

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Tuesday, February 28, 2012 9:59 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Up-Date

Bill you need to enable DXKeeper logging. The titlebar message "[No Log"] indicates you have no log enabled. You need to enable logging by ticking the checkbox on the "DXLab DXKeeper" section of the configuration window. Once that is done, the "[DXKeeper]" message will appear in the JT-Alert titlebar. Logging will now be operational.

de Laurie, VK3AMA

On 29-February-2012 05:46, Bill Duffy wrote:

Hi Laurie…… It’s installed per instruction.

Only problem is that it does not talk to DXK 10.0.2!

I checked the config file and it seems to be correct.

Suggestions?

73

Bill

KA0VXK

,_._,___

[zldxc] HRD 5.11a released

BuDJie

#757

-------- Original Message --------

Subject:	[zldxc] HRD 5.11a released
Date:	Thu, 1 Mar 2012 10:36:33 +1300 (New Zealand Daylight Time)
From:	Phillip
Reply-To:	zldxc@...
To:

Tampa, FL February 29, 2012: HRD Software, LLC announced today they have released version 5.11a of Ham Radio Deluxe.

This latest version follows the release of version 5.1 on Feb 10, 2012 and is another step in the continuing project of the company to eliminate outstanding issues found in previous versions of HRD. Rick Ruhl, W4PC, co-owner and lead programmer said, "We’ll continue to update the 5.1x releases with "bug fixes" as the development of enhancements for the 6.0 release continues.

To facilitate both bug fixes and enhancements to Ham Radio Deluxe, the development team is to moving the program source code from the obsolete Visual C++ 6.0 development environment to current Visual Studio 2010 development environment. This major step enables a more straightforward, bug-free development process and better program integration using the more powerful VS 2010 and its support tools for enhancements to HRD."

The 5.x releases of HRD are free. HRD Software LLC does have direct paid support with phone and email for the 5.1x products for an introductory price of $59.95. This pricing plan includes version 6.0 at no additional charge. The introductory price expires upon release of Ham Radio Deluxe 6.0.

The scheduled release of Ham Radio Deluxe 6.0 is May 18, 2012 at the Dayton Hamvention and on line. The MSRP for Ham Radio Deluxe 6.0 with support will be $79.95 when it is released.

HRD Downloads: http://www.ham-radio-deluxe.com

HRD Forum: http://forums.hrdsoftwarellc.com

Ham Radio Deluxe 5.11 is here and its FREE. http://www.ham-radio-deluxe.com

Radio Operations Center for your AEA/Timewave or Kantronics TNC, Now sync's with DM-780

EmComm Ops for Packet TNCs, be ready.

Check it out at http://www.w4pcsoftware.com

FREE Animations for your email




	Click Here!

~-|**|PrettyHtmlEnd|**|-~ ~-|**|PrettyHtmlStart|**|-~

Re: [Ham-Apps] HRD logging

Laurie, VK3AMA <groups03@...>

#756

Bill,

If you are trying to use JT-Alert to log JT65-HF QSOs to HRD (not clear from your message) please use the "Contact Support" menu of JT-Alert so I can review your config and session files to determine why logging is not working for you.

de Laurie, VK3AMA

On 01-March-2012 06:34, ab9qu wrote:

Show quoted text

I have the box checked for HRD logging but get an error message. It does load to the jt logger so I have been loading that into the HRD log.
Is there something you need to do in HRD to make the log from jt65 to work?
thanks
73  Bill  ab9qu

Re: [Ham-Apps] WANTED STATE alert only on CQ from that state?

Laurie, VK3AMA <groups03@...>

#755

Dave,

You have described exactly my thinking when I coded the US States alert.

Once you get down to one or two left to complete WAS, then all alerts for a needed State and not just a CQing State are the best way to catch that elusive one.

I will add the CQ only option to the todo list. It will require some changes to the alerting logic as all alerts are currently independent of each other. It probably wont make the next release as I am focusing on the bugs and missing log scan for Continent alerts of the last fast-tracked release.

Regards
Laurie, VK3AMA

On 01-March-2012 03:30, Dave Wright wrote:

Show quoted text

Personally, I like it the way it is.ï¿½ Sometimes, that "hard to catch" station isn't calling CQ, but is working those that are calling CQ.ï¿½ Just the other day, I caught an Arkansas station that I needed to finish my WAS JT-65.ï¿½ He wasn't calling CQ, but was chasing others that were. Once I knew he was active and was alerted by JT-Alert, I was able to find a clear space on the band and when he finished his QSO, I just put the call out there to him....he came back to me right away and now I'm just waiting for LoTW to match the QSO and I have my WAS JT-65.ï¿½

If it were set for CQ only, I would have missed that opportunity as I wasn't looking at the rig.

Now, if it could be selectable "on/off" for CQ only, then that might be useful.

Dave
K3DCW
www.k3dcw.net

"Real radio bounces off of the sky"

On Wed, Feb 29, 2012 at 11:17 AM, n0rq <n0rq-lists@...> wrote:

ï¿½

I'm wondering if anyone else would be interested in an option like this...

Instead of an alert when a wanted state is decoded, I was thinking it would be nice to have the option of having the alert only if the wanted state is sending a CQ (instead of just being heard).

Right now, JT-Alert tells me "CQ West Virginia" -- but the CQ is from Texas (or wherever), and the WV station was answering someone else. I'd like to hear the "West Virginia" announced only if the WV station is himself calling CQ.

Is that something that others would like? It is feasible?

I'm not trying to create more work for Laurie -- really! :-) ----- but just thought it would be a useful enhancement/option.

73, Dave N0RQ
http://www.powerlinenoise.com/n0rq/JT65-HF/

HRD logging

AB9QU

#754

					I have the box checked for HRD logging but get an error message. It does load to the jt logger so I have been loading that into the HRD log.
Is there something you need to do in HRD to make the log from jt65 to work?
thanks
73  Bill  ab9qu
				

Re: WANTED STATE alert only on CQ from that state?

n0rq

#752

					Understood, and agreed - that scenario is real as well.

And yes, I was suggesting only that it be ON/OFF (an option in the settings).

Dave N0RQ

Show quoted text

							--- In Ham-Apps@..., Dave Wright <hfradiopro@...> wrote:
Now, if it could be selectable "on/off" for CQ only, then that might be useful.
						

Re: [Ham-Apps] WANTED STATE alert only on CQ from that state?

KB3TC <kb3tc1@...>

#753

I think that would be a great option to have. Many times I have come back to the screen (you are not always watching it are you) to find out it was not a state I was looking for calling CQ but it just recognized that it WAS that state that I needed.
Then, I would sit and wait for my turn to call that station, sometimes to no avail.
So, if it were an 'option', that would be good.
Tim, KB3TC

On 2/29/2012 11:17 AM, n0rq wrote:

Show quoted text

I'm wondering if anyone else would be interested in an option like this...

Instead of an alert when a wanted state is decoded, I was thinking it would be nice to have the option of having the alert only if the wanted state is sending a CQ (instead of just being heard).

Right now, JT-Alert tells me "CQ West Virginia" -- but the CQ is from Texas (or wherever), and the WV station was answering someone else. I'd like to hear the "West Virginia" announced only if the WV station is himself calling CQ.

Is that something that others would like? It is feasible?

I'm not trying to create more work for Laurie -- really! :-) ----- but just thought it would be a useful enhancement/option.

73, Dave N0RQ
http://www.powerlinenoise.com/n0rq/JT65-HF/

Re: [Ham-Apps] WANTED STATE alert only on CQ from that state?

Dave Wright <hfradiopro@...>

#751

Personally, I like it the way it is. Sometimes, that "hard to catch" station isn't calling CQ, but is working those that are calling CQ. Just the other day, I caught an Arkansas station that I needed to finish my WAS JT-65. He wasn't calling CQ, but was chasing others that were. Once I knew he was active and was alerted by JT-Alert, I was able to find a clear space on the band and when he finished his QSO, I just put the call out there to him....he came back to me right away and now I'm just waiting for LoTW to match the QSO and I have my WAS JT-65.

If it were set for CQ only, I would have missed that opportunity as I wasn't looking at the rig.

Now, if it could be selectable "on/off" for CQ only, then that might be useful.

Dave
K3DCW
www.k3dcw.net

"Real radio bounces off of the sky"

Show quoted text

On Wed, Feb 29, 2012 at 11:17 AM, n0rq <n0rq-lists@...> wrote:

I'm wondering if anyone else would be interested in an option like this...

Instead of an alert when a wanted state is decoded, I was thinking it would be nice to have the option of having the alert only if the wanted state is sending a CQ (instead of just being heard).

Right now, JT-Alert tells me "CQ West Virginia" -- but the CQ is from Texas (or wherever), and the WV station was answering someone else. I'd like to hear the "West Virginia" announced only if the WV station is himself calling CQ.

Is that something that others would like? It is feasible?

I'm not trying to create more work for Laurie -- really! :-) ----- but just thought it would be a useful enhancement/option.

73, Dave N0RQ
http://www.powerlinenoise.com/n0rq/JT65-HF/

WANTED STATE alert only on CQ from that state?

n0rq

#750

					I'm wondering if anyone else would be interested in an option like this...

Instead of an alert when a wanted state is decoded, I was thinking it would be nice to have the option of having the alert only if the wanted state is sending a CQ (instead of just being heard).

Right now, JT-Alert tells me "CQ West Virginia" -- but the CQ is from Texas (or wherever), and the WV station was answering someone else.  I'd like to hear the "West Virginia" announced only if the WV station is himself calling CQ.

Is that something that others would like?  It is feasible?

I'm not trying to create more work for Laurie -- really! :-) ----- but just thought it would be a useful enhancement/option.

73, Dave N0RQ
http://www.powerlinenoise.com/n0rq/JT65-HF/

Re: [Ham-Apps] Up-Date

Bill Duffy

#749

Tnx for both your emails!

I looked at that page a loot of times and never saw the Box to check!

73

Bill

KA0VXK

Show quoted text

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Tuesday, February 28, 2012 9:59 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Up-Date

Bill you need to enable DXKeeper logging. The titlebar message "[No Log"] indicates you have no log enabled. You need to enable logging by ticking the checkbox on the "DXLab DXKeeper" section of the configuration window. Once that is done, the "[DXKeeper]" message will appear in the JT-Alert titlebar. Logging will now be operational.

de Laurie, VK3AMA

On 29-February-2012 05:46, Bill Duffy wrote:

Hi Laurie…… It’s installed per instruction.

Only problem is that it does not talk to DXK 10.0.2!

I checked the config file and it seems to be correct.

Suggestions?

73

Bill

KA0VXK

,_._,___

Re: [Ham-Apps] Up-Date

Laurie, VK3AMA <groups03@...>

#748

Bill you need to enable DXKeeper logging. The titlebar message "[No Log"] indicates you have no log enabled. You need to enable logging by ticking the checkbox on the "DXLab DXKeeper" section of the configuration window. Once that is done, the "[DXKeeper]" message will appear in the JT-Alert titlebar. Logging will now be operational.

de Laurie, VK3AMA

On 29-February-2012 05:46, Bill Duffy wrote:

Show quoted text

Hi Laurie…… It’s installed per instruction.

Only problem is that it does not talk to DXK 10.0.2!

I checked the config file and it seems to be correct.

Suggestions?

73

Bill

KA0VXK

,_._,___

Re: [Ham-Apps] Up-Date

Laurie, VK3AMA <groups03@...>

#747

Bill,

Are you getting an error message?

Use the "Contact Support" menu to send me your session files for review.

I am using DXKeeper 10.0.2 without problem.

de Laurie, VK3AMA

On 29-February-2012 05:46, Bill Duffy wrote:

Show quoted text

Hi Laurie…… It’s installed per instruction.

Only problem is that it does not talk to DXK 10.0.2!

I checked the config file and it seems to be correct.

Suggestions?

73

Bill

KA0VXK

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Monday, February 27, 2012 9:01 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Up-Date

Hi Bill,

Yes, these are the latest instructions. They only apply if upgrading from ver 1.4.x or earlier. If already running a 1.5.x version then just apply the latest setup.

de Laurie, VK3AMA

On 28-February-2012 13:17, Bill Duffy wrote:

Laurie……With the recent changes, are these instructions still the latest?

Tnx es 73

Bill

KA0VXK

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Sunday, February 26, 2012 6:05 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Up-Date

Bill,

A minor change to the upgrade instructions.

Download 1.5.2 from here.

Install JT-Alert 1.5.2

Run JT-Alert 1.5.2 then close.

Download the latest JT-Alert 1.6.0 from here.

Upgrade 1.5.2 to 1.6.0 by running the 1.6.0 setup.

de Laurie, VK3AMA

On 27-February-2012 10:55, Laurie, VK3AMA wrote:

Hi Bill,

You should be able to upgrade without error. What error are you getting?

Since you are trying to upgrade a very old version, your registry based settings will not get upgraded to the new file based settings introduced in v1.5.0 The upgrade code to migrate those settings was removed with v1.5.4 due to some compatibility issues with the v1.5.3 code.

The best way to upgrade and retain your settings follow these steps...

Download 1.5.2 from here.

Run JT-Alert 1.5.2 then close.

Download the latest JT-Alert 1.6.0 from here.

Upgrade 1.5.2 to 1.6.0 by running the 1.6.0 setup.

That should get you running.

Let me know if this works for you.

de Laurie, VK3AMA

On 27-February-2012 10:37, Bill Duffy wrote:

I currently am using JT-Alert 1.4.1.

I have tried , unsuccessfully several times to upgrade it.

Should I delete 1.4.1 BEFORE attempting an upgrade or???

Suggestions are welcome.

Tnx es 73

Bill

KA0VXK

_

Re: [Ham-Apps] Up-Date

Bill Duffy

#746

Hi Laurie…… It’s installed per instruction.

Only problem is that it does not talk to DXK 10.0.2!

I checked the config file and it seems to be correct.

Suggestions?

73

Bill

KA0VXK

Show quoted text

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Monday, February 27, 2012 9:01 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Up-Date

Hi Bill,

Yes, these are the latest instructions. They only apply if upgrading from ver 1.4.x or earlier. If already running a 1.5.x version then just apply the latest setup.

de Laurie, VK3AMA

On 28-February-2012 13:17, Bill Duffy wrote:

Laurie……With the recent changes, are these instructions still the latest?

Tnx es 73

Bill

KA0VXK

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Laurie, VK3AMA
Sent: Sunday, February 26, 2012 6:05 PM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Up-Date

Bill,

A minor change to the upgrade instructions.

Download 1.5.2 from here.
Install JT-Alert 1.5.2
Run JT-Alert 1.5.2 then close.
Download the latest JT-Alert 1.6.0 from here.
Upgrade 1.5.2 to 1.6.0 by running the 1.6.0 setup.

de Laurie, VK3AMA

On 27-February-2012 10:55, Laurie, VK3AMA wrote:

Hi Bill,

You should be able to upgrade without error. What error are you getting?

Since you are trying to upgrade a very old version, your registry based settings will not get upgraded to the new file based settings introduced in v1.5.0 The upgrade code to migrate those settings was removed with v1.5.4 due to some compatibility issues with the v1.5.3 code.

The best way to upgrade and retain your settings follow these steps...

Download 1.5.2 from here.
Run JT-Alert 1.5.2 then close.
Download the latest JT-Alert 1.6.0 from here.
Upgrade 1.5.2 to 1.6.0 by running the 1.6.0 setup.

That should get you running.

Let me know if this works for you.

de Laurie, VK3AMA

On 27-February-2012 10:37, Bill Duffy wrote:

I currently am using JT-Alert 1.4.1.

I have tried , unsuccessfully several times to upgrade it.

Should I delete 1.4.1 BEFORE attempting an upgrade or???

Suggestions are welcome.

Tnx es 73

Bill

KA0VXK

__

Re: [Ham-Apps] New JT-Alert Sound & Voice Files V1.0.3 available for download

hb9ari <hb9ari@...>

#745

Hi Laurie,

Difficult to explain for a French speaking OM...

With the V 1.0.2, i can hear: " see q " for "CQ" UFB !
with V 1.0.3, i hear something like " ee kay oh"
(in both case female voices)

But, no importance, both JT-Alert and JT-Macros are
used "intensively" here with great pleasure!

Thank you and 73 QRO

Rudi

PS Just a little "info" last week i saw you calling (or in QSO i don't remember
exactly) in JT65, on 20 or 30m; what i can be sure, is that you effectively
had some drift (~20 to 30 Hz) during the 1 min sequence. I'm sure because
i thought : " Hi, Laurie has some drift " (hi!)
If this can help you ?

Le 23.02.2012 07:43, Laurie, VK3AMA a écrit :

Show quoted text

Hi Rudi,

Not sure I fully understand what you are describing.
Was this on all Female voice files or only specific files?

The voice wave files were created on my Win7 X64/Professional PC.

When I release the next version of JT-Alert there will be a new release of voice files that will provide some additional voice types that may be easier to understand along with some additional files for the new WAC alert.

Regards
Laurie, VK3AMA

On 23-February-2012 17:29, hb9ari wrote:

Hi Laurie,

I tried V 1.0.3 with female voices but on
my system (W7 64b/ultimate) i can't
understand the alerts; for example,
CQ is CQ (...) with V 1.0.2 and was something
like EKO with V 1.0.3; after re-installing
V 1.0.2, all is ok.

Thank you for your sharing your work.

73 QRO,
Rudi, HB9ARI

Le 19.02.2012 06:34, Laurie, VK3AMA a écrit :

JT-Alert Sound & Voice Files V1.0.3 is available for download from...
http://ham-apps.com/dnl/JT-Alert/JT-Alert_Sounds_1.0.3_Setup.exe

This release includes an additional wave file for the new JT-Alert WAZ alert (available in the next release).

All the voice files have been regenerated using newer voice synthesis software to overcome some of the pronunciation oddities of the old files. All the voice files have been normalised in volume so that regarless of the alert, the files all play at the same volume.

de Laurie, VK3AMA