Date   

Re: Deleting dupes

Richard M. Gillingham
 

WOW!!

There a lot of interesting files here.  DUPE_Selector works Gangbusters!

Many thanks for pointing this out Jose.

73
Gil,W1RG

On Wednesday, March 3, 2021, 02:55:44 PM EST, Jose EA7BJ <ea7bj@...> wrote:


You can use the SP7DQR application called DUPE_Selector on its page

http://sp7dqr.pl/en/converters.php


73 EA7BJ Jose.


SteppIR VSC + FT897D

Paul - W1PR
 

Has anybody in the group succeeded in using the FT897 with Logger32 (which is easily done with Yaesu's CT62 cable) and L32's Virtual SteppIR Control?

TNX de Pail W1PR


Re: Cherry Picking Event *9 question

Vlad M
 

Bob,
Thank you for the reply.
I completely understand the fact of stopping the cherry picker upon the CQ station answering someone else.
Unfortunately, this is different. I took some time analyzing events numbered from *1 to *13, but wasn't sure on whos end this *9 is originated - my or the other station.
The only speculation I have (I could be wrong, though). If the station had previously unsuccessful incomplete QSO then gave up on it and went CQ-ing, maybe the previous QSO is still somewhere in a buffer "waiting" to be completed?
Like I said, it is just a pure speculation, unless it would make some sense to you.
Thank you very much again for your cooperation
--
73 de Vlad, NØSTL


Re: Cherry Picking Event *9 question

Bob
 

The idea is that your call to KP4MAQ was not answered, but CT1GFK called. So, the cherry-picker stopped calling KP4MAQ and should have replied to CT1GFK. Apparently it didn't call CT1GFK. I don't know why, I will investigate. SeventyThree(s).
 

On 03/03/2021 3:26 PM Vlad M <n0stl@...> wrote:
 
 
I apologize in advance if this question has already been answered or addressed, I thoroughly searched the group messages, but couldn't find the answer.
Observing the logic and behavior of the cherry picker with JTDX, I noticed that quite often after initiating a call of the "CQing" station, the cherry pickers "gives up" after the first call attempt.
There is a number of "legitimate" reasons why the cherry picker stops calling the station (e.g. the station has answered someone else or 3 times calling were exceeded).
However this one I cannot understand. I ran the event monitor to capture this:

I have been trying to to figure out why, but alas...
Any help would be appreciated.
I am running the latest version of Logger32 (4.xx) and latest stable JTDX.
--
73 de Vlad, NØSTL


Re: Country database exceptions from Club log - update error

Kenneth Hansen
 

Works fine on my WINDOWS 7 machine 

On Wed, Mar 3, 2021 at 2:21 PM Chris.9A2X <chris.9a2x@...> wrote:
Thanks for responses.
This info. could possibly be useful for some Win7 users.
My Win7 instance is running on linux host and is totaly unpatched and without new features enabled and old/obsolete disabled.
Wireshark gave me idea where to look.

39      41.680110       95.168.206.70   192.168.10.5    SSLv3   73      Alert (Level: Fatal, Description: Handshake Failure)
54      14.629615       5.153.81.176    192.168.10.5    SSLv3   73      Alert (Level: Fatal, Description: Handshake Failure)

Internet options -> Advanced -> ticking the box 'Use TLS v1.2' solved the problem with Clublog updates.

When I red that v4.0.245 is out I tried to make update:

8       2.615927        192.168.10.5    95.168.206.70   HTTP    141     GET /autoupdates/updateList%204.0.txt HTTP/1.1
14      2.671097        192.168.10.5    95.168.206.70   TLSv1.2 238     Client Hello
16      2.698141        95.168.206.70   192.168.10.5    TLSv1.2 73      Alert (Level: Fatal, Description: Handshake Failure)

I'm giving up now with win7.

73 chris





--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC


Cherry Picking Event *9 question

Vlad M
 

I apologize in advance if this question has already been answered or addressed, I thoroughly searched the group messages, but couldn't find the answer.
Observing the logic and behavior of the cherry picker with JTDX, I noticed that quite often after initiating a call of the "CQing" station, the cherry pickers "gives up" after the first call attempt.
There is a number of "legitimate" reasons why the cherry picker stops calling the station (e.g. the station has answered someone else or 3 times calling were exceeded).
However this one I cannot understand. I ran the event monitor to capture this:

I have been trying to to figure out why, but alas...
Any help would be appreciated.
I am running the latest version of Logger32 (4.xx) and latest stable JTDX.
--
73 de Vlad, NØSTL


Re: Deleting dupes

Jose EA7BJ
 

You can use the SP7DQR application called DUPE_Selector on its page

http://sp7dqr.pl/en/converters.php


73 EA7BJ Jose.


Re: Country database exceptions from Club log - update error

Chris.9A2X
 

Thanks for responses.
This info. could possibly be useful for some Win7 users.
My Win7 instance is running on linux host and is totaly unpatched and without new features enabled and old/obsolete disabled.
Wireshark gave me idea where to look.

39 41.680110 95.168.206.70 192.168.10.5 SSLv3 73 Alert (Level: Fatal, Description: Handshake Failure)
54 14.629615 5.153.81.176 192.168.10.5 SSLv3 73 Alert (Level: Fatal, Description: Handshake Failure)

Internet options -> Advanced -> ticking the box 'Use TLS v1.2' solved the problem with Clublog updates.

When I red that v4.0.245 is out I tried to make update:

8 2.615927 192.168.10.5 95.168.206.70 HTTP 141 GET /autoupdates/updateList%204.0.txt HTTP/1.1
14 2.671097 192.168.10.5 95.168.206.70 TLSv1.2 238 Client Hello
16 2.698141 95.168.206.70 192.168.10.5 TLSv1.2 73 Alert (Level: Fatal, Description: Handshake Failure)

I'm giving up now with win7.

73 chris


Re: Deleting dupes

Rick EA4M
 

Ok.... I'll test it


On Wed, Mar 3, 2021, 15:25 Vilhjalmur Sigurjonsson <vilhj@...> wrote:

Rick,

If they are real duplicates the easiest way would be to export the logfile to ADIF, make a new log and import the ADIF fil. Then you would get a clean log with the reported dupes in the BAD.ADI file.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick EA4M via groups.io
Sent: miðvikudagur, 3. mars 2021 13:30
To: hamlogger@groups.io
Subject: [hamlogger] Deleting dupes

 

Hello is there any way to delete dupes more than one by one? 

 

I have a bunch of them....

 

Thanks

 

73'de Rick EA4M


Re: Deleting dupes

Vilhjalmur Sigurjonsson
 

Rick,

If they are real duplicates the easiest way would be to export the logfile to ADIF, make a new log and import the ADIF fil. Then you would get a clean log with the reported dupes in the BAD.ADI file.

73 Villi
TF3VS

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick EA4M via groups.io
Sent: miðvikudagur, 3. mars 2021 13:30
To: hamlogger@groups.io
Subject: [hamlogger] Deleting dupes

 

Hello is there any way to delete dupes more than one by one? 

 

I have a bunch of them....

 

Thanks

 

73'de Rick EA4M


Deleting dupes

Rick EA4M
 

Hello is there any way to delete dupes more than one by one? 

I have a bunch of them....

Thanks

73'de Rick EA4M


Re: Finding and flagging unconfirmed QSOs

Dean W8ZF
 

Pete,
Again, thanks!
73!
Dean


Re: Finding and flagging unconfirmed QSOs

n5kd
 

That’s amazing Bob.

 

9M6SSL is the granted one for sure.

 

I’m going to spend the next six months trying to figure out how you did that.

 

73’ Pete, N5KD.

 

From: Bob
Sent: Tuesday, March 2, 2021 10:36 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Finding and flagging unconfirmed QSOs

 

Pete, I suspect you will find the 'granted' QSO in the generic QSOs window will be appropriately highlighted (if you have things setup to do so). Or, you might even be able to sort the list of QSOs by the appropriate column. The picture shows an extract from your logbook (DXCC award in the background). I clicked on the Spratley Island 20m G. The Generic QSO window shows two Spratley Island QSOs. Guess which one is granted?

 

Additionally, the awards table can be exported to personalized spreadsheet templates to massage the presentation to suit ones taste (or in simple .CSV format for off-line manipulation.

 

SeventyThree(s).

 

On 03/02/2021 5:12 PM n5kd <n5kd@...> wrote:

 

 

Hi Dean.

 

If you have a DXCC band point Granted, then the Logger32 award screen will list all QSOs on that band country.
So if you wanted to know which specific QSO was the Granted one, it is a lot harder.

 

Maybe Logger32 should only display the actual granted QSO when you click on a G in the award screens. Maybe that ONE QSO could be in a different color to the others that are confirmed on that band point, but not blessed by the ARRL.

 

Maybe Bob would consider a feature request for that. I think it’s a great idea.

 

Band points that are only confirmed show as I would expect. You can easily choose which one you want to submit.

 

Glad you made backups. I’m 100% about backups.

 

If you need any more pointers, please ask.    Good DX.

 

73’ Pete, N5KD.

 

From: dwfred@...
Sent: Tuesday, March 2, 2021 8:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Finding and flagging unconfirmed QSOs

 

Thanks, Pete!
Yes, I'm using v4.
I'll try this out.  I have tried something similar but could only get a list of the COUNTRIES that needed confirmation, not the QSOs that would help me pick out from my alphabetized cards.  Also, what I did not give results differentiated by mode on each band.  I have already synchronized ClubLog to LotW.  Then I synchronized L32 to LotR.  Should I expect different results if sync'ing L32 to ClubLog, rather than to LotW?
I hope I didn't mess up.  At least I made backups!
73,
Dean W8ZF

 

 

 

Virus-free. www.avg.com

 


Re: Finding and flagging unconfirmed QSOs

Bob
 

Pete, I suspect you will find the 'granted' QSO in the generic QSOs window will be appropriately highlighted (if you have things setup to do so). Or, you might even be able to sort the list of QSOs by the appropriate column. The picture shows an extract from your logbook (DXCC award in the background). I clicked on the Spratley Island 20m G. The Generic QSO window shows two Spratley Island QSOs. Guess which one is granted?
 
Additionally, the awards table can be exported to personalized spreadsheet templates to massage the presentation to suit ones taste (or in simple .CSV format for off-line manipulation.
 
SeventyThree(s).
 

On 03/02/2021 5:12 PM n5kd <n5kd@...> wrote:
 
 

Hi Dean.

 

If you have a DXCC band point Granted, then the Logger32 award screen will list all QSOs on that band country.
So if you wanted to know which specific QSO was the Granted one, it is a lot harder.

 

Maybe Logger32 should only display the actual granted QSO when you click on a G in the award screens. Maybe that ONE QSO could be in a different color to the others that are confirmed on that band point, but not blessed by the ARRL.

 

Maybe Bob would consider a feature request for that. I think it’s a great idea.

 

Band points that are only confirmed show as I would expect. You can easily choose which one you want to submit.

 

Glad you made backups. I’m 100% about backups.

 

If you need any more pointers, please ask.    Good DX.

 

73’ Pete, N5KD.

 

From: dwfred@...
Sent: Tuesday, March 2, 2021 8:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Finding and flagging unconfirmed QSOs

 

Thanks, Pete!
Yes, I'm using v4.
I'll try this out.  I have tried something similar but could only get a list of the COUNTRIES that needed confirmation, not the QSOs that would help me pick out from my alphabetized cards.  Also, what I did not give results differentiated by mode on each band.  I have already synchronized ClubLog to LotW.  Then I synchronized L32 to LotR.  Should I expect different results if sync'ing L32 to ClubLog, rather than to LotW?
I hope I didn't mess up.  At least I made backups!
73,
Dean W8ZF

 

 


Virus-free. www.avg.com


Re: Finding and flagging unconfirmed QSOs

n5kd
 

Hi Dean.

 

If you have a DXCC band point Granted, then the Logger32 award screen will list all QSOs on that band country.
So if you wanted to know which specific QSO was the Granted one, it is a lot harder.

 

Maybe Logger32 should only display the actual granted QSO when you click on a G in the award screens. Maybe that ONE QSO could be in a different color to the others that are confirmed on that band point, but not blessed by the ARRL.

 

Maybe Bob would consider a feature request for that. I think it’s a great idea.

 

Band points that are only confirmed show as I would expect. You can easily choose which one you want to submit.

 

Glad you made backups. I’m 100% about backups.

 

If you need any more pointers, please ask.    Good DX.

 

73’ Pete, N5KD.

 

From: dwfred@...
Sent: Tuesday, March 2, 2021 8:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Finding and flagging unconfirmed QSOs

 

Thanks, Pete!
Yes, I'm using v4.
I'll try this out.  I have tried something similar but could only get a list of the COUNTRIES that needed confirmation, not the QSOs that would help me pick out from my alphabetized cards.  Also, what I did not give results differentiated by mode on each band.  I have already synchronized ClubLog to LotW.  Then I synchronized L32 to LotR.  Should I expect different results if sync'ing L32 to ClubLog, rather than to LotW?
I hope I didn't mess up.  At least I made backups!
73,
Dean W8ZF

 


Virus-free. www.avg.com


Re: Finding and flagging unconfirmed QSOs

Dean W8ZF
 

Thanks, Pete!
Yes, I'm using v4.
I'll try this out.  I have tried something similar but could only get a list of the COUNTRIES that needed confirmation, not the QSOs that would help me pick out from my alphabetized cards.  Also, what I did not give results differentiated by mode on each band.  I have already synchronized ClubLog to LotW.  Then I synchronized L32 to LotR.  Should I expect different results if sync'ing L32 to ClubLog, rather than to LotW?
I hope I didn't mess up.  At least I made backups!
73,
Dean W8ZF


Re: Finding and flagging unconfirmed QSOs

n5kd
 

Hi Dean……

The award screens of Logger32 have three conditions it it track for each band slot. These are
W - worked but no confirmation
C - confirmed by either pater QSL or via LoTW
G - granted - clicking on the band slot in the award table with give you the details of the granted (awarded) QSO.

So, assuming you have just done a LoTW submission to DXCC, then your LoTW web page should have a lot of granted QSOs from LoTW.

The easiest way to do this, is to go to ClubLog and do a “LOTW SYNC” - it’s the third from the bottom of the options on the left hand side.

Once ClubLog agrees with your LoTW account, you can go to the next step.

In Logger32, Select File | Synchronize LoTW (From ClubLog), and do that.

Then L32 awards table should match LoTW.

In that awards table anything confirmed (not Granted) must, by definition, be a QSL card and needs submitting.

It’s not an automatic printout, but will give you all the information you are looking for.

73’ Pete, N5KD.

P.S.  I presume you are using L32 V4.




On Mar 2, 2021, at 18:37, dwfred@... wrote:

I have been trying out logging programs after retiring.  Since I don't  have much of a station in the near future, I've decided to work on my awards.  While I have confirmed QSOs with over 300 countries, I have never submitted for an award (other than 5BDXCC).  To get started, I renewed my ARRL membership and joined LOTW & ClubLog.  I uploaded my log to LotW and I have credits for some 250 countries or so.  Many of the credits I need aren't available through LotW, so I need to submit paper QSLs.  My previous logger (DXbase) had the ability to generate reports which would show which cards I needed to send in for confirmation.  The DXbase logic would allow me to generate the QSL "pick" list using any combination of worked/confirmed/band/mode.  I cannot find this function in Logger32.  You can get close in DxLab with SQL queries, but this process is not simply a filter.  It is a filter on the result of selection logic, so it doesn't seem to be a convenient function in DxLab either.

Does anyone know of a way to accomplish this essential DXing task (picking out the cards you need to submit for confirmation) with L32?  I don't want a summary of the worked/confirmed status.  I want to take that aggregated worked/confirm data and go find the QSLs that I have marked as "QSL received" in my log, for those countries that remain unconfirmed through online log submissions.

Thanks for any ideas!
73,
Dean W8ZF


Finding and flagging unconfirmed QSOs

Dean W8ZF
 

I have been trying out logging programs after retiring.  Since I don't  have much of a station in the near future, I've decided to work on my awards.  While I have confirmed QSOs with over 300 countries, I have never submitted for an award (other than 5BDXCC).  To get started, I renewed my ARRL membership and joined LOTW & ClubLog.  I uploaded my log to LotW and I have credits for some 250 countries or so.  Many of the credits I need aren't available through LotW, so I need to submit paper QSLs.  My previous logger (DXbase) had the ability to generate reports which would show which cards I needed to send in for confirmation.  The DXbase logic would allow me to generate the QSL "pick" list using any combination of worked/confirmed/band/mode.  I cannot find this function in Logger32.  You can get close in DxLab with SQL queries, but this process is not simply a filter.  It is a filter on the result of selection logic, so it doesn't seem to be a convenient function in DxLab either.

Does anyone know of a way to accomplish this essential DXing task (picking out the cards you need to submit for confirmation) with L32?  I don't want a summary of the worked/confirmed status.  I want to take that aggregated worked/confirm data and go find the QSLs that I have marked as "QSL received" in my log, for those countries that remain unconfirmed through online log submissions.

Thanks for any ideas!
73,
Dean W8ZF


Re: Power Setting in an IC 756 Pro11

Ian Morrison
 

You folks are far too clever.

Thanks Dave et al.

Adding 01 brings the power up to 80 watts.

 

73,

Ian

 

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: Tuesday, March 2, 2021 12:46 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Power Setting in an IC 756 Pro11

 

Yes if i remember right its 0 to 250 but in 2x2 so 01 25 will be 125.

Dave N8DC

On 03/02/2021 12:42 PM n5kd <n5kd@...> wrote:

 

 

Why don’t you try changing the 00 to 01 and experiment.

 

I think that’s the next higher power denomination.

 

73’ Pete, N5KD.



On Mar 2, 2021, at 11:29, Ian Morrison <imorrison@...> wrote:

Nice try guys, but no go.

 

Here are the results I get.

$hexcommand FE FE 64 E0 14 0A 00 50 FD$ set the output to 10 w

$hexcommand FE FE 64 E0 14 0A 00 99 FD$ sets the output to 25 w

Any number larger than 99 and the command id ignored. Even if I try FF for 255 as the book proclaims as full power.

Hmmmm………………

Strange

Ian

 

 

 

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: Tuesday, March 2, 2021 12:03 PM
To: hamlogger@groups.io; n5kd
Subject: Re: [hamlogger] Power Setting in an IC 756 Pro11

 

Oops. I missed the 0A was looking at 02 and yup the numerals have to be 00 62 or whatever you want for power .

Dave N8DC

On 03/02/2021 11:37 AM n5kd <n5kd@...> wrote:

 

 

On a IC7300 this sets 24w

$hexcommand FE FE 94 E0 14 0A 00 62 FD$

 

And this sets 95w

$hexcommand FE FE 94 E0 14 0A 02 44 FD$ 95 WATTS

 

The 94 is the ID for a 7300. Change that to 64 for your rig.

 

73’ Pete, N5KD.

 

<7BF7944E94F94507922E11A93B04325C[29095963].png>

 

 

From: Bob
Sent: Tuesday, March 2, 2021 4:01 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Power Setting in an IC 756 Pro11

 

Did I really say there's no 9 in hex? I don't know the correct command structure for your Icom, but the 99 you've entered is 153 decimal which is 0.6 of full output (or something like that). SeventyThree(s).

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

 

 

There is no 9 in hex. 0 to 255 decimal = 00 to FF in hex maybe?  So half power is 80 hex (or something like that). SeventyThree(s).

On 03/02/2021 9:58 AM Ian Morrison <imorrison@...> wrote:

 

 

Hi all,

Does any know why using the following command in the RCP to set the power doesn’t work?

$HEXCOMMAND FE FE 64 E0 14 0A 99  FD$

Entering and 3 digit number causes the command not to work, 2 digit do change the power setting

The manual says “ [RF POWER] setting (0=mini, to 255=max)

 

Thanks, Ian

VE3EP

 

Sent from Mail for Windows 10

 

From: Ian Morrison
Sent: Tuesday, March 2, 2021 9:25 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Suggestion: Synchronize Radio Clock

 

I’m confused. Why is this a logger problem? I have an IC PRO11. I just noticed the clock on the display. It  tracks with my WWV clock, no connection. I

Am I missing something here?

 

73,

VE3EP

 

Sent from Mail for Windows 10

 

From: Fabio IZ8MBW via groups.io
Sent: Monday, March 1, 2021 11:07 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Suggestion: Synchronize Radio Clock

 

Dave, modern Radio can, for example, do RTTY "inside" the radio and log the QSO "inside" the radio.

Have the right time in the radio clock is not only to know the current time.

We have PC, mobile phone and why not, also a clock on the wall.

 

 

73s

Fabio, IZ8MBW

 

 

 

On Monday, March 1, 2021, 04:38:51 PM GMT+1, Dave Colliau <n8dc-8@...> wrote:

 

 

Never could figure out the actual need for a clock in the rig. If your using Logger and you have a time sync program and your using the floating clock in logger why would you even worry about the clock in the 7300. The clock in the rig does nothing !.  I see these posts all the time. People are having a fit that the new 101's dont have a clock . Big deal. My logging program ( logger 32 ) takes care of this for me . I also have a clock on the wall and my cell phone is pretty damn close to the right time all day long .

 

73

Dave N8DC

On 03/01/2021 10:19 AM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:

 

 

In fact, I have executed it also on my Windows PC and works.

 

73s

Fabio, IZ8MBW

 

 

 

On Monday, March 1, 2021, 03:11:17 PM GMT+1, Per <pmolund@...> wrote:

 

 

This script is not Linux specific, it is written in Python which is also supported under Windows. You just have to change the script to use Windows serial port, ex. COM1: instead of /dev/ttyUSB0.

73 de LA9XKA - Per

On 01.03.2021 13:41, Fabio IZ8MBW via groups.io wrote:

I also have an Icom IC-7300 and it will nice if Logger32 can update the clock on the radio via CAT (after updating the PC clock via NTP).

On the Web I found this, but it's for Linux:  loughkb/IC-7300-time-sync

 

 

 

loughkb/IC-7300-time-sync

Python3 script to sync the radio's clock with your computer via CAT commands - loughkb/IC-7300-time-sync

 

 

 

 

73s

Fabio, IZ8MBW

 

 

 

 

Virusfri. www.avg.com

 

 

 

 

 

 

 

 

<6F57852DBF1A4B08BF4CA3D7C00097E3.png>

<7BF7944E94F94507922E11A93B04325C[29095963].png>

 


Re: Power Setting in an IC 756 Pro11

Steve VE3RX
 

A single set of digits is NOT an option for power settings. While it may work by fluke in some cases, the 14 0A command must have 2 "sets" of digits after the command when setting power level.
So, 02 55 is full power, 01 27 will be 50%, 00 64 will be about 25%, 0032 will be about 12%, give or take some.
A command FE FE 64 E0 14 0A 01 99 FD is a valid command, saying set power to 199/255 of full scale. Values are read as "text" values, what you see is what you get.

73
Steve

1 - 20 of 82960