Lpc2000

Well SPI, I2C and even TTL can handle 10ft runs, I2C only requires 3 wires 
no matter how many sensors, SPI takes 3 + 1 per sensor, however I'm not 
sure on the noise tolerance.  I suspect you will be fine if you use 
shielded wiring, clock them low enough, use filter caps, and design your 
protocol to have a simple error detection algorithm.

-- Sean

At 17:31 2/10/2006, you wrote:
> > You say that you're designing the interface yourself, so you don't
>need to
> > use CAN, so what about other interfaces?  How much distance will
>there be
> > between the micro and the sensors?  How many sensors will you be
> > interfacing to?  If the distance is small then you can always use
>I2C or
> > SPI.  Even for medium distances these will work by adding in driver
> > chips.  If you have a longer distance, you could try RS485 or even
>RS232 or
> > even just plain TTL logic levels (possibly with a
>driver/isolator).  These
> > are simpler than CAN AFAIK.  How noisy is the environment where
>these will
> > need to operate?
> >
> > -- Sean
>
>It'll be about 10 ft of wire between sensor and controller. There
>doesn't need to be any other nodes on the network (at least that's
>what they say now). Data payload is about 3 bytes every 5mS and it'll
>be very noisy (automotive engine compartment) I suspect I could
>design it robust enough so that single packet loss could be
>tolerated.  Like I mentioned I have control over both ends of the
>system, so it could be any interface I see fit. I was thinking that
>CAN would be good for several reasons:
>It's a standard
>Noise resistant
>Easy to add to in the future
>
>That last one's the big deal, they swear that these are the only
>sensors they need on the system, but they made a big deal about
>wanting to tweek the algorithim and logging the results so I strongly
>suspect the sensor requirements are likely to change in unpredictable
>ways.
>
>-Denny
>
>
>
>
>
>
>
>SPONSORED LINKS
><http://groups.yahoo.com/gads?t=ms&k=Microcontrollers&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers&c=4&s=95&.sig=mfaAujKZXA2Z_vxre9sGnQ>Microcontrollers 
><http://groups.yahoo.com/gads?t=ms&k=Microprocessor&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers&c=4&s=95&.sig=9jjd2D3GOLIESVQssLmLsA>Microprocessor 
><http://groups.yahoo.com/gads?t=ms&k=Intel+microprocessors&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers&c=4&s=95&.sig=OMnZuqMZX95mgutt4B-tDw>Intel 
>microprocessors
><http://groups.yahoo.com/gads?t=ms&k=Pic+microcontrollers&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers&c=4&s=95&.sig=Malspbd0T4Rq3M4Q0nHrfw>Pic 
>microcontrollers
>
>
>----------
>YAHOO! GROUPS LINKS
>
>    *  Visit your group "<http://groups.yahoo.com/group/lpc2000>lpc2000" 
> on the web.
>    *
>    *  To unsubscribe from this group, send an email to:
>    * 
> <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>lpc2000-unsubscribe@yahoogroups.com 
>
>    *
>    *  Your use of Yahoo! Groups is subject to the 
> <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
>
>
>----------