Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id wBCHfbgH022834 for ; Wed, 12 Dec 2018 18:41:38 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gX8Rs-0004fK-Ln for rs_out_1@blacksheep.org; Wed, 12 Dec 2018 17:37:28 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gX8Rs-0004fB-5b for rsgb_lf_group@blacksheep.org; Wed, 12 Dec 2018 17:37:28 +0000 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.91_59-0488984) (envelope-from ) id 1gX8Rq-0004LS-EF for rsgb_lf_group@blacksheep.org; Wed, 12 Dec 2018 17:37:27 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 91F022400E6 for ; Wed, 12 Dec 2018 18:37:24 +0100 (CET) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1544636244; bh=g15s+Ug7MX6Y2KxBA+zvJRKxXJ2eLvc5f2meH7wzBLQ=; h=Date:From:To:Subject:From; b=myOew0ddf7fiPACo3UWz6p5KLfEffVUaE3NIIFhqKxNByf0Q0JsLdaJFXdeA7LNtG blOjQSqDkCsSuQ/LRJiLXkVLLYm2+69Jamf25Gxcgy91VlcC8T191cdoNrlqt9HprQ AnRz+wjixgMrL8p4x1yAjiaHPd2r8hMcNMA+pbnJ615l9YWLDtSFWqV1h5lEs4w96b bG2fuhsRM3bAPtqdtvTGxo4AMgaUONYSDfWcyUu9uHuNdCP+TS6ExTVYdeCpG+bmDA fMAOAGNT6NlZxXmX0S8BqR56JXG8HuVBcplvRibjO9eyG6qPMN6i4t3t6003ALhGTE 6XGOxvjbCsfTg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 43FPC80CsZz9rxN for ; Wed, 12 Dec 2018 18:37:23 +0100 (CET) Message-ID: <5C114753.6080307@posteo.de> Date: Wed, 12 Dec 2018 18:37:23 +0100 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: <719851106.2631422.1544562473988.ref@mail.yahoo.com> <719851106.2631422.1544562473988@mail.yahoo.com> <1UQfYRgA9a.2Q5z0iIYaE7@optiplex980-pc> <5C10F0BA.6050304@posteo.de> <6DB8451D7F3D3947A5918808A59621EA26394EE6@servigilant.vigilant.local> <5C10FACD.7080706@posteo.de> <6DB8451D7F3D3947A5918808A59621EA26394FBE@servigilant.vigilant.local> <5C110AB4.70700@posteo.de> <6DB8451D7F3D3947A5918808A59621EA26395029@servigilant.vigilant.local> In-Reply-To: <6DB8451D7F3D3947A5918808A59621EA26395029@servigilant.vigilant.local> X-Spam-Score: -2.3 (--) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Am 12.12.2018 14:34, schrieb VIGILANT Luis Fernández: > > Clearly not my day > Did you get it meanwhile? Am 12.12.2018 17:15, schrieb Markus Vester: > Stefan, may I suggest using opposite time slots for America and > Europe, i.e. VO1NA starting at hh:00 and DK7FC at hh:30? Yes, yes, certainly a good idea [...] Content analysis details: (-2.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [185.67.36.66 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: df2e2c1e83972f6e42eeb17d78e70347 Subject: Re: LF: EbNaut LF message announcement Content-Type: multipart/alternative; boundary="------------040900070805060906020409" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.2 required=5.0 tests=HTML_50_60,HTML_MESSAGE autolearn=no version=2.63 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 This is a multi-part message in MIME format. --------------040900070805060906020409 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Am 12.12.2018 14:34, schrieb VIGILANT Luis Fernández: > > Clearly not my day > Did you get it meanwhile? Am 12.12.2018 17:15, schrieb Markus Vester: > Stefan, may I suggest using opposite time slots for America and > Europe, i.e. VO1NA starting at hh:00 and DK7FC at hh:30? Yes, yes, certainly a good idea. I didn't know that Jay and Rob is still transmitting. Am 12.12.2018 16:14, schrieb jrusgrove@comcast.net: > Beware ... there are also counterfeit NEO6M out there ... ask me how I > know! The counterfeits seem to function normal except one is not able > to store setup changes. Aah, that explains much. I seem to have a few of those ;-) But it doesn't matter, i built my solutions arround that behaviour. Jay, did you try stacking? Maybe it actually was an SNR issue so there could be some result with stacking. And/or normalizing. But that's effort... Am 12.12.2018 15:53, schrieb Domenico IZ7SLZ: > A question for Stefan: the necessary 0.3 s correction is needed > becouse your transmission starts later (maybe due to the special SL Tx > configuration) or transmission timing is precise, but our SL based > decoder needs that corrections ? > I have received your signal this night without any time-offsets in > the auto decoder. > https://www.qsl.net/iz7slz/EBNAUT/DECODED.TXT The 0.3 second offset is a SpecLab internal phenomenon, affecting TX stations (and those who try to decode these messages). I don't know if it is 0.3 seconds exactly. At a symbol length of just 1 second it may be useful to know that offset better than just with 100 ms accuracy. But obviously even the 0.3 second / 30 % offset didn't cause failed decodes at your side. So thanks for your reports :-) 73, Stefan --------------040900070805060906020409 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Am 12.12.2018 14:34, schrieb VIGILANT Luis Fernández:

Clearly not my day

Did you get it meanwhile?


Am 12.12.2018 17:15, schrieb Markus Vester:
Stefan, may I suggest using opposite time slots for America and Europe, i.e. VO1NA starting at hh:00 and DK7FC at hh:30?
Yes, yes, certainly a good idea. I didn't know that Jay and Rob is still transmitting.


Am 12.12.2018 16:14, schrieb jrusgrove@comcast.net:
Beware ... there are also counterfeit NEO6M out there ... ask me how I know! The counterfeits seem to function normal except one is not able to store setup changes.
Aah, that explains much. I seem to have a few of those ;-) But it doesn't matter, i built my solutions arround that behaviour.
Jay, did you try stacking? Maybe it actually was an SNR issue so there could be some result with stacking. And/or normalizing. But that's effort...


Am 12.12.2018 15:53, schrieb Domenico IZ7SLZ:
A question for Stefan: the necessary  0.3 s correction is needed becouse your transmission starts later (maybe due to the special SL Tx configuration)  or transmission timing is precise, but  our SL based decoder needs that corrections ? 
I have received your signal this night without any  time-offsets in the auto decoder.
The 0.3 second offset is a SpecLab internal phenomenon, affecting TX stations (and those who try to decode these messages). I don't know if it is 0.3 seconds exactly. At a symbol length of just 1 second it may be useful to know that offset better than just with 100 ms accuracy.
But obviously even the 0.3 second / 30 % offset didn't cause failed decodes at your side. So thanks for your reports :-)


73, Stefan
--------------040900070805060906020409--