Date   

locked Re: JTAlertX 2.10.1 with DXKeeper V14.1.0 #DXLAB

Joe Subich, W4TV
 

As I am I the same camp as you we can only hope that the ability to populate the Capture window will be re-introduced in a future
version of JT-Alert that is actually coded to do this rather than be
an error.
There is *never* any reason to display the WSJT-X/JTAlertX data in
DXKeeper's Capture window as that window is not used for logging with
JT-Alert. At best Capture provides only a sub-set of the data available
in DXKeeper's Log QSOs tab (for stations previously worked) or
Pathfinder (for stations not worked).

JT-Alert 2.10.1 provides the opportunity to display the results of any
look-up in DXKeeper (Main Window - previous QSOs), DXView (DXCC Realtime
Award Tracking), and Pathfinder (QRZ.com or HamQTH.com "callbook"
lookup) based on the user's choices in "Settings -> Applications ->
DXLab Suite".

73,

... Joe, W4TV


On 8/20/2017 10:43 AM, John Etling wrote:
This issue was previously discussed in the wsjtgroup forum – originated by myself. It was determined at that time that DXCapture would no longer be populated and was previously populated as the result of some error in the code (never reported properly the working mode). It was/is being considered to reintroduce that possibility in a future update of WSJT-x (BTW: this is NOT a DXLabs issue).
As I am I the same camp as you we can only hope that the ability to populate the Capture window will be re-introduced in a future version of JT-Alert that is actually coded to do this rather than be an error.
I’m Just Sayin’
73 de K3JAE
John
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of on6at@telenet.be
Sent: Sunday, August 20, 2017 09:32
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlertX 2.10.1 with DXKeeper V14.1.0 #DXLAB
Hello,
I use DxLab with the latest versions. (DxKeeper V14.1.0 - Pathfinder 5.2.2 - DXView 4.3.2.)
together with JTAlertX v2.10.1 and WSJT-X v1.8.0-rc1
What's the problem?
I'm making a qso with eg EA8AQV.
Via JTAlert, a command is sent to DxKeeper to request the call sign.
In the past, this call sign came in the Capture window. On that way, all the data was visible through Pathfinder.
Now the call sign EA8AQV is just displayed in DXView and Pathfinder,
but NOW I have to click on the QRZ tab test to see the data.
I have checked all settings of JTAlert
(Settings> Manage Settings> Applications> DXLab Suite).
Nothing helps me to see the data automatically in Pathfinder again.
I do not know if it is JTAlert or DXKeeper that causes the problem.
BTW, DXLab is running before JTAlert and all DDE Connect tests are "Connected"
Does anyone have an idea?
73 de ON6AT Patrick


locked Re: QSO Relay

k5rcd
 

Daniel:
Not that I am aware of.
You might ask on the io Groups if it can be made to work, or if they intend to do so in the future.
--
73,
RANDY
K5RCD
South Texas


locked Re: QSO Relay

daniel lavocat
 

Randy

Could this application be adapted to work also with Logger32 ?
Thanks

--
Daniel

F6FLU
Daniel Lavocat
F6FLU@...
http://F6FLU.fr

F6KOP Team #1277


UFT #1277
  
CDXC #1632   DXCC CW #13586 


20 août 2017 à 17:56
Laurie:

First off, thanks for making JT Alert work with HRD Logbook on your latest release. I understand it is for the final time, and I can appreciate your position.

Can you post a link to QSO Relay? As you undoubtedly know, this fine free program interfaces JT Alert and HRD Logbook. You might consider making it a sticky, perhaps something like below. It would help keep folks from continuing to rehashing the JT Alert - HRD question.

To install the free / shareware software, QSO Relay, a seamless interface between HRD LOGBOOK and JT Alert, go to  http://www.vk2byi.com.au/qsorelay/

They have a io Groups page at https://groups.io/g/vk2byi-qsorelay
--
73,
RANDY
K5RCD
South Texas


locked QSO Relay

k5rcd
 

Laurie:

First off, thanks for making JT Alert work with HRD Logbook on your latest release. I understand it is for the final time, and I can appreciate your position.

Can you post a link to QSO Relay? As you undoubtedly know, this fine free program interfaces JT Alert and HRD Logbook. You might consider making it a sticky, perhaps something like below. It would help keep folks from continuing to rehashing the JT Alert - HRD question.

To install the free / shareware software, QSO Relay, a seamless interface between HRD LOGBOOK and JT Alert, go to  http://www.vk2byi.com.au/qsorelay/

They have a io Groups page at https://groups.io/g/vk2byi-qsorelay
--
73,
RANDY
K5RCD
South Texas


locked Re: Logging Address

Joe Smith <boat.anchor@...>
 

Laurie
I have corrected the email prob I dad with domain.
Barry


locked Re: Time is time

Joe WB9SBD
 

it cant be longer than 15 seconds. the next cycle is coming through then.
Joe WB9SBD

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

On 8/20/2017 10:07 AM, Albert Müller wrote:
Hello,

At the next update of JTAlert, would it be possible to leave more time in order to see the stations that appear in the boxes longer, because when you have for example 22 stations that appear, it's hard to make a choice!

de Albert ON5AM


locked Time is time

Albert Müller <100almu@...>
 

Hello,

At the next update of JTAlert, would it be possible to leave more time in order to see the stations that appear in the boxes longer, because when you have for example 22 stations that appear, it's hard to make a choice!

de Albert ON5AM


locked Re: JTAlertX 2.10.1 with DXKeeper V14.1.0 #DXLAB

John Etling
 

This issue was previously discussed in the wsjtgroup forum – originated by myself. It was determined at that time that DXCapture would no longer be populated and was previously populated as the result of some error in the code (never reported properly the working mode). It was/is being considered to reintroduce that possibility in a future update of WSJT-x (BTW: this is NOT a DXLabs issue).

 

As I am I the same camp as you we can only hope that the ability to populate the Capture window will be re-introduced in a future version of JT-Alert that is actually coded to do this rather than be an error.

 

 

I’m Just Sayin’

73 de K3JAE

 

John

 

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of on6at@...
Sent: Sunday, August 20, 2017 09:32
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlertX 2.10.1 with DXKeeper V14.1.0 #DXLAB

 

Hello,

I use DxLab with the latest versions. (DxKeeper V14.1.0 - Pathfinder 5.2.2 - DXView 4.3.2.)
together with JTAlertX v2.10.1 and WSJT-X v1.8.0-rc1

What's the problem?
I'm making a qso with eg EA8AQV.
Via JTAlert, a command is sent to DxKeeper to request the call sign.
In the past, this call sign came in the Capture window. On that way, all the data was visible through Pathfinder.
Now the call sign EA8AQV is just displayed in DXView and Pathfinder,
but NOW I have to click on the QRZ tab test to see the data.
I have checked all settings of JTAlert
(Settings> Manage Settings> Applications> DXLab Suite).
Nothing helps me to see the data automatically in Pathfinder again.
 
I do not know if it is JTAlert or DXKeeper that causes the problem.
BTW, DXLab is running before JTAlert and all DDE Connect tests are "Connected"
 
Does anyone have an idea?

73 de ON6AT Patrick


locked JTAlertX 2.10.1 with DXKeeper V14.1.0 #DXLAB

on6at@telenet.be
 

Hello,
I use DxLab with the latest versions. (DxKeeper V14.1.0 - Pathfinder 5.2.2 - DXView 4.3.2.)
together with JTAlertX v2.10.1 and WSJT-X v1.8.0-rc1
What's the problem? I'm making a qso with eg EA8AQV.
Via JTAlert, a command is sent to DxKeeper to request the call sign. In the past, this call sign came in the Capture window. On that way, all the data was
visible through Pathfinder. Now the call sign EA8AQV is just displayed in DXView and Pathfinder,
but NOW I have to click on the QRZ tab test to see the data.
I have checked all settings of JTAlert
(Settings> Manage Settings> Applications> DXLab Suite).
Nothing helps me to see the data automatically in Pathfinder again.
I do not know if it is JTAlert or DXKeeper that causes the problem. BTW, DXLab is running before JTAlert and all DDE Connect tests are "Connected" Does anyone have an idea?

73 de ON6AT Patrick


locked Re: Looking at conditional alerts...

Michael Black
 

Not quite...but you can prioritize the alerts.  So you can make state the #1 priority for example.  Than you have the "*" and "#" CQ tags you can add too.

Settings/Alerts/CQ and QRZ
Settings/Alerts/Alert Priorities

de Mike W9MDB
 


From: Dave Cole <dave@...>
To: Support@HamApps.groups.io
Sent: Sunday, August 20, 2017 5:34 AM
Subject: [HamApps] Looking at conditional alerts...

Are there conditional alerts that can be cascaded using "and", and "or",
available?

i.e. I want to set a color for the display of say GREEN, only for the
stations calling CQ, AND that I need as a state?

73s and thanks,
Dave
NK7Z
http://www.nk7z.net







locked Re: Looking at conditional alerts...

Joe Subich, W4TV
 

Settings -> Alerts -> Filters

73,

... Joe, W4TV

On 8/20/2017 6:34 AM, Dave Cole wrote:
Are there conditional alerts that can be cascaded using "and", and "or", available?
i.e. I want to set a color for the display of say GREEN, only for the stations calling CQ, AND that I need as a state?
73s and thanks,
Dave
NK7Z
http://www.nk7z.net


locked Re: How do you pronounce 73? #POLL

Bruce VK2RT
 

It's a fun show Charlie.

Actually the best number is 42, the meaning of life.
 
 
73 DE VK2RT Bruce


locked Looking at conditional alerts...

Dave (NK7Z)
 

Are there conditional alerts that can be cascaded using "and", and "or", available?

i.e. I want to set a color for the display of say GREEN, only for the stations calling CQ, AND that I need as a state?

73s and thanks,
Dave
NK7Z
http://www.nk7z.net


locked Re: How do you pronounce 73? #POLL

chas cartmel
 

And in binary it is a palindrome.

 

I watch ‘the Big bang Theory’ where this was touted as ‘the best number’

https://www.youtube.com/watch?v=RyFr279K9TE

 

73

Charlie

www.G4EST.me.uk

Twitter:@ccartmel

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Bruce VK2RT
Sent: 20 August 2017 00:46
To: Support@HamApps.groups.io
Subject: Re: [HamApps] How do you pronounce 73? #poll

 

And of interest...

73 is the 21st prime number, it's mirror 37 is the 12th prime number, and it's mirror 21 is the product of 7 and 3.

Wow, go figure...

 

The usage of "73" comes from the Phillips Code, originally devised in the era of telegraphs to speed up transmission of common messages by mapping them to numbers. The numeric code is a small part of the abbreviations outlined in the Phillips Code (developed by telegrapher Walter P. Phillips).
e.g.
73 -> Best regards

 

With phone modes SSB, FM etc. "Seventy Three" seems to be the norm.

 

Sometimes you’ll hear 73 expressed as “Seven Three”, which corresponds to how the Morse characters were sent. It is incorrect to say “Seventy-Three’s” since this would literally mean “Best Regards’s”.

 

73 DE Bruce

VK2RT


Virus-free. www.avg.com


locked Re: scan log and up date

on5po
 

Laurie,
Thank you for your reply, if I understand correctly, I must before doing an update, make sure that I have done well "dowload log returns" LOTW and or "Eqslcc"
My other question "Eqslcc" is it only necessary or do the two
Your answer will ask me to do the update, I hope in good conditions
73 Janny


locked Re: Logging Address

HamApps Support (VK3AMA)
 

Barry,

Please forward a valid email address. The yahoo address you used when joining the Group keeps bouncing with an "User does not exist" message from Yahoo.
Since you don't sign with a Callsign, I can't look you up on QRZ.com

I have a new build of JTAlert for you to test.

de Laurie VK3AMA


locked Re: Logging Address

HamApps Support (VK3AMA)
 

On 20/08/2017 11:00 AM, Bruce Croskey wrote:
I am confused... for the past few days we were told this is a defect in HRD and we are told it is a defect in JTAlert and that there is a work around... how do we get access to this ??

Bruce M. Croskey
AH0U

On Aug 19, 2017, at 5:53 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

VK3AMA
The defect is with the HRD 6.3+ TCP API logging interface. The Address does not get logged for people running the latest HRD versions.

This message thread relates to HRD v5 and pre 6.3 versions that don't use the defective HRD API.

In your original message regarding a failure to log the address you quoted that you were using HRD 6.4.0.780. This test build does not address you problem, so providing you with the link would achieve nothing but more confusion.

de Laurie VK3AMA
   


locked Re: Logging Address

AH0U
 

I am confused... for the past few days we were told this is a defect in HRD and we are told it is a defect in JTAlert and that there is a work around... how do we get access to this ??

Bruce M. Croskey
AH0U

On Aug 19, 2017, at 5:53 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@gmail.com> wrote:

VK3AMA


locked Re: Logging Address

HamApps Support (VK3AMA)
 

On 20/08/2017 2:15 AM, boat.anchor via Groups.Io wrote:

Good morning

I am using WSJT-X v1.8.0-rc1 JTAlertX 2.10.1 HRD 5.0 XML paid subsciption at QRZ

I have also wondered about logging full address. I cannot seem to find the button to enable this. I do have "Log full name" and "Log full QTH" checked in JTAlert and the Name logs OK. The city logs OK into the QTH field in HRD. The full address labelled ADRESS in HRD never populates with full address.

Is it possible to do this?

TIA Barry VB7150
Barry,

This is a defect within JTAlert. At some time in the past when I disabled the Address logging for HRD V6.3+ (due to its API defect), because of the shared code used for the HRD logging, Address logging for HRD V5 and HRD per V6.3 were incorrectly disabled.

I will send you a link to a new JTAlert build with the V5 address logging enabled. Please test and report back if it is now working for you.

de Laurie VK3AMA


locked Re: How do you pronounce 73? #POLL

Bruce VK2RT
 

And of interest...
73 is the 21st prime number, it's mirror 37 is the 12th prime number, and it's mirror 21 is the product of 7 and 3.
Wow, go figure...
 
The usage of "73" comes from the Phillips Code, originally devised in the era of telegraphs to speed up transmission of common messages by mapping them to numbers. The numeric code is a small part of the abbreviations outlined in the Phillips Code (developed by telegrapher Walter P. Phillips).
e.g.
73 -> Best regards

With phone modes SSB, FM etc. "Seventy Three" seems to be the norm.
 
Sometimes you’ll hear 73 expressed as “Seven Three”, which corresponds to how the Morse characters were sent. It is incorrect to say “Seventy-Three’s” since this would literally mean “Best Regards’s”.
 
73 DE Bruce
VK2RT