On 09/16/2021 9:29 AM Bob <k4cy@...> wrote:

 

 

Gary, to investigate I'd need to see the LoTW records from Clublog.txt file that contains the JH1HFE record. SeventyThree(s)

On 09/15/2021 8:17 PM Gary Hinson <gary@...> wrote:

 

 

Errrrr, I was over-excited: we are no longer getting the red warning message, but the LoTW sync via Club Log still isn’t working properly.

 

Club Log knows about QSOs that have been matched and confirmed on LoTW, but isn’t passing those details to Logger32 e.g. after synchronising Logger32, Club Log and LoTW:

 

Here are my recent QSOs on LoTW:

 

 

This one with JH1HFE has been matched and confirmed already:

 

 

On Club Log it is shown as confirmed:

 

 

In  my log, that QSO remains stubbornly unconfirmed:

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 16 September 2021 07:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

 

 

Hey thanks everyone.  It looks like - having been hammered by all our tests - whatever wasn’t working is now running properly again.  We must have knocked the bits back into place, or something.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: 16 September 2021 01:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Just done a Clublog sync worked ok down loaded 5 new mode/band updates.

 

73

Ian G4GIR

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

To: <hamlogger@groups.io>, <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log

---

 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Do: hamlogger@groups.io

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick Spears
Sent: Thursday, September 16, 2021 9:49 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

Hi Paul. Using MMVARI I select the mode RTTY-R and select Radio 1 to use AFSK for RTTY.

Rick

Virus-free. www.avast.com

On 09/15/2021 8:17 PM Gary Hinson <gary@...> wrote:

 

 

Errrrr, I was over-excited: we are no longer getting the red warning message, but the LoTW sync via Club Log still isn’t working properly.

 

Club Log knows about QSOs that have been matched and confirmed on LoTW, but isn’t passing those details to Logger32 e.g. after synchronising Logger32, Club Log and LoTW:

 

Here are my recent QSOs on LoTW:

 

 

This one with JH1HFE has been matched and confirmed already:

 

 

On Club Log it is shown as confirmed:

 

 

In  my log, that QSO remains stubbornly unconfirmed:

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 16 September 2021 07:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

 

 

Hey thanks everyone.  It looks like - having been hammered by all our tests - whatever wasn’t working is now running properly again.  We must have knocked the bits back into place, or something.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: 16 September 2021 01:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Just done a Clublog sync worked ok down loaded 5 new mode/band updates.

 

73

Ian G4GIR

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

To: <hamlogger@groups.io>, <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log

---

 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Do: hamlogger@groups.io

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

 

On 09/16/2021 8:15 AM Peter Eckersberger <oe3epw@...> wrote:

 

 

Hello Bob,

Sorry I'm late. Have been out of my home. To answer your question ... YES, its ON TOP. Here some pics ...

That's the one where only 'TCP' is on. But no 'UDP" ... therefore no 'band plan'. Parallel logging is OK, but JTDX vanishes every time at the end of every single logging procedure. That means ... 1 QSO logged and fiddling with the mouse to recall 'JTDX' to the foreground ...

Here the start of 'JTDX' via 'start menus' within 'band plan' ...




This shows the activated 'ON TOP' switch ...





Finally the operating position when 'JTDX' and Logger32' is 'parallel logging' ...
 



Well, that's it. Hope you're getting the point.


73 de Peter, OE3EPW

On 09/15/2021If your going to do rtty  6:47 PM Gary Hinson <gary@...> wrote:

 

 

Hi Rick.

 

Have you been following the IC-7300 section of the User Manual?

 

The advice in there was proffered by various ICOM users.

 

If you spot errors or improvement opportunities, please let me know.  I’m not an ICOMmer and need the help.

 

73 & GL

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Spears
Sent: 16 September 2021 10:22
To: hamlogger@groups.io
Subject: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

 

Hello. Been struggling to resolve and hoping for some suggestions.
Using ICOM IC-7300 with L32. Set up CAT using USB port on PC into USB CAT port on ICOM.
Set for Serial Port 7 and using input and output USB sound card drivers from ICOM.
JTDX works fine!
I have JTDX off when using MMVARI.
MMVARI seems to be working fine. I see signals and can decode RTTY sigs on MMVARI waterfall.
When I click a macro I see it sending and can see waterfall showing sending my text.
However it does not key transmitter.
One weird thing is the freq display in MMVARI is not working or in sync with my radio.
However when I move my VFO manually on Rig I can see that the waterfall is also moving and correct.
I am set for LSB on radio. Tried LSB DATA but not working.
Tried everything I can think of.
I figure at this point must be some CAT radio setting.

Any help would be greatly appreciated.

73, Rick W4HRA

 

On my 2^nd monitor, the ghostly window only seems to appear if I eagerly click the band pulldown to change bands in JTDX too soon after JTDX starts up.  If I patiently wait for it to start fully and settle itself down before changing bands, no ghost, no ghouls, no apparitions.

 

Another way to avoid being spooked is to use Logger32’s JTDX Control Panel to change bands, rather than the JTDX band control.  There’s no need to wait with this approach. 

 

Hinson tip: with Mode ‘Quick Switch’ enabled, if I simply click an FT8 spot having been using, say, CW, Logger32 handles the whole sequence for me, changing bands and modes on the rig and starting JTDX plus JTDX Control Panel automatically.   For more on this, see the manual section 2.6.4.    Right-click “Mode” for starters …

 

 

73

Gary  ZL2iFB

 

PS  I successfully busted the ghost by resetting the video card controlling the 2^nd monitor by changing and then resetting the monitor resolution.  If that doesn’t work, try rebooting.

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Vince Shirley
Sent: 16 September 2021 05:19
To: hamlogger@groups.io
Subject: Re: [hamlogger] ghost

 

Hiya,

 

I've had this for a long time - my guess its something to do with you local graphics setup.

 

Vince G0ORC

 

On Wed, 15 Sept 2021 at 18:16, Richard Zalewski <dick.w7zr@...> wrote:

When I close WSJT the display on my second monitor leaves a "ghost" image.  That image disappears when I close L32.

Richard 

W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV

 

Be joyful in hope, patient in affliction, faithful in prayer

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

To: <hamlogger@groups.io>, <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log

---

 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Do: hamlogger@groups.io

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

Hello. Been struggling to resolve and hoping for some suggestions.
Using ICOM IC-7300 with L32. Set up CAT using USB port on PC into USB CAT port on ICOM.
Set for Serial Port 7 and using input and output USB sound card drivers from ICOM.
JTDX works fine!
I have JTDX off when using MMVARI.
MMVARI seems to be working fine. I see signals and can decode RTTY sigs on MMVARI waterfall.
When I click a macro I see it sending and can see waterfall showing sending my text.
However it does not key transmitter.
One weird thing is the freq display in MMVARI is not working or in sync with my radio.
However when I move my VFO manually on Rig I can see that the waterfall is also moving and correct.
I am set for LSB on radio. Tried LSB DATA but not working.
Tried everything I can think of.
I figure at this point must be some CAT radio setting.

Any help would be greatly appreciated.

73, Rick W4HRA

On 09/15/2021 2:47 PM kenfilmer@... <kenfilmer@...> wrote:

 

 

 

Uploading contacts to LOTW recently has increased the list of QSOs in my BAD adi file.

 

The reason given is – QSO NOT FOUND IN LOGBOOK. The QSOs are credited in LOTW but not shown as confirmed by LOTW in my Logger logbook.

 

Checking the QSOs in the L32 log I can’t see anything wrong with the entry. Manually changing LOTW QSL RECEIVED from N to Y in my log doesn’t work, I get the message – I’M GETTING OLD AND FORGETFUL_ I’M ABOUT TO RESET THE COMPLEX KEYS IN THE DATABASE......  I don’t know what that means.

 

This only seems to happen if I use FT4 or 8 which automatically logs the contact.

 

This is now happening more often with around a third of my contacts being put in the BAD adi file.

 

I’m sure this is once again operator error, but can anybody suggest what I’ve done wrong or how I can resolve this?

 

73

 

Ken

G3XPO

 

 

 

Sent from Mail for Windows

 

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

To: <hamlogger@groups.io>, <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log

---

 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Do: hamlogger@groups.io

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB