Return-Path: Received: (qmail 19078 invoked from network); 16 Aug 2002 06:51:25 -0000 Received: from marstons.services.quay.plus.net (212.159.14.223) by mailstore with SMTP; 16 Aug 2002 06:51:25 -0000 Received: (qmail 26064 invoked by uid 10001); 16 Aug 2002 06:55:48 -0000 Received: from post.thorcom.com (193.82.116.70) by marstons.services.quay.plus.net with SMTP; 16 Aug 2002 06:55:48 -0000 X-SQ: A Received: from majordom by post.thorcom.com with local (Exim 3.33 #2) id 17fcTT-00014v-00 for rsgb_lf_group-outgoing@blacksheep.org; Fri, 16 Aug 2002 09:28:51 +0100 Received: from mail.mcf.com ([165.254.158.18]) by post.thorcom.com with esmtp (Exim 3.33 #2) id 17fcTS-00014q-00 for rsgb_lf_group@blacksheep.org; Fri, 16 Aug 2002 09:28:50 +0100 Received: from w2ksn (192.55.122.104) by mail.mcf.com with ESMTP (Eudora Internet Mail Server 3.1.3) for ; Fri, 16 Aug 2002 02:36:41 -0400 Message-ID: <001901c244ee$bb1e5e30$687a37c0@w2ksn> From: "Stewart Nelson" To: rsgb_lf_group@blacksheep.org References: <76.20a5d68e.2a8954d1@aol.com> <5.1.0.14.0.20020813153546.00aa3f28@gemini.herts.ac.uk> <004101c244a2$6b6b73b0$687a37c0@w2ksn> <006e01c244ad$addf03a0$612565d5@oemcomputer> Subject: LF: Re: Limiter in Jason reception Date: Thu, 15 Aug 2002 23:32:43 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Sender: Hi Johan and all, > does your Jason decoder try to keep track of symbol timing > or does it only wait looking for the next transition (as the native > decoder)? It averages over the last 16 or so symbols (~8 characters) to find the symbol boundaries. > If timing is important, how will slight timing errors affect > performance? The present decoder is not hurt much by a symbol frequency error of a few parts per thousand. But future decoders might examine longer stretches. If symbol timing is derived from even a mediocre crystal oscillator, e.g. 100 ppm error, that should be adequate for presently foreseen enhancements. Of course, if you could use same clock as generates the carrier, that would be even better. > You mentioned "symbol phase", do you mean MSNibble/LSNibble > or does the decoder expect the signal to be "phase coherent"? The current decoder is noncoherent. One might expect that 3 dB could be gained from coherent detection, but that is not the case with M-ary FSK systems. In fact, as M goes to infinity, the performance asymptotically approaches the Shannon limit, even when noncoherent detection is used! For M = 16, only about 1 dB gain is possible. However, if many symbols are transmitted for each symbol of useful information content (because error correction is employed, and/or integration is performed over multiple repetitions of the message), then the gain from coherent detection is greater. Such a system would not interoperate with the current Jason standard, but could potentially offer much better performance. If your PIC design is flexible and could eventually handle a new format, it would be nice if it could avoid losing coherency on symbol transitions. > playing with a PIC/DDS Jason beacon, currently on HF, 7000.038 kHz...) I don't recommend my decoder for HF; it was designed with the stability of a typical LF path in mind. When there is significant multipath, or the effective height of the ionosphere is rapidly changing, Alberto's decoder will perform much better. 73, Stewart KK7KA