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

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

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

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

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

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

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>