Cherry-picking during Hound (DXPedition) operation


Fabio IZ8MBW
 

Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off

16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off

16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off

16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off

16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off



See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image


Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW


ja1nlx
 

Fabio

Why Why you use cherry-picking for F/H ?
Just turn off cherry-picking and keep calling him.
my 2 cents...

73 de aki
JA1NLX

------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "Logger32 Groups Io" <hamlogger@groups.io>
Date: 2021/04/07 1:31:41
Subject [hamlogger] Cherry-picking during Hound (DXPedition) operation

Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off

16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off

16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off

16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off

16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off



See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image">


Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW


Dave Colliau
 

I wanted to ask the same thing but I didnt. F/H no cherry picking on a DX station .
Dave N8DC
 
 

On 04/06/2021 5:43 PM ja1nlx <ayoshida0205@...> wrote:
 
 
Fabio
 
Why Why you use cherry-picking for F/H ?
Just turn off cherry-picking and keep calling him.
my 2 cents...
 
73 de aki
JA1NLX
 
------ Original message ------
From: "Fabio IZ8MBW via groups.io" < iz8mbw@...>
To: "Logger32 Groups Io" < hamlogger@groups.io>
Date: 2021/04/07 1:31:41
Subject [hamlogger] Cherry-picking during Hound (DXPedition) operation
 
Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during  Hound operation.
I'm testing/using  Cherry-picking during C92RU DXPedition.
 
As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same  stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.
 
 
Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).
 
Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded  RR73 message?
 
 
This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...
 
16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off
 
16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off
 
16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off
 
16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off
 
16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off
 
 
 
See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image">

 
Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let  Cherry-picking to transmit at every RR73 decoded?
 
Thanks.
 
73s
Fabio, IZ8MBW
 

 

 


Tom Wylie
 

Why would you use cherry picking in f/h mode????   I don't think it is designed to work that way....

Gm4fdm



On 6 April 2021, at 17:31, "Fabio IZ8MBW via groups.io" <iz8mbw@...> wrote:


Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off

16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off

16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off

16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off

16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off



See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:



Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW


Fabio IZ8MBW
 

Hi Aki, hi all.
Sorry but I do not understand your wonder about my comments about Cherry-picking during Hound (DXPedition) operations and I have not found anything in the manual that specifies that Cherry-picking does not work for Hound operations.

I personally use Cherry-picking for New Ones and in that case was a New One and I expected that Cherry-picking will works also in F/H operations.

Yes, I can call the DX Station anyway as we can do everyday directly from JTDX but it was/will nice if the Cherry-picking works also for F/H operations.
I cannot understand why the Logger32 Cherry-picking function cannot works also in F/H operations: does Logger32 receive the "RR73" messages? Yes, ok, go ahead to transmit.

Also because, in Cherry-picking mode, Logger32 will go to call the highlighted DX Station when it receive the "RR73" and will go to call the station if/when decoded.
So Cherry-picking will stop to call if it's not more decoded the DX Station (for example for very low signal) and will call again the DX Station when it is again decoded. And THIS IS FANTASTIC!
Instead calling the DX Station directly from JTDX this "concept" died because JTDX will go always to call until the Watch Dog goes in timeout (settings into JTDX). So can happens that JTDX calls also if the DX Station is not more decoded....

Anyway personally I can only see advantage to have the Logger32 Cherry-picking function working also during F/H operations.

Thanks.


73s
Fabio, IZ8MBW



On Tuesday, April 6, 2021, 11:43:20 PM GMT+2, ja1nlx <ayoshida0205@...> wrote:


Fabio

Why Why you use cherry-picking for F/H ?
Just turn off cherry-picking and keep calling him.
my 2 cents...

73 de aki
JA1NLX

------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "Logger32 Groups Io" <hamlogger@groups.io>
Date: 2021/04/07 1:31:41
Subject [hamlogger] Cherry-picking during Hound (DXPedition) operation

Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off

16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off

16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off

16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off

16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off



See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image">


Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW


Jim Cox
 

I don’t think cherry picking was ever intended to work in F/H mode.  Personally I see no use for it in F/H operations.   Jim K4JAF
 

From: Fabio IZ8MBW via groups.io
Sent: Wednesday, April 7, 2021 6:13 AM
To: hamlogger
Subject: Re: [hamlogger] Cherry-picking during Hound (DXPedition) operation
 
Hi Aki, hi all.
Sorry but I do not understand your wonder about my comments about Cherry-picking during Hound (DXPedition) operations and I have not found anything in the manual that specifies that Cherry-picking does not work for Hound operations.
 
I personally use Cherry-picking for New Ones and in that case was a New One and I expected that Cherry-picking will works also in F/H operations.
 
Yes, I can call the DX Station anyway as we can do everyday directly from JTDX but it was/will nice if the Cherry-picking works also for F/H operations.
I cannot understand why the Logger32 Cherry-picking function cannot works also in F/H operations: does Logger32 receive the "RR73" messages? Yes, ok, go ahead to transmit.
 
Also because, in Cherry-picking mode, Logger32 will go to call the highlighted DX Station when it receive the "RR73" and will go to call the station if/when decoded.
So Cherry-picking will stop to call if it's not more decoded the DX Station (for example for very low signal) and will call again the DX Station when it is again decoded. And THIS IS FANTASTIC!
Instead calling the DX Station directly from JTDX this "concept" died because JTDX will go always to call until the Watch Dog goes in timeout (settings into JTDX). So can happens that JTDX calls also if the DX Station is not more decoded....
 
Anyway personally I can only see advantage to have the Logger32 Cherry-picking function working also during F/H operations.
 
Thanks.
 
 
73s
Fabio, IZ8MBW
 
 
 
On Tuesday, April 6, 2021, 11:43:20 PM GMT+2, ja1nlx <ayoshida0205@...> wrote:
 
 
Fabio
 
Why Why you use cherry-picking for F/H ?
Just turn off cherry-picking and keep calling him.
my 2 cents...
 
73 de aki
JA1NLX
 
------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "Logger32 Groups Io" <hamlogger@groups.io>
Date: 2021/04/07 1:31:41
Subject [hamlogger] Cherry-picking during Hound (DXPedition) operation
 
Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off
 
16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off
 
16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off
 
16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off
 
16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off
 
 
 
See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image">

 
Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW
 


ja1nlx
 

Fabio

Current cherry-picking does not support what you want. You should ask this to the author of Logger32.

73 de aki
JA1NLX

------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "hamlogger" <hamlogger@groups.io>
Date: 2021/04/07 20:13:56
Subject Re: [hamlogger] Cherry-picking during Hound (DXPedition) operation

Hi Aki, hi all.
Sorry but I do not understand your wonder about my comments about Cherry-picking during Hound (DXPedition) operations and I have not found anything in the manual that specifies that Cherry-picking does not work for Hound operations.

I personally use Cherry-picking for New Ones and in that case was a New One and I expected that Cherry-picking will works also in F/H operations.

Yes, I can call the DX Station anyway as we can do everyday directly from JTDX but it was/will nice if the Cherry-picking works also for F/H operations.
I cannot understand why the Logger32 Cherry-picking function cannot works also in F/H operations: does Logger32 receive the "RR73" messages? Yes, ok, go ahead to transmit.

Also because, in Cherry-picking mode, Logger32 will go to call the highlighted DX Station when it receive the "RR73" and will go to call the station if/when decoded.
So Cherry-picking will stop to call if it's not more decoded the DX Station (for example for very low signal) and will call again the DX Station when it is again decoded. And THIS IS FANTASTIC!
Instead calling the DX Station directly from JTDX this "concept" died because JTDX will go always to call until the Watch Dog goes in timeout (settings into JTDX). So can happens that JTDX calls also if the DX Station is not more decoded....

Anyway personally I can only see advantage to have the Logger32 Cherry-picking function working also during F/H operations.

Thanks.


73s
Fabio, IZ8MBW



On Tuesday, April 6, 2021, 11:43:20 PM GMT+2, ja1nlx <ayoshida0205@...> wrote:


Fabio

Why Why you use cherry-picking for F/H ?
Just turn off cherry-picking and keep calling him.
my 2 cents...

73 de aki
JA1NLX

------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "Logger32 Groups Io" <hamlogger@groups.io>
Date: 2021/04/07 1:31:41
Subject [hamlogger] Cherry-picking during Hound (DXPedition) operation

Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off

16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off

16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off

16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off

16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off



See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image">">


Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW


Fabio IZ8MBW
 

Yes, I have understood that, also using it.
I just write how I'd like it to be.


73s
Fabio, IZ8MBW



On Wednesday, April 7, 2021, 02:27:56 PM GMT+2, ja1nlx <ayoshida0205@...> wrote:


Fabio

Current cherry-picking does not support what you want. You should ask this to the author of Logger32.

73 de aki
JA1NLX

------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "hamlogger" <hamlogger@groups.io>
Date: 2021/04/07 20:13:56
Subject Re: [hamlogger] Cherry-picking during Hound (DXPedition) operation

Hi Aki, hi all.
Sorry but I do not understand your wonder about my comments about Cherry-picking during Hound (DXPedition) operations and I have not found anything in the manual that specifies that Cherry-picking does not work for Hound operations.

I personally use Cherry-picking for New Ones and in that case was a New One and I expected that Cherry-picking will works also in F/H operations.

Yes, I can call the DX Station anyway as we can do everyday directly from JTDX but it was/will nice if the Cherry-picking works also for F/H operations.
I cannot understand why the Logger32 Cherry-picking function cannot works also in F/H operations: does Logger32 receive the "RR73" messages? Yes, ok, go ahead to transmit.

Also because, in Cherry-picking mode, Logger32 will go to call the highlighted DX Station when it receive the "RR73" and will go to call the station if/when decoded.
So Cherry-picking will stop to call if it's not more decoded the DX Station (for example for very low signal) and will call again the DX Station when it is again decoded. And THIS IS FANTASTIC!
Instead calling the DX Station directly from JTDX this "concept" died because JTDX will go always to call until the Watch Dog goes in timeout (settings into JTDX). So can happens that JTDX calls also if the DX Station is not more decoded....

Anyway personally I can only see advantage to have the Logger32 Cherry-picking function working also during F/H operations.

Thanks.


73s
Fabio, IZ8MBW



On Tuesday, April 6, 2021, 11:43:20 PM GMT+2, ja1nlx <ayoshida0205@...> wrote:


Fabio

Why Why you use cherry-picking for F/H ?
Just turn off cherry-picking and keep calling him.
my 2 cents...

73 de aki
JA1NLX

------ Original message ------
From: "Fabio IZ8MBW via groups.io" <iz8mbw@...>
To: "Logger32 Groups Io" <hamlogger@groups.io>
Date: 2021/04/07 1:31:41
Subject [hamlogger] Cherry-picking during Hound (DXPedition) operation

Hi all.
Sorry but made on my experience the Cherry-picking function does not work well during Hound operation.
I'm testing/using Cherry-picking during C92RU DXPedition.

As we know during Fox / Hound operation the DX Station send multiple stream (multiple messages) so the DX Station is able to send the report to STATION #1 and send RR73 to STATION #2 in the same stream transmission.
So, in this case, probably is the case to call the DX Station every transmission cycle.


Well, Logger32 received dozens and dozens of RR73 messages but it tries to call (to transmit) only 5 times (all in about 20 minutes).

Why? Why Logger32 (if Cherry-picking is enabled) did not call / transmit to every decoded RR73 message?


This is the Cherry-picking log. As you can see (and I don't know why) Logger32 will transmit sometimes when it decodes reports (sent by DX Station to others station) and sometimes when it decodes  "RR73"...

16:01:45 Cherry-picking turned on
16:01:59 JTDX Decoding on
16:02:02 JTDX Decoding off
16:02:14 JTDX Decoding on
16:02:15 JTDX Decoding off

16:02:15 Cherry-picking C92RU started
C92RU sent:  UR3IQ C92RU -08
C92RU not worked on 30m/digital
Need on 30m
16:02:15 Sent message to JTDX to call C92RU
16:02:15 JTDX TxEnable on
16:02:15 JTDX Transmit on
16:02:15 JTDX is transmitting to C92RU
16:02:28 JTDX Transmit off
16:02:44 JTDX Decoding on
16:02:45 JTDX Transmit on
16:02:45 JTDX is transmitting to C92RU
16:02:45 C92RU sent:  UR3IQ C92RU -07
16:02:45 C92RU replied to UR3IQ
16:02:45 Sent Tx Halt message to JTDX
16:02:45 Cherry-picking C92RU ended *2
16:02:45 JTDX TxEnable off
16:02:45 JTDX Transmit off
16:02:45 JTDX Decoding off
16:02:59 JTDX Decoding on
16:03:01 JTDX Decoding off
16:03:14 JTDX Decoding on
16:03:15 JTDX Decoding off
16:03:29 JTDX Decoding on
16:03:31 JTDX Decoding off
16:03:44 JTDX Decoding on
16:03:44 JTDX Decoding off
16:03:59 JTDX Decoding on
16:04:01 JTDX Decoding off
16:04:14 JTDX Decoding on
16:04:14 JTDX Decoding off
16:04:29 JTDX Decoding on
16:04:31 JTDX Decoding off
16:04:44 JTDX Decoding on
16:04:45 JTDX Decoding off
16:04:59 JTDX Decoding on
16:05:02 JTDX Decoding off
16:05:14 JTDX Decoding on
16:05:15 JTDX Decoding off
16:05:29 JTDX Decoding on
16:05:31 JTDX Decoding off
16:05:44 JTDX Decoding on
16:05:45 JTDX Decoding off
16:05:59 JTDX Decoding on
16:06:01 JTDX Decoding off
16:06:29 JTDX Decoding on
16:06:31 JTDX Decoding off
16:06:44 JTDX Decoding on
16:06:45 JTDX Decoding off

16:06:45 Cherry-picking C92RU started
C92RU sent:  UT3IJ C92RU -05
C92RU not worked on 30m/digital
Need on 30m
16:06:45 Sent message to JTDX to call C92RU
16:06:45 JTDX TxEnable on
16:06:45 JTDX Transmit on
16:06:45 JTDX is transmitting to C92RU
16:06:58 JTDX Transmit off
16:07:14 JTDX Decoding on
16:07:14 C92RU sent:  RA3FH C92RU -05
16:07:14 C92RU replied to RA3FH
16:07:14 Sent Tx Halt message to JTDX
16:07:14 Cherry-picking C92RU ended *2
16:07:14 JTDX TxEnable off
16:07:15 JTDX Decoding off
16:07:29 JTDX Decoding on
16:07:31 JTDX Decoding off
16:07:44 JTDX Decoding on
16:07:45 JTDX Decoding off
16:07:59 JTDX Decoding on
16:08:01 JTDX Decoding off
16:08:14 JTDX Decoding on
16:08:17 JTDX Decoding off
16:08:29 JTDX Decoding on
16:08:31 JTDX Decoding off
16:08:44 JTDX Decoding on
16:08:45 JTDX Decoding off
16:08:59 JTDX Decoding on
16:09:02 JTDX Decoding off
16:09:14 JTDX Decoding on
16:09:17 JTDX Decoding off
16:09:29 JTDX Decoding on
16:09:32 JTDX Decoding off
16:09:44 JTDX Decoding on
16:09:45 JTDX Decoding off
16:09:59 JTDX Decoding on
16:10:01 JTDX Decoding off
16:10:14 JTDX Decoding on
16:10:15 JTDX Decoding off
16:10:29 JTDX Decoding on
16:10:31 JTDX Decoding off
16:10:44 JTDX Decoding on
16:10:45 JTDX Decoding off
16:10:59 JTDX Decoding on
16:11:02 JTDX Decoding off
16:11:14 JTDX Decoding on
16:11:15 JTDX Decoding off

16:11:15 Cherry-picking C92RU started
C92RU sent:  I4SJZ C92RU RR73
C92RU not worked on 30m/digital
Need on 30m
16:11:15 Sent message to JTDX to call C92RU
16:11:15 JTDX TxEnable on
16:11:15 JTDX Transmit on
16:11:15 JTDX is transmitting to C92RU
16:11:28 JTDX Transmit off
16:11:44 JTDX Decoding on
16:11:44 C92RU sent:  RA3LAL C92RU RR73
16:11:44 C92RU sent:  UA3GAF C92RU -06
16:11:44 C92RU replied to UA3GAF
16:11:44 Sent Tx Halt message to JTDX
16:11:44 Cherry-picking C92RU ended *2
16:11:44 JTDX TxEnable off
16:11:45 JTDX Decoding off
16:11:59 JTDX Decoding on
16:12:03 JTDX Decoding off
16:12:14 JTDX Decoding on
16:12:15 JTDX Decoding off
16:12:29 JTDX Decoding on
16:12:33 JTDX Decoding off
16:12:44 JTDX Decoding on
16:12:45 JTDX Decoding off
16:12:59 JTDX Decoding on
16:13:03 JTDX Decoding off
16:13:14 JTDX Decoding on
16:13:17 JTDX Decoding off
16:13:29 JTDX Decoding on
16:13:34 JTDX Decoding off
16:13:44 JTDX Decoding on
16:13:46 JTDX Decoding off
16:13:59 JTDX Decoding on
16:14:03 JTDX Decoding off
16:14:14 JTDX Decoding on
16:14:15 JTDX Decoding off
16:14:29 JTDX Decoding on
16:14:33 JTDX Decoding off
16:14:44 JTDX Decoding on
16:14:45 JTDX Decoding off
16:14:59 JTDX Decoding on
16:15:02 JTDX Decoding off
16:15:14 JTDX Decoding on
16:15:15 JTDX Decoding off
16:15:29 JTDX Decoding on
16:15:32 JTDX Decoding off
16:15:44 JTDX Decoding on
16:15:45 JTDX Decoding off

16:15:45 Cherry-picking C92RU started
C92RU sent:  RX6DX C92RU -03
C92RU not worked on 30m/digital
Need on 30m
16:15:45 Sent message to JTDX to call C92RU
16:15:45 JTDX TxEnable on
16:15:45 JTDX Transmit on
16:15:45 JTDX is transmitting to C92RU
16:15:58 JTDX Transmit off
16:16:14 JTDX Decoding on
16:16:14 C92RU sent:  RX6DX C92RU RR73
16:16:14 C92RU sent:  OE5RAL C92RU -06
16:16:14 C92RU replied to OE5RAL
16:16:14 Sent Tx Halt message to JTDX
16:16:14 Cherry-picking C92RU ended *2
16:16:14 JTDX TxEnable off
16:16:15 JTDX Decoding off
16:16:29 JTDX Decoding on
16:16:34 JTDX Decoding off
16:16:44 JTDX Decoding on
16:16:45 JTDX Decoding off
16:16:59 JTDX Decoding on
16:17:02 JTDX Decoding off
16:17:14 JTDX Decoding on
16:17:15 JTDX Decoding off
16:17:29 JTDX Decoding on
16:17:31 JTDX Decoding off
16:17:44 JTDX Decoding on
16:17:44 JTDX Decoding off
16:17:59 JTDX Decoding on
16:18:01 JTDX Decoding off
16:18:14 JTDX Decoding on
16:18:15 JTDX Decoding off
16:18:29 JTDX Decoding on
16:18:32 JTDX Decoding off
16:18:44 JTDX Decoding on
16:18:45 JTDX Decoding off
16:18:59 JTDX Decoding on
16:19:02 JTDX Decoding off
16:19:14 JTDX Decoding on
16:19:16 JTDX Decoding off



See also this screenshot (sorry for big size), you can see dozen of RR73 but only one call / transmission:
Inline image">">


Is it a my fault?
Or there is some of strange about Cherry-picking?
How to let Cherry-picking to transmit at every RR73 decoded?

Thanks.

73s
Fabio, IZ8MBW