-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jan 28, 2008 at 07:24:32AM -0700, Bob Axtell wrote:
> David VanHorn wrote:
> >>         I searched everywhere I could thing of and did not find John's code
> >> or yours :-( Could you post some reference to it or repost the code ? It is
> >> a very interesting technique and I would love to see how you approached the
> >> "clock recovery".. I use bit-bang a lot for serial comms but never thought
> >> about using a bit buffer to make a better decision about the timing...
> >>     
> >
> > I'd be interested too.   I've used a single pin with my "pong" routine
> > (Ping just blips a bit N times) to output multiple bytes in
> > wide-narrow form, such that for any combination of timings, the byte
> > is the same length.  Helps enormously when you're capturing say 50
> > bytes of data on the scope.
> >   
> Are you guys talking to me? I have the PIC code as well as the DOS PC 
> receiver app for Manchester-
> like coding, which is not sensitive to timing errors. While I usually 
> send my code at 4mS per bit, it
> will work at 50mS/bit or at 1mS/bit just as well.
> 
> Let me know.

Send it over! Much appreciated.

(so long as I can combine it in GPLed code)

- -- 
http://petertodd.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHneZ13bMhDbI9xWQRAimvAJ93NduL2a/s96CNEIhro+IuAqwLjACZAc7Z
yIigkMag3SBr4owNPNONUjA=
=c0RP
-----END PGP SIGNATURE-----
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist