Re: Switching from N3FJP - best solution for CNTY field issues? Plus a solution to 4m QSOs all being rejected
ja1nlx
Mike You are welcome. Enjoy 73 de aki JA1NLX
|
||
|
||
Re: Switching from N3FJP - best solution for CNTY field issues? Plus a solution to 4m QSOs all being rejected
Mike M0AGP
On Wed, Dec 29, 2021 at 12:59 AM, ja1nlx wrote:
https://www.qsl.net/kl7j/county.htmlArigato gosaimazu Aki-san! 73 Mike
|
||
|
||
Re: Switching from N3FJP - best solution for CNTY field issues? Plus a solution to 4m QSOs all being rejected
ja1nlx
Mike Look at the following web page to find the correct county in Alaska. https://www.qsl.net/kl7j/county.html 73 de aki JA1NLX
|
||
|
||
Switching from N3FJP - best solution for CNTY field issues? Plus a solution to 4m QSOs all being rejected
Mike M0AGP
I'm switching after a year of using N3FJP and have a couple dozen cases where QSOs are being rejected due to the county in the CNTY field not looking the way Logger32 wants.
I'm happy to go edit the CNTY fields in the relevant records in N3FJP, but I'm not sure how to take the info from the N3FJP log and convert it to what Logger32 wants. Here is n example of what I mean. I set up user field 6 to be P.Adm (STATE) and user field 7 to be S.Adm (CNTY). I started to enter a QSO, and clicked on the "?" icon to get a box that seems to show the counties that Logger32 would not reject. Here is what I see for Alaska: But in N3FJP I see this info : So it's not obvious which of the counties I'm supposed to choose... All of my Alaska QSOs with CNTY info were rejected. I did see the Logger32 v4 user guide by G4IFB and the FAQ entry that shows a way of just easily dropping the all the CNTY information. But is there a (relatively simple) way of keeping the info by somehow determining the version Logger32 wants? Or if I drop all CNTY info is there a big table that can later be used to add the county info to each of the US QSOs in Logger32? If not, no worry I will just drop the county info. I guess in future if I become a county hunter I would need another solution! One other question: it seems that Q65 contacts are not allowed ("Error in the SUBMODE field") - true? Also a solution to a problem in case any other noob needs it: all of my 4m contacts were rejected as they were "not in the 4m band". Actually, the 4m band had not been defined in the "Bands & Modes" table. Entering the relevant info there caused all the QSOs to be accepted. Btw I have been using the application for like one day - sorry for any dumb questions! Thanks Mike M0AGP
|
||
|
||
Fw: [hamlogger] Worked/Confirmed Window
G4GIR
Garry I think I have found the fly in the ointment!!
Add "Show a Column for SAT QSO's"
Then turn on/off the Show consolidated DIGI/PHONE modes.
What happens?
73
Ian
|
||
|
||
Re: Worked/Confirmed Window
G4GIR
Thanks' Gary
I will keep looking, What also would be good to see is the section for [WndWorkedConfirmed Settings] in your INI file?
This is how mine is:-
[WndWorkedConfirmed Settings]
Column 0 Width=975 Selected Band=8454143 Include eQSL=False Show SAT Column=True Current Operator Only=True Consolidate DIGital=True Consolidate PHOne=True HScrollbar=True Complex Display=True Adjusted Columns=|PHO|CW|DIG|FT8|SAT|||||| Column 1 Width=435 Column 2 Width=375 Column 3 Width=375 Column 4 Width=660 Column 5 Width=1035 Column 6 Width=105 Column 7 Width=105 Column 8 Width=120 Column 9 Width=120 Column 10 Width=120 Column 11 Width=120 Include QSL=True Include LoTW=True [Globals] I could Paste yours into mine and see how it goes from there.
Yes Bob has reminded me a few times of his other activities Lol, I am aware.
Thanks' for the help
73
Ian
|
||
|
||
Re: Worked/Confirmed Window
OK Ian.
Here’s my normal setup:
If I un-tick the consolidated DIG and PHO modes, and widen the table columns to see them:
Does that help??
73 Gary ZL2iFB
PS Despite appearances, I gather Bob ‘has a life’ beyond Logger32. He’s relatively normal i.e. he has a family, and it is christmas after all.
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of G4GIR via groups.io
Sent: Wednesday, 29 December 2021 7:46 am To: hamlogger@groups.io Subject: Re: [hamlogger] Worked/Confirmed Window
Morning Gary,
Hope you had a good one, hope Bob hasn't hit the Grouse to much!! Guess he is taking a well deserved break, unlike me, every days a holiday!!
Strangely enough I read through that section this afternoon, but nowhere could I find information regarding the disappearance of columns!
You could do one thing for me? If you have "Show consolidated Digital Modes in the W/C Window" Ticked and you then un-tick it, what happens to you columns in that window?
I have L32 on several Laptops/PC's and each machine is behaving the same way.
From your reply I guess the answer to the problem is in the manual?
As for the .INI file, it's usually the first place I look if I have a problem, comparing it to other good Config.INI's
I didn't get it from a back up but from a working INI, I have 8 different startup configurations!
Looking forward to your findings.
73
Ian
|
||
|
||
logger32 QRX ...Connection to https://clublog.org/cty.php failed
jselmi@...
I get this error everytime I start L32. I've noticed others have received it to.
Is there a fix or someting for me to look into? Tia, Jim K6JS
|
||
|
||
Change mail
LU3VA <lu3va@...>
|
||
|
||
Re: Worked/Confirmed Window
G4GIR
Morning Gary,
Hope you had a good one, hope Bob hasn't hit the Grouse to much!! Guess he is taking a well deserved break, unlike me, every days a holiday!!
Strangely enough I read through that section this afternoon, but nowhere could I find information regarding the disappearance of columns!
You could do one thing for me? If you have "Show consolidated Digital Modes in the W/C Window" Ticked and you then un-tick it, what happens to you columns in that window?
I have L32 on several Laptops/PC's and each machine is behaving the same way.
From your reply I guess the answer to the problem is in the manual?
As for the .INI file, it's usually the first place I look if I have a problem, comparing it to other good Config.INI's
I didn't get it from a back up but from a working INI, I have 8 different startup configurations!
Looking forward to your findings.
73
Ian
|
||
|
||
Re: slow input of callsign
Joe N3XLS
I always had a delay on some calls when the previous QSO's needs to pull a lot ( pushing close to 1k QSO's on some calls. That not what was the delay was i was experiencing it was a delay on any call typed in. i wouldn't get past the first letter and it would start spinning, when it stop it would "reset" the windows then let me type the call in further. It would do this again on the next call. To stop it i had to exit L32 and start it up again. then about 1 or 2 hours it would start doing it again. It would get slower and slower. I did the re-cal stats last night, it takes over 20mins! It failed and had to do it over again this morning, that one worked fine.
somewhere when i restarted L32 yesterday the problem went away. have yet to see it. Maybe it was a file that was getting to large and it finally reset itself?
|
||
|
||
Re: slow input of callsign
kenfilmer@outlook.com
Hi John
I now know my computer spec, thanks! ken G3XPO
|
||
|
||
Re: slow input of callsign
Jason N3YUG
So I updated QRZLookup yesterday, that did nothing to fix the problem. My log had 28,500 Q’s in it. I have seen DK stations, any R station, some A , N, and K station are slow also. The other thing I have noticed is my Worked/Confirm window it changing setting by itself. I found the other day, instead of being set to “Include LOTW for confirmations” only, it unchecked that, and put a check in QSL and EQSL. I turned those off, and LOTW back on, and it was good for a while. Just today, it was set to just show LOTW confirmations, and out of no where it switched off LOTW and on EQSL and QSL.
I am running 4.0.288 with a Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz 2.81 GHz and 8GB ram on windows 10.
Jason N3YUG
|
||
|
||
Re: slow input of callsign
Bruce Meier
I have to agree that L32 V4.0.288 is very slow for both entering a call or clicking on a spot in the band map. I also agree that the delay (response) time for L32 to take the requested action varies based on the prefix of the call entered or clicked on. If clicking on a spot the call will immediately appear in the CALL window, but it will take several seconds for the K3S to move to the correct frequency. However, if entering a call directly in the CALL window, after the prefix is entered the magic spinning CIRCLE appears showing something is going on. Then, after several seconds the circle goes away and the curser reappears. Then I can type in the rest of the call.
I am running L32 on Windows 10 Pro 64bit, I7-quad core 3.4GHz cpu, 16.0GB of memory, SSD drive.
My log contains 220017 QSOs, but I am a very basic user and don’t have much going on.
73 and Happy New Year,
Bruce N1LN -- 73, Bruce N1LN
|
||
|
||
Re: slow input of callsign
f4azf_damien
Hello , also same problem since 10days , but i think that L32lookup is slowing + windows10 64 updates..
I7 /3.4gHz , 8giga ram ,ssd.
So i ll test without l32lookup
73s Damien
De : hamlogger@groups.io <hamlogger@groups.io> De la part de Fabio IZ8MBW via groups.io
Do you have a SSD Hard Disk? Is Logger32 installed into a SSD Hard Disk?
73 Fabio, IZ8MBW
On Monday, December 27, 2021, 10:47:03 PM GMT+1, g4girhb0 via groups.io <ian.frith@...> wrote:
Thanks Fabio/Mike
That's not a lot of QSO's to sort through. my log has 80,000 QSO's and I am sure that is nowhere near as many as some L32 users, so maybe your logs are small enough to not see the delays like others have. Hopefully Bob is looking at the issue.
Thanks for the replies.
73
Ian G4GIR
Ian 600-700 Q’s
Mike
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of g4girhb0 via groups.io
How many Q's in the log Mike?
Ian
|
||
|
||
Re: Worked/Confirmed Window
Mornin’ Ian.
There are quite a few config options for the worked/confirmed table, and loads of permutations/combinations, which we’ve tried to explain in the manual.
Between the excesses of Christmas and New Year’s Eve, try to find a moment to sit quietly in a darkened room with just Logger32 and the User Manual for company. As you work systematically through section 10.2, reading the text, peering at the pictures, scratching your temples and trying out the various settings, you will hopefully figure out what the settings do and so get the hang of it, well enough to get your worked/confirmed table looking ‘just so’.
You shouldn’t need to meddle with the innards of your .INI files … but good on you for having saved a backup/archive of a working configuration. It’s easy enough to cut-n-paste the relevant section/s from a backup into the current .INI, then re-start Logger32 to pick them up – a trick that has saved me the tedium of reconfiguring my logbook columns and so forth from scratch in the past.
73 HNY Gary ZL2iFB
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: Wednesday, 29 December 2021 3:57 am To: hamlogger@groups.io Subject: Re: [hamlogger] Worked/Confirmed Window
Found the reason for loosing the columns. When I de-select Show consolidated Digital Modes in the W/C window All my Columns disappear from the W/C window except for my SAT column.
Looking in the Config files for two different configurations I find a difference :-
This is the entries in the config file that works as I want it. Adjusted Columns=|PHO|DIG|CW|FT8
This is what happens to the config file after de-selecting "Show consolidated Digital Modes" and or de-selecting "Show consolidated Phone Modes"
Complex Display=False
Cheers 73 Ian G4GIR
|
||
|
||
Re: slow input of callsign
kenfilmer@outlook.com
One thing, its reassuring to me to hear that so many others have the same problem (I think mine is the same as yours Ian) so its not me having done something wrong.
It seems that as soon as a call gets entered the programme checks through the log for previous contacts and it is that action which seems to slow it down. if logs are below a certain size the problem doesn't occur. I'm sure Bob will be able to resolve this. Like all computer problems I will puzzle for days and somebody who knows what they are doing will resolve it in seconds. Ken G3XPO
|
||
|
||
Re: slow input of callsign
kenfilmer@outlook.com
Hi John
Going back to a previous version did cross my mind. something happened at some time i didn't realise, whether it was a MS or Logger update. I shall try that! 73 Ken G3XPO
|
||
|
||
Re: Worked/Confirmed Window
g4girhb0 <ian.frith@...>
Found the reason for loosing the columns.
When I de-select Show consolidated Digital Modes in the W/C window All my Columns disappear from the W/C window except for my SAT column.
Looking in the Config files for two different configurations I find a difference :-
This is the entries in the config file that works as I want it.
Adjusted Columns=|PHO|DIG|CW|FT8
Column 1 Width=435 Column 2 Width=375 Column 3 Width=375 Column 4 Width=660 Column 5 Width=1035 Column 6 Width=105 Column 7 Width=105 Column 8 Width=120 Column 9 Width=120 Column 10 Width=120 Column 11 Width=120 Column 12 Width=120 Column 13 Width=120 Column 14 Width=120 Column 15 Width=120 Column 16 Width=120 Column 17 Width=120 Column 18 Width=120 Column 19 Width=120 Complex Display=False This is what happens to the config file after de-selecting "Show consolidated Digital Modes" and or de-selecting "Show consolidated Phone Modes"
Complex Display=False
Column 1 Width=435 Column 2 Width=375 Column 3 Width=375 Column 4 Width=660 Column 5 Width=1035 Column 6 Width=105 Column 7 Width=105 Column 8 Width=120 Column 9 Width=120 Column 10 Width=120 Column 11 Width=120 Cheers
73
Ian G4GIR
|
||
|
||
Re: slow input of callsign
g4girhb0 <ian.frith@...>
Hello Kenneth
Yes that seems to confirm that the Worked/Confirmed Table is playing a part in the delay problem, with Manual entry the W/C table doesn't do anything.
Thanks
73
Ian G4GIR
|
||
|