At 12:33 PM 6/18/04 +0000, you wrote:
>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 :-)
:)
Well, I'm thinking of it using ARMs mostly as master devices using LIN
slaves for remote sensor/actuator. Although I do have a case where
reducing the number of connections is a big plus and the amount of
communication is small so....
>In order to make the protocol more interchangeable with "embedded
>networks" we came up with MicroMessaging one could say a subset of
>CANopen.
Have you read though the LIN 2.0 spec? I just recently got it. I had
previously been through the 1.3 spec at an earlier job. They have updated
the higher levels in particular. The LIN spec very nearly weaves itself
into the application layer. I can see where that would be quite useful
when you are integrating multiple third party slaves. With proper tools
the complete network interface would conceivably be built in a matter of
minutes.
" '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, IIIMessage
Re: [lpc2000] Re: LIN/Flexray
2004-06-18 by Robert Adsett
Attachments
- No local attachments were found for this message.