To: rsgb_lf_group@blacksheep.org
References: <CAC+C6w6vu6WsszmBSerXqRj5_G6Oabcq4KydZASKQnoSG_=okw@mail.gmail.com>
 <595CB879.6040207@posteo.de> <595CC4B1.8030902@posteo.de>
 <595CD25A.8050009@posteo.de>
From: iz7lsz <iz7slz.domenico@gmail.com>
Message-ID: <595D340A.50803@gmail.com>
Date: Wed, 5 Jul 2017 18:46:34 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <595CD25A.8050009@posteo.de>
Subject: Re: LF: Auto-EbNaut reception on LF in JN80
Content-Type: multipart/alternative;
 boundary="------------030204060503020907020409"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

This is a multi-part message in MIME format.
--------------030204060503020907020409
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Stefan,

again thanks for testing this system !

I did some changes and now log is arranged in lifo style. I think is 
better for browsing now.

About the different list numbers on different channels, it's seem a good 
idea. I will try to modify the script for the third channel and for the 
vari-list.

This is the actual sequence of the script :

- exactly at XX.17, after  transmission period,  ebnaut program starts 
(parameters for RX1) and it ends at XX.31 (about). This time depends 
from my slow pc.
- after that DETECTED.TXT file is updated and uploaded on my ftp site
- than , exactly at XX.37 ebnaut program starts again  (parameters for 
RX2) and it ends at XX.46 (about).
- after that DETECTED.TXT file is updated again  and uploaded on my ftp site
There is room for a third decoding process (even at same list=20000)  
before that the script loops again at XX.00 hour.

...stay tuned .

73, Domenic iz7slz


BTW this is a very


On 7/5/2017 11:49, DK7FC wrote:
> Hi all,
>
> I'm sorry for the many emails today. But i have another idea for 
> Domenico:
>
> You could run a 3rd 'channel', e.g. 137.485 kHz (still oriented on the 
> current frequency section) and indicate/define this channel (3) as a 
> 'local' channel, whereas the other channels are indicated as 'medium' 
> (2) and 'DX' (1).
> The difference in the settings in these channels (apart from the 
> frequency of course) is the list size!
> Local stations or strong stations like me will decode almost every 
> time at rank 0, so you can use a very small list length for that 
> channel, e.g. 50.
> A weak/distant station or in times of high QRN one (e.g. VO1NA) would 
> prefer to use one of the other channels, just in case that the rank 
> will be much worse.
> You can see that most of the 'false' decodes happen at list lengths of 
> > 5000. So with the use of different list lengths you can avoid 
> several false decodes, CPU usage and false entries in the log file.
> For the 'medium' channel you could use a list length of 1000 and for 
> DX maybe 20000.
>
> Just an idea :-)
>
> Using two frequencies has already improved the situation:
>
> -----------------------------------------
> 2017-07-05_09:59:30   start time + 30 s  on 137.490 kHz
> found rank 0 ber 8.0645e-02 Eb/N0 10.6 M -9.849675903e+02 [*GM ALL IW4DXW K*] ps [  1  180  180  180  180]
> 2017-07-05_10:59:30   start time + 30 s  on 137.495 kHz
> found rank 0 ber 2.3185e-01 Eb/N0 4.9 M -5.360782471e+02 [*73 FROM DL TO I*] ps [  0    0    0    0    0]
> --------------------------------------------------------
> In a few minutes i will try to run less antenna current to come closer 
> to the limit :-)
>
> Thanks for the great service :-)
>
> 73, Stefan


--------------030204060503020907020409
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Stefan,<br>
    <br>
    again thanks for testing this system !<br>
    <br>
    I did some changes and now log is arranged in lifo style. I think is
    better for browsing now.<br>
    <br>
    About the different list numbers on different channels, it's seem a
    good idea. I will try to modify the script for the third channel and
    for the vari-list.<br>
    <br>
    This is the actual sequence of the script :<br>
    <br>
    - exactly at XX.17, after  transmission period,  ebnaut program
    starts (parameters for RX1) and it ends at XX.31 (about). This time
    depends from my slow pc.<br>
    - after that DETECTED.TXT file is updated and uploaded on my ftp
    site<br>
    - than , exactly at XX.37 ebnaut program starts again  (parameters
    for RX2) and it ends at XX.46 (about).<br>
    - after that DETECTED.TXT file is updated again  and uploaded on my
    ftp site<br>
    There is room for a third decoding process (even at same
    list=20000)  before that the script loops again at XX.00 hour.<br>
    <br>
    ...stay tuned .<br>
    <br>
    73, Domenic iz7slz<br>
    <br>
    <br>
    <br>
    BTW this is a very <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 7/5/2017 11:49, DK7FC wrote:<br>
    </div>
    <blockquote cite="mid:595CD25A.8050009@posteo.de" type="cite">
      <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
      Hi all, <br>
      <br>
      I'm sorry for the many emails today. But i have another idea for
      Domenico: <br>
      <br>
      You could run a 3rd 'channel', e.g. 137.485 kHz (still oriented on
      the
      current frequency section) and indicate/define this channel (3) as
      a
      'local' channel, whereas the other channels are indicated as
      'medium'
      (2) and 'DX' (1).<br>
      The difference in the settings in these channels (apart from the
      frequency of course) is the list size! <br>
      Local stations or strong stations like me will decode almost every
      time
      at rank 0, so you can use a very small list length for that
      channel,
      e.g. 50.<br>
      A weak/distant station or in times of high QRN one (e.g. VO1NA)
      would
      prefer to use one of the other channels, just in case that the
      rank
      will be much worse. <br>
      You can see that most of the 'false' decodes happen at list
      lengths of
      &gt; 5000. So with the use of different list lengths you can avoid
      several false decodes, CPU usage and false entries in the log
      file.<br>
      For the 'medium' channel you could use a list length of 1000 and
      for DX
      maybe 20000.<br>
      <br>
      Just an idea :-)<br>
      <br>
      Using two frequencies has already improved the situation: <br>
      <br>
      <pre>-----------------------------------------
2017-07-05_09:59:30   start time + 30 s  on 137.490 kHz 
found rank 0 ber 8.0645e-02 Eb/N0 10.6 M -9.849675903e+02 [<big><b>GM ALL IW4DXW K</b></big>] ps [  1  180  180  180  180]
2017-07-05_10:59:30   start time + 30 s  on 137.495 kHz 
found rank 0 ber 2.3185e-01 Eb/N0 4.9 M -5.360782471e+02 [<big><b>73 FROM DL TO I</b></big>] ps [  0    0    0    0    0]
--------------------------------------------------------</pre>
      In a few minutes i will try to run less antenna current to come
      closer
      to the limit :-)<br>
      <br>
      Thanks for the great service :-)<br>
      <br>
      73, Stefan<br>
    </blockquote>
    <br>
  </body>
</html>

--------------030204060503020907020409--