Date   

locked Re: JTMacros

Laurie, VK3AMA <groups07@...>
 

On 21/02/2015 6:24 AM, jean raynaud f8rz@... [HamApps] wrote:
Hello...

In a previous setup, I used a macro "@ RRR 73" which worked fine and
checked the right "target" in the "next" column od WSJT-X.

Now, the macro still works but doesn't anymore check the right "target",
and if I am not very careful, I send anything but what I should like to.

And YES, the "Don't activate" box in JTMacros is UNchecked...

Anyone has a solution ?

Thanks by advance

73 Jean F8RZ

Jean,

What version of WSJT-X? I may have to make adjustments if it is a version I have not tested yet.

Due to the QT library used by WSJT-X, there is no way to programatically set the Tx5 radio button, so JTAlert has to use the physical position of the radio button on the WSJT-X window and generate a mouse-click at that position. The position tends to change with each version of WSJT-X. Please advise the version.

de Laurie VK3AMA
   


locked Re: jt alert not working

Jim - N4ST
 

Have you thought about trying WSJT-X?
You would get JT65 & JT9 and the software has been very reliable for me and works well with JT-Alert-X.

_________
73,
Jim - N4ST


From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Friday, February 20, 2015 12:09
To: HamApps@yahoogroups.com.au
Subject: [HamApps] jt alert not working


my wife is having a problem with jt alert, we have completely uninstall all version have disable the real time scan of McAfee went a older version of jt alert that did not work, Uninstall McAfee removed all version of Jt Alert for jt-65 comfort. Can anyone tell us what else We can do. and Yes everytime we uninstalled the program we did a reboot. She is running window 7 64 bit.
Wade K5WPN


locked JTMacros

F8RZ
 

Hello...

In a previous setup, I used a macro "@ RRR 73" which worked fine and
checked the right "target" in the "next" column od WSJT-X.

Now, the macro still works but doesn't anymore check the right "target",
and if I am not very careful, I send anything but what I should like to.

And YES, the "Don't activate" box in JTMacros is UNchecked...

Anyone has a solution ?

Thanks by advance

73 Jean F8RZ

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com


locked jt alert not working

Wade Norris
 

my wife is having a problem with jt alert, we have completely uninstall all version have disable the real time scan of McAfee went a older version of jt alert that did not work, Uninstall McAfee removed all version of Jt Alert for jt-65 comfort. Can anyone tell us what else We can do. and Yes everytime we uninstalled the program we did a reboot. She is running window 7 64 bit.

Wade K5WPN


locked WSJT-Suite v1.0.18 Available - (Hamlib3 & WSJT-X 1.5 Updates)

KI7MT <ki7mt@...>
 

Hello All,

Bill has recently committed a number of Hamlib3 rig control improvements, and several WSJTX-1.5 / 1.4 RC updates. The summary of changes is listed below. I dug out as many rigs as I could identify from a query between my last Hamlib3 build and today's, see list below. WSJTX 1.5 / 1.4 RC were both built against the Hamlib3 build I ran today.

If your using JTSDK v2, you can build the latest public version posted in Bills Git repo by opening JTSDK-MSYS, then type: build-hamlib3
After completion re-build WSJT-X 1.5 / 1.4 RC with JTSDK-QT.


INSTALLATION

DOWNLOAD v1.0.18:
-Preview Link: http://preview.tinyurl.com/m7mvm77
-Download Link: http://tinyurl.com/m7mvm77
-SHA1: 90ecdf0d1986f0c7608befb33ce95bae97e73a40
-MD5SUM: 376c253c0dd2b6003d7df67c45dc5164

UNINSTALL & INSTALL
* Using the uninstaller, remove any previous installations
* Install v.1.0.18 as you normally would


BRIEF CHANGE LOG SUMMARY
* WSJT-X v1.5:
-Add a progress dialog to show that FFT optimization is doing something
-Updated abbreviations in DXXCC country names
-Updated split functionality
-Added scroll bard for extended country names if needed
-Populate serial port lists with available actual devices

* WSJT-X v1.4 (RC)
-Updated split functionality

* Hamlib3 build date: 20-FEB-2015
-Many rigs received updates

* WSPR, no change for Windows
* WSJT, no change
* WSPR-X, no change
* MAP65, no change

Full change history & comments:
https://sourceforge.net/p/wsjt/wsjt/4980/log/


HAMLIB3 RIG CONTROL UPDATES
flex6xxx, k2, k3, r5000, thd72, thf6a, thf7
thg71, tmd710, tmv7, transfox, ts140, ts2000
ts2k, ts440, ts480, ts570, ts680, ts711,
ts811, ts850, ts870s, ts940, xg3, ft817
ft857, ft897, ft980


As always, if you have problems with the WSJT-Suite, please report them
to the WSJT-Devel List: < wsjt-devel@lists.sourceforge.net >


73's
Greg, KI7MT

----------------------------------------------------------------
Launchpad....: https://launchpad.net/~ki7mt
Ubuntu Hams..: https://launchpad.net/~ubuntu-hams-devel
Debian hams..: https://alioth.debian.org/projects/pkg-hamradio/
JTSDK .......: https://sourceforge.net/projects/jtsdk/
OpenPGP......: C177 6630 7115 78FE 9A2B 9F7F 18C0 F6B7 0DA2 F991


locked JTSDK v1.0.0 Win32 End Of Life Notification

KI7MT <ki7mt@...>
 

Hello All,

This is a notification that on or about March 1st 2015, we will be
ending support for the original JTSDK (v1.0.0) for Windows.

An archive copy of the original installers, dev-guide, build and
environment scripts will be available on SourceForge JTSDK in the
Files/Win32/1.0.0 folder.

Baring any unforeseen critical issues, the intension is to release JTSDK
v2 at the same time. Over the last month or so there has been a few new
issues reported, most were minor clerical items. If you have a problem
or feel something needs to be addressed, added or tweaked, the next week
or so would be a good time to get them taken care of before the initial
release of JTSDK v2

Many thanks goes out to all those giving their time testing, using and
reporting issues, all of which helps Joe, Bill, John and the rest of the
core developers give us a fantastic set applications to use in our hobby.


73's
Greg, KI7MT

----------------------------------------------------------------
Launchpad....: https://launchpad.net/~ki7mt
Ubuntu Hams..: https://launchpad.net/~ubuntu-hams-devel
Debian Hams..: https://alioth.debian.org/projects/pkg-hamradio/
JTSDK........: https://sourceforge.net/projects/jtsdk/
OpenPGP......: C177 6630 7115 78FE 9A2B 9F7F 18C0 F6B7 0DA2 F991


locked Re: Wrong Time Being Logged

Joe Subich, W4TV
 

Rather than clearing and re-entering the DX Call in WSJT-X, a
double-click of the time field of JTAlert will reset the time to the
current UTC minute. JTAlert will use this time as the "TIME_ON" for
logging.
That's fine if one displays all the extra stuff. I don't - I only
display the two rows of calls rather than give up all the extra
vertical height on the display.

73,

... Joe, W4TV


On 2015-02-19 7:28 PM, 'Laurie, VK3AMA' groups07@vkdxer.com [HamApps] wrote:


On 19/02/2015 7:25 AM, 'Joe Subich, W4TV' lists@subich.com [HamApps] wrote:
The only way to avoid the problem is to strike F4 to clear the DX
station and then reneter the DX Station each time you call. I find
it far easier to edit the start time in the logger (DXKeeper, in my
case).

The start time is recorded by WSJT-X not JT-Alert.

73,

... Joe, W4TV
Joe, WSJT-X doesn't provide a QSO start time. It records the end time only (QSO
logged time), but logs it as the adif tag "TIME_ON" which should be "TIME_OFF".
Rather than clearing and re-entering the DX Call in WSJT-X, a double-click of
the time field of JTAlert will reset the time to the current UTC minute. JTAlert
will use this time as the "TIME_ON" for logging.

de Laurie VK3AMA




locked Re: Wrong Time Being Logged

Laurie, VK3AMA <groups07@...>
 

On 19/02/2015 10:46 AM, 'Michael Black' mdblack98@... [HamApps] wrote:

Or you can manually set the time in the alert field.

 

Double click the time field will set it to the current UTC time. Hover the mouse over the "Time" label for a tooltip explanation.

de Laurie VK3AMA
   


locked Re: Wrong Time Being Logged

Laurie, VK3AMA <groups07@...>
 

On 19/02/2015 7:25 AM, 'Joe Subich, W4TV' lists@... [HamApps] wrote:
The only way to avoid the problem is to strike F4 to clear the DX
station and then reneter the DX Station each time you call. I find
it far easier to edit the start time in the logger (DXKeeper, in my
case).

The start time is recorded by WSJT-X not JT-Alert.

73,

... Joe, W4TV
Joe, WSJT-X doesn't provide a QSO start time. It records the end time only (QSO logged time), but logs it as the adif tag "TIME_ON" which should be "TIME_OFF". Rather than clearing and re-entering the DX Call in WSJT-X, a double-click of the time field of JTAlert will reset the time to the current UTC minute. JTAlert will use this time as the "TIME_ON" for logging.

de Laurie VK3AMA
   


locked Re: Wrong Time Being Logged

Laurie, VK3AMA <groups07@...>
 

On 19/02/2015 6:23 AM, Jim Preston jpreston1@... [HamApps] wrote:
Laurie,

First, thank you for an excellent program and excellent support.

Now for my problem.

I have JTAlert 2.5.6 set to log to Ham Radio Deluxe. Everything works
fine except for the time. As an example, today another station called CQ
at 1817. I answered him at 1818, but he came back to another station. He
called CQ again at 1825 and I called him again. This time we had a QSO.
However, when it was logged to HRD, the time of the QSO showed as 1817.

This time difference is probably acceptable to LOTW, etc. However, I
recently had another QSO where the time difference was more than 90 minutes.

It seems the time logged is based on the first time I call a station,
regardless of whether this is the actual time of the QSO.

I realize I can just edit the HRD log (which I do), but it nice not to
have to do so.

Is there any way to change this?

I also use WSJT-X v1.4.0-rc2 and HRD 6.2.8.330 on Win 8.1

73,

N6VH
That start time being logged is the time when JTAlert first detected a new QSO partner callsign. Which occured when you first double-clicked the decode. You will see the time in the log fields area of JTAlert. JTAlert has no way of knowing that youu were not in QSO with that callsign until much later. In the situation you describe, a double-click on the time field will reset it to the current UTC time.

This time field was provided
due to many requests I received for accurate start time logging since WSJT-X only includes the end time (when logged) in the log data. Since JTAlert doesn't track the progress of QSOs, only looking at decodes and the logging event of WSJT-X, it has no way of knowing when the QSO actually started, so a change in QSO partner callsign (which usually occurs when you first double-click a decode for that callsign) was the only way to get a best guess of the start time.

Rather than edit the HRD log post logging, it would be easier to simply double-click the time field when the QSO does indeed start.

de Laurie VK3AMA
   


locked Re: late TX with WSJTX

Laurie, VK3AMA <groups07@...>
 

On 20/02/2015 2:11 AM, wa7ag@... [HamApps] wrote:
 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .
 I recently changed PC's and that's when the problem started. 
 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .
 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,
ans it won't decode rec"d signals .
  Has anyone had this problem , and if so, what was the " fix " ?
thanks,
Art

Art,

If your TX is starting late as indicated by the Clock in WSJT-X then it is unlikely to be a time sync problem. If you time was grossly out, you would still see WSJT-X starting to TX at the start of the minute, regardless of how far out the clock is.

I don't have a definitive answer, but I suggest you look to your Virus/Malware software as possible causes. Try disabling them to see if that removes the delay. My thinking is that your virus software is delaying a process or some sort of internal Windows communication and WSJT-X is waiting for that to complete before starting to TX.

de Laurie VK3AMA


locked Re: late TX with WSJTX

Michael Black
 

Also…a couple of freebees…ensure you are not underclocking the CPU or overclocking it.

And if you have power saving settings in the BIOS turn them off.  I had problems with some systems before due to the power saving messing with the clock.

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 5:19 PM
To: HamApps@...
Subject: RE: [HamApps] late TX with WSJTX

 

 

Try replacing the CMOS battery in your computer.

It can make the clock behave strangely if it'slow.

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 4:45 PM
To: HamApps@...
Subject: RE: [HamApps] late TX with WSJTX

 

 

 

 

Art's time may be a bit off (been there, had that done to me); but I'm surprised by the duration of his transmissions. Way too short.

 

Can that be caused by not being within a few seconds of real time?

 

Erik

 

 

K5WW ~ on the road!


"'Michael Black' mdblack98@... [HamApps]" <HamApps@...> wrote:
 

Tune your radio to WWV for a sanity check on time.

WWV runs on 2.5, 5, 10, 15, and 20MHz

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 4:25 PM
To: HamApps@...
Subject: Re: [HamApps] late TX with WSJTX

 

 

I use " ATOMIC " to syc the computer to UTC from Boulder Colorado .

You can Google " atomic "  to download .

73,

Art

 

On Thursday, February 19, 2015 1:36 PM, "Robert Lorenzini bob@... [HamApps]" <HamApps@...> wrote:

 

 

Tell us how you sync your time.

Bob - wd6dod

On 2/19/2015 7:11 AM, wa7ag@... [HamApps] wrote:

 

 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .

 I recently changed PC's and that's when the problem started. 

 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .

 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,

ans it won't decode rec"d signals .

  Has anyone had this problem , and if so, what was the " fix " ?

thanks,

Art

 

 


locked Re: late TX with WSJTX

Michael Black
 

Try replacing the CMOS battery in your computer.

It can make the clock behave strangely if it'slow.

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 4:45 PM
To: HamApps@...
Subject: RE: [HamApps] late TX with WSJTX

 

 

 

 

Art's time may be a bit off (been there, had that done to me); but I'm surprised by the duration of his transmissions. Way too short.

 

Can that be caused by not being within a few seconds of real time?

 

Erik

 

 

K5WW ~ on the road!


"'Michael Black' mdblack98@... [HamApps]" <HamApps@...> wrote:
 

Tune your radio to WWV for a sanity check on time.

WWV runs on 2.5, 5, 10, 15, and 20MHz

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 4:25 PM
To: HamApps@...
Subject: Re: [HamApps] late TX with WSJTX

 

 

I use " ATOMIC " to syc the computer to UTC from Boulder Colorado .

You can Google " atomic "  to download .

73,

Art

 

On Thursday, February 19, 2015 1:36 PM, "Robert Lorenzini bob@... [HamApps]" <HamApps@...> wrote:

 

 

Tell us how you sync your time.

Bob - wd6dod

On 2/19/2015 7:11 AM, wa7ag@... [HamApps] wrote:

 

 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .

 I recently changed PC's and that's when the problem started. 

 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .

 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,

ans it won't decode rec"d signals .

  Has anyone had this problem , and if so, what was the " fix " ?

thanks,

Art

 

 


locked Re: late TX with WSJTX

Erik - K5WW <k5ww@...>
 



Art's time may be a bit off (been there, had that done to me); but I'm surprised by the duration of his transmissions. Way too short.

Can that be caused by not being within a few seconds of real time?

Erik


K5WW ~ on the road!

"'Michael Black' mdblack98@... [HamApps]" <HamApps@...> wrote:
 

Tune your radio to WWV for a sanity check on time.

WWV runs on 2.5, 5, 10, 15, and 20MHz

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 4:25 PM
To: HamApps@...
Subject: Re: [HamApps] late TX with WSJTX

 

 

I use " ATOMIC " to syc the computer to UTC from Boulder Colorado .

You can Google " atomic "  to download .

73,

Art

 

On Thursday, February 19, 2015 1:36 PM, "Robert Lorenzini bob@... [HamApps]" <HamApps@...> wrote:

 

 

Tell us how you sync your time.

Bob - wd6dod

On 2/19/2015 7:11 AM, wa7ag@... [HamApps] wrote:

 

 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .

 I recently changed PC's and that's when the problem started. 

 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .

 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,

ans it won't decode rec"d signals .

  Has anyone had this problem , and if so, what was the " fix " ?

thanks,

Art

 

 


locked Re: late TX with WSJTX

Michael Black
 

Tune your radio to WWV for a sanity check on time.

WWV runs on 2.5, 5, 10, 15, and 20MHz

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Thursday, February 19, 2015 4:25 PM
To: HamApps@...
Subject: Re: [HamApps] late TX with WSJTX

 

 

I use " ATOMIC " to syc the computer to UTC from Boulder Colorado .

You can Google " atomic "  to download .

73,

Art

 

On Thursday, February 19, 2015 1:36 PM, "Robert Lorenzini bob@... [HamApps]" <HamApps@...> wrote:

 

 

Tell us how you sync your time.

Bob - wd6dod

On 2/19/2015 7:11 AM, wa7ag@... [HamApps] wrote:

 

 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .

 I recently changed PC's and that's when the problem started. 

 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .

 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,

ans it won't decode rec"d signals .

  Has anyone had this problem , and if so, what was the " fix " ?

thanks,

Art

 

 


locked Re: late TX with WSJTX

Art Galvez <wa7ag@...>
 

I use " ATOMIC " to syc the computer to UTC from Boulder Colorado .
You can Google " atomic "  to download .
73,
Art


On Thursday, February 19, 2015 1:36 PM, "Robert Lorenzini bob@... [HamApps]" wrote:


 
Tell us how you sync your time.

Bob - wd6dod

On 2/19/2015 7:11 AM, wa7ag@... [HamApps] wrote:
 
 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .
 I recently changed PC's and that's when the problem started. 
 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .
 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,
ans it won't decode rec"d signals .
  Has anyone had this problem , and if so, what was the " fix " ?
thanks,
Art




locked Re: late TX with WSJTX

Robert Lorenzini
 

Tell us how you sync your time.

Bob - wd6dod

On 2/19/2015 7:11 AM, wa7ag@... [HamApps] wrote:
 

 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .

 I recently changed PC's and that's when the problem started. 

 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .

 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,

ans it won't decode rec"d signals .

  Has anyone had this problem , and if so, what was the " fix " ?

thanks,

Art



locked late TX with WSJTX

wa7ag@...
 

 My transmit strats 29 seconds past the minuet ,and stops at 58 seconds past the minuet .

 I recently changed PC's and that's when the problem started. 

 I am using a Gateway Laptop with 500 gig HDD, 4 gigs DDR3 of memory .

 WSJTX worked fine for about two days the the late transmitt started, and of course, no contacts are made,

ans it won't decode rec"d signals .

  Has anyone had this problem , and if so, what was the " fix " ?

thanks,

Art


locked Re: Wrong Time Being Logged

Jim N6VH
 

Joe and Mike,

Thanks for the replies. I see that I will need to pay better attention to the time field.

Normally, I do check help files in situations like this, but this time I failed to do so. My apologies.

73,

Jim N6VH

On 18-Feb-15 3:46 PM, 'Michael Black' mdblack98@yahoo.com [HamApps] wrote:
JT-Alert does control the start time…it's the one sending the log entry
and the start time is in the "Time" box of the alert fields on JTAlert.

The start time is set when you double-click an entry different from what
you currently have.

So…click off differerent…click on…will get you where you need to go.

Or you can manually set the time in the alert field.

I'd like to see it take the first message to the callsign as the start
time. But JTAlert doesn't have that info and I think Laurie has
addressed this before.

Search the Help for "Time Field" and select "Log Fields Display". It
explains it there.

Mike W9MDB

*From:*HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
*Sent:* Wednesday, February 18, 2015 2:25 PM
*To:* HamApps@yahoogroups.com.au
*Subject:* Re: [HamApps] Wrong Time Being Logged


> Is there any way to change this?

The only way to avoid the problem is to strike F4 to clear the DX
station and then reneter the DX Station each time you call. I find
it far easier to edit the start time in the logger (DXKeeper, in my
case).

The start time is recorded by WSJT-X not JT-Alert.

73,

... Joe, W4TV

On 2015-02-18 2:23 PM, Jim Preston jpreston1@cox.net
<mailto:jpreston1@cox.net> [HamApps] wrote:
> Laurie,
>
> First, thank you for an excellent program and excellent support.
>
> Now for my problem.
>
> I have JTAlert 2.5.6 set to log to Ham Radio Deluxe. Everything works
> fine except for the time. As an example, today another station called CQ
> at 1817. I answered him at 1818, but he came back to another station. He
> called CQ again at 1825 and I called him again. This time we had a QSO.
> However, when it was logged to HRD, the time of the QSO showed as 1817.
>
> This time difference is probably acceptable to LOTW, etc. However, I
> recently had another QSO where the time difference was more than 90
minutes.
>
> It seems the time logged is based on the first time I call a station,
> regardless of whether this is the actual time of the QSO.
>
> I realize I can just edit the HRD log (which I do), but it nice not to
> have to do so.
>
> Is there any way to change this?
>
> I also use WSJT-X v1.4.0-rc2 and HRD 6.2.8.330 on Win 8.1
>
> 73,
>
> N6VH
>
>
> ------------------------------------
> Posted by: Jim Preston <jpreston1@cox.net <mailto:jpreston1@cox.net>>
> ------------------------------------
>
>
> ------------------------------------
>
> Yahoo7 Groups Links
>
>
>
>


locked Re: Wrong Time Being Logged

Michael Black
 

JT-Alert does control the start time…it's the one sending the log entry and the start time is in the "Time" box of the alert fields on JTAlert.

The start time is set when you double-click an entry different from what you currently have.

So…click off differerent…click on…will get you where you need to go.

Or you can manually set the time in the alert field.

 

I'd like to see it take the first message to the callsign as the start time.  But JTAlert doesn't have that info and I think Laurie has addressed this before.

 

Search the Help for "Time Field" and select "Log Fields Display".  It explains it there.

 

Mike W9MDB

 

 

From: HamApps@... [mailto:HamApps@...]
Sent: Wednesday, February 18, 2015 2:25 PM
To: HamApps@...
Subject: Re: [HamApps] Wrong Time Being Logged

 

 


> Is there any way to change this?

The only way to avoid the problem is to strike F4 to clear the DX
station and then reneter the DX Station each time you call. I find
it far easier to edit the start time in the logger (DXKeeper, in my
case).

The start time is recorded by WSJT-X not JT-Alert.

73,

... Joe, W4TV

On 2015-02-18 2:23 PM, Jim Preston jpreston1@... [HamApps] wrote:
> Laurie,
>
> First, thank you for an excellent program and excellent support.
>
> Now for my problem.
>
> I have JTAlert 2.5.6 set to log to Ham Radio Deluxe. Everything works
> fine except for the time. As an example, today another station called CQ
> at 1817. I answered him at 1818, but he came back to another station. He
> called CQ again at 1825 and I called him again. This time we had a QSO.
> However, when it was logged to HRD, the time of the QSO showed as 1817.
>
> This time difference is probably acceptable to LOTW, etc. However, I
> recently had another QSO where the time difference was more than 90 minutes.
>
> It seems the time logged is based on the first time I call a station,
> regardless of whether this is the actual time of the QSO.
>
> I realize I can just edit the HRD log (which I do), but it nice not to
> have to do so.
>
> Is there any way to change this?
>
> I also use WSJT-X v1.4.0-rc2 and HRD 6.2.8.330 on Win 8.1
>
> 73,
>
> N6VH
>
>
> ------------------------------------
> Posted by: Jim Preston <jpreston1@...>
> ------------------------------------
>
>
> ------------------------------------
>
> Yahoo7 Groups Links
>
>
>
>