Date   

Re: Granted

G4GIR
 

1.0.16, DATED 2015!! Guess its a wee bit old?
 
73
 
Ian
 
 

----- Original Message -----
From: Bob <k4cy@...>
Sent: 08/09/2021 21:07:48
Subject: Re: [hamlogger] Granted

... and what is the version number of the ARRL scraper.exe? SeventyThree(s).
On 09/08/2021 3:58 PM G4GIR via groups.io <i.frith@...> wrote:
Hello All
I have tried to update my QSO's to Granted using ARRL Scraper.
I get the file down loaded ok around 3000 QSO's
Try to Import into L32 but every QSO is rejected.
When I start the import I get a message in the box saying Waiting, Valid Callsigns for this Certificate are: G4GIR, 0 QSO's WILL BE REDIRECTED TO CORRECT ENTRIES IN THIS LOG BOOK.
The end result is 3598 QSO's not updated.
Have I missed something?
A lot of the QSO's have no Call Signs in the down loaded file due to the Paper Submissions back in the 70's/80's so understand that but others should be ok.
Thanks
Ian G4GIR


Re: Starting JTDX from L32 closes a serial port in radio control #ft8 #serial'

Bob
 

No. Logger32 closes/relinquishes radio control to JTDX. Isn't the simple solution to your problem to have a single radio port configured? That was a rhetorical question, you configure it anyway you like. SeventyThree(s).

On 09/08/2021 3:54 PM Alexey Antipov via groups.io <nw7m@...> wrote:
 
 
Hi folks,

Is there a way to stop closing a radio serial port when JTDX starts from the logger?
In my case I have both radio ports (IC-7610, USB emulated COM and CAT COM) active and connected to a PC - one is configured for JTDX, the second for L32 radio control, both can read Freq/mode/control independently
When I start JTDX from L32, it closes the radio port, so I need to open it back every time.

P.S. I read page 266 statement:
• Allow JTAlert to set Logger32 band/mode: if you change band or mode in the digimode software, Logger32 follows suit, provided Logger32’s radio port is closed so that the digimode software can open its CAT connection to control the radio.
but the question is how to disable this feature.

73!
Alexey - NW7M


Re: Granted

Bob
 

... and what is the version number of the ARRL scraper.exe? SeventyThree(s).

On 09/08/2021 3:58 PM G4GIR via groups.io <i.frith@...> wrote:
 
 
Hello All
 
I have tried to update my QSO's to Granted using ARRL Scraper.
 
I get the file down loaded ok around 3000 QSO's
 
Try to Import into L32 but every QSO is rejected.
 
When I start the import I get a message in the box saying Waiting, Valid Callsigns for this Certificate are: G4GIR, 0 QSO's WILL BE REDIRECTED TO CORRECT ENTRIES IN THIS LOG BOOK.
 
The end result is 3598 QSO's not updated.
 
Have I missed something?
 
A lot of the QSO's have no Call Signs in the down loaded file due to the Paper Submissions back in the 70's/80's so understand that but others should be ok.
 
 
Thanks
 
Ian G4GIR


Granted

G4GIR
 

Hello All
 
I have tried to update my QSO's to Granted using ARRL Scraper.
 
I get the file down loaded ok around 3000 QSO's
 
Try to Import into L32 but every QSO is rejected.
 
When I start the import I get a message in the box saying Waiting, Valid Callsigns for this Certificate are: G4GIR, 0 QSO's WILL BE REDIRECTED TO CORRECT ENTRIES IN THIS LOG BOOK.
 
The end result is 3598 QSO's not updated.
 
Have I missed something?
 
A lot of the QSO's have no Call Signs in the down loaded file due to the Paper Submissions back in the 70's/80's so understand that but others should be ok.
 
 
Thanks
 
Ian G4GIR


Starting JTDX from L32 closes a serial port in radio control #ft8 #serial'

Alexey - NW7M
 

Hi folks,

Is there a way to stop closing a radio serial port when JTDX starts from the logger?
In my case I have both radio ports (IC-7610, USB emulated COM and CAT COM) active and connected to a PC - one is configured for JTDX, the second for L32 radio control, both can read Freq/mode/control independently
When I start JTDX from L32, it closes the radio port, so I need to open it back every time.

P.S. I read page 266 statement:
• Allow JTAlert to set Logger32 band/mode: if you change band or mode in the digimode software, Logger32 follows suit, provided Logger32’s radio port is closed so that the digimode software can open its CAT connection to control the radio.
but the question is how to disable this feature.

73!
Alexey - NW7M


Re: Logger32 v4.0.275 auto-update is online ...

Gary Hinson <Gary@...>
 

Good point Jose!  My fault.  I’ll fix that.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jose EA7BJ
Sent: 08 September 2021 22:44
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 v4.0.275 auto-update is online ...

 

Hi all.

In the manual you suggest that we can change the port such as 737373, I think the highest number that can be used is 65535. Correct me if I'm dodged.


73 EA7BJ Jose.


Re: Logger32 v4.0.275 auto-update is online ...

Per
 

Jose,

You are quit right, the TCP/IP port number is a 16 bit unsigned number, hence it must be in the range 1 to 65535 (port number 0 is invalid).

73 de LA9XKA - Per


On Wed, Sep 8, 2021 at 12:44 PM, Jose EA7BJ wrote:
Hi all.

In the manual you suggest that we can change the port such as 737373, I think the highest number that can be used is 65535.
Correct me if I'm dodged.


73 EA7BJ Jose.


Re: Logger32 v4.0.275 auto-update is online ...

Jose EA7BJ
 

Hi all.

In the manual you suggest that we can change the port such as 737373, I think the highest number that can be used is 65535.
Correct me if I'm dodged.


73 EA7BJ Jose.


Re: Logger32 v4.0.275 auto-update is online ...

Jan <hamlogger@...>
 

Importing a log is very veerry slow

73
Jan
PA4JJ

Op 7-9-2021 om 22:01 schreef Bob:
The release includes a new feature that allows two PCs, each with a copy of Logger32, to add/delete/modify logbook entries on both PCs. See section 31.2 on page 561 of the current help file. Or, use this link
 
 
If you're interested in the capabilities, remember that this in new code, please test it thoroughly using dummy data to understand its capabilities and weaknesses.
 
Operational notes:
1) When parallel logging is enabled, any automatic backups after xxx QSOs is disabled.
2) The logbooks on each PC must have the same name.
3) When configuring the parallel logging option, you have the option to enable a network monitor that pings the other PC every second and will warn you if the remote PC is not visible.
 
Let the games begin, SeventyThree(s).

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


Re: Logger32 v4.0.275 auto-update is online ...

Peter Eckersberger
 

Hi

Fantastic feature. Thanks a lot, Bob!


73 de Peter, OE3EPW

AR  SK



Am 07.09.2021 um 22:01 schrieb Bob:

The release includes a new feature that allows two PCs, each with a copy of Logger32, to add/delete/modify logbook entries on both PCs. See section 31.2 on page 561 of the current help file. Or, use this link
 
 
If you're interested in the capabilities, remember that this in new code, please test it thoroughly using dummy data to understand its capabilities and weaknesses.
 
Operational notes:
1) When parallel logging is enabled, any automatic backups after xxx QSOs is disabled.
2) The logbooks on each PC must have the same name.
3) When configuring the parallel logging option, you have the option to enable a network monitor that pings the other PC every second and will warn you if the remote PC is not visible.
 
Let the games begin, SeventyThree(s).


Logger32 v4.0.275 auto-update is online ...

Bob
 

The release includes a new feature that allows two PCs, each with a copy of Logger32, to add/delete/modify logbook entries on both PCs. See section 31.2 on page 561 of the current help file. Or, use this link
 
 
If you're interested in the capabilities, remember that this in new code, please test it thoroughly using dummy data to understand its capabilities and weaknesses.
 
Operational notes:
1) When parallel logging is enabled, any automatic backups after xxx QSOs is disabled.
2) The logbooks on each PC must have the same name.
3) When configuring the parallel logging option, you have the option to enable a network monitor that pings the other PC every second and will warn you if the remote PC is not visible.
 
Let the games begin, SeventyThree(s).


Re: FTdx5000 CAT control

Gary Hinson <Gary@...>
 

😊

 

For some years, I have used a well-loved RS232/USB adapter with a worn RS232 plug (or is it a socket?  I forget).  With no locking bolts to hold it in place on the radio, I have learnt to double-check that it is properly seated whenever I notice CAT strangeness, especially after I have been fiddling about with cables behind the shack desk.

 

From what you’ve said, Vince, it’s amazing that it worked even one way!

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Vince Shirley
Sent: 07 September 2021 23:36
To: hamlogger@groups.io
Subject: Re: [hamlogger] FTdx5000 CAT control

 

Rob and Aki,

 

Thanks for your help.

 

It took a little detective work but was a hardware failure in the end.

 

There is a short ribbon connector between the 9 pin RS232 socket on the motherboard and the connector on the rear of the PC.  For the want of trying everything I replaced that with one out of my very large collection of redundant PC bits and bobs.

 

The original 9 pin connector when removed simply fell apart in my hand, the ribbon cable having long since parted company with the socket.

 

It works!!

 

Regards and thanks again,

 

Vince G0ORC

 

 

 

On Tue, 7 Sept 2021 at 11:43, Rob <g4ujs@...> wrote:

Hi Vince,

This is my 5K config (attached)...works perfectly.

73

Rob G4UJS

On Tue, Sep 7, 2021 at 10:07 AM, Vince Shirley wrote:

Hi all,

 

For many years I've used Yaesu transceivers CAT control via a Microham Microkeyer 2 and Logger32 with perfect results. For a number of reasons I wish to use a straight RS232 to replace the MK virtual CAT port.

 

I've done this and it works - up to a point.  What I'm seeing using, a straight RS232 serial cable to a standard RS232 serial port on the PC is this.

 

Click on a spot - radio follows obediently, transfers callsign and frequency to the Log Entry Window and changes mode and frequency. Then, seemingly at the next poll of the transceiver, the callsign and frequency disappears from the Log Entry window.

 

After a few seconds the callsign re-appears in the Log Entry window but the frequency does not.  Trying to log the station says I am trying to log a frequency of 0.00, as I would have expected.

 

So far I've tried every combination of RTS, DTS baud rate, polling rate, stop bits without success.  Display frequency is on (always has been) 

 

Radio debug window shows all of the pretty lights lit but showing no response from the radio.

 

I've changed the serial cable between the radio and the PC (just in case I'd hit upon a null modem cable by mistake) with no change.

 

Radio settings are unchanged

 

 i.e.CAT RTS disable - changed to enable to test but no good.

Baud Rates correspond to Logger32.

 

There is only one way communication i.e. Logger32 to radio. but what to do about it.

 

I still suspect the cable...  anyone any other ideas?

 

Vince G0ORC

 

 

 

 


Re: FTdx5000 CAT control

Vince Shirley
 

Rob and Aki,

Thanks for your help.

It took a little detective work but was a hardware failure in the end.

There is a short ribbon connector between the 9 pin RS232 socket on the motherboard and the connector on the rear of the PC.  For the want of trying everything I replaced that with one out of my very large collection of redundant PC bits and bobs.

The original 9 pin connector when removed simply fell apart in my hand, the ribbon cable having long since parted company with the socket.

It works!!

Regards and thanks again,

Vince G0ORC



On Tue, 7 Sept 2021 at 11:43, Rob <g4ujs@...> wrote:
Hi Vince,

This is my 5K config (attached)...works perfectly.

73

Rob G4UJS

On Tue, Sep 7, 2021 at 10:07 AM, Vince Shirley wrote:
Hi all,
 
For many years I've used Yaesu transceivers CAT control via a Microham Microkeyer 2 and Logger32 with perfect results. For a number of reasons I wish to use a straight RS232 to replace the MK virtual CAT port.
 
I've done this and it works - up to a point.  What I'm seeing using, a straight RS232 serial cable to a standard RS232 serial port on the PC is this.
 
Click on a spot - radio follows obediently, transfers callsign and frequency to the Log Entry Window and changes mode and frequency. Then, seemingly at the next poll of the transceiver, the callsign and frequency disappears from the Log Entry window.
 
After a few seconds the callsign re-appears in the Log Entry window but the frequency does not.  Trying to log the station says I am trying to log a frequency of 0.00, as I would have expected.
 
So far I've tried every combination of RTS, DTS baud rate, polling rate, stop bits without success.  Display frequency is on (always has been) 
 
Radio debug window shows all of the pretty lights lit but showing no response from the radio.
 
I've changed the serial cable between the radio and the PC (just in case I'd hit upon a null modem cable by mistake) with no change.
 
Radio settings are unchanged
 
 i.e.CAT RTS disable - changed to enable to test but no good.
Baud Rates correspond to Logger32.
 
There is only one way communication i.e. Logger32 to radio. but what to do about it.
 
I still suspect the cable...  anyone any other ideas?
 
Vince G0ORC
 
 
 
 


Re: FTdx5000 CAT control

ja1nlx
 

Vince

I suppose your TRX is in MEM mode ?

ver3.50 Help says that...

When Logger32 polls radio for Frequency and Mode of VFO-A, it only reports the correct frequency and Mode if the radio is in VFO mode. If the radio is in MEM, M-TUNE or QMB, an error flag will pop up on the RCP spectrum and the bottom of the radio de-bug window. This flag advises the operator to turn off the MEM. M-TUNE or QMB as appropriate.


73 de aki
JA1NLX


------ Original message ------
From: "Vince Shirley" <vince.g0orc@...>
Date: 2021/09/07 18:07:09
Subject [hamlogger] FTdx5000 CAT control

Hi all,

For many years I've used Yaesu transceivers CAT control via a Microham Microkeyer 2 and Logger32 with perfect results. For a number of reasons I wish to use a straight RS232 to replace the MK virtual CAT port.

I've done this and it works - up to a point.  What I'm seeing using, a straight RS232 serial cable to a standard RS232 serial port on the PC is this.

Click on a spot - radio follows obediently, transfers callsign and frequency to the Log Entry Window and changes mode and frequency. Then, seemingly at the next poll of the transceiver, the callsign and frequency disappears from the Log Entry window.

After a few seconds the callsign re-appears in the Log Entry window but the frequency does not.  Trying to log the station says I am trying to log a frequency of 0.00, as I would have expected.

So far I've tried every combination of RTS, DTS baud rate, polling rate, stop bits without success.  Display frequency is on (always has been) 

Radio debug window shows all of the pretty lights lit but showing no response from the radio.

I've changed the serial cable between the radio and the PC (just in case I'd hit upon a null modem cable by mistake) with no change.

Radio settings are unchanged

 i.e.CAT RTS disable - changed to enable to test but no good.
Baud Rates correspond to Logger32.

There is only one way communication i.e. Logger32 to radio. but what to do about it.

I still suspect the cable...  anyone any other ideas?

Vince G0ORC





Re: FTdx5000 CAT control

Rob
 

Hi Vince,

This is my 5K config (attached)...works perfectly.

73

Rob G4UJS


On Tue, Sep 7, 2021 at 10:07 AM, Vince Shirley wrote:
Hi all,
 
For many years I've used Yaesu transceivers CAT control via a Microham Microkeyer 2 and Logger32 with perfect results. For a number of reasons I wish to use a straight RS232 to replace the MK virtual CAT port.
 
I've done this and it works - up to a point.  What I'm seeing using, a straight RS232 serial cable to a standard RS232 serial port on the PC is this.
 
Click on a spot - radio follows obediently, transfers callsign and frequency to the Log Entry Window and changes mode and frequency. Then, seemingly at the next poll of the transceiver, the callsign and frequency disappears from the Log Entry window.
 
After a few seconds the callsign re-appears in the Log Entry window but the frequency does not.  Trying to log the station says I am trying to log a frequency of 0.00, as I would have expected.
 
So far I've tried every combination of RTS, DTS baud rate, polling rate, stop bits without success.  Display frequency is on (always has been) 
 
Radio debug window shows all of the pretty lights lit but showing no response from the radio.
 
I've changed the serial cable between the radio and the PC (just in case I'd hit upon a null modem cable by mistake) with no change.
 
Radio settings are unchanged
 
 i.e.CAT RTS disable - changed to enable to test but no good.
Baud Rates correspond to Logger32.
 
There is only one way communication i.e. Logger32 to radio. but what to do about it.
 
I still suspect the cable...  anyone any other ideas?
 
Vince G0ORC
 
 
 
 


FTdx5000 CAT control

Vince Shirley
 

Hi all,

For many years I've used Yaesu transceivers CAT control via a Microham Microkeyer 2 and Logger32 with perfect results. For a number of reasons I wish to use a straight RS232 to replace the MK virtual CAT port.

I've done this and it works - up to a point.  What I'm seeing using, a straight RS232 serial cable to a standard RS232 serial port on the PC is this.

Click on a spot - radio follows obediently, transfers callsign and frequency to the Log Entry Window and changes mode and frequency. Then, seemingly at the next poll of the transceiver, the callsign and frequency disappears from the Log Entry window.

After a few seconds the callsign re-appears in the Log Entry window but the frequency does not.  Trying to log the station says I am trying to log a frequency of 0.00, as I would have expected.

So far I've tried every combination of RTS, DTS baud rate, polling rate, stop bits without success.  Display frequency is on (always has been) 

Radio debug window shows all of the pretty lights lit but showing no response from the radio.

I've changed the serial cable between the radio and the PC (just in case I'd hit upon a null modem cable by mistake) with no change.

Radio settings are unchanged

 i.e.CAT RTS disable - changed to enable to test but no good.
Baud Rates correspond to Logger32.

There is only one way communication i.e. Logger32 to radio. but what to do about it.

I still suspect the cable...  anyone any other ideas?

Vince G0ORC





FTdx5000 - CAT control

Vince Shirley
 

Hi all,

For many years I've used Yaesu transceivers CAT control via a Microham Microkeyer 2 and Logger32 with perfect results.

For a number of reasons I wish to use a straight RS232 to replace the MK virtual CAT port.

I've done this and it works - up to a point.  What I'm seeing using, a straight RS232 serial cable to a standard RS232 serial port on the PC is this.

Click on a spot - radio follows obediently, transfers callsign and frequency to the Log Entry Window and changes mode and frequency. Then, seemingly at the next poll of the transceiver, the callsign and frequency disappears from the Log Entry window.



Re: TS 590S displaying incorrect band in the Log Entry Pane

Vince Shirley
 

Bob, Gary...

One slight problem with doing what is suggested on P35 and making the first entry in the bands and modes table "band wide" means that that if "MODE SEGMENT" is selected in the first band-map - i.e. the one where all of the other band maps are selected, the mode segment is thus the whole band, which rather defeats the exercise.

If you can live with that then fine....

Vince G0ORC

On Tue, 7 Sept 2021 at 00:41, David Leckie <djcleckie@...> wrote:

Hi Gary

 

I read the section on page 35 which said

Hinson tip: strange things happen if Logger32 isn’t given a default mode for the current VFO frequencies … so define CW from the very bottom edge to the very top of every band you use. Without exception. Just do it. Trust me, I’m a doctor.”

Having read the above I was pretty sure that I had some form of obscure error in my Bands and Modes settings but I was looking for the error in the affected bands setup whereas the error was actually in the setup for the band above. 

 

“Strange things” certainly happen and don’t just affect the current band.

 

73

 

And thanks

 

Dave

 

 

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gary Hinson
Sent: 06 September 2021 22:21
To: hamlogger@groups.io
Subject: Re: [hamlogger] TS 590S displaying incorrect band in the Log Entry Pane

 

Thank you for closing the loop on this curious problem Dave.

 

I ASSumed Logger32’s bands-and-modes editing function would prevent us saving an incompletely entered line in the same way as it performs other integrity checks (e.g. warning us if the lower frequencies aren’t in sequence) but it seems I was wrong.

 

I’ll probably add a wee note to the User Manual.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of David Leckie
Sent: 07 September 2021 05:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] TS 590S displaying incorrect band in the Log Entry Pane

 

I have had another close look at this issue and I seem to have solved it.
I am posting this just in case it helps someone else.
My problem only affected 80M and 40M

Suppose I am on 7.028MHz and the band is displaying 80M
If I QSY to 30M it now gets the band correct and displays 30M as it should
If I continue to QSY up to 20M it displays the band correctly.
I can go right up to 6M and each band is displayed correctly.
Now if I QSY down it is fine until I get to 30M which is still fine.
If I then QSY to 40M (or 80M) it still displays 30M.

Now I assumed there was an error in my "Bands and Modes" table on the 40M entry as that is where the error started.

Tonight I checked the 30M "Bands and Modes" and I had an error there an incomplete entry with the band but the lower and upper limits were missing.
I had started adding an FT8 but had not completed the line.
When I corrected this everything started working.

So if your "Bands and Modes" are acting strangely don't just check the band where the error occurs but also check the band above.

Hope this helps somebody.

73
Dave
GM4NFI


Re: TS 590S displaying incorrect band in the Log Entry Pane

David Leckie
 

Hi Gary

 

I read the section on page 35 which said

Hinson tip: strange things happen if Logger32 isn’t given a default mode for the current VFO frequencies … so define CW from the very bottom edge to the very top of every band you use. Without exception. Just do it. Trust me, I’m a doctor.”

Having read the above I was pretty sure that I had some form of obscure error in my Bands and Modes settings but I was looking for the error in the affected bands setup whereas the error was actually in the setup for the band above. 

 

“Strange things” certainly happen and don’t just affect the current band.

 

73

 

And thanks

 

Dave

 

 

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gary Hinson
Sent: 06 September 2021 22:21
To: hamlogger@groups.io
Subject: Re: [hamlogger] TS 590S displaying incorrect band in the Log Entry Pane

 

Thank you for closing the loop on this curious problem Dave.

 

I ASSumed Logger32’s bands-and-modes editing function would prevent us saving an incompletely entered line in the same way as it performs other integrity checks (e.g. warning us if the lower frequencies aren’t in sequence) but it seems I was wrong.

 

I’ll probably add a wee note to the User Manual.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of David Leckie
Sent: 07 September 2021 05:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] TS 590S displaying incorrect band in the Log Entry Pane

 

I have had another close look at this issue and I seem to have solved it.
I am posting this just in case it helps someone else.
My problem only affected 80M and 40M

Suppose I am on 7.028MHz and the band is displaying 80M
If I QSY to 30M it now gets the band correct and displays 30M as it should
If I continue to QSY up to 20M it displays the band correctly.
I can go right up to 6M and each band is displayed correctly.
Now if I QSY down it is fine until I get to 30M which is still fine.
If I then QSY to 40M (or 80M) it still displays 30M.

Now I assumed there was an error in my "Bands and Modes" table on the 40M entry as that is where the error started.

Tonight I checked the 30M "Bands and Modes" and I had an error there an incomplete entry with the band but the lower and upper limits were missing.
I had started adding an FT8 but had not completed the line.
When I corrected this everything started working.

So if your "Bands and Modes" are acting strangely don't just check the band where the error occurs but also check the band above.

Hope this helps somebody.

73
Dave
GM4NFI


Re: Club Log Upload: Error 'Forbidden'

Bob
 

... I'm not even going to dignify with an answer ... Without a doubt, Clark is/was the author of the US's Afghanistan evacuation plan ... SeventyThree(s),AndLimboDancingIs ... The mind boggles.

On 09/06/2021 6:48 PM Gary Hinson <gary@...> wrote:
 
 

Hi Clark.

 

Maybe I’m still sleepy but I don’t know what “yellow field” you mean. 

 

Any chance of a screen shot, please, showing the yellow field and scary red bit?  Or a better description of the problem?

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Clark WU4B
Sent: 07 September 2021 09:39
To: hamlogger@groups.io
Subject: [hamlogger] Club Log Upload: Error 'Forbidden'

 

Just upgraded the utility to 4.13 with L32 4.0.274.  Upon starting L32, get message that utility is connected to Club Log.  
When trying to upload after logging a Q, I get  red "Forbidden" in the yellow field.  Rather daunting message!

Unable to find any documentation on this.  What am I doing wrong?
--
73,

Clark
WU4B

 

3681 - 3700 of 89337