01-11-2012, 04:11 PM
In-Vehicle Networking
In-Vehicle.pdf (Size: 637.48 KB / Downloads: 46)
History
Automotive networking has always relied
on standardized serial communications
hardware, but it was rarely compatible.
In the late 1990s, the LIN Consortium
was founded by five European
automakers, Volcano Automotive Group
and Freescale (at the time Motorola)
to solve this problem. The first fully
implemented version of the new LIN
specification was published in November
2002 as LIN version 1.3. In September
2003, version 2.0 was introduced to
expand configuration capabilities and
make provisions for significant additional
diagnostics features and tool interfaces.
Some North American automakers were
concerned about the rising complexity
and lack of direct North American
representation in the LIN Consortium.
As a result of their concerns, a Society
of American Engineers (SAE) task force,
which was part of the committee that
standardizes vehicle networking, was
formed to help ensure LIN 2.0 was
suitable for global implementation.
Although a full consensus was never
reached, the task force published the
SAE J2602 Recommended Practice for
LIN Networks document, which seeks
to fully specify ambiguities and optional
features of the LIN 2.0 specification.
Slave LIN Interface Controller (SLIC)
Enables Higher Integration
Freescale offers an exceptional embedded
SLIC module that automates LIN message
handling to help increase performance while
reducing development time and cost. It allows
you to devote more CPU to the application
and gives you the ability to use ROM devices
or state machines.
SLIC helps increase performance in
several ways. True auto-synchronization
and auto-bauding find LIN frames and
automatically adjust the baud rate without
CPU intervention. SLIC reduces interrupt
processing up to 83 percent over UART
solutions with only two interrupts for any
message. This makes it possible to use
SYNCH data from messages to trim the
oscillator. SLIC also eliminates many steps
normally required by UART solutions (trim
oscillator, detect break, measure sync
signal, adjust baud rate, calculate and
verify checksum, handle individual data
bytes, detect errors and more).
SLIC helps reduce development time by
eliminating message processing steps,
simplifying and minimizing driver code to
as small as 120 bytes (refer to Freescale’s
Application Note AN2633). Minimized driver
code translates into shortened debug and
development time, which enables you to
use your engineering time to debug the
application rather than LIN communication.
RKE Systems
RKE systems make it possible to unlock
doors and release trunk latches remotely
using a key fob or other similar device. Many
include some security functionality, such
as anti-theft alarms, remote start and panic
buttons. Freescale was an early pioneer
in RKE system development and is now
the first to offer an integrated low-voltage
microcontroller with embedded RF for RKE
applications developers.
In-Vehicle.pdf (Size: 637.48 KB / Downloads: 46)
History
Automotive networking has always relied
on standardized serial communications
hardware, but it was rarely compatible.
In the late 1990s, the LIN Consortium
was founded by five European
automakers, Volcano Automotive Group
and Freescale (at the time Motorola)
to solve this problem. The first fully
implemented version of the new LIN
specification was published in November
2002 as LIN version 1.3. In September
2003, version 2.0 was introduced to
expand configuration capabilities and
make provisions for significant additional
diagnostics features and tool interfaces.
Some North American automakers were
concerned about the rising complexity
and lack of direct North American
representation in the LIN Consortium.
As a result of their concerns, a Society
of American Engineers (SAE) task force,
which was part of the committee that
standardizes vehicle networking, was
formed to help ensure LIN 2.0 was
suitable for global implementation.
Although a full consensus was never
reached, the task force published the
SAE J2602 Recommended Practice for
LIN Networks document, which seeks
to fully specify ambiguities and optional
features of the LIN 2.0 specification.
Slave LIN Interface Controller (SLIC)
Enables Higher Integration
Freescale offers an exceptional embedded
SLIC module that automates LIN message
handling to help increase performance while
reducing development time and cost. It allows
you to devote more CPU to the application
and gives you the ability to use ROM devices
or state machines.
SLIC helps increase performance in
several ways. True auto-synchronization
and auto-bauding find LIN frames and
automatically adjust the baud rate without
CPU intervention. SLIC reduces interrupt
processing up to 83 percent over UART
solutions with only two interrupts for any
message. This makes it possible to use
SYNCH data from messages to trim the
oscillator. SLIC also eliminates many steps
normally required by UART solutions (trim
oscillator, detect break, measure sync
signal, adjust baud rate, calculate and
verify checksum, handle individual data
bytes, detect errors and more).
SLIC helps reduce development time by
eliminating message processing steps,
simplifying and minimizing driver code to
as small as 120 bytes (refer to Freescale’s
Application Note AN2633). Minimized driver
code translates into shortened debug and
development time, which enables you to
use your engineering time to debug the
application rather than LIN communication.
RKE Systems
RKE systems make it possible to unlock
doors and release trunk latches remotely
using a key fob or other similar device. Many
include some security functionality, such
as anti-theft alarms, remote start and panic
buttons. Freescale was an early pioneer
in RKE system development and is now
the first to offer an integrated low-voltage
microcontroller with embedded RF for RKE
applications developers.