Date   

Re: Notes window

ja1nlx
 

Bob

I do not duplicate reported problem, however I see this.

1. Note is already logged for QSO with K4CY.

2. Select this QSO and click "Show note window"

3. Click any row in Note window. Grid width is narrowed.

4. Delete this note. I see this.

5. Re-open Note window.


73


.

On 2020/10/15 5:17, Bob wrote:
I spent some time investigating this today, and it could be one of many things. Please help me zero in on the problem.

Was it a short note, or an autobiography?
I the problem for this particular QSO only?
Can you add a note to a non 60m band QSO?
Despite the warning message, is the note actually added?
If you recalculate you stats for this logbook, does the have any effect?
Can you log a QSO with a note? If so, can you then delete the note? if so, can you add a note?

Anything you can do to help narrow it down would be appreciated. 73.
On 10/13/2020 10:36 PM Vince Shirley <vince.g0orc@...> wrote:


Hi all I'll try again - Google mail screwed up the image and text - this showld be OK...


Hi all,

I' haven't used the Notes window for a while and everything OK except for this.

If I try and add a note for a selected QSO I get this

"Unable to add notes to selected QSO with 44117.2921990741"  The number varies depending on the QSO selected.

I something broken?

Vince


--
73 de aki
JA1NLX


Re: Notes window

Vince Shirley
 

Bob,

Thank you - I'll certainly do that but give me a couple of days as I'm not likely to be near the radio for a while..

Vince

On Wed, 14 Oct 2020 at 21:17, Bob <k4cy@...> wrote:
I spent some time investigating this today, and it could be one of many things. Please help me zero in on the problem.

Was it a short note, or an autobiography?
I the problem for this particular QSO only?
Can you add a note to a non 60m band QSO?
Despite the warning message, is the note actually added?
If you recalculate you stats for this logbook, does the have any effect?
Can you log a QSO with a note? If so, can you then delete the note? if so, can you add a note?

Anything you can do to help narrow it down would be appreciated. 73.
On 10/13/2020 10:36 PM Vince Shirley <vince.g0orc@...> wrote:


Hi all I'll try again - Google mail screwed up the image and text - this showld be OK...


Hi all,

I' haven't used the Notes window for a while and everything OK except for this.

If I try and add a note for a selected QSO I get this

"Unable to add notes to selected QSO with 44117.2921990741"  The number varies depending on the QSO selected.

I something broken?

Vince



Re: Notes window

Bob
 

I spent some time investigating this today, and it could be one of many things. Please help me zero in on the problem.

Was it a short note, or an autobiography?
I the problem for this particular QSO only?
Can you add a note to a non 60m band QSO?
Despite the warning message, is the note actually added?
If you recalculate you stats for this logbook, does the have any effect?
Can you log a QSO with a note? If so, can you then delete the note? if so, can you add a note?

Anything you can do to help narrow it down would be appreciated. 73.

On 10/13/2020 10:36 PM Vince Shirley <vince.g0orc@...> wrote:


Hi all I'll try again - Google mail screwed up the image and text - this showld be OK...


Hi all,

I' haven't used the Notes window for a while and everything OK except for this.

If I try and add a note for a selected QSO I get this

"Unable to add notes to selected QSO with 44117.2921990741"  The number varies depending on the QSO selected.

I something broken?

Vince



Re: JCC/JCG Tracking in L32

ja1nlx
 

John

One more picture for you. I do not know why many JCC, JCG in upper right box
in your picture.


73


On 2020/10/14 16:42, ja1nlx via groups.io wrote:

John

Check again step-by-step....

1. Open JCC.csv with NotePad. I see like this.

2. Open secondary admin database maintenance table. Tools/database maintenance/Secondary admin database maintenance.  I see like this.


3. Right click on any QSO in Logbook page window. Click "Edit admin subdivision info"
Select Japan for country. Select JCC for award. I see like this.


If you open JCC.csv with Excel then you may see like this. No leading ZERO.

So If you open JCC.csv with Excel and save it then no leading ZERO in saved JCC.csv.
If you import this saved JCC.CSV then you may miss leading ZERO in Logger32.

73


On 2020/10/14 15:55, John Muzyka via groups.io wrote:
Hi Guys,
I have tracked the JCC/JCG award in L32 for years and have worked well over 1K JCC/JCG a few months ago after working a couple oj JA's with new JCC numbers which my L32 did not recognise I decided to upload the latest JCC/JCG.CSV file.

It went on no problem but after checking my total number of JCC/JCG my worked number was down to below 200?? and when I tried putting in some JCC/JCG numbers say 0101 L32 gave me a message saying that it did not recognise 01. 

I didn't bother with it much then but now I am starting to work JA's and the error message kept on coming up again, so a few weeks I tried to get down to the bottom of this problem, first of all I tried to see if I had a copy of the original JCC/JCG file which had worked for lots of years, no unfortunately I did not keep the original (note to oneself, rename a file before deleting it!!) so because it was a new file I looked at the JCC.SCV that I had download from Aki san JA1NLX and what I found was that the EXCEL file showed the numbers of the prefectures without the leading 0 (zero) in both the first part of the number and the second part of the number so instead of 0101 it looked like it was 11 Also when I worked a station which was already in my log with a JCC number in the full fout figure format if there was a 0 (zero) in the number when I tried to enter it again it would not recognize the number even if I edited the number by right clicking on the call in the log and choosing Edit Admin Subdivision Info 

I spoke to a radio friend of mine who knows a lot more about PC programmes than me and he said that EXCEL files will sometimes depending on their format with automatically take out the 0 (zero) and that I should report this back to the writer of the programme file. So hence this message before messing around with the file myself. Has anyone else had this problem or is it something with my PC? 

I have attached a few screen shots and a copy of the .CSV file 

Cheers
John G4RCG 
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX


Re: JCC/JCG Tracking in L32

ja1nlx
 

John

Check again step-by-step....

1. Open JCC.csv with NotePad. I see like this.

2. Open secondary admin database maintenance table. Tools/database maintenance/Secondary admin database maintenance.  I see like this.


3. Right click on any QSO in Logbook page window. Click "Edit admin subdivision info"
Select Japan for country. Select JCC for award. I see like this.


If you open JCC.csv with Excel then you may see like this. No leading ZERO.

So If you open JCC.csv with Excel and save it then no leading ZERO in saved JCC.csv.
If you import this saved JCC.CSV then you may miss leading ZERO in Logger32.

73


On 2020/10/14 15:55, John Muzyka via groups.io wrote:
Hi Guys,
I have tracked the JCC/JCG award in L32 for years and have worked well over 1K JCC/JCG a few months ago after working a couple oj JA's with new JCC numbers which my L32 did not recognise I decided to upload the latest JCC/JCG.CSV file.

It went on no problem but after checking my total number of JCC/JCG my worked number was down to below 200?? and when I tried putting in some JCC/JCG numbers say 0101 L32 gave me a message saying that it did not recognise 01. 

I didn't bother with it much then but now I am starting to work JA's and the error message kept on coming up again, so a few weeks I tried to get down to the bottom of this problem, first of all I tried to see if I had a copy of the original JCC/JCG file which had worked for lots of years, no unfortunately I did not keep the original (note to oneself, rename a file before deleting it!!) so because it was a new file I looked at the JCC.SCV that I had download from Aki san JA1NLX and what I found was that the EXCEL file showed the numbers of the prefectures without the leading 0 (zero) in both the first part of the number and the second part of the number so instead of 0101 it looked like it was 11 Also when I worked a station which was already in my log with a JCC number in the full fout figure format if there was a 0 (zero) in the number when I tried to enter it again it would not recognize the number even if I edited the number by right clicking on the call in the log and choosing Edit Admin Subdivision Info 

I spoke to a radio friend of mine who knows a lot more about PC programmes than me and he said that EXCEL files will sometimes depending on their format with automatically take out the 0 (zero) and that I should report this back to the writer of the programme file. So hence this message before messing around with the file myself. Has anyone else had this problem or is it something with my PC? 

I have attached a few screen shots and a copy of the .CSV file 

Cheers
John G4RCG 
--
73 de aki
JA1NLX


JCC/JCG Tracking in L32

John Muzyka
 

Hi Guys,
I have tracked the JCC/JCG award in L32 for years and have worked well over 1K JCC/JCG a few months ago after working a couple oj JA's with new JCC numbers which my L32 did not recognise I decided to upload the latest JCC/JCG.CSV file.

It went on no problem but after checking my total number of JCC/JCG my worked number was down to below 200?? and when I tried putting in some JCC/JCG numbers say 0101 L32 gave me a message saying that it did not recognise 01. 

I didn't bother with it much then but now I am starting to work JA's and the error message kept on coming up again, so a few weeks I tried to get down to the bottom of this problem, first of all I tried to see if I had a copy of the original JCC/JCG file which had worked for lots of years, no unfortunately I did not keep the original (note to oneself, rename a file before deleting it!!) so because it was a new file I looked at the JCC.SCV that I had download from Aki san JA1NLX and what I found was that the EXCEL file showed the numbers of the prefectures without the leading 0 (zero) in both the first part of the number and the second part of the number so instead of 0101 it looked like it was 11 Also when I worked a station which was already in my log with a JCC number in the full fout figure format if there was a 0 (zero) in the number when I tried to enter it again it would not recognize the number even if I edited the number by right clicking on the call in the log and choosing Edit Admin Subdivision Info 

I spoke to a radio friend of mine who knows a lot more about PC programmes than me and he said that EXCEL files will sometimes depending on their format with automatically take out the 0 (zero) and that I should report this back to the writer of the programme file. So hence this message before messing around with the file myself. Has anyone else had this problem or is it something with my PC? 

I have attached a few screen shots and a copy of the .CSV file 

Cheers
John G4RCG 


Notes window

Vince Shirley
 

Hi all I'll try again - Google mail screwed up the image and text - this showld be OK...


Hi all,

I' haven't used the Notes window for a while and everything OK except for this.

If I try and add a note for a selected QSO I get this

"Unable to add notes to selected QSO with 44117.2921990741"  The number varies depending on the QSO selected.

I something broken?

Vince



Notes window.

Vince Shirley
 

Hi all,

Not used the notes window for a while and all seems OK, except for this.  If I select a QSO from the Logbook Page and try and enter a note against it I get a message window pop up, with the information:-

I something broken?

Vince G0ORC



"Unable to add notes to selected QSO with 4417.2921990741"

The number varies depending on the QSO selected.


Re: Connecting my Elecraft K3 to Logger32 - still problem

Steve VE3RX
 

As Aki says above, open device manager. Plug in the USB cable and see what port shows up. Unplug the USB to confirm that port then disappears. Plug it back in once you know for sure what the port number is.
Make sure no other application is trying to use that COM port to connect to the K3.

I've seen some computers (like Dell), that reserves a COM port like COM3 for diagnostic uses, and will conflict with other port drivers.


Re: Connecting my Elecraft K3 to Logger32 - still problem

ja1nlx
 

Hello

Try following steps.

1. Unplug ALL usb cables from PC including KUSB cable for K3.

2. Look at device manager. What COM port you see ?

3. Plug ONLY KUSB cable.

4. Look at device manager. Do you see new COM port ?  If so this is COM port for K3.

73

On 2020/10/14 7:09, SM0YHN@... wrote:
Hello,
It is still a problem for me to connect my Elecraft K3 to Logger32 and specially to open a COM-port.

I have configurated my Radio 1 like this:



In the droplist for Com port in radio setup I have to choise between None and Com 3. It is impossible to use another Comport number.

After clicking on Apply, I click on Radio 1 box at the bottom of the screren. It is red and I get the message Radio1:  Com 3  closed. I rightclick and select Open port Radio 1. and I get the message:
The device is not open: Comm port 3.

I do not know which Comport I can use. In device manager I can only see Com 2 and Com 3, but I think that those comports are already reserved by other devices that I have used earlier together with my laptop, (e.g. printer and remote radio control unit for Remoterig). And as it is impossible to change from Com 3 to any other comport in Logger32 setup for radio, I do not know how  to come further, so I hope that the Logger32-support can help me.
Thank you in advance for you assistance.
73 de
SM0YHN/Thorbjörn Odsjö
--
73 de aki
JA1NLX


Connecting my Elecraft K3 to Logger32 - still problem

SM0YHN@...
 

Hello,
It is still a problem for me to connect my Elecraft K3 to Logger32 and specially to open a COM-port.

I have configurated my Radio 1 like this:



In the droplist for Com port in radio setup I have to choise between None and Com 3. It is impossible to use another Comport number.

After clicking on Apply, I click on Radio 1 box at the bottom of the screren. It is red and I get the message Radio1:  Com 3  closed. I rightclick and select Open port Radio 1. and I get the message:
The device is not open: Comm port 3.

I do not know which Comport I can use. In device manager I can only see Com 2 and Com 3, but I think that those comports are already reserved by other devices that I have used earlier together with my laptop, (e.g. printer and remote radio control unit for Remoterig). And as it is impossible to change from Com 3 to any other comport in Logger32 setup for radio, I do not know how  to come further, so I hope that the Logger32-support can help me.
Thank you in advance for you assistance.
73 de
SM0YHN/Thorbjörn Odsjö


Re: Logged DXCC

Bob
 

... then you might want to consider UNchecking this option. SeventyThree(s).


On 10/13/2020 9:47 AM Ian Morrison <imorrison@...> wrote:


They have eliminated the DXCC  field, or so I have been told.


73,

Ian VE3EP


Sent from Mail for Windows 10


From: Bob
Sent: Monday, October 12, 2020 5:02 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logged DXCC


... and if you look at the ADIF file from N1MM, what is in the DXCC field? 73.

On 10/12/2020 4:11 PM Ian Morrison <imorrison@...> wrote:



I uploaded an adi file from N1MM. The DXCC column shows all contact as "Not acceptable for DXCC".
Operator error, maybe> But where?
Logger32 V350.432

Thanks,
Ian
VE3EP




Re: Logged DXCC

Ian Morrison
 

They have eliminated the DXCC  field, or so I have been told.

 

73,

Ian VE3EP

 

Sent from Mail for Windows 10

 

From: Bob
Sent: Monday, October 12, 2020 5:02 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logged DXCC

 

... and if you look at the ADIF file from N1MM, what is in the DXCC field? 73.

On 10/12/2020 4:11 PM Ian Morrison <imorrison@...> wrote:

 

 

I uploaded an adi file from N1MM. The DXCC column shows all contact as "Not acceptable for DXCC".
Operator error, maybe> But where?
Logger32 V350.432

Thanks,
Ian
VE3EP

 


Re: Help needed

Jim Hargrave
 

Jan,

Have you identified a default Profile?

 

Open the L32 help file and select: Commutating with RTTY > Paragraph 6.8.1

Follow the procedure for establishing a Menu and Profile.

 

It should then open with all your settings.

 

Also , set your RTTY keying configuration

 

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jan
Sent: Tuesday, October 13, 2020 3:21 AM
To: hamlogger@groups.io
Subject: [hamlogger] Help needed

 

Hello

Using Logger32 Ver3.50.423

I am struggeling with the setup of MMTTY in Logger.

I am not using SO2R or SO2V

I want to use EXTFSK64 and use COM+TxD(FSK).
So I put these settings in the corresponing Tabs (TX and Misc) of the MMTTY setup.
I click OK and the setup window closes and the small EXTFSK window pops up.
Now I can transmit FSK using MMTTY. Sofar so good.

I used the save current profile settings
I even used save rtty profile to file
But when I Load rtty profile from file the com5 is still there.
BUT when I close the MMTTY engine and reopen it again it does not remember its settings.


MMTTY is installed in D:\mmtty
Logger32 is installed in D:\Logger32

Did I miss something?

73
Jan PA4JJ


 


Help needed

Jan
 

Hello

Using Logger32 Ver3.50.423

I am struggeling with the setup of MMTTY in Logger.

I am not using SO2R or SO2V

I want to use EXTFSK64 and use COM+TxD(FSK).
So I put these settings in the corresponing Tabs (TX and Misc) of the MMTTY setup.
I click OK and the setup window closes and the small EXTFSK window pops up.
Now I can transmit FSK using MMTTY. Sofar so good.

I used the save current profile settings
I even used save rtty profile to file
But when I Load rtty profile from file the com5 is still there.
BUT when I close the MMTTY engine and reopen it again it does not remember its settings.


MMTTY is installed in D:\mmtty
Logger32 is installed in D:\Logger32

Did I miss something?

73
Jan PA4JJ


  


Re: Import

ja1nlx
 

Paul

There are several ways.

a. ignore ONE minute difference.

or

b. use another logging program.

or

c. make new Logbook in Logger32 then import correct logbook adif

or

d. delete all current Logbook files in Logger32 then import correct logbook adif.

73

On 2020/10/13 15:29, Paul F6EXV wrote:
Hi all
I have my L32 log, in which many QSOs come from JTDX logged directly.
For some reason, I have had to import that JTDX log, and MANY QSOs were then duplicate, by a 1 minute difference . I have about 1,000 QSOs in this case.
I do not plan on erasing them 1 by 1...
Is there any procedure to take care of these dupes  ?
If not, I have the correct log under another logging program, that I can export to adif. How can I completely erase the incorrect L32 log, and import that ?

Thanks + 73
Paul F6EXV
--
73 de aki
JA1NLX


Import

Paul F6EXV
 

Hi all
I have my L32 log, in which many QSOs come from JTDX logged directly.
For some reason, I have had to import that JTDX log, and MANY QSOs were then duplicate, by a 1 minute difference . I have about 1,000 QSOs in this case.
I do not plan on erasing them 1 by 1...
Is there any procedure to take care of these dupes  ?
If not, I have the correct log under another logging program, that I can export to adif. How can I completely erase the incorrect L32 log, and import that ?

Thanks + 73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


Re: Logged DXCC

Bob
 

... and if you look at the ADIF file from N1MM, what is in the DXCC field? 73.

On 10/12/2020 4:11 PM Ian Morrison <imorrison@...> wrote:


I uploaded an adi file from N1MM. The DXCC column shows all contact as "Not acceptable for DXCC".
Operator error, maybe> But where?
Logger32 V350.432

Thanks,
Ian
VE3EP


Logged DXCC

Ian Morrison
 

I uploaded an adi file from N1MM. The DXCC column shows all contact as "Not acceptable for DXCC".
Operator error, maybe> But where?
Logger32 V350.432

Thanks,
Ian
VE3EP


Re: Unable to update Logger32 from 3.50.347 to any newer version

Bob
 

.. or, if you're still on ver 3.50, try a URL of http://www1.Logger32.net/autoupdates/updateList 3.50.txt

SeventyThree(s).

On 10/09/2020 10:03 AM Bob <k4cy@...> wrote:


You said: I wish I could see what gets returned to Logger32 as the latest version in ...

In your browser put this: http://www1.Logger32.net/autoupdates/updateList 4.0.txt   The correct response is: 4.0.165


SeventyThree(s).

On 10/08/2020 8:59 PM Joe Deres <af5hz.joe@...> wrote:


Joe

Try this.

Look for Logger32.ini in Logger32 folder.

Rename Logger32.ini to Logger32.old.

Run Logger32 and try "look for update"

73
Thanks.

I tried your rename suggestion several times throughout the day. Same result: "..no new updates".

The first time through it did remind me of a "same but different" problem I'm having. The Clublog update fails too, but for what looks like a totally different reason. Without the gory details it looks like the http request goes through the Microsoft contol "msinet.ocx". This sends the server a user agent string "Microsoft URL Control ...". Numerous sources on the web say that this is classified as a "bot" and is blocked by a number of internet service providers. Indeed buried in my packet log is an error message referring to a Cloudfare block. So the Logger32 program gets the error packet returned as a .gz file that Logger32 tries to decode. I have seen other references on this forum about Cloudfare blocks that seem to come and go. FYI: I can run the clublog.org URL and token through Firefox and I get the correct file returned. So this is an annoyance, but I have a crude work-around.

I don't THINK that my main Logger32 version update problem is related to this. The path to www1.logger32.net doesn't appear to have any Cloudfare related servers.

I got brave (or stupid - but no harm done) and tried using the latest lgr32full3500.zip full install file to install a second version of Logger32 in a brand new clean directory. The new "clean" base version also behaved exactly the same: no new updates found.

I wish I could see what gets returned to Logger32 as the latest version in case there is some other packet "corruption", but https makes that difficult. It would be nice to know if Logger32 gets bad version information from the net, or if it gets it correctly and then doesn't do the right thing with it. I'd like to rule out (or rule in) some internet-related issue.

So open to other ideas. I'll also look at the people who have problems doing a new install on Windows 10 to see if anything stands out that I missed before.

73

2741 - 2760 of 84036