>-----Original Message-----
>From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] 
>Sent: 29 April 2005 16:48
>To: piclist@mit.edu
>Subject: RE: [EE] RF encoding
>
>
>Michael Rigby-Jones <Michael.Rigby-Jones@bookham.com> wrote:
>> (e.g.) an (8,4) hamming code, an 8 bit code can represent 16 
>discrete 
>> values (same as manchester) but with the advantage of being able to 
>> correct 2 bit errors.
>
>Not quite. As I explained before, an (8,4) code is a SECDED 
>code -- it can correct single-bit errors and detect all 
>double-bit errors.
>
>And I also explained how to avoid using 0x00 and 0xFF as valid 
>code words.

Dave,

Thanks, I must have missed your post. I'll have a hunt through the
archives in a bit.  You are correct of course, a Hamming distance of
2d+1 is required where d is the number of correctable bits.  I hope I'm
correct in saying that an (8,4) code can detect up to 3 bit errors
though?

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist