<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>Kip, / Eric</DIV>
<DIV> </DIV>
<DIV>Was just wondering how he might deal with many sources of PWM from many
processors / sensors.. with limited number of input capture resources?</DIV>
<DIV> </DIV>
<DIV>Certainly one processor could time division multiplex (if that is the
correct term-- or serialize) PWM stream, but with many processors maybe
there would be a way to request a signal so as not to have redundant data missed
by receiving processor that is using a multiplexer tied to input capture
pin.</DIV>
<DIV> </DIV>
<DIV>Interesting a friend uses components designed for an automotive throttle
control that is exactly compatible with RC servo pulse 1.0 to 2.0 ms. (If I did
not mention)</DIV>
<DIV> </DIV>
<DIV>Wonder what would be a practical frequency upper-limit for Eric's
application?</DIV>
<DIV> </DIV>
<DIV>One thing that does scare me about using more complex forms of
communication such as I2C...</DIV>
<DIV>is you have to make sure you have carefully covered the bases to avoid
states that might hang up a system whereas with PWM or analog performance might
suffer if implementation is not perfect (free from noise...), but at least
typically you won't experience a crash. Just me talking.</DIV>
<DIV> </DIV>
<DIV>Ron</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></FONT><BR><BR><BR><DIV><FONT style="color: black; font: normal 10pt ARIAL, SAN-SERIF;"><HR style="MARGIN-TOP: 10px">The year's hottest artists on the red carpet at the Grammy Awards. <A title="http://music.aol.com/grammys?NCID=aolcmp00300000002565" href="http://music.aol.com/grammys?NCID=aolcmp00300000002565" target="_blank">AOL Music takes you there.</A></FONT></DIV></BODY></HTML>