Date   

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


Re: CW machine issue

Mike
 

Blame Bill G.
Look into windows logs, you might find something interesting about that issue there.
Mike


CW machine issue

Antonis Parashis
 

CW machine fails to load:
Any help?


Re: Error 6

HB9DDS
 

On Fri, Jul 16, 2021 at 12:08 PM, Bob wrote:
The error is happening when the BandMap is opening and the arrow that shows the VFO frequency is being painted. When you see the error and click on the OK button, does the program continue to run normally? Do you see the BandMap and do you see the arrow on the BandMap?
 
Suggestions? You could temporarily rename the Logger32.INI file and see if that fixes the problem. You could click on the VIEW menu and turn off the Enable Error trapping option (that doesn't fix the problem, it just hides it). 
Hello Bob

When the error message appears, I have to press OK about 3-4 times until the window goes away.
Whether after that the red VFO arrow appears in the bandmap window, I do not know now.
 
Strangely enough, it now works again without the error. And here the red arrow appears in the bandmap window.

Daniel, HB9DDS


Re: WAS

Bob
 

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


Re: WAS

Kenneth Hansen <khansen@...>
 

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


Re: WAS

Bob
 

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


WAS

Kenneth Hansen <khansen@...>
 

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


Re: Error 6

Bob
 

The error is happening when the BandMap is opening and the arrow that shows the VFO frequency is being painted. When you see the error and click on the OK button, does the program continue to run normally? Do you see the BandMap and do you see the arrow on the BandMap?
 
Suggestions? You could temporarily rename the Logger32.INI file and see if that fixes the problem. You could click on the VIEW menu and turn off the Enable Error trapping option (that doesn't fix the problem, it just hides it). 
 
SeventyThree(s)
 
 

On 07/16/2021 12:14 PM HB9DDS <hb9dds@...> wrote:
 
 

[Edited Message Follows]

Hi Folks

Since 2 days I see this after I start the SW:

https://up.picr.de/41632234ms.jpg

And after the update:

https://up.picr.de/41632243uf.jpg

Any sughestions? Solution?

Daniel, HB9DDS


Re: Manually add QSOs

kenfilmer@outlook.com
 

I didn’t have error trapping checked Bob, but now I have and things seem OK, I can export logs without L32 locking up.

 

Maybe the best thing for me to do is to load L32 again in case I ended up with some weird things in this download.

 

Thanks for your time!

 

73

 

Ken

G3XPO

 

 

Sent from Mail for Windows 10

 

From: Bob
Sent: 16 July 2021 16:49
To: hamlogger@groups.io
Subject: Re: [hamlogger] Manually add QSOs

 

Ken, something is seriously wrong. Do you have error trapping enabled (Click VIEW and see if 'enable error trapping' is checked). If something is missing/broken during the installation of Logger32 you can expect to see an error/warning message. SeventyThree(s).

On 07/16/2021 5:00 AM kenfilmer@... <kenfilmer@...> wrote:

 

 

Hi Bob

 

I just downloaded the latest complete version V4.0.268 from the L32 website as I’ve done before with previous versions.

 

The  PC said that what I was downloading was unsafe so I had to tell it that it was safe since I’ve been happily using L32 for some 20 years and it all loaded OK.

 

Its not the end of the world, apart from the Manual QSOs bit everything is working fine although I haven’t tried uploading to LoTW yet, waiting for my TQSL certificate.

 

73

 

Ken

G3XPO

 

 

 

Sent from Mail for Windows 10

 

From: Bob
Sent: 15 July 2021 20:25
To: hamlogger@groups.io
Subject: Re: [hamlogger] Manually add QSOs

 

Tell us more Ken. How did you get Logger32 reinstalled (exactly)? 73.

On 07/15/2021 2:33 PM kenfilmer@... <kenfilmer@...> wrote:

 

 

I just put a new HDD in my Windows 10 PC. Prior to the old HDD dying L32 was 100% fine.

 

Now if I try to add Manual QSOs the Sound Card Window disappears and the wait symbol comes up and L32 sort of locks up so I have to go to task manager to stop L32 and reload it.

 

I do need to manually add QSOs sometimes so if anybody can help with this I will be grateful.

 

Great programme, been using it for 20 years!

 

73

 

Ken

G3XPO

 

 

 

Sent from Mail for Windows 10

 

 

 

 


Error 6

HB9DDS
 
Edited

Hi Folks

Since 2 days I see this after I start the SW:

https://up.picr.de/41632234ms.jpg

And after the update:

https://up.picr.de/41632243uf.jpg

Any sughestions? Solution?

Daniel, HB9DDS


Re: Manually add QSOs

Bob
 

Ken, something is seriously wrong. Do you have error trapping enabled (Click VIEW and see if 'enable error trapping' is checked). If something is missing/broken during the installation of Logger32 you can expect to see an error/warning message. SeventyThree(s).

On 07/16/2021 5:00 AM kenfilmer@... <kenfilmer@...> wrote:
 
 

Hi Bob

 

I just downloaded the latest complete version V4.0.268 from the L32 website as I’ve done before with previous versions.

 

The  PC said that what I was downloading was unsafe so I had to tell it that it was safe since I’ve been happily using L32 for some 20 years and it all loaded OK.

 

Its not the end of the world, apart from the Manual QSOs bit everything is working fine although I haven’t tried uploading to LoTW yet, waiting for my TQSL certificate.

 

73

 

Ken

G3XPO

 

 

 

Sent from Mail for Windows 10

 

From: Bob
Sent: 15 July 2021 20:25
To: hamlogger@groups.io
Subject: Re: [hamlogger] Manually add QSOs

 

Tell us more Ken. How did you get Logger32 reinstalled (exactly)? 73.

On 07/15/2021 2:33 PM kenfilmer@... <kenfilmer@...> wrote:

 

 

I just put a new HDD in my Windows 10 PC. Prior to the old HDD dying L32 was 100% fine.

 

Now if I try to add Manual QSOs the Sound Card Window disappears and the wait symbol comes up and L32 sort of locks up so I have to go to task manager to stop L32 and reload it.

 

I do need to manually add QSOs sometimes so if anybody can help with this I will be grateful.

 

Great programme, been using it for 20 years!

 

73

 

Ken

G3XPO

 

 

 

Sent from Mail for Windows 10

 

 

 

2381 - 2400 of 87439