Return-Path: Received: from rly-db10.mx.aol.com (rly-db10.mail.aol.com [172.19.130.85]) by air-db07.mail.aol.com (v123.4) with ESMTP id MAILINDB073-aee4a00a59b1; Tue, 05 May 2009 16:46:34 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-db10.mx.aol.com (v123.4) with ESMTP id MAILRELAYINDB104-aee4a00a59b1; Tue, 05 May 2009 16:46:22 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1M1RWQ-0003Kh-Vu for rs_out_1@blacksheep.org; Tue, 05 May 2009 21:45:50 +0100 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1M1RWQ-0003KY-9E for rsgb_lf_group@blacksheep.org; Tue, 05 May 2009 21:45:50 +0100 Received: from mout5.freenet.de ([195.4.92.95]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1M1RWP-0006NW-BC for rsgb_lf_group@blacksheep.org; Tue, 05 May 2009 21:45:50 +0100 Received: from [195.4.92.17] (helo=7.mx.freenet.de) by mout5.freenet.de with esmtpa (ID beckmann.erlangen@freenet.de) (port 25) (Exim 4.69 #89) id 1M1RWO-0002HI-37 for rsgb_lf_group@blacksheep.org; Tue, 05 May 2009 22:45:48 +0200 Received: from w0464.w.pppool.de ([89.58.4.100]:1327 helo=2a2d7ed321c6425) by 7.mx.freenet.de with esmtpa (ID beckmann.erlangen@freenet.de) (port 25) (Exim 4.69 #79) id 1M1RWN-0007tM-2b for rsgb_lf_group@blacksheep.org; Tue, 05 May 2009 22:45:48 +0200 From: "Beckmann, Gerhard" To: References: <200904031959.n33Jxrvn028438@smtpa1.mediabeam.com><20090504220936.59jcwemhlo004wkk@webmail4.kuleuven.be><01a401c9ccfd$f04e8640$6401a8c0@asus><20090504233650.cpq3ip6kir688ogo@webmail4.kuleuven.be><005d01c9cd6b$620ddc00$6401a8c0@asus><20090505121435.9F59DF3863@smtps02.kuleuven.be><20090505152548.71C37F3865@smtps02.kuleuven.be><00df01c9cdac$e9a407c0$6401a8c0@asus><20090505214422.o47capffyyb4oog0@webmail4.kuleuven.be> <20090505221513.oso5g5yn6csgwsw4@webmail4.kuleuven.be> Date: Tue, 5 May 2009 22:45:43 +0200 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20090505221513.oso5g5yn6csgwsw4@webmail4.kuleuven.be> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: AcnNvrpPKZrtSmtzTiucWasGazeOXwAA1POw X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: AW: LF: RE: rtty test Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none 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-IP: 193.82.116.20 Hello Rik, Your signal is fine visible on my waterfall, but with deep QSB-Phases. Vy 73 de Gerhard // DK6NI (JN59LN) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =20 -----Urspr=FCngliche Nachricht----- Von: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] Im Auftrag von Rik Strobbe Gesendet: Dienstag, 5. Mai 2009 22:15 An: rsgb_lf_group@blacksheep.org Betreff: RE: LF: RE: rtty test Faint traces of my signal are showing up on the G4WGT grabber. I will transmit every 10 minutes starting 20:40 UTC until 21:30 UTC =20 and listen inbetween. 73, Rik ON7YD - OR7T Quoting Rik Strobbe : > Hello Gary, LF, > > I just had a first transmission. > I will try short transmissions every 10-15 minutes or so until my > signal shows up un your grabber. Then I will start longer transmissions. > > 73, Rik ON7YD - OR7T > > Quoting Gary - G4WGT : > >> OK Rik, >> >> I will look at the settings you describe in MTTY to allow me to monitor, I >> normally use TrueTTY. >> >> Thanks for the info. >> >> Cheers, >> >> Gary - G4WGT. >> >> -----Original Message----- >> From: owner-rsgb_lf_group@blacksheep.org >> [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Rik Strobbe >> Sent: 05 May 2009 16:26 >> To: rsgb_lf_group@blacksheep.org >> Subject: RE: LF: RE: rtty test >> >> Gary, LF, >> >> I just had a look at MMTTY and it seems pretty easy to set it to 50Hz >> shift and 22Bd baudrate. >> The way I did it: >> 1. As a start select 23Hz RTTY (in "Profiles") >> 2. In "Options" select "Setup MMTTY" >> 3. In the tab "Demodulator" change "Shift" from 23 tot 50 (it is not >> a standard option, but you can just type 50 into the field) >> 4. In the tab "Demodulator" change "Mark" to a suitable value (that >> is the audio frequency you get) >> 5. In the tab "Demodulator" change "Discriminator Type" from VCO to FIR BPF >> 6. In the tab "Demodulator" change "Tap" from 72 to 256 >> 7. In the tab "Demodulator" click on "OK" >> 8. In the tab "Decode" change "BaudRate" from 45 tot 22 and click "OK" >> Steps 5-7 set demodulator type, the values above are the result of >> some brief dry tests and can most likely still be optimized. You can >> do that in the main screen. >> >> If WX permits (no rain) I intend to run some tests between 20:30 and >> 21:30 UTC on 503.5kHz in mode USB (so if you listen in LSB don't >> forget to select reverse mode). >> I will announce the exact hours later this evening. >> Between transmissions I will listen on the same frequency. >> >> All reports (or replies) are welcome. >> >> 73, Rik ON7YD - OR7T >> >> At 14:14 5/05/2009, you wrote: >>> Hello Gary, >>> >>> I had a closer look at the 23Hz shift option of MMTTY and it seems >>> to run at 45Bd what is on the edge regarding the shift/baudrate >>> ratio. That is most likely the reason why it is not so robust. >>> Using 45Bd at 85Hz shift would exceed the 100Hz bandwidth limit. >>> I guess the best option for RTTY would be a shift around 50Hz and a >>> lower baudrate (say 20Bd) what would well fit within the 100Hz >>> bandwidth and would have a sufficient shift/baudrate ratio to >>> provide a robust signal. >>> I will see if I can get such signal out of MMTTY and - if time >>> permits - run some tests tonight. >>> >>> 73, Rik ON7YD - OR7T >>> >>> At 12:22 5/05/2009, you wrote: >>>> Hi Rik, >>>> >>>> You have experienced the same as I did with 23Hz shift, the signal needs >> to >>>> be very strong to decode. It was in the last 2 minutes that I got the >>>> partial decode. >>>> >>>> A much better shift to use is the 85Hz which will fit into your spec. >>>> >>>> I have had good QSO's with Chris G3XIZ in Biggleswade both of us using >> 85Hz. >>>> >>>> Give that a try next time & I believe I will get a much better decode >>>> judging by the strength of your signal. >>>> >>>> 73 >>>> >>>> Gary - G4WGT. >>>> >>>> -----Original Message----- >>>> From: owner-rsgb_lf_group@blacksheep.org >>>> [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Rik Strobbe >>>> Sent: 04 May 2009 22:37 >>>> To: rsgb_lf_group@blacksheep.org >>>> Subject: Re: LF: RE: rtty test >>>> >>>> Hello Gary, >>>> >>>> call the is almost right, locator completely. >>>> But not really impressive for 500mW ERP. >>>> I could see my signal on your grabber, some slow QSB but strong for >>>> the last 2 minutes or so. >>>> I used MTTY with the profile "23Hz RTTY (MTTY)" without any further >>>> changes, not sure that this is the best mode. >>>> So any advice is welcome. >>>> I have also installed MultiPSK, but am still overwhelmed by the colors >>>> and options. >>>> I am allowed to use any digital mode as long as I stick to max. 100Hz >>>> bandwidth. >>>> >>>> 73, Rik ON7YD - OR7T >>>> >>>> >>>> >>>> Quoting Gary - G4WGT : >>>> >>>>> Hi Rik, >>>>> >>>>> This is the best I could do, it looks like almost your call sign & >> locator >>>>> :- >>>>> >>>>> RHTQHTST DE TC(TIOJ7T OR1T JO20IX >>>>> >>>>> 73 >>>>> >>>>> Gary - G4WGT. >>>>> >>>>> -----Original Message----- >>>>> From: owner-rsgb_lf_group@blacksheep.org >>>>> [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Rik Strobbe >>>>> Sent: 04 May 2009 21:10 >>>>> To: rsgb_lf_group@blacksheep.org >>>>> Subject: LF: rtty test >>>>> >>>>> dear all, >>>>> >>>>> I will run a short (10 minute) rtty test (23Hz shift) on 503.500 at >> 21UTC >>>>> Reports and/or reply welcome. >>>>> >>>>> 73, Rik ON7YD - OR7T >>>>> >>>>> >>>>> >>> >> >> >> >>