Re: icom-7610 Split QSY Macro
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 … ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bob
Sent: 27 July 2021 23:43
To: [email protected]
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). 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. ? Try this? ?$qsy #Split+01q#$ ? ?Not $QSY... ------ Original message ------ 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
? ?
|
Re: Porting Logger32 from old PC to new PC
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
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Michael Harris via groups.io Sent: 28 July 2021 01:58 To: [email protected]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
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?
toggle quoted message
Show quoted text
-------- Original message -------- From: "Michael Harris via groups.io" <mike.harris@...> Date: 27/07/2021 14:58 (GMT+00:00) 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
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@...>:
toggle quoted message
Show quoted text
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
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
toggle quoted message
Show quoted text
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
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
toggle quoted message
Show quoted text
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).
?
?
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
Vince
?
Try this? ?$qsy #Split+01q#$ ? ?Not $QSY...
?
?
?
------ Original message ------
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
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
Vince
?
Try this? ?$qsy #Split+01q#$ ? ?Not $QSY...
?
?
?
------ Original message ------
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
toggle quoted message
Show quoted text
------ Original message ------
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
Vince
Try this? ?$qsy #Split+01q#$
? ?Not $QSY...
------ Original message ------
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
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
Vince
Try this? ?$qsy #Split+01q#$
? ?Not $QSY...
------ Original message ------
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
Try this? ?$qsy #Split+01q#$
? ?Not $QSY...
------ Original message ------
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
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
|
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:
?
?
|
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:
?
?
|
|
|
Gary.
Thanks for the ideas.
Borrowed a "ini" file from a nearby ham, and compared the two files. Didnt find much difference except the obvious ones.
So tried a few things as I wanted to avoid a new install.
?
I think this is?something that relates to WSJT-X and/ or UDP. I use UDP to allow WSJT send qso info to logger.
If I have WSJT running with UDP open, but switch to CW (didnt test other modes) and manually log, then the Grid is populated with my own.
WSJT-X then show OOB (out of band) since I "override" by turning the VFO and manually control the rig mode etc.?
However if I close the UDP connection and WSJT-X it works as before.
Hugo / LA4WKA
|
Hmmmm, OK Hugo, so it’s not the preset text as I thought.. ? It may be a Logger32 configuration problem, something odd stored in your C:\Logger32\Logger32.INI file.? ? You could try editing Logger32.INI with Notepad.? Close Logger32, then maybe try deleting the whole section that starts with [wndLogbookEntry Settings], and then restart Logger32 and manually reconfigure your log entry pane.? Alternatively, you could search the Logger32.INI file for any line containing your grid square, and delete just that line. ? Either way, the first thing is to make a backup of Logger32.INI.? If it was me, I would also make an ADIF export of my log as a further insurance backup at this point, just in case I make the situaton even worse rather than better. ? 73 Gary? ZL2iFB ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of la4wka
Sent: 26 July 2021 07:26
To: [email protected]
Subject: Re: [hamlogger] Grid square? The field for preset text is empty.
I only noticed this after the last update, howecver I went back and had to edit about 75 qso's with my own grid, and dint pay attention to what date it was.
Hugo / LA4WKA
|
The field for preset text is empty. I only noticed this after the last update, howecver I went back and had to edit about 75 qso's with my own grid, and dint pay attention to what date it was.  Hugo / LA4WKA
|
Ah, OK Hugo. ? It looks to me as if you may have defined your grid square as the ‘preset text’ for that log entry field. ? ? The mentions it in section 6.2 on page 114. ? The ‘preset text’ should probably be empty … and maybe we ought to revise the screenshot and text in the manual to clarify how it works. ? 73 Gary? ZL2iFB ? ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of la4wka
Sent: 26 July 2021 06:04
To: [email protected]
Subject: Re: [hamlogger] Grid square? In the box where you type the callsign, there are many fields you can customize.
I have one field that is made for Grid Square......from the drop down adif menu.
Used to collect ....yes grid squares.
Thing is no matter what callsign I type in the log entry window it shown my own grid reference. This also happen if I click on a cluster spot.
Even though we have worked befor Gary, and another value is in log for previous qso's, it shown up like in the red cirkle.
Hope this gives a better explanation og the issue.
Hugo / LA4WKA
|
That's right, now it works!
Thanks Bob.
?
|
John Munton - G7SSE