Hi, Bob
 
	Actually my original message was directed at Dwayne reed ( or I
though it was :-) )....

	I was interested in the code that captures 40 bit samples for a
bit-bang serial routine and decides tha timing by analysing the samples
after capture and not in real time.
 
	I would love to see your code, specially if it extracts "timing
clues" from regular async serial streams.
 
Best regards,
Alexandre Guimaraes


-----Mensagem original-----
De: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] Em nome de Bob
Axtell
Enviada em: segunda-feira, 28 de janeiro de 2008 12:25
Para: Microcontroller discussion list - Public.
Assunto: Re: [EE] wierd idea: power LED blinks status barcode

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.

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

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