Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 X-Spam-DCC: wuwien: mailn 1290; Body=2 Fuz1=2 Fuz2=2 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by lipkowski.org (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id v4BBVUl9008693 for ; Thu, 11 May 2017 13:31:31 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1d8mFQ-0002FS-2K for rs_out_1@blacksheep.org; Thu, 11 May 2017 12:27:08 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1d8mEz-0002FF-KP for rsgb_lf_group@blacksheep.org; Thu, 11 May 2017 12:26:41 +0100 Received: from mout02.posteo.de ([185.67.36.66]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1d8mEv-0005Gf-0X for rsgb_lf_group@blacksheep.org; Thu, 11 May 2017 12:26:39 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 3014A20EB1 for ; Thu, 11 May 2017 13:26:35 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3wNrQy3mYJz109t for ; Thu, 11 May 2017 13:26:34 +0200 (CEST) Message-ID: <59144A6A.9030405@posteo.de> Date: Thu, 11 May 2017 13:26:34 +0200 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <1494434057.289033747@f20.i.mail.ru> <9ca738eb-6a64-a922-356a-6891cd122dc8@abelian.org> In-Reply-To: <9ca738eb-6a64-a922-356a-6891cd122dc8@abelian.org> X-Scan-Signature: 87525734ac0bb319fb3f44295fe6963b Subject: Re: LF: my results on VLF 05-08 May 2017 Content-Type: multipart/alternative; boundary="------------000101030703060407060303" X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Scanned-By: MIMEDefang 2.75 Status: RO X-Status: X-Keywords: X-UID: 11666 This is a multi-part message in MIME format. --------------000101030703060407060303 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Paul, Alex, VLF, Paul, thanks for working out the decode and timing problem, good work. Alex, i don't know if this is just a PC time problem. At least what i can recommend is to control the PC clock by SpecLab! ...because there is no internet access in the garden. Not sure if you are already using this function. Make a right click on the SpecLab icon, select properties and enable "start as administrator". Disable the time sync (from a time server) function in windows. Now when starting SpecLab, you need to confirm that the program will be started with admin privileges. Since you are using a GPS module which provides PPS+NMEA, SpecLab knows the accurate time. Open the GPS receiver function and enable the function "periodically synchronize PC's system date/time with data from GPS". Before doing this, take a look on the value from "Current measured difference (System -GPS time): /w.xyz/ sec". After enabling the function, this value should be in a range of 0.00x sec. On the cope function of the Samlping rate Correction, what does the PC and EC show, or what is the ratio EC/PC? It should be less than 5% maybe. Maybe it helps... 73, Stefan Am 11.05.2017 09:02, schrieb Paul Nicholson: > > Alex wrote: > > > I think I have only false decodes of > > {05 May 19:15 8270.1 4-char} > > http://rn3aus.narod.ru/ebnaut-8270-05may2017-1915z.zip > > I got a successful genuine decode of the 4-char message > from Alex's file > > ebnaut06_MAY_0136_8270-1pps.wav > > Eb/N0 = 0.0 dB, constant reference phase > > carrier S/N: 13.62 dB in 31.2 uHz, > -31.43 dB in 1Hz, > -65.41 dB in 2.5kHz > > The decode needed a time offset of +1001 seconds > which doesn't agree with difference between the WAV > timestamp and the start of the message. Something > wrong with the clock at the RX site? > > Alex, try the decode again, > > Symbols: 40.0 > Message length: 4 > Start offset: 1001 > List length: 100 > > Now I go look at the 2-char.... > -- > Paul Nicholson > -- > > > --------------000101030703060407060303 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Paul, Alex, VLF,

Paul, thanks for working out the decode and timing problem, good work.

Alex, i don't know if this is just a PC time problem. At least what i can recommend is to control the PC clock by SpecLab! ...because there is no internet access in the garden. Not sure if you are already using this function.

Make a right click on the SpecLab icon, select properties and enable "start as administrator".
Disable the time sync (from a time server) function in windows.
Now when starting SpecLab, you need to confirm that the program will be started with admin privileges.
Since you are using a GPS module which provides PPS+NMEA, SpecLab knows the accurate time.
Open the GPS receiver function and enable the function "periodically synchronize PC's system date/time with data from GPS".
Before doing this, take a look on the value from "Current measured difference (System -GPS time): w.xyz sec".
After enabling the function, this value should be in a range of 0.00x sec.

On the cope function of the Samlping rate Correction, what does the PC and EC show, or what is the ratio EC/PC? It should be less than 5% maybe.

Maybe it helps...

73, Stefan

Am 11.05.2017 09:02, schrieb Paul Nicholson:

Alex wrote:

> I think I have only false decodes of
> {05 May 19:15 8270.1 4-char}
> http://rn3aus.narod.ru/ebnaut-8270-05may2017-1915z.zip

I got a successful genuine decode of the 4-char message
from Alex's file

 ebnaut06_MAY_0136_8270-1pps.wav

Eb/N0 = 0.0 dB, constant reference phase

carrier S/N: 13.62 dB in 31.2 uHz,
            -31.43 dB in 1Hz,
            -65.41 dB in 2.5kHz

The decode needed a time offset of +1001 seconds
which doesn't agree with difference between the WAV
timestamp and the start of the message.  Something
wrong with the clock at the RX site?

Alex, try the decode again,

 Symbols: 40.0
 Message length: 4
 Start offset: 1001
 List length: 100

Now I go look at the 2-char....
--
Paul Nicholson
--



--------------000101030703060407060303--