Lpc2000

As already mentioned, the nice thing about LIN is the simple 1-wire 
signal layer - this is really made for the smallest controllers with 
limited horsepower (makes you wonder why we talk about it in this 
group :-)

In order to make the protocol more interchangeable with "embedded 
networks" we came up with MicroMessaging – one could say a subset of 
CANopen. So a MicroMessaging network could use LIN (or other lowest 
cost serial channels like I2C), but could also be interfaced to 
CANopen – providing a transparent network infrastructure across 
serial network technologies.

For more info see www.MicroMessaging.com and www.MicroCANopen.com 

Olaf
Tutor at ESAcademy
www.esacademy.com

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> At 10:04 PM 6/17/04 +0000, you wrote:
> >In which markets do you expect LIN and Flexray to be valuable ?
> >Only automotive ?
> 
> Automotive is certainly their origin but I do expect to see other 
> uses.  Flexray I would expect to enter certain industrial markets 
just as 
> CAN did.  The question there is how big a niche it can find when 
compared 
> to existing CAN implementations and various other fieldbuses.
> 
> CAN is being adopted in the industrial electric vehicle market 
(it's 
> actually being used for some drive-by-wire applications), Flexray 
would 
> actually be a better fit there but it will take some time to grow 
into it.
> 
> LIN I see being used (at least the signalling layer) just about 
everywhere 
> that needs a cheap 1-wire serial bus.  I'm working on some stuff 
that would 
> make use of LIN, whether it will ever see the light of day is still 
open to 
> question at the moment but the bus makes sense in the application.
> 
> Robert
> 
> " 'Freedom' has no meaning of itself.  There are always 
restrictions,
> be they legal, genetic, or physical.  If you don't believe me, try 
to
> chew a radio signal. "
> 
>                          Kelvin Throop, III