|
Re: icom-7610 Split QSY Macro
Vince Shirley
Thanks Bob... Vince G0ORC
On Tue, 27 Jul 2021 at 12:43, Bob <k4cy@...> wrote:
|
|
|
|
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).
|
|
|
|
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
|
|
|
|
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:
|
|
|
|
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
|
|
|
|
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
|
|
|
|
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.
|
|
|
|
Got this . Why ?
Dave Colliau
|
|
|
|
Re: Grid square
la4wka
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
|
|
|
|
Re: Grid square
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
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of la4wka
Sent: 26 July 2021 07:26 To: hamlogger@groups.io Subject: Re: [hamlogger] Grid square
The field for preset text is empty.
|
|
|
|
Re: Grid square
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
|
|
|
|
Re: Grid square
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 User Manual 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
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of la4wka
Sent: 26 July 2021 06:04 To: hamlogger@groups.io Subject: Re: [hamlogger] Grid square
In the box where you type the callsign, there are many fields you can customize.
|
|
|
|
Re: Cherry picking
Luis EA5L
That's right, now it works!
Thanks Bob.
|
|
|
|
Re: Grid square
la4wka
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
|
|
|
|
Re: Cherry picking
Bob
On the UDP BandMap, click CONFIG. Check the option HIGHLIGHT CALLS/GRIDS AS "DIG" MODE. SeventyThree(s).
|
|
|
|
Re: Cherry picking
Thanks Bob, but I think I have marked what you indicate, in ft4 it keeps calling stations that I already have in ft8 in the same band. In band / mode the same thing happens.VE1CNS I already have it in FT8.
I'm sending you a capture.
 
|
|
|
|
Re: Grid square
Bob
You could try loading the Club Log Prefix exceptions database again, and loading the Club Log LoTW users database again. SeventyThree(s).
|
|
|
|
Re: Grid square
Hello Hugo.
Your email has so little useful information that it is unanswerable.
What is the ‘it’ that is being ‘populated with your own gridsquare’?
Presumably you are talking about a grid field, somewhere, but please spare a moment to clarify/explain the problem if you expect a sensible response.
73 Gary ZL2iFB
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of la4wka
Sent: 25 July 2021 19:24 To: hamlogger@groups.io Subject: [hamlogger] Grid square
Hello group
|
|
|
|
Re: Generic QSO Window
Jan <hamlogger@...>
Please do not remove the adifmodes.txt
and bands & modes
73 Jan PA4JJ Op 25-7-2021 om 15:35 schreef Panos:
Hi Bob thanks for removing. I think that files such adifmodes.txt and bands & modes shouldn't implemented by the user. Would you please in the future supply them in not editable manner? Thanks 73 -- ____________________________________________________ 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
|
|
|
