Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mi01.r1000.mx.aol.com (Internet Inbound) with ESMTP id 6B18D3800008C; Tue, 12 Mar 2013 07:24:50 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UFMsm-0001mx-0B for rs_out_1@blacksheep.org; Tue, 12 Mar 2013 10:56:36 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UFMsl-0001mo-5V for rsgb_lf_group@blacksheep.org; Tue, 12 Mar 2013 10:56:35 +0000 Received: from nm1.bt.bullet.mail.ird.yahoo.com ([212.82.108.232]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1UFMsj-00082q-9w for rsgb_lf_group@blacksheep.org; Tue, 12 Mar 2013 10:56:34 +0000 Received: from [212.82.108.231] by nm1.bt.bullet.mail.ird.yahoo.com with NNFMP; 12 Mar 2013 10:56:16 -0000 Received: from [46.228.39.177] by tm4.bt.bullet.mail.ird.yahoo.com with NNFMP; 12 Mar 2013 10:56:16 -0000 Received: from [127.0.0.1] by smtp118.bt.mail.ir2.yahoo.com with NNFMP; 12 Mar 2013 10:56:15 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1363085775; bh=zoN/SuCibNU3zH4QdRXEamW+41VwJOqAs7oDa/Me9zQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=a96113RZtJYnsw3AWyP3KqyVuYqSflEg7aXSkOn2oWEjQ5sgPV6OOlfbM7N7n/wRUHiHdMlCblE4N+Oq5BegjmNRuXJmM3Jje1B5VDt6A9ZfxyiP+i7UMbJ3aTLI40q9/WaJzCbG3L/fBeXAr5162OiPXgybzSXS3i2bkVCvq6k= X-Yahoo-Newman-Id: 991620.65616.bm@smtp118.bt.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 0XZzrFYVM1lhC8SIY7fMxyk8cWe3ugBWsDvMKcz3ASBDEjj Zc68vmCyyVCKCNzOeVolPcJ92d7z0MnfXFq_6Nn.LpwtFPLfCh0Qr_90T9SW BW7f9zxZ9iusyH3e6aMst8xESxjM1jMID0Q4Da_ajrzpZN9Lv9N3wE_AaJjG S8163.WrYwpmm_04bssk4U.E_yLvqy_37vUsVLWL2kIzJ4lUGBHYJZiR0HHU .I6K4Xb5GSOpUdvgsvlfSZzgHb.sTFkbMUopdIKDeAADBVYPvM1hLvaEizja CM2W7cYvn3LAwurnW58K8A4eH.IeCmsU4N5Po.SMQm4YjMqXXfiq1gGnoObY .0FezF9y2nq.5IE2CyE9t14bUVIqbROItETHKU4gIvoLqAiVYMiGgK4ZsMQ1 R.cDR7PqDXJK.oM4RXgMvkL40pES9Ug3XzgpS2W6Yw3UnX_1N0fxZyBF4ssZ Qm5tu3Z_QoQ-- X-Yahoo-SMTP: .u8e2g.swBByWKjbpA3lR6Fw.2ZEQrJJpVsTSrpXLCffsPaCEMY- Received: from IBM7FFA209F07C (c.ashby435@81.152.224.235 with login) by smtp118.bt.mail.ir2.yahoo.com with SMTP; 12 Mar 2013 10:56:15 +0000 UTC Message-ID: From: "Chris" To: References: <513E5241.40807@psk31.plus.com> Date: Tue, 12 Mar 2013 10:56:15 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Spam-Score: 0.0 (/) 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: Hi Eddie, Did you get my e-mail to you direct yesterday - no reply? Re: narrow keyboard QSO mode, have you thought of CW? Local station G6PKS and myself have been testing computer generated CW to see how fast we can reliably get it to work, 40 wpm is no problem. Faster than RTTY I think (?) and faster than we can type anyway! We have been using CWType/CWGet. Might be worth an experiment? Vy 73, Chris, G4AYT, Whitstable, Kent. ----- Original Message ----- From: g3zjo To: rsgb_lf_group@blacksheep.org Sent: Monday, March 11, 2013 9:53 PM Subject: LF: 630m Narrow Keyboard Mode [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.82.108.232 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Scan-Signature: 4e28719a46cd3d69582e1b8d1c614db3 Subject: LF: Re: 630m Narrow Keyboard Mode Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01CE1F10.38165AD0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: *** X-Spam-Status: No, hits=3.3 required=5.0 tests=FORGED_MUA_OUTLOOK, FROM_ENDS_IN_NUMS,HTML_30_40,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 x-aol-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mtain-mi01.r1000.mx.aol.com ; domain : btinternet.com DKIM : fail x-aol-sid: 3039ac1d7b89513f108216c3 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_0019_01CE1F10.38165AD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Eddie, Did you get my e-mail to you direct yesterday - no reply? Re: narrow keyboard QSO mode, have you thought of CW? Local station = G6PKS and myself have been testing computer generated CW to see how fast = we can reliably get it to work, 40 wpm is no problem. Faster than RTTY I = think (?) and faster than we can type anyway! We have been using = CWType/CWGet. Might be worth an experiment? Vy 73, Chris, G4AYT, Whitstable, Kent. ----- Original Message -----=20 From: g3zjo=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Monday, March 11, 2013 9:53 PM Subject: LF: 630m Narrow Keyboard Mode LF Searching for a Narrow Keyboard QSO mode suitable for QRP on 630m. I = went back to a program I used several years ago. Currently Testing GMFSK not to be confused with gMFSK which is a Linux = program. GMFSK is an FSK Mode using Varicode by JE3HHT Makoto Mori included in = MMVari.not new program it is of the usual high standard found in his = software. GMFSK has variable width, currently I am running at 15.625Hz wide. = 474.200 Dial 1900 tone frequency. JE3HHT provides fine documentation with his software, for some reason = all the other modes covered by MMVari are well covered but when he gets = to GMFSK he says that it is beyond the scope of the instructions. I have = yet to find more details about the mode.=20 This Mode should be better than RTTY and faster MFSK for higher power = stations too. 73 Eddie G3ZJO ------=_NextPart_000_0019_01CE1F10.38165AD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Eddie,
Did you get my e-mail to you direct = yesterday - no=20 reply?
Re: narrow keyboard QSO mode, have you = thought of=20 CW? Local station G6PKS and myself have been testing computer generated = CW to=20 see how fast we can reliably get it to work, 40 wpm is no problem. = Faster than=20 RTTY I think (?) and faster than we can type anyway! We have been using=20 CWType/CWGet. Might be worth an experiment?
Vy 73,
Chris, G4AYT, Whitstable, = Kent.
----- Original Message -----
From:=20 g3zjo=20
Sent: Monday, March 11, 2013 = 9:53=20 PM
Subject: LF: 630m Narrow = Keyboard=20 Mode

LF

Searching for a=20 Narrow Keyboard QSO mode suitable for QRP on 630m. I went back to a = program I=20 used several years ago.

Currently Testing GMFSK not to be = confused with=20 gMFSK which is a Linux program.

GMFSK is an FSK Mode using = Varicode by=20 JE3HHT Makoto Mori included in MMVari.not new program it is of the = usual high=20 standard found in his software.

GMFSK has variable width, = currently I=20 am running at 15.625Hz wide. 474.200 Dial 1900 tone = frequency.

JE3HHT=20 provides fine documentation with his software, for some reason all the = other=20 modes covered by MMVari are well covered but when h
e=20 gets to GMFSK he says that it is beyond = the scope of=20 the instructions. I have yet to find more details about the mode.=20

This Mode should = be better=20 than RTTY and faster MFSK for higher power stations = too.

73=20 Eddie G3ZJO

------=_NextPart_000_0019_01CE1F10.38165AD0--