Date   

Update: Cherry picking

Howard McVay
 

Just discovered that,  in JTDX, the "AutoTx" button needs to be enabled for Logger32 Cherry Picking to work.  Guess I inadvertently toggled it off somehow.  Nothing to do with Logge32 update.  Might there be a similar setting in WSJT-X?  At least for me, puzzle solved.


Re: Cherry picking

n5kd
 

And….. on the right hand side of the front screen, check the AutoTX button is green.

 

Sent from Mail for Windows 10

 

From: Bob
Sent: Monday, July 19, 2021 16:51
To: hamlogger@groups.io
Subject: Re: [hamlogger] Cherry picking

 

On JTDX click FILE | SETTINGS. Click the REPORTING tab. Make sure ACCEPT UDP REQUESTS is checked. Click OK.

 

On JTDX Click MISC | ACCEPT UDP REPLY MESSAGES. Make sure ANY MESSAGE is checked.

 

SeventyThree(s)

On 07/19/2021 12:31 PM Howard McVay <kd7ma.ae@...> wrote:

 

 

I too experience this behavior using JTDX v156.   This began shortly after I updated Logger32 to V4.0.469.  Nothing else has changed (to my knowledge) in a while.
In the Cherry Picking Event viewer,  I see the following:   Note the message "JTDX did not switch to transmit".  I've verified JTDX works normally with manual activation of Txd.



Howard KD7MA

 


Re: Cherry picking

Bob
 

On JTDX click FILE | SETTINGS. Click the REPORTING tab. Make sure ACCEPT UDP REQUESTS is checked. Click OK.
 
On JTDX Click MISC | ACCEPT UDP REPLY MESSAGES. Make sure ANY MESSAGE is checked.
 
SeventyThree(s)

On 07/19/2021 12:31 PM Howard McVay <kd7ma.ae@...> wrote:
 
 
I too experience this behavior using JTDX v156.   This began shortly after I updated Logger32 to V4.0.469.  Nothing else has changed (to my knowledge) in a while.
In the Cherry Picking Event viewer,  I see the following:   Note the message "JTDX did not switch to transmit".  I've verified JTDX works normally with manual activation of Txd.



Howard KD7MA


Re: Cherry picking

Howard McVay
 

I too experience this behavior using JTDX v156.   This began shortly after I updated Logger32 to V4.0.469.  Nothing else has changed (to my knowledge) in a while.
In the Cherry Picking Event viewer,  I see the following:   Note the message "JTDX did not switch to transmit".  I've verified JTDX works normally with manual activation of Txd.



Howard KD7MA


Re: Jim (W5IFP)

Rick Williams - VE7TK
 

Thanks for the update Bob. I hope Jim gets better soon. We all miss him, his calm demeanor and his expertise!

Get well soon Jim!

73, Rick
VE7TK


Re: Jim (W5IFP)

BD4EPV
 

And hope Jim for all the best!  I just want to tell that there are friends on another side of the earth caring about him.

73 de Joseph, BD4EPV

On Monday, July 19, 2021, 07:43:18 AM GMT+8, Bob <k4cy@...> wrote:


Randall, thanks so much for your message. We, the Logger32 community and Beta testers, have been very concerned for Jim's well being for a few weeks. Please tell Jim we are all rooting for him, and he is in our thoughts and prayers. And to Mrs. Hargrave (Mary, I think) we wish her well, strength, and courage as time progresses. I have sent a copy of this message to the almost 4000 active Logger32 users who have benefited so much from Jim's 20+ years of tireless support of this project. 
 
The kd5wkk@... mailbox will overflow in the next 24 hours. Good luck, and may your God bless you. Your Father in law is without a doubt 'one of the good guys'.  With my love and affection, SeventyThree(s), Bob.
 
On 07/18/2021 6:57 PM Randall Booth <kd5wkk@...> wrote:
 
 

Bob,

 

I’m Randall Booth (KD5WKK) Jim’s son-in-law.  Jim wanted me to let you know he is currently in a physical therapy facility and will not be able to participate in the Logger32 testing for the next week or so.

 

Jim is doing fine but needed some Occupational and Physical therapy related to his Parkinson’s diagnosis.

 

Regards,

 

Randall Booth

KD5WKK

 

 


Re: Jim (W5IFP)

Larry Fravel
 

Thanks you for sharing and your eloquence Bob.  My prayers for Jim and his family. 

Larry K8YYY

Shinnston WV EM99uk

--
I got expelled from school on Pajama Day. Not my fault - I sleep naked.


Re: Jim (W5IFP)

ja1nlx
 

I really hope Jim is back again.

73 de aki
JA1NLX

------ Original message ------
From: "Bob" <k4cy@...>
To: "Randall Booth" <kd5wkk@...>
Date: 2021/07/19 8:43:13
Subject Re: [hamlogger] Jim (W5IFP)

Randall, thanks so much for your message. We, the Logger32 community and Beta testers, have been very concerned for Jim's well being for a few weeks. Please tell Jim we are all rooting for him, and he is in our thoughts and prayers. And to Mrs. Hargrave (Mary, I think) we wish her well, strength, and courage as time progresses. I have sent a copy of this message to the almost 4000 active Logger32 users who have benefited so much from Jim's 20+ years of tireless support of this project. 
 
The kd5wkk@... mailbox will overflow in the next 24 hours. Good luck, and may your God bless you. Your Father in law is without a doubt 'one of the good guys'.  With my love and affection, SeventyThree(s), Bob.
 
On 07/18/2021 6:57 PM Randall Booth <kd5wkk@...> wrote:
 
 

Bob,

 

I’m Randall Booth (KD5WKK) Jim’s son-in-law.  Jim wanted me to let you know he is currently in a physical therapy facility and will not be able to participate in the Logger32 testing for the next week or so.

 

Jim is doing fine but needed some Occupational and Physical therapy related to his Parkinson’s diagnosis.

 

Regards,

 

Randall Booth

KD5WKK

 

 


Re: Jim (W5IFP)

Kenneth Hansen <khansen@...>
 

Very nice said Bob
Get well Jim
de KB2SSE

On Sun, Jul 18, 2021 at 7:43 PM Bob <k4cy@...> wrote:
Randall, thanks so much for your message. We, the Logger32 community and Beta testers, have been very concerned for Jim's well being for a few weeks. Please tell Jim we are all rooting for him, and he is in our thoughts and prayers. And to Mrs. Hargrave (Mary, I think) we wish her well, strength, and courage as time progresses. I have sent a copy of this message to the almost 4000 active Logger32 users who have benefited so much from Jim's 20+ years of tireless support of this project. 
 
The kd5wkk@... mailbox will overflow in the next 24 hours. Good luck, and may your God bless you. Your Father in law is without a doubt 'one of the good guys'.  With my love and affection, SeventyThree(s), Bob.
 
On 07/18/2021 6:57 PM Randall Booth <kd5wkk@...> wrote:
 
 

Bob,

 

I’m Randall Booth (KD5WKK) Jim’s son-in-law.  Jim wanted me to let you know he is currently in a physical therapy facility and will not be able to participate in the Logger32 testing for the next week or so.

 

Jim is doing fine but needed some Occupational and Physical therapy related to his Parkinson’s diagnosis.

 

Regards,

 

Randall Booth

KD5WKK

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Re: Jim (W5IFP)

Bob
 

Randall, thanks so much for your message. We, the Logger32 community and Beta testers, have been very concerned for Jim's well being for a few weeks. Please tell Jim we are all rooting for him, and he is in our thoughts and prayers. And to Mrs. Hargrave (Mary, I think) we wish her well, strength, and courage as time progresses. I have sent a copy of this message to the almost 4000 active Logger32 users who have benefited so much from Jim's 20+ years of tireless support of this project. 
 
The kd5wkk@... mailbox will overflow in the next 24 hours. Good luck, and may your God bless you. Your Father in law is without a doubt 'one of the good guys'.  With my love and affection, SeventyThree(s), Bob.
 

On 07/18/2021 6:57 PM Randall Booth <kd5wkk@...> wrote:
 
 

Bob,

 

I’m Randall Booth (KD5WKK) Jim’s son-in-law.  Jim wanted me to let you know he is currently in a physical therapy facility and will not be able to participate in the Logger32 testing for the next week or so.

 

Jim is doing fine but needed some Occupational and Physical therapy related to his Parkinson’s diagnosis.

 

Regards,

 

Randall Booth

KD5WKK

 

 


Re: LOTW showing “cross” band contacts

Bob
 

When logging FT4/FT8 contacts that originated from UDP messages, a single frequency is part of the message. It is the radio VFO frequency plus the transmit audio. This is logged as the ADIF FREQ field. How does Logger32 calculate the ADIF FREQ_RX field? The UDP Status messages tell the audio offset of each station it decodes. So, the station being logged was transmitting on the frequency (as shown in the Logbook Entry Window) plus the audio offset as shown in the UDP BandMap. This is logged as the ADIF FREQ field. Or something like that ... SeventyThree(s).

On 07/18/2021 6:29 PM Bruce B <dxman340@...> wrote:
 
 

I also had the issue. But it was operator error.

 

WSJT you never changed the frequency in the program.  Mine was a 60m contact and I had 6m on wsjt. That’s why it di the cross band.

 

Sent from Mail for Windows 10

 

From: Gary Hinson
Sent: Sunday, July 18, 2021 4:58 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW showing “cross” band contacts

 

Hi Dale.

 

Please check section 38.10 of the User Manual for me.  Does that help?  I don’t use SO2R so haven’t had the chance to test the details.  Corrections & comments welcome. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dale Peterson
Sent: 19 July 2021 09:46
To: hamlogger@groups.io
Subject: [hamlogger] LOTW showing “cross” band contacts

 

On a recent manual upload (from Logger 32 to LOTW) many Qs in LOTW showed the band as “cross”…which they were not. Everything in Logger looks fine and all the Qs were made with WSJT X.  Upon looking at these Qs in LOTW, they showed the “receive” freq as the  freq. of my second rig ( always set to 2 meters).  I’m not sure what caused this nor how to fix it. Help appreciated.
thanks,
Dale WA4CQG 

 

 


Re: LOTW showing “cross” band contacts

Gary Hinson
 

???

 

IF you start WSJT-X from the Start menu on the UDP BandMap, it takes control of the radio away from Logger32 (Logger32 drops its CAT connection, then WSJT-X opens its CAT connection).  This happens because only one program at a time can access/control the serial port used for the CAT connection.

 

WSJT-X then tells Logger32 what radio frequencies you are using via UDP messages.  So if you are using FT8 on 6m, WSJT-X tells Logger32 the frequency.  Any completed digi QSOs are passed from WSJT-X to Logger32 with their frequencies and modes, and the details get logged.

 

When you stop WSJT-X from the Stop menu on the UDP BandMap, it drops the CAT connection to the radio, and Logger32 picks it up.  Logger32 is then aware of the radio frequencies etc. like normal.

 

HOWEVER, if you start and stop WSJT-X independently (not using the start and stop menu options on the UDP BandMap), Logger32 is clueless.  Whichever program opens the CAT port first wins.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bruce B
Sent: 19 July 2021 10:30
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW showing “cross” band contacts

 

I also had the issue. But it was operator error.

 

WSJT you never changed the frequency in the program.  Mine was a 60m contact and I had 6m on wsjt. That’s why it di the cross band.

 

Sent from Mail for Windows 10

 

From: Gary Hinson
Sent: Sunday, July 18, 2021 4:58 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW showing “cross” band contacts

 

Hi Dale.

 

Please check section 38.10 of the User Manual for me.  Does that help?  I don’t use SO2R so haven’t had the chance to test the details.  Corrections & comments welcome. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dale Peterson
Sent: 19 July 2021 09:46
To: hamlogger@groups.io
Subject: [hamlogger] LOTW showing “cross” band contacts

 

On a recent manual upload (from Logger 32 to LOTW) many Qs in LOTW showed the band as “cross”…which they were not. Everything in Logger looks fine and all the Qs were made with WSJT X.  Upon looking at these Qs in LOTW, they showed the “receive” freq as the  freq. of my second rig ( always set to 2 meters).  I’m not sure what caused this nor how to fix it. Help appreciated.
thanks,
Dale WA4CQG 

 


Re: LOTW showing “cross” band contacts

Bruce B
 

I also had the issue. But it was operator error.

 

WSJT you never changed the frequency in the program.  Mine was a 60m contact and I had 6m on wsjt. That’s why it di the cross band.

 

Sent from Mail for Windows 10

 

From: Gary Hinson
Sent: Sunday, July 18, 2021 4:58 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW showing “cross” band contacts

 

Hi Dale.

 

Please check section 38.10 of the User Manual for me.  Does that help?  I don’t use SO2R so haven’t had the chance to test the details.  Corrections & comments welcome. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dale Peterson
Sent: 19 July 2021 09:46
To: hamlogger@groups.io
Subject: [hamlogger] LOTW showing “cross” band contacts

 

On a recent manual upload (from Logger 32 to LOTW) many Qs in LOTW showed the band as “cross”…which they were not. Everything in Logger looks fine and all the Qs were made with WSJT X.  Upon looking at these Qs in LOTW, they showed the “receive” freq as the  freq. of my second rig ( always set to 2 meters).  I’m not sure what caused this nor how to fix it. Help appreciated.
thanks,
Dale WA4CQG 

 


Re: LOTW showing “cross” band contacts

Gary Hinson
 

Hi Dale.

 

Please check section 38.10 of the User Manual for me.  Does that help?  I don’t use SO2R so haven’t had the chance to test the details.  Corrections & comments welcome. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Dale Peterson
Sent: 19 July 2021 09:46
To: hamlogger@groups.io
Subject: [hamlogger] LOTW showing “cross” band contacts

 

On a recent manual upload (from Logger 32 to LOTW) many Qs in LOTW showed the band as “cross”…which they were not. Everything in Logger looks fine and all the Qs were made with WSJT X.  Upon looking at these Qs in LOTW, they showed the “receive” freq as the  freq. of my second rig ( always set to 2 meters).  I’m not sure what caused this nor how to fix it. Help appreciated.
thanks,
Dale WA4CQG 


LOTW showing “cross” band contacts

Dale Peterson
 
Edited

On a recent manual upload (from Logger 32 to LOTW) many Qs in LOTW showed the band as “cross”…which they were not. Everything in Logger looks fine and all the Qs were made with WSJT X.  I’m logging from 2 radios via UDP.  Upon looking at these Qs in LOTW, they showed the “receive” freq as the  freq. of my second rig ( always set to 2 meters).  I’m not sure what caused this nor how to fix it. Help appreciated.
thanks,
Dale WA4CQG


Re: CW machine issue

Panos
 

Hi, open radio 1 (or 2), does your computer sees the radio? 73


Re: Cherry picking

Bob
 

What do you see in the cherry-picking event viewer? SeventyThree(s).

On 07/18/2021 2:44 PM Andy VA3PL <va3pl@...> wrote:
 
 
 
Due to computer failure, I am setting up Logger32 and WSJT-x again.
All seems to work now except that Cherry picking is not working.
Seems to me that Logger32 is picking up callsigns and immediately dropping them.
Running the latest version of Logger32 and WSJT-x ver 2.2.1.
 
Any suggestions are greatly appreciated.
 
Andy SP9KR
 


Cherry picking

Andy VA3PL
 

Due to computer failure, I am setting up Logger32 and WSJT-x again.
All seems to work now except that Cherry picking is not working.
Seems to me that Logger32 is picking up callsigns and immediately dropping them.
Running the latest version of Logger32 and WSJT-x ver 2.2.1.

Any suggestions are greatly appreciated.

Andy SP9KR


Re: WAS

Joe N3XLS
 

there are also several AK callsign stations that are in the 48 states so make sure it really is AK.


Re: WAS

Kenneth Hansen <khansen@...>
 

Thanks Bob

It is now fixed, state field was the issue

On 7/16/2021 1:58 PM, Bob wrote:
Also, check the QSO to make sure thew STATE field says AK, 73.
On 07/16/2021 1:53 PM Kenneth Hansen <khansen@...> wrote:
 
 
I will check, 
Thanks for theinfo
On Fri, Jul 16, 2021 at 1:52 PM Bob < k4cy@...> wrote:
Are you sure the DXCC field for the 30m contact is 006 and not 291? 73.
On 07/16/2021 1:37 PM Kenneth Hansen < khansen@...> wrote:
 
 
I need a little help/hint
For some reason my 30m LOTW confirmed FT8 contact with Alaska don’t show up in WAS, other bands does.
Spent a few hours trying to solve this, don’t know what I’m missing 
 
73 de KB2SSE
--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC
 

 

 

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

1641 - 1660 of 86710