Date   
Re: Club Log Exceptions Issue

Richard M. Gillingham
 

Thanks for finding that.

I'll exercise my patience...  
73
Gil, W1RG



From: "paul@... [hamlogger]" <hamlogger@...>
To: hamlogger@...
Sent: Tuesday, February 13, 2018 9:44 AM
Subject: Re: [hamlogger] Club Log Exceptions Issue

 
Yes, it's at ClubLog. The cty_xml.gz file is sent to your machine and saved in C:\Logger32.

It contains the following (strangely in HTML, but maybe for human readability or other programs which check for HTML 'announcement' content [maybe logger32 should do this]):









   
   

Sorry, Club Log is currently unavailable.



   

13 Feb 2018: Club Log is currently being migrated to new equipment!



   

Further details are posted in the Club Log Google Group (click here)



   

Club Log will be back online shortly.







73, Paul VP9KF


Logger32 Won't Accept New Qs For Entry

Al, K6RIM
 

OK, I understand why Club Log Exceptions is not working.

But now I just noticed a much bigger issue: I just made a Q and Logger32 won't accept it when I press *Enter*.

Is that glitch related to the Club Log issue?

Very strange morning on the radio today ....................

Anyone?

73,

Al, K6RIM

Re: Club Log Exceptions Issue

Dan Atchison
 

My I refer everyone to the ClubLog site?  It states that ClubLog is down due to moving to new equipment.

73,
Dan


On 2/13/2018 9:29 AM, 'john_pink@...' john_pink@... [hamlogger] wrote:
 

Same here on this side of the pond.

It looks like a Club Log issue not L32!

John

----Original Message----
From: hamlogger@...
Date: 13/02/2018 13:47:51
To:
Subj: [hamlogger] Club Log Exceptions Issue

Using current version of Logger32 (3.350.347).

This AM when starting Logger32, when it started loading Club Log exceptions, it stopped with this error:

"Failed to decompress CTY XML GZ"

After I closed the Club Log exceptions Update, Logger32 loaded normally.

Having seen the previous post, I turned off my anti-virus software and tried again. No joy.

Have never seen this issue before.

Sudden cockpit trouble?

Solution?

With thanks and 73,

Al, K6RIM 





Re: Club Log Exceptions Issue

Paul Evans W4/VP9KF
 

Yes, it's at ClubLog. The cty_xml.gz file is sent to your machine and saved in C:\Logger32.

It contains the following (strangely in HTML, but maybe for human readability or other programs which check for HTML 'announcement' content [maybe logger32 should do this]):

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Temporarily Unavailable</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>
<div style='padding-top:50px;text-align:center;font-family:arial,sans-serif;'>
    <IMG SRC="/.extra/logo.png" ALT="" border="0">
    <h2>Sorry, Club Log is currently unavailable.</h2>

    <p>13 Feb 2018: Club Log is currently being migrated to new equipment!</p>

    <p>Further details are posted in the Club Log Google Group (<a href='https://groups.google.com/d/msg/clublog/ezaOfl_G-M0/rPzzMtecAwAJ'>click here</a>)</p>

    <p>Club Log will be back online shortly.</p>

</div>
</body>
</html>

73, Paul VP9KF

Re: Club Log Exceptions Issue

John Pink
 

Same here on this side of the pond.

It looks like a Club Log issue not L32!

John

----Original Message----
From: hamlogger@...
Date: 13/02/2018 13:47:51
To:
Subj: [hamlogger] Club Log Exceptions Issue

Using current version of Logger32 (3.350.347).

This AM when starting Logger32, when it started loading Club Log exceptions, it stopped with this error:

"Failed to decompress CTY XML GZ"

After I closed the Club Log exceptions Update, Logger32 loaded normally.

Having seen the previous post, I turned off my anti-virus software and tried again. No joy.

Have never seen this issue before.

Sudden cockpit trouble?

Solution?

With thanks and 73,

Al, K6RIM 




Re: Club Log Exceptions Issue

Richard M. Gillingham
 

Having the same problem here.  Running Win 10, Administrator, no recent changes in system.
73
Gil, W1RG



From: "k6rim@... [hamlogger]"
To: hamlogger@...
Sent: Tuesday, February 13, 2018 8:48 AM
Subject: [hamlogger] Club Log Exceptions Issue

 
Using current version of Logger32 (3.350.347).

This AM when starting Logger32, when it started loading Club Log exceptions, it stopped with this error:

"Failed to decompress CTY XML GZ"

After I closed the Club Log exceptions Update, Logger32 loaded normally.

Having seen the previous post, I turned off my anti-virus software and tried again. No joy.

Have never seen this issue before.

Sudden cockpit trouble?

Solution?

With thanks and 73,

Al, K6RIM 



Club Log Exceptions Issue

Al, K6RIM
 

Using current version of Logger32 (3.350.347).

This AM when starting Logger32, when it started loading Club Log exceptions, it stopped with this error:

"Failed to decompress CTY XML GZ"

After I closed the Club Log exceptions Update, Logger32 loaded normally.

Having seen the previous post, I turned off my anti-virus software and tried again. No joy.

Have never seen this issue before.

Sudden cockpit trouble?

Solution?

With thanks and 73,

Al, K6RIM 


Re: Clublog Exceptions Problem

John, G4DRS
 

Fixed!
It turns out that, somehow, when updating AVG, I had installed the trial version of their paid Anti-Virus/Firewall/stop everything software.
I uninstalled and reinstalled just AVG Free and let Windows Firewall do its bit and the Clublog Exceptions update as normal.
Thanks, everybody, for the advice.


John
G4DRS

Re: Importing ADIF from N1MM Fails

Gary Hinson
 

Hi Tom.

 

Presumably you are referring to the WPX RTTY contest at the weekend.

 

What is the mode error, exactly?  Can you give us an example of an ADIF record from the BAD.ADI file?

 

Is it a legitimate ADIF mode?

 

Is the same mode listed in your bands and modes table in Logger32?  Is it one of the modes listed in the ADIFModes.txt file in C:\Logger32?

 

73

Gary  ZL2iFB

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, 13 February 2018 6:14 a.m.
To: hamlogger@...
Subject: [hamlogger] Importing ADIF from N1MM Fails

 

 

Tried many times to import N1MM WPX log to Logger32 and it failed. BAD
file says that their is a mode error. I didn't have this problem in
other contests.

Any suggestions?

73,

Tom W8JWN

Importing ADIF from N1MM Fails

Tom Martin
 

Tried many times to import N1MM WPX log to Logger32 and it failed. BAD file says that their is a mode error. I didn't have this problem in other contests.

Any suggestions?

73,

Tom W8JWN

Re: IOTA Activity Utility

jim_k2qb
 

Gary not an issue at all and thanks for the feedback. I totally get the volunteering of time as I am involved in a few things in my life as well and I totally understand and appreciate all the time and effort you folks put into this.

Jim K2QB

Re: Setup Radio - Custom Settings Button.

Jim Cox
 

Well glad you found it...  I wasn’t much help for sure.... Something in Logger32 must have gotten corrupted.  Have a good week.
Jim K4JAF
 

From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 4:58 PM
To: hamlogger@...
Subject: Re: [hamlogger] Setup Radio - Custom Settings Button.
 
 

Jim,
 
Thanks for your help - the further I went into this issue, the more things I found that didn't add up.  There were any number off issues concerning com ports, sound cards, bands and modes tables not being adhered to, Lockups on start and refusing to shut down... and more.
 
To my mind something was corrupted and a re-boot didn't solve it.
 
I'm a bit paranoid about backups and I restored everything from one of the many backups I took earlier in the day, then restored the log from a separate backup and everything fell back into place and now works
 
Sorry for the bandwidth and thanks again for your help.
 
Vince
 
On 11 February 2018 at 21:25, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 
I had a Yaesu FT-5000 and the command strings worked at that time..  No Yaesu now, so cant give you any kind of answer. What does it show in the debug screen when the commands are sent?  (sent ok but not recognized)???
 
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 12:07 PM
To: hamlogger@...
Subject: Re: [hamlogger] Setup Radio - Custom Settings Button.
 
 
......but when set to FT-991, the radio does not respond to the FA command and doesn't change frequency, which is also a bit odd....
 
 
Vince G0ORC
 
On 11 February 2018 at 17:46, Vince Shirley <vince.g0orc@...> wrote:
Well, this is a bit odd.
 
If I change the radio from Yaesu FT-5000 to a Yaesu FT-991 (which has a similar command set) then it works, the command string is sent.
 
If I then change it back to FT-5000, it doesn't.
 
As Alice said...."Curiouser and Curiouser"

Vince G0ORC
 
 
On 11 February 2018 at 17:28, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 
Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 
For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC
 
 
 
 
 

Re: CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Jim Hargrave
 

Hi Ted,

Logger32 "CW Module"



Please send me a copy of your file "Logger32.ini" and I'll help you
find it.



73, Jim - w5ifp@...



From: hamlogger@... [mailto:hamlogger@...]
Sent: Sunday, February 11, 2018 3:45 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR








Hi Jim....thanks for all the tips....I can probably change the port
used and solve it that way

but I am curious as to what is really causing it...

What do you mean by the term "CWM"??

73 Ted VE3SS



From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 7:02 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR





Ted,

Well, you have eliminated the sound card.

Suggest you move the radio cable and configure an un-used Com port
for the radio, like #8

Make no other changes. Does that work?

Another source, do you have comm 4 configured in the CWM?

If push comes to shove, send me a copy of your Logger32.ini (By
direct e-mail shown below)

Hang in there, it's doable.

73, Jim - w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 5:39 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Hi Jim....tried your instructions to the letter but no dice.....the
pop up still happens with the same message

when I try to startup Logger32. Everything works fine though. Its
just an irritating pop up.

73 Ted VE3SS

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 3:30 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Ted,

I suspect the port is already open.

If you are configured to run MMTTY in the Logger32 sound card, you
should disable radio control in MMTTY.

If that is the case, try this:

1) open MMTTY setup "TX" Tab | PTT & FSK = set port to NONE

2) Select "Radio Command" and set port to NONE

3) Close MMTTY, then close Logger32

4) Reboot & Open Logger32 and see if the error still comes up.

We'll go from there.

73, Jim - w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 1:07 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Hi Jim.....As logger32 is opening, this small window eventually pops
open

and the message is "cant open com4 for radio commands"

Yet when its finished loading everything, rig control which is on
com4 works fine.

I am using an edgeport/8 to provide comports while it plugs into a
usb port on

the ham computer. Nothing else uses that comport as I have it
connected

from the edgeport to the back of the FT1000mp.

I actually only use 3 of the 8 ports on the edgeport.

I know that mmtty references that comport for rig control as well,
but it doesn't startup

when the computer is first turned on, and I have checked the task
manager

to see if an old mmtty executables might still be running..but its
not.

I am having another issue with Writelog not seeing comports and so I
had uninstalled

and reinstalled the drivers for the edgeport and it made no
difference for that situation

as well.

I know I have seen others with similar issues in the past, but

haven't seen any fixes come of them.

I hope that gives you more details....

Thanks 73 Ted VE3SS

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 12:31 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Ted,

Please tell us what the message says specifically and is it a
Logger32 or system error message? The re-mailer strips attachments.

Is comm4 a USB port built into the radio? If so the radio may have
to be turned on first..

Do you have anything else that is using the same port?

This type error is typically when the port is not visible to the OS
or it is already open by another or same application.

More details will be helpful.

73, Jim - w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 10:04 AM
To: hamlogger@...
Subject: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Hello all...just wondering why when I start up logger32 normally I
get the above error popping

onto my screen but yet the rig control works fine??? How do I get
rid of this error??

Any suggestions welcome.

Thanks

Ted VE3SS



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link
&utm_campaign=sig-email&utm_content=emailclient>

Virus-free.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link
&utm_campaign=sig-email&utm_content=emailclient> www.avg.com



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link
&utm_campaign=sig-email&utm_content=emailclient>

Virus-free.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link
&utm_campaign=sig-email&utm_content=emailclient> www.avg.com









<http://www.avg.com/email-signature?utm_medium=email&utm_source=link
&utm_campaign=sig-email&utm_content=emailclient>

Virus-free.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link
&utm_campaign=sig-email&utm_content=emailclient> www.avg.com

Re: Setup Radio - Custom Settings Button.

Vince Shirley
 

Jim,

Thanks for your help - the further I went into this issue, the more things I found that didn't add up.  There were any number off issues concerning com ports, sound cards, bands and modes tables not being adhered to, Lockups on start and refusing to shut down... and more.

To my mind something was corrupted and a re-boot didn't solve it.

I'm a bit paranoid about backups and I restored everything from one of the many backups I took earlier in the day, then restored the log from a separate backup and everything fell back into place and now works

Sorry for the bandwidth and thanks again for your help.

Vince 

On 11 February 2018 at 21:25, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 

I had a Yaesu FT-5000 and the command strings worked at that time..  No Yaesu now, so cant give you any kind of answer. What does it show in the debug screen when the commands are sent?  (sent ok but not recognized)???
 
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 12:07 PM
To: hamlogger@...
Subject: Re: [hamlogger] Setup Radio - Custom Settings Button.
 
 

......but when set to FT-991, the radio does not respond to the FA command and doesn't change frequency, which is also a bit odd....
 
 
Vince G0ORC
 
On 11 February 2018 at 17:46, Vince Shirley <vince.g0orc@...> wrote:
Well, this is a bit odd.
 
If I change the radio from Yaesu FT-5000 to a Yaesu FT-991 (which has a similar command set) then it works, the command string is sent.
 
If I then change it back to FT-5000, it doesn't.
 
As Alice said...."Curiouser and Curiouser"

Vince G0ORC
 
 
On 11 February 2018 at 17:28, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 
Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 
For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC
 
 
 
 


Re: CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Ted Boerkamp <tboerkamp@...>
 

Hi Jim....thanks for all the tips....I can probably change the port used and solve it that way

but I am curious as to what is really causing it...

What do you mean by the term  “CWM”??

73  Ted VE3SS

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 7:02 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

 

 

Ted,

Well, you have eliminated the sound card.

Suggest you move the radio cable and configure an un-used Com port
for the radio, like #8

Make no other changes. Does that work?

Another source, do you have comm 4 configured in the CWM?

If push comes to shove, send me a copy of your Logger32.ini (By
direct e-mail shown below)

Hang in there, it's doable.

73, Jim - w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 5:39 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Hi Jim....tried your instructions to the letter but no dice.....the
pop up still happens with the same message

when I try to startup Logger32. Everything works fine though. Its
just an irritating pop up.

73 Ted VE3SS

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 3:30 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Ted,

I suspect the port is already open.

If you are configured to run MMTTY in the Logger32 sound card, you
should disable radio control in MMTTY.

If that is the case, try this:

1) open MMTTY setup "TX" Tab | PTT & FSK = set port to NONE

2) Select "Radio Command" and set port to NONE

3) Close MMTTY, then close Logger32

4) Reboot & Open Logger32 and see if the error still comes up.

We'll go from there.

73, Jim - w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 1:07 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Hi Jim.....As logger32 is opening, this small window eventually pops
open

and the message is "cant open com4 for radio commands"

Yet when its finished loading everything, rig control which is on
com4 works fine.

I am using an edgeport/8 to provide comports while it plugs into a
usb port on

the ham computer. Nothing else uses that comport as I have it
connected

from the edgeport to the back of the FT1000mp.

I actually only use 3 of the 8 ports on the edgeport.

I know that mmtty references that comport for rig control as well,
but it doesn't startup

when the computer is first turned on, and I have checked the task
manager

to see if an old mmtty executables might still be running..but its
not.

I am having another issue with Writelog not seeing comports and so I
had uninstalled

and reinstalled the drivers for the edgeport and it made no
difference for that situation

as well.

I know I have seen others with similar issues in the past, but

haven't seen any fixes come of them.

I hope that gives you more details....

Thanks 73 Ted VE3SS

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 12:31 PM
To: hamlogger@...
Subject: RE: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Ted,

Please tell us what the message says specifically and is it a
Logger32 or system error message? The re-mailer strips attachments.

Is comm4 a USB port built into the radio? If so the radio may have
to be turned on first..

Do you have anything else that is using the same port?

This type error is typically when the port is not visible to the OS
or it is already open by another or same application.

More details will be helpful.

73, Jim - w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Saturday, February 10, 2018 10:04 AM
To: hamlogger@...
Subject: [hamlogger] CANT OPEN COM4 FOR RADIO COMMANDS ERROR

Hello all...just wondering why when I start up logger32 normally I
get the above error popping

onto my screen but yet the rig control works fine??? How do I get
rid of this error??

Any suggestions welcome.

Thanks

Ted VE3SS

[Non-text portions of this message have been removed]

&utm_campaign=sig-email&utm_content=emailclient>

Virus-free.
&utm_campaign=sig-email&utm_content=emailclient> www.avg.com

[Non-text portions of this message have been removed]

&utm_campaign=sig-email&utm_content=emailclient>

Virus-free.
&utm_campaign=sig-email&utm_content=emailclient> www.avg.com

[Non-text portions of this message have been removed]

 

Virus-free. www.avg.com

 

Re: Setup Radio - Custom Settings Button.

Jim Cox
 

I had a Yaesu FT-5000 and the command strings worked at that time..  No Yaesu now, so cant give you any kind of answer. What does it show in the debug screen when the commands are sent?  (sent ok but not recognized)???
 
 

From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 12:07 PM
To: hamlogger@...
Subject: Re: [hamlogger] Setup Radio - Custom Settings Button.
 
 

......but when set to FT-991, the radio does not respond to the FA command and doesn't change frequency, which is also a bit odd....
 
 
Vince G0ORC
 
On 11 February 2018 at 17:46, Vince Shirley <vince.g0orc@...> wrote:
Well, this is a bit odd.
 
If I change the radio from Yaesu FT-5000 to a Yaesu FT-991 (which has a similar command set) then it works, the command string is sent.
 
If I then change it back to FT-5000, it doesn't.
 
As Alice said...."Curiouser and Curiouser"

Vince G0ORC
 
 
On 11 February 2018 at 17:28, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 
Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 
For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC
 
 
 
 

Re: Setup Radio - Custom Settings Button.

Vince Shirley
 

......but when set to FT-991, the radio does not respond to the FA command and doesn't change frequency, which is also a bit odd....


Vince G0ORC

On 11 February 2018 at 17:46, Vince Shirley <vince.g0orc@...> wrote:
Well, this is a bit odd.

If I change the radio from Yaesu FT-5000 to a Yaesu FT-991 (which has a similar command set) then it works, the command string is sent.

If I then change it back to FT-5000, it doesn't.

As Alice said...."Curiouser and Curiouser"

Vince G0ORC


On 11 February 2018 at 17:28, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 

Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 

For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC
 
 



Re: Setup Radio - Custom Settings Button.

Vince Shirley
 

Well, this is a bit odd.

If I change the radio from Yaesu FT-5000 to a Yaesu FT-991 (which has a similar command set) then it works, the command string is sent.

If I then change it back to FT-5000, it doesn't.

As Alice said...."Curiouser and Curiouser"

Vince G0ORC


On 11 February 2018 at 17:28, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 

Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 

For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC
 
 


Re: Setup Radio - Custom Settings Button.

Vince Shirley
 

Jim,

Thank you.

If I send the same string from an RCP button, it works.  If I then copy that and paste it into the Command Settings Box, preface it by the RTTY= then it doesn't.

So no, I'm pretty sure there isn't an error.


Vince

On 11 February 2018 at 17:28, 'Jim Cox' jcox123@... [hamlogger] <hamlogger@...> wrote:
 

Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 
From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 

For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC
 
 


Re: Setup Radio - Custom Settings Button.

Jim Cox
 

Still works ok here, are you sure you don’t have a mistake in the command string?  Jim K4JAF
 

From: Vince Shirley vince.g0orc@... [hamlogger]
Sent: Sunday, February 11, 2018 11:24 AM
To: hamlogger@...
Subject: [hamlogger] Setup Radio - Custom Settings Button.
 
 

For longer than I care to remember, I've used the Custom Settings Button to send a command string to the radio when I click on a spot.  
 
The helpfile indicates this should still work.
 
I've just changed a few settings and note this no longer works.
 
The debug window sends the normal data when a spot is clicked on but the additional string from the custom settings box is no longer sent.
 
Is this by design, or has something broken?
 
Vince G0ORC