The manchester encoding only tells you how to transmit ones and zeros. Specific implementations need to know when a valid transmission has started and ended. Sometimes these start and ending sequences are manchester encoded, and sometimes they are specifically illegal for manchester encoding so they are easy to spot among manchester data. In this case I bet that they are simply long start and stop 'bits'. You may also find that the first manchester encoded bit is always the same so that after the start low you always have a high at the beginning of the machester encoding, which allows you to easily synchronize where the actual transitions are in the manchester stream. -Adam Matt wrote: >On Fri, 16 Jul 2004 23:29:35 -0400, M. Adam Davis wrote: > > >>Looks like it might be manchester encoding to me. Look that up and see >>if it matches your expectations. >> >>-Adam >> >> >> > >This seems to be getting closer to what this might be, but how does >the long gap at the end of the 7 digit's code fit into the manchester >encoding method? > >Long gaps like that seem to not be allowed in machester encoding. > >-Matt > >-- >http://www.piclist.com hint: The list server can filter out subtopics >(like ads or off topics) for you. See http://www.piclist.com/#topics > > > > > -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.