Date   

Re: Rcp

John Munton - G7SSE
 

Hi Andy

The best I came up with for mine were;

LSB    $hexcommand FE FE 98 E0 01 00 ## FD$

USB    $hexcommand FE FE 98 E0 01 01 ## FD$

CW    $hexcommand FE FE 98 E0 01 03 ## FD$

RTTY    $hexcommand FE FE 98 E0 01 04 ## FD$

Replace the ## with 01 , 02 , 03 for the corresponding filter.

You would need to use three buttons (one for each filter) in the RCP for each mode.

(I could not find a method that did not include the mode in the command)


There is also a command with which you can change the width of the currently selected filter;

$hexcommand FE FE 98 E0 1A 03 ** FD$

Replace ** with the required number as per this table:


Again, multiple RCP buttons would be required for different choices.

Tip; if you only are using one radio at a time open the RCP in SO2V mode, it doubles the number of available buttons.

Hope this is of some use to you.

73

John - G7SSE


------ Original Message ------
From: "Andy M0NKR via groups.io" <andrewgoldsmith22@...>
Sent: 27/07/2021 16:32:47
Subject: [hamlogger] Rcp

Hi
 
New to the RCP screen
 
Can you set a button for the different filter setting on the radio?
 
If so can someone help please.
 
Radio is icom 7610
 
73
Andy
M0NKR
 
 
 
 

--
73, John - G7SSE


Re: VIS_DESK_ERROR

Bob
 

Peter, your Zone Exceptions database has crashed. Look in the Logger32 directory for these three files:
 
 
I is possible you have four files. Delete them all. Start Logger32. It will create new/empty files. Load the Club Log Exceptions file, and the data will be entered into the new files. Ja alles gut? SeventyThree(s).

On 07/27/2021 1:08 PM Peter Eckersberger <oe3epw@...> wrote:
 
 
Hello,

I need some help. Since yesterday evening I'm unable to start Logger32. Whenever I click on the Desktop icon Logger32 comes up for a fraction of a second and is immediately replaced by this little error window ...



I've to restart the computer and do something else. Logger32 is NOT operational.


Previous history ... I'm using Logger32 together with JTDX and/or WSJT-X. Fantastic combo, serves me very well. With one small glitch ... Start sequence is "Logger32" > right click "UDP" > left click "UDP Band Map"> right click "Start" > left click "JTDX" or "WSJT-X". The latter both via Shortcut "On Top" & "High Priority". Both programs start as expected but are loosing connection within seconds to my radio IC-7300. I've to close all the software involved and make a total restart including Windows10. From now on all works fine for hours.

Extra note ... That procedure has to be followed every day when loading the combo L32_JTDX for the first time.
For the time being no Logger32 at all!!


Well, here some facts concerning my station ... Radio "IC-7300" together with a microKEYER II by microHAM


Computer ...






That's it. Any suggestion to overcome that inconvenience? Maybe there is a trick Bob can advise. TIA



73 de Peter, OE3EPW
<oe3epw@...>


VIS_DESK_ERROR

Peter Eckersberger
 

Hello,

I need some help. Since yesterday evening I'm unable to start Logger32. Whenever I click on the Desktop icon Logger32 comes up for a fraction of a second and is immediately replaced by this little error window ...



I've to restart the computer and do something else. Logger32 is NOT operational.


Previous history ... I'm using Logger32 together with JTDX and/or WSJT-X. Fantastic combo, serves me very well. With one small glitch ... Start sequence is "Logger32" > right click "UDP" > left click "UDP Band Map"> right click "Start" > left click "JTDX" or "WSJT-X". The latter both via Shortcut "On Top" & "High Priority". Both programs start as expected but are loosing connection within seconds to my radio IC-7300. I've to close all the software involved and make a total restart including Windows10. From now on all works fine for hours.

Extra note ... That procedure has to be followed every day when loading the combo L32_JTDX for the first time.
For the time being no Logger32 at all!!


Well, here some facts concerning my station ... Radio "IC-7300" together with a microKEYER II by microHAM


Computer ...






That's it. Any suggestion to overcome that inconvenience? Maybe there is a trick Bob can advise. TIA



73 de Peter, OE3EPW
<oe3epw@...>


Re: Rcp

Bob
 

Look in the radio documentation for the CAT command to change the filter setting. Then look at page 594 of the help file for examples of Icom CAT commands. The only thing to be wary of is the CI-V address of your radio may not be the same as the examples. SeventyThree(s).

On 07/27/2021 11:32 AM Andy M0NKR via groups.io <andrewgoldsmith22=yahoo.co.uk@groups.io> wrote:


Hi

New to the RCP screen

Can you set a button for the different filter setting on the radio?

If so can someone help please.

Radio is icom 7610

73
Andy
M0NKR



Re: Rcp

Dave Colliau
 

Download the Cat command manual for the 7610 then study it along with the Icom cat commands in the logger user manual . Its pretty easy to do and you should learn how it all works. There are endless possibilities for commands.
I would look it up for you but I am heading out the door .
73
Dave N8DC

On 07/27/2021 11:32 AM Andy M0NKR via groups.io <andrewgoldsmith22=yahoo.co.uk@groups.io> wrote:


Hi

New to the RCP screen

Can you set a button for the different filter setting on the radio?

If so can someone help please.

Radio is icom 7610

73
Andy
M0NKR



Rcp

Andy M0NKR
 

Hi

New to the RCP screen

Can you set a button for the different filter setting on the radio?

If so can someone help please.

Radio is icom 7610

73
Andy
M0NKR


Re: icom-7610 Split QSY Macro

Gary Hinson
 

With amazing foresight and without changing the wording, section 36.3.4 of the manual will become correct as the universe snaps neatly back into alignment with Logger32 version 4.0.290.   😊

 

Well spotted, Vince.  Well I never, Bob. 

 

Hopefully there are no other weird case-dependent macro oddities and the like but anything is possible – including oversites, errrors and typoos lurking in the manual and, yes, pesky bugs lurking under the covers of Logger32. 

 

Please continue reporting them.  We’ll get there in the end.  Expect jam tomorrow.

 

73

Gary  ZL2iFB

 

PS  Nobody has yet reported the Easter eggs hidden somewhere in the manual …

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 27 July 2021 23:43
To: hamlogger@groups.io
Subject: Re: [hamlogger] icom-7610 Split QSY Macro

 

Oops, my fault. There are six places in the code that look for '$qsy ...' in a macro. one of them was case sensitive. It is fixed for th next auto-update. SeventyThree(s).

On 07/27/2021 6:41 AM Vince Shirley <vince.g0orc@...> wrote:

 

 

Aki,

 

Thank you - I was replicating what was in the manual. Perhaps Gary could amend Section 36.3.4 to reflect the use of the lower case.

 

The manual shows upper case.

 

Thank you again

 

Vince G0ORC

 

On Tue, 27 Jul 2021 at 10:18, ja1nlx < ayoshida0205@...> wrote:

Vince

 

Try this   $qsy #Split+01q#$    Not $QSY...

 

 

73 de aki

JA1NLX

 

------ Original message ------

From: "Vince Shirley" < vince.g0orc@...>

Date: 2021/07/27 17:52:41

Subject [hamlogger] icom-7610 Split QSY Macro

 

Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.

 

When using the macro   $QSY #Split+01q#$

 

I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz

 

i.e MHz instead of kHz 

 

Odd?

 

Vince

 

 


Re: Porting Logger32 from old PC to new PC

Gary Hinson
 

Aside from the auto-start utilities, you might also need to check that the particular fonts used in your installation of Logger32 are installed on the new PC.

Oh and if it is not stored in the Logger32 folder that you copied, you'll also need to transfer your log across - preferably doing a full ADIF export from the old PC, then an import on the new one.

73
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Michael Harris via groups.io
Sent: 28 July 2021 01:58
To: hamlogger@groups.io
Subject: Re: [hamlogger] Porting Logger32 from old PC to new PC

Hi Normal,

Install a fresh copy on the new PC ensuring you use the same file path.
Don't mess about with any configuration all you are interested in is setting up the registration entries. Then replace it with your existing
L32 folder. You might have to correct any utility file paths in the .INI if they have not been installed in the same file locations.

Job done.

Regards,

Mike VP8NO

On 27/07/2021 10:04, norman9795 via groups.io wrote:
I am looking for the easiest way to port my rxisting installation to a
new PC with the minimum of effort.

Norman
G2DWB


Re: Porting Logger32 from old PC to new PC

John Munton - G7SSE
 

Comports numbers and audio device settings might need changing too.

Also, any utility programs that Logger32 might use need reinstalling. Especially if Logger32 auto starts them.

John G7SSE 




-------- Original message --------
From: "Michael Harris via groups.io" <mike.harris@...>
Date: 27/07/2021 14:58 (GMT+00:00)
To: hamlogger@groups.io
Subject: Re: [hamlogger] Porting Logger32 from old PC to new PC

Hi Normal,

Install a fresh copy on the new PC ensuring you use the same file path.
Don't mess about with any configuration all you are interested in is
setting up the registration entries. Then replace it with your existing
L32 folder. You might have to correct any utility file paths in the .INI
if they have not been installed in the same file locations.

Job done.

Regards,

Mike VP8NO

On 27/07/2021 10:04, norman9795 via groups.io wrote:
> I am looking for the easiest way to port my rxisting installation to a
> new PC with the minimum of effort.
>
> Norman
> G2DWB






--
73, John - G7SSE


Re: Porting Logger32 from old PC to new PC

Mathias Grallert
 

Install Logger on the new PC, then copy complete directory
( C:/Logger32 ) from the old to new PC. Works fine here.

73 DK5MO

27.07.2021 15:04:14 norman9795 via groups.io <normanwebster@...>:

I am looking for the easiest way to port my rxisting installation to a new PC with the minimum of effort.

Norman
G2DWB


Re: Porting Logger32 from old PC to new PC

Michael Harris
 

Hi Normal,

Install a fresh copy on the new PC ensuring you use the same file path. Don't mess about with any configuration all you are interested in is setting up the registration entries. Then replace it with your existing L32 folder. You might have to correct any utility file paths in the .INI if they have not been installed in the same file locations.

Job done.

Regards,

Mike VP8NO

On 27/07/2021 10:04, norman9795 via groups.io wrote:
I am looking for the easiest way to port my rxisting installation to a new PC with the minimum of effort.
Norman
G2DWB


Porting Logger32 from old PC to new PC

norman9795
 

I am looking for the easiest way to port my rxisting installation to a new PC with the minimum of effort.

Norman
G2DWB


Re: icom-7610 Split QSY Macro

Vince Shirley
 

Thanks Bob...

Vince G0ORC

On Tue, 27 Jul 2021 at 12:43, Bob <k4cy@...> wrote:
Oops, my fault. There are six places in the code that look for '$qsy ...' in a macro. one of them was case sensitive. It is fixed for th next auto-update. SeventyThree(s).
On 07/27/2021 6:41 AM Vince Shirley <vince.g0orc@...> wrote:
 
 
Aki,
 
Thank you - I was replicating what was in the manual. Perhaps Gary could amend Section 36.3.4 to reflect the use of the lower case.
 
The manual shows upper case.
 
Thank you again
 
Vince G0ORC

On Tue, 27 Jul 2021 at 10:18, ja1nlx < ayoshida0205@...> wrote:
Vince
 
Try this   $qsy #Split+01q#$    Not $QSY...
 
 
73 de aki
JA1NLX
 
------ Original message ------
From: "Vince Shirley" < vince.g0orc@...>
Date: 2021/07/27 17:52:41
Subject [hamlogger] icom-7610 Split QSY Macro
 
Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.
 
When using the macro   $QSY #Split+01q#$
 
I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz
 
i.e MHz instead of kHz 
 
Odd?
 
Vince

 

 


Re: icom-7610 Split QSY Macro

Bob
 

Oops, my fault. There are six places in the code that look for '$qsy ...' in a macro. one of them was case sensitive. It is fixed for th next auto-update. SeventyThree(s).

On 07/27/2021 6:41 AM Vince Shirley <vince.g0orc@...> wrote:
 
 
Aki,
 
Thank you - I was replicating what was in the manual. Perhaps Gary could amend Section 36.3.4 to reflect the use of the lower case.
 
The manual shows upper case.
 
Thank you again
 
Vince G0ORC

On Tue, 27 Jul 2021 at 10:18, ja1nlx < ayoshida0205@...> wrote:
Vince
 
Try this   $qsy #Split+01q#$    Not $QSY...
 
 
73 de aki
JA1NLX
 
------ Original message ------
From: "Vince Shirley" < vince.g0orc@...>
Date: 2021/07/27 17:52:41
Subject [hamlogger] icom-7610 Split QSY Macro
 
Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.
 
When using the macro   $QSY #Split+01q#$
 
I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz
 
i.e MHz instead of kHz 
 
Odd?
 
Vince

 

 


Re: icom-7610 Split QSY Macro

ja1nlx
 

🙂

73 de aki
JA1NLX

------ Original message ------
From: "Vince Shirley" <vince.g0orc@...>
Date: 2021/07/27 19:41:42
Subject Re: [hamlogger] icom-7610 Split QSY Macro

Aki,

Thank you - I was replicating what was in the manual. Perhaps Gary could amend Section 36.3.4 to reflect the use of the lower case.

The manual shows upper case.

Thank you again

Vince G0ORC

On Tue, 27 Jul 2021 at 10:18, ja1nlx <ayoshida0205@...> wrote:
Vince

Try this   $qsy #Split+01q#$    Not $QSY...


73 de aki
JA1NLX

------ Original message ------
From: "Vince Shirley" <vince.g0orc@...>
Date: 2021/07/27 17:52:41
Subject [hamlogger] icom-7610 Split QSY Macro

Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.

When using the macro   $QSY #Split+01q#$

I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz

i.e MHz instead of kHz 

Odd?

Vince


Re: icom-7610 Split QSY Macro

Vince Shirley
 

Aki,

Thank you - I was replicating what was in the manual. Perhaps Gary could amend Section 36.3.4 to reflect the use of the lower case.

The manual shows upper case.

Thank you again

Vince G0ORC

On Tue, 27 Jul 2021 at 10:18, ja1nlx <ayoshida0205@...> wrote:
Vince

Try this   $qsy #Split+01q#$    Not $QSY...


73 de aki
JA1NLX

------ Original message ------
From: "Vince Shirley" <vince.g0orc@...>
Date: 2021/07/27 17:52:41
Subject [hamlogger] icom-7610 Split QSY Macro

Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.

When using the macro   $QSY #Split+01q#$

I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz

i.e MHz instead of kHz 

Odd?

Vince


Re: icom-7610 Split QSY Macro

ja1nlx
 

Vince

Try this   $qsy #Split+01q#$    Not $QSY...


73 de aki
JA1NLX

------ Original message ------
From: "Vince Shirley" <vince.g0orc@...>
Date: 2021/07/27 17:52:41
Subject [hamlogger] icom-7610 Split QSY Macro

Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.

When using the macro   $QSY #Split+01q#$

I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz

i.e MHz instead of kHz 

Odd?

Vince


icom-7610 Split QSY Macro

Vince Shirley
 

Apologies for repeating myself but this one from a  few days ago appears to have go lost amongst a slew of responses to more important issues.

When using the macro   $QSY #Split+01q#$

I get a response from Logger32 "The BandPlan has no entries that match a frequency of  18099.0 MHz" -  which is true if it really did mean 18099.0 MHz but I suspect it should be 18099.0 kHz

i.e MHz instead of kHz 

Odd?

Vince


Re: Got this . Why ?

Dave Colliau
 

Thanks Bob . I was on teamviewer and tryin 8 things at once with a friend we have it now
73
Dave N8DC
 

On 07/26/2021 2:08 PM Bob <k4cy@...> wrote:
 
 
You have just started logger32. Now it is trying to start the utility programs you told it to. It doesn't like the commands to told it to execute. 73.
On 07/26/2021 2:01 PM Dave Colliau <n8dc-8@...> wrote:
 
 


Re: Got this . Why ?

Bob
 

You have just started logger32. Now it is trying to start the utility programs you told it to. It doesn't like the commands to told it to execute. 73.

On 07/26/2021 2:01 PM Dave Colliau <n8dc-8@...> wrote:
 
 

2261 - 2280 of 87443