Lpc2000

> 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