Date   

Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Rick. I have tried both LSB and LSB-D and still didn't key transmit. Will try again.
I am wondering about the PTT option. I know in JTDX there is a CAT Option for PTT.
However in MMVARI I dont have that option and chose PTT using serial port, which is assigned to the ICOM driver assigned serial port.7 for me.

73 Rick W4HRA


Re: LoTW sync via Club Log

Bob
 

Gary, also, make an ADIF export of the offending JH1HFW QSO so I can see exactly what's in the requested/granted fields of the logbook. 73.

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>

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@...>

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

 

 

 


v4.0.277 auto-update is on-line

Bob
 

Auto-update v4.0.277 has bug fixes and enhancements to parallel logging. 73.


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Ellison
 

To use MMVARI in AFSK you need to have the radio set to USB-D or LSB-D otherwise the radio will trying to use the FSK output on the radio.

 

73 Rick N2AMG

 

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


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

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

Rick


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Dave. Thanks for response. When I use JTDX it works fine. It hears and decodes the FT8, Keys my transmitter and logs the QSO in L32.  So to me MMVARI ought to do the same?
All with the existing USB CAT connection.
Rick


Re: LoTW sync via Club Log

Bob
 

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>

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@...>

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

 

 

 


Re: JTDX on-top ...

Bob
 

Peter, your pictures show that JTDX is not starting on top. The JTDX title bar shows JTDX by HF community. Maybe Logger32 started JTDX, but is did not control it. On the UDP BandMap, click the START/STOP menu. Click DELAY AFTER STARTING JTDX. Set the time to 20 seconds (or maybe more). Now, after starting JTDX from Logger32 does the title bat say JTDX & Logger32 (on-top). SeventyThree(s).

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



Re: No Transmit for RTTY using IC-7300 and MMVARI

Paul Sturpe
 

Are you trying to operate FSK or AFSK?

 

Paul Sturpe, W3GQ

QSL Bureau Mgr. W4 K4 N4 Prefixes

8860 Peninsula Dr

Terrell, NC  28682

 


Re: JTDX on-top ...

Peter Eckersberger
 

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



Re: No Transmit for RTTY using IC-7300 and MMVARI

Dave Colliau
 

If your going to do rtty and other modes with the 7300 you need to buy a cat cable that plugs into the remote jack in the rear . This along with the USB cable give you 2 ports instead of one . You use the remote jack for cat and the usb for the sound card and RTTY ,psk,etc keying .  I have an extra USB unit to plug in to the remote jack if your interested. Its the better FTDI chip not a Prolific.
Dave N8DC

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

 


Re: ghost

Alec SP2EWQ <aleksander.otulak@...>
 




Hi,

with W10 - In the Advanced system settings
provide the following options stay UNclicked:

Best regards,
Alec





------ Wiadomość oryginalna ------
Od: "Gary Hinson" <Gary@...>
Data: 15.09.2021 21:15:30
Temat: Re: [hamlogger] ghost

On my 2nd 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 2nd 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


Re: LoTW sync via Club Log

Gary Hinson
 

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@...>

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 ------

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

 

 


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Gary. I did read through and made some changes based upon the manual but certainly may have missed something. Will be reading again just in case.
Thanks and 73. Rick


Re: No Transmit for RTTY using IC-7300 and MMVARI

Gary Hinson
 

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


Re: Logprint crashes

ja1nlx
 

and you are trying to print entire Logbook or partial Logbook ?

73 de aki
JA1NLX

------ Original message ------
From: "ja1nlx via groups.io" <ayoshida0205@...>
Date: 2021/09/16 7:07:39
Subject Re: [hamlogger] Logprint crashes

Wayne

Which option you check to print Log ?
Do you see any error message ?
Do you set "Run this program as administrator" for LogPrint.exe ?

73 de aki
JA1NLX

------ Original message ------
From: "wjheil via groups.io" <wjheil@...>
Date: 2021/09/15 23:03:37
Subject [hamlogger] Logprint crashes

[Edited Message Follows]

I am unable to use Logprint.  Whenever I try to print my log, the  the "loading log progress" bar starts filling on then stops after about 1/5 of the bar is filled in.  It freezes for maybe 10 seconds and then the Logprint screen aborts and disappears.

I am using the latest version of Windows 10, Logger32 3.50.424, and Logprint 3.1.2.

Any ideas or suggestions?

-Wayne, KB6OQJ


Note:  The windows event viewer states that the crash was caused by ntdll.dll


No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

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


Re: Logprint crashes

ja1nlx
 

Wayne

Which option you check to print Log ?
Do you see any error message ?
Do you set "Run this program as administrator" for LogPrint.exe ?

73 de aki
JA1NLX

------ Original message ------
From: "wjheil via groups.io" <wjheil@...>
Date: 2021/09/15 23:03:37
Subject [hamlogger] Logprint crashes

[Edited Message Follows]

I am unable to use Logprint.  Whenever I try to print my log, the  the "loading log progress" bar starts filling on then stops after about 1/5 of the bar is filled in.  It freezes for maybe 10 seconds and then the Logprint screen aborts and disappears.

I am using the latest version of Windows 10, Logger32 3.50.424, and Logprint 3.1.2.

Any ideas or suggestions?

-Wayne, KB6OQJ


Note:  The windows event viewer states that the crash was caused by ntdll.dll


Re: FW: QSO not found in logbook

Bob
 

Please make an ADIF export or one of the offending QSOs in your logbook ... You can do a partial export and select only the QSO number of the QSO. Also, copy/paste the corresponding QSO from the LoTW file. Send them to my eMail address. I'll take a peek. SeventyThree(s).

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

 

 


Re: LoTW sync via Club Log

Gary Hinson
 

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@...>

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 ------

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

 

 

2661 - 2680 of 88450