Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-ma03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 5CC3F38000092 for ; Wed, 13 Mar 2013 18:39:41 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UFsJG-0008VF-7E for rs_out_1@blacksheep.org; Wed, 13 Mar 2013 20:30:02 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UFsJF-0008V1-Jl for rsgb_lf_group@blacksheep.org; Wed, 13 Mar 2013 20:30:01 +0000 Received: from out1.ip04ir2.opaltelecom.net ([62.24.128.240]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UFsJB-0006Zo-Ca for rsgb_lf_group@blacksheep.org; Wed, 13 Mar 2013 20:30:00 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvkCAKvgQFFcGSQi/2dsb2JhbAANNsF0gmAEAYFvgx4BAQEBA3EYCwkPCRYPCQMCAQIBRRMIAQG4EZM1F41WByqBDYNAA5ZWlACBag X-IronPort-AV: E=Sophos;i="4.84,839,1355097600"; d="scan'208,217";a="403020047" Received: from host-92-25-36-34.as13285.net (HELO [127.0.0.1]) ([92.25.36.34]) by out1.ip04ir2.opaltelecom.net with ESMTP; 13 Mar 2013 20:29:36 +0000 Message-ID: <5140E1AD.5030606@psk31.plus.com> Date: Wed, 13 Mar 2013 20:29:33 +0000 From: g3zjo User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <513E5241.40807@psk31.plus.com> <513E6015.30901@psk31.plus.com> <514092DF.3030500@iup.uni-heidelberg.de> In-Reply-To: <514092DF.3030500@iup.uni-heidelberg.de> X-Antivirus: avast! (VPS 130313-0, 13/03/2013), Outbound message X-Antivirus-Status: Clean 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 Stefan I am sure Gary is keeping track of the modes he is testing. All I can say is that RTTY, Amtor and most common MFSK modes are too fast for use by lower power stations of for greater distance working, and wide often. I set my criteria on being able to communicate 2 way over 100Km from my wee station and Class D PA. JT Modes do the job but being not real keyboard modes and the limited message capability (everyone now knows I have no dog or a cat) put those in the boring category. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 7a5eab5982daca5912e6e97333848fe5 Subject: Re: LF: 630m Narrow Keyboard Mode Content-Type: multipart/alternative; boundary="------------050702020602020101040401" 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=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-sid: 3039ac1d600b5141002d0479 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. --------------050702020602020101040401 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Stefan I am sure Gary is keeping track of the modes he is testing. All I can say is that RTTY, Amtor and most common MFSK modes are too fast for use by lower power stations of for greater distance working, and wide often. I set my criteria on being able to communicate 2 way over 100Km from my wee station and Class D PA. JT Modes do the job but being not real keyboard modes and the limited message capability (everyone now knows I have no dog or a cat) put those in the boring category. Years before all the internet connected, time sync'd and bloated software arrived, work was done on narrow, slow MFSK modes. GMFSK has been the most sophisticated of these tried here up to now. Not only does it work but it is fast enough to allow full speed, live, 2 finger, arthritic grandad typing QSO's with no long lead in sync, or tail. If I am around using GMFSK I will be on 476.100. Getting more people interested so that there is a possibility of random QSO's, err, I will leave that to you. 73 Eddie P.S. Mal, yes missing him already. PPS. I had my first QRSS3 QSO today with G4AYT 167Km daytime path, not random though. On 13/03/2013 14:53, Stefan Schäfer wrote: > Hi Eddie, LF/MF, > > I'm a bit confused in the last days by the number of various digimodes > which have been tested. Gary started with RTTY which is fun and allows > real QSOs on 630m, apart from CW. But if each mode is done as a short > test to check its performance, then it quickly becomes boring. What i > would like to have is a mode which is used by several active amateurs, > a real QSO mode like CW. A mode that lasts longer than a day. I > thought that AMTOR-FEC could be useful but i didn't make any tests > yet. However if i have to assume that there will be 2 or 3 interested > QSO partners who will be available for a short test QSO and then QSY > to GADFDSMSFASKMDKFK-4 or whatever, then none of these modes are > actually interesting for me and i come back to CW where i can be sure > to find a QSO partner without announcing my activity before. Today, > tomorrow, next week and next year :-) > > What do you suggest? :-) > > 73, Stefan/DK7FC > > PS: And where is Mal? :-) > > > Am 11.03.2013 23:52, schrieb g3zjo: >> Sucess. >> >> Just a little more signal and this would have been a really good QSO >> over our path of 127Km conditions are not good tonight, my antenna >> current is down. >> >> Eddie >> >> On 11/03/2013 21:53, g3zjo wrote: >>> 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 getsto GMFSK he says that it is beyond the scope of the >>> instructions. I have yet to find more details about the mode. >>> >>> This Mode should be better than RTTY and faster MFSK for higher >>> power stations too. >>> >>> 73 Eddie G3ZJO >>> >> --------------050702020602020101040401 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Stefan

I am sure Gary is keeping track of the modes he is testing.

All I can say is that RTTY, Amtor and most common MFSK modes are too fast for use by lower power stations of for greater distance working, and wide often.
I set my criteria on being able to communicate 2 way over 100Km from my wee station and Class D PA. JT Modes do the job but being not real keyboard modes and the limited message capability (everyone now knows I have no dog or a cat) put those in the boring category.

Years before all the internet connected, time sync'd and bloated software arrived, work was done on narrow, slow MFSK modes. GMFSK has been the most sophisticated of these tried here up to now. Not only does it work but it is fast enough to allow full speed, live, 2 finger, arthritic grandad typing QSO's with no long lead in sync, or tail.

If I am around using GMFSK I will be on 476.100. Getting more people interested so that there is a possibility of random QSO's, err, I will leave that to you.

73 Eddie

P.S. Mal, yes missing him already.

PPS. I had my first QRSS3 QSO today with G4AYT 167Km daytime path, not random though.



On 13/03/2013 14:53, Stefan Schäfer wrote:
Hi Eddie, LF/MF,

I'm a bit confused in the last days by the number of various digimodes which have been tested. Gary started with RTTY which is fun and allows real QSOs on 630m, apart from CW. But if each mode is done as a short test to check its performance, then it quickly becomes boring. What i would like to have is a mode which is used by several active amateurs, a real QSO mode like CW. A mode that lasts longer than a day. I thought that AMTOR-FEC could be useful but i didn't make any tests yet. However if i have to assume that there will be 2 or 3 interested QSO partners who will be available for a short test QSO and then QSY to GADFDSMSFASKMDKFK-4 or whatever, then none of these modes are actually interesting for me and i come back to CW where i can be sure to find a QSO partner without announcing my activity before. Today, tomorrow, next week and next year :-)

What do you suggest? :-)

73, Stefan/DK7FC

PS: And where is Mal? :-)


Am 11.03.2013 23:52, schrieb g3zjo:
Sucess.

Just a little more signal and this would have been a really good QSO over our path of 127Km conditions are not good tonight, my antenna current is down.

Eddie

On 11/03/2013 21:53, g3zjo wrote:
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.

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

73 Eddie G3ZJO



--------------050702020602020101040401--