Date   
Anyone in Marion County Florida a subscriber here?

Bob
 

If you are in Marion County (or an adjacent County) and have experience with tower ordinances/permissions, please eMail me directly at k4cy@...  Apologies for the bandwidth. SeventyThree(s).

Re: Help file corrections

Hew Lines
 

Many thanks Jim. That is exactly the type of issue I am looking for. I can't keep track of link changes myself, there are simply TOO MANY of them :-)). Leting me know of any you guys find  enables me to fix them one at a time.

73 Hew VA7HU


On 12/8/2019 2:45 PM, Jim Altman wrote:

DX Spots Window

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Sunday, December 8, 2019 5:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Help file corrections

 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

Re: Auto-update version 3.50.403

larry fields
 

is the updater always slow down loading seems to take a while to finish

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES
n6hpx/du1@...

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz & 7165 khz
DX1PAR HF NET  7095.00 khz
(0900,1100 & 2300 utc)
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY











Re: Help file corrections

ja1nlx
 

Jim

Thanks. We will correct these in the next update.

73

On 2019/12/09 7:45, Jim Altman wrote:

DX Spots Window

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Sunday, December 8, 2019 5:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Help file corrections

 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

Re: Help file corrections

Jim Altman
 

DX Spots Window

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Sunday, December 8, 2019 5:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Help file corrections

 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

Re: Help file corrections

ja1nlx
 

Jim

Which topic are you referring to ?

73

On 2019/12/09 5:42, Jim Altman wrote:

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

Help file corrections

Jim Altman
 

In section 2.6.4 and 2.10.2 there are references to alerts section 2.9.5, but these should reference 2.10.5.  The clickable link in 2.10.2 does in fact, take you to 2.10.5 despite the text being wrong.  Thanks for all your hard work to unravel the many mysteries in the complexities of Logger32.

 

73 de w4uck

 

Jim Altman

jaltman636@...

 

Re: Question WSJT and Operator Window

Bob
 

There's no such thing as a dumb question Glen, only a dumb answer. Maybe we don't always understand exactly what is being asked, but we keep trying till we get it right. And, forget the 'Sir', I don't want to be accused of impersonating an Officer :). SeventyThree(s).

On December 7, 2019 at 9:57 PM Glen - W5IF <W5IF@...> wrote:

L I B Bob, got to the paragraph about running JTDX first, then Logger 32 and BAM!  Thanks for pointing in the right direction and planting a swift kick.  Now to set up highlights!  Thank you Sir!

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Sunday, December 8, 2019 01:13
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

It ain't so. This is the UDP BandMap, and all these callsigns are decoded by JTDX. I never connect to a DX Cluster (I have low intestinal fortitude, or as you'd say in Oklahoma, it makes me puke). SeventyThree(s).

 

On December 7, 2019 at 6:39 PM Glen - W5IF <W5IF@...> wrote:

Have the UDP Bandmap up and running.  It is showing what is “spotted” via my Telnet connection not what WSJT is actually decoding, as in stations calling CQ.  Still reading and working with it.

Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 21:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)

 

 

December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 

 


 

 

 


 

 



 

Re: Question WSJT and Operator Window

Glen - W5IF
 

L I B Bob, got to the paragraph about running JTDX first, then Logger 32 and BAM!  Thanks for pointing in the right direction and planting a swift kick.  Now to set up highlights!  Thank you Sir!

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Sunday, December 8, 2019 01:13
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

It ain't so. This is the UDP BandMap, and all these callsigns are decoded by JTDX. I never connect to a DX Cluster (I have low intestinal fortitude, or as you'd say in Oklahoma, it makes me puke). SeventyThree(s).

 

On December 7, 2019 at 6:39 PM Glen - W5IF <W5IF@...> wrote:

Have the UDP Bandmap up and running.  It is showing what is “spotted” via my Telnet connection not what WSJT is actually decoding, as in stations calling CQ.  Still reading and working with it.

Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 21:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)

 

 

December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 

 


 

 

 


 

Re: Question WSJT and Operator Window

Bob
 

Is it possible you're looking at an old version of the Help file? Click HELP menu. Then click HELP again ,,, What version are you using? SeventyThree(s).

On December 7, 2019 at 9:33 PM Glen - W5IF <W5IF@...> wrote:

That made me laugh…but so true.  Okay, will work with JTDX and see what I need to set up.  Have JTDX and Bandmap but will keep working and reading.  Thanks!

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Sunday, December 8, 2019 01:13
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

It ain't so. This is the UDP BandMap, and all these callsigns are decoded by JTDX. I never connect to a DX Cluster (I have low intestinal fortitude, or as you'd say in Oklahoma, it makes me puke). SeventyThree(s).

 

On December 7, 2019 at 6:39 PM Glen - W5IF <W5IF@...> wrote:

Have the UDP Bandmap up and running.  It is showing what is “spotted” via my Telnet connection not what WSJT is actually decoding, as in stations calling CQ.  Still reading and working with it.

Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 21:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)

 

 

December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 

 


 

 

 


 

 



 

Re: Question WSJT and Operator Window

Glen - W5IF
 

That made me laugh…but so true.  Okay, will work with JTDX and see what I need to set up.  Have JTDX and Bandmap but will keep working and reading.  Thanks!

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Sunday, December 8, 2019 01:13
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

It ain't so. This is the UDP BandMap, and all these callsigns are decoded by JTDX. I never connect to a DX Cluster (I have low intestinal fortitude, or as you'd say in Oklahoma, it makes me puke). SeventyThree(s).

 

On December 7, 2019 at 6:39 PM Glen - W5IF <W5IF@...> wrote:

Have the UDP Bandmap up and running.  It is showing what is “spotted” via my Telnet connection not what WSJT is actually decoding, as in stations calling CQ.  Still reading and working with it.

Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 21:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)

 

 

December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 

 


 

 

 


 

Re: Question WSJT and Operator Window

Bob
 

It ain't so. This is the UDP BandMap, and all these callsigns are decoded by JTDX. I never connect to a DX Cluster (I have low intestinal fortitude, or as you'd say in Oklahoma, it makes me puke). SeventyThree(s).


On December 7, 2019 at 6:39 PM Glen - W5IF <W5IF@...> wrote:

Have the UDP Bandmap up and running.  It is showing what is “spotted” via my Telnet connection not what WSJT is actually decoding, as in stations calling CQ.  Still reading and working with it.

Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 21:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)







December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 

 


 

 



 

Re: Question WSJT and Operator Window

Glen - W5IF
 

Have the UDP Bandmap up and running.  It is showing what is “spotted” via my Telnet connection not what WSJT is actually decoding, as in stations calling CQ.  Still reading and working with it.

Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 21:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)







December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 

 


 

Re: Question WSJT and Operator Window

Bob
 

You said:  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes. Try this, and Dupes will disappear all by themselves. You have an additional menu option that lets you determine if mode is FT4 (or FT8) or DIG. I have tried to cover all the bases. SeventyThree(s)



December 7, 2019 at 3:53 PM Glen - W5IF <W5IF@...> wrote:

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

 



 

Re: Question WSJT and Operator Window

Glen - W5IF
 

Thanks Bob for confirming what I was seeing.  I will dive into the UDP Bandmap and start learning how to use it.  Love the program and have used it for many years!  Thanks!

73 Glen W5IF

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Saturday, December 7, 2019 19:10
To: hamlogger@groups.io
Subject: Re: [hamlogger] Question WSJT and Operator Window

 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

Re: Question WSJT and Operator Window

Bob
 

I think the TX audio offset is sent to Logger32 only as part of a QSO Logged message. So, implementing your request would be of little/no value. SeventyThree(s).

On December 7, 2019 at 2:21 PM "Andy None via Groups.Io" <va3pl@...> wrote:

 
Would it be difficult for you Bob to add to UDP band map little arrow similar in style to those on band map?
That will indicate user current audio frequency that she / he have set up.
Andy SP9KR

On Saturday, December 7, 2019, 8:10:00 p.m. GMT+1, Bob <k4cy@...> wrote:


The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).
On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 
 

 

Re: Question WSJT and Operator Window

Bob
 

If you want it, then yes.  If you are cherry-picking, then on the UDP BandMap click CONFIG | CHERRY-PICKING OPTIONS and check the option to CLEAR/ENTER THE LOGBOOK ENTRY WHEN SENDING A UDP REPLY. If you are working stations by double clicking on WSJT/JTDX then on the UDP BandMap click CONFIG and check the option ENABLE CALLSIGN LOOKUP WHEN CLICKING ON WSJT/JTDX. SeventyThree(s).


On December 7, 2019 at 2:19 PM Jan <hamlogger@...> wrote:

How about that when a station replies to my cq (and I see  e.g. PA4JJ K4YC LOCATOR  or PA4JJ K4YC Rxx) his call is being transferred to the logbook input window?

73
Jan
PA4JJ

Op 7-12-2019 om 20:09 schreef Bob:
The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).
On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

 

Re: Question WSJT and Operator Window

Andy None
 

Would it be difficult for you Bob to add to UDP band map little arrow similar in style to those on band map?
That will indicate user current audio frequency that she / he have set up.
Andy SP9KR

On Saturday, December 7, 2019, 8:10:00 p.m. GMT+1, Bob <k4cy@...> wrote:


The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).
On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

Re: Question WSJT and Operator Window

Jan
 

How about that when a station replies to my cq (and I see  e.g. PA4JJ K4YC LOCATOR  or PA4JJ K4YC Rxx) his call is being transferred to the logbook input window?

73
Jan
PA4JJ

Op 7-12-2019 om 20:09 schreef Bob:
The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).
On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF

 


 

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

Re: Question WSJT and Operator Window

Bob
 

The simple answer is no. One click on WSJT does not pass any information to Logger32, So no lookup can be done. A double click will do as you want, but of course that will make WSJT start to call the station. not what you want. But let's review what you currently have ... The UDP BandMap shows a list of all the decoded callsigns (except those you have purposely filtered out). The callsigns are color-coded to show if they are calling CQ, have called CQ. There is an indicator that tells you if you have worked each station in this band/mode before, and the decoded callsigns have a background color (that you setup) to show Country want needs status. Similarly, gridsquares are color-coded to show want/need status ... just about everything you could want. SeventyThree(s).

On December 7, 2019 at 1:53 PM Howard <W5IF@...> wrote:

Using latest Logger 32 and WSJT with Icom 7600 on FT4/FT8.  All working well there and logging is working great.

 

Is there a way while I am monitoring WSJT that I can double click on a CQ call and have it populate Logger32 Operator window and thus invoking Previous QSO window.  Right now I am manually inputting a questioned call into Operator window of Logger32 to check for dupes.

 

Read help files in both programs and don’t see this addressed.  Suggestions appreciated. 

 

Glen – W5IF