Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-de02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 7FD1338000095 for ; Wed, 6 Mar 2013 08:39:49 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UDDyA-0005qT-N1 for rs_out_1@blacksheep.org; Wed, 06 Mar 2013 13:01:18 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UDDy9-0005qJ-Sr for rsgb_lf_group@blacksheep.org; Wed, 06 Mar 2013 13:01:17 +0000 Received: from mail-ee0-f53.google.com ([74.125.83.53]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1UDDy2-0006GQ-Tn for rsgb_lf_group@blacksheep.org; Wed, 06 Mar 2013 13:01:16 +0000 Received: by mail-ee0-f53.google.com with SMTP id e53so5492770eek.12 for ; Wed, 06 Mar 2013 05:00:43 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:from:to:references:in-reply-to:subject:date :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole; bh=xIeL1OXUVyOgxi7vFHRAq32ss0R9YvepGVbrkCcXpDI=; b=0RuA8yONsEgj0fffb0n66csWTuzhwUEnL+e7hUshBD4ItyOziwjjGy4gJFuY3UskTQ IPz8SSP/y+U/EdbSN5Qq2gDsqRls7AfiZnUY5g8oPZbhK0dmuUYN5EdNp8nW1f2tVV8A UdV1Zsm/C0Wdz2D8pvd5Wg1uPDR6UOn3vybVKQumOQ8JYXdbBbuX4EAUKpan7nx3aUic 1XOIHv7kLuM0+K8RHRu5IM4tX/H791DPK63z8w9wHvvMAp0563DerB/+Gnz/RRETMbmD o2tkV3RpEp2bhCSaVErP2FLvFsi7IY2Nms23vTPKeIozBMVE/jOVNR9iMLXTzxwGoULe THuQ== X-Received: by 10.14.182.137 with SMTP id o9mr81331674eem.13.1362574843083; Wed, 06 Mar 2013 05:00:43 -0800 (PST) Received: from PcMinto (dhcp-077-248-065-057.chello.nl. [77.248.65.57]) by mx.google.com with ESMTPS id o3sm42366276eem.15.2013.03.06.05.00.42 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Mar 2013 05:00:42 -0800 (PST) Message-ID: <83DB03CF474946D991BEA4BE85C9895B@PcMinto> From: Minto Witteveen To: References: <58DDEF66BD1F4FCDA781E159BB3130D4@GaryAsus> <5133BADE.9070906@iup.uni-heidelberg.de> <5133C67A.10300@psk31.plus.com> <5133C9E6.5070406@iup.uni-heidelberg.de> <5133D161.4080703@psk31.plus.com> <5134A7AB.6020202@iup.uni-heidelberg.de> <5134F966.5090807@psk31.plus.com> <5135D5E8.7040304@iup.uni-heidelberg.de> <5135FDDC.2020100@iup.uni-heidelberg.de> <1AD9CFA88EB9476B81C3CD9EE515BB31@PcMinto> <51362618.2040709@iup.uni-heidelberg.de> <51364368.3090204@psk31.plus.com> <51364D95.7090009@psk31.plus.com> <93266BE26B7D4C14A04471501FB9D23A@AGB> <51367D85.2020607@psk31.plus.com> <92C760BF2A3C46C1A7AD6EDF566DE96F@IBM7FFA209F07C> <5137192A.7040103@iup.uni-heidelberg.de> In-Reply-To: <5137192A.7040103@iup.uni-heidelberg.de> Date: Wed, 6 Mar 2013 14:00:41 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I had the same problem – initially the first character of every transmission would be garbled. In my case this was because after starting the transmitter (with a ‘mark’) the first character was immediately transmitted, i.e. the start bit (space) came 50us after start of transmission. Never giving the decoder a chance to notice the start bit. I resolved this by starting the TX (mark), then delaying 500 ms before sending the first character (start bit). Not sure if fldigi suffers from the same bug... [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [74.125.83.53 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (minto.witteveen[at]gmail.com) -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: 9b622d5c6a961580a0f289e85f67bcca Subject: LF: Re: RTTY test transmission Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A9_01CE1A72.FD22BFF0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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 x-aol-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mtain-de02.r1000.mx.aol.com ; domain : gmail.com DKIM : fail x-aol-sid: 3039ac1d40ca5137472449fe X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_00A9_01CE1A72.FD22BFF0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I had the same problem =E2=80=93 initially the first character of every = transmission would be garbled. In my case this was because after starting the transmitter (with a = =E2=80=98mark=E2=80=99) the first character was immediately transmitted, = i.e. the start bit (space) came 50us after start of transmission. Never = giving the decoder a chance to notice the start bit. I resolved this by starting the TX (mark), then delaying 500 ms before = sending the first character (start bit).=20 Not sure if fldigi suffers from the same bug... Alternatively you may send one or more NULL characters to get the = receiver in sync. -------------------------------------------------------------------------= - Ceterum censeo Carthaginem delendam esse From: Stefan Sch=C3=A4fer=20 Sent: Wednesday, March 06, 2013 11:23 To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Re: RTTY test transmission Am 06.03.2013 10:50, schrieb Chris:=20 [...] Every burst of transmission lost the first 'T' in TEST, maybe an idea = to send 'V V V' or something at the start to allow the system to lock. Hi Chris,=20 Yes, i had the same thought. Will change that today.=20 Was most excellent copy anyway much of the time. Didn't hear anything of the GM station on CW, but maybe closed down = too early. Hope we get another chance with that one! Stefan, if you're reading this, called you several times when you were = CQing in CW a few evenings back, but my 25W did not get to you. Also = heard G3PDN calling you and you didn't hear him either. No idea who or = where G3PDN is, not on QRZ. Thanks for the info Chris. Well you know and see, when studying the WSPR = database, that the 630m S/N drops significantly over the land path. That = makes it more difficult for me to copy UK stations while they can hear = each other perfectly (as well as PA stns).=20 However i had an excellent QSO with Chris/G3XIZ some days ago, where he = was reaking RST 589. So it must also be a question of local propagation. = Let's try again tonite! Vy 73, Chris, G4AYT, Whitstable, Kent. JO01MI. 73, Stefan/DK7FC ------=_NextPart_000_00A9_01CE1A72.FD22BFF0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I had the same problem = =E2=80=93 initially=20 the first character of every transmission would be garbled.
In my = case this=20 was because after starting the transmitter (with a = =E2=80=98mark=E2=80=99) the first character=20 was immediately transmitted, i.e. the start bit (space) came 50us after = start of=20 transmission. Never giving the decoder a chance to notice the start = bit.
I=20 resolved this by starting the TX (mark), then delaying 500 ms before = sending the=20 first character (start bit).
Not sure if fldigi suffers from the = same=20 bug...

Alternatively you may = send one or=20 more NULL characters to get the receiver in sync.

 
-------------------------------------------------------------------= -------
Ceterum=20 censeo Carthaginem delendam esse
 
From: Stefan = Sch=C3=A4fer
Sent: Wednesday, March 06, 2013 11:23
Subject: Re: LF: Re: RTTY test = transmission
 

Am=20 06.03.2013 10:50, schrieb Chris:=20
[...]
Every burst of transmission lost the = first 'T' in=20 TEST, maybe an idea to send 'V V V' or something at the start to allow = the=20 system to lock.

Hi Chris,

Yes, i = had the=20 same thought. Will change that today.


Was most excellent copy anyway much = of the=20 time.
Didn't hear anything of the GM = station on CW, but=20 maybe closed down too early. Hope we get another chance with that=20 one!
Stefan, if you're reading this, = called you=20 several times when you were CQing in CW a few evenings back, but my = 25W did=20 not get to you. Also heard G3PDN calling you and you didn't hear him = either.=20 No idea who or where G3PDN is, not on = QRZ.

Thanks=20 for the info Chris. Well you know and see, when studying the WSPR = database, that=20 the 630m S/N drops significantly over the land path. That makes it more=20 difficult for me to copy UK stations while they can hear each other = perfectly=20 (as well as PA stns).
However i had an excellent QSO with = Chris/G3XIZ some=20 days ago, where he was reaking RST 589. So it must also be a question of = local=20 propagation.
Let's try again tonite!

Vy 73,
Chris, G4AYT, Whitstable, Kent.=20 JO01MI.


73,=20 Stefan/DK7FC
------=_NextPart_000_00A9_01CE1A72.FD22BFF0--