Android for Automotive - Yes We CAN

Android for Automotive – Yes We CAN

Michael Uelschen, Ralph Rakers
Hochschule Osnabrück

Titelmasterformat durch
Yes We CAN
Klicken bearbeiten
Overview
_ Introduction
_ Innovation Cycle Dilemma
_ Our Approach
_ Electric Vehicle Charging App*
_ Results
_ Conclusion
_ Discussion
* Supported by Lemförder Electronic GmbH, Espelkamp (ZF)

droidcon.2012 | A Android for Automotive | Uelschen, Rakers 2

Yes We CAN

INTRODUCTION


Yes We CAN
Klicken bearbeiten
Distributed System
_ A modern car is a distributed system with up
to 100 nodes.
_ Several networks with different physical layers
and protocols are used depending on the
application.
_ Controller Area Network is central network
and connects engine, transmission, and driver
information and control etc.


Yes We CAN
Klicken bearbeiten
Controller Area Network (CAN)
_ Developed by BOSCH and Intel in 1983.
_ Major design goals:
 High reliability
 Low costs
_ Event-based communication with short
messages (130 bits) with high bandwidth (up
to 1 Mbit/s).
_ CSMA/CD to fulfill real time requirements.

Yes We CAN
Klicken bearbeiten
CAN Message (Data Frame)

1 11 1 1 1 4 0-64 16 2 7

SOF Ident RTR IDE r. DLC Data Field CRC ACK EOF

Type of the message Data length and payload of the message

_ Frame is read by all nodes (no address field).
_ Data field depends on data length counter.


Yes We CAN

INNOVATION CYCLE DILEMMA


Yes We CAN
Klicken bearbeiten
Innovation Cycles -- Examples
1. CAN Bus: 10 years
 Development by BOSCH started in 1983
 Introduction to Mercedes S-class in 1991
 Introduction to lower-mid segment cars in 2001
2. Apple iPod: 1 year
 Introduced in 2001
 5th generation introduced in 2005
 Innovation cycle shorter than 1 year
3. Mobile phone: < 1 year
 New devices every 6 months or less

Yes We CAN
Consumer vs. Automotive Domain
Consumer Electronics Domain Automotive Domain
_ “Fast moving” technologies _ Vehicle related technologies
 short lifecycles  long lifecycles
 high requirements on  high requirements on
• Performance • Quality
• Flexibility • Reliability
 high volume / low cost  low volume
 driven by IT, Telecom und CE  driven by vehicle industry
 new upcoming applications  fix attached components
 fast growing performance  scalable over segments
requirements  automotive ease to use
_ Open System _ Reliable System


Yes We CAN

OUR APPROACH


Yes We CAN
Klicken bearbeiten
Linux inside the car?
_ Linux was ignored for automotive applications
 Development model : community-based
 License model : open source (e.g. GPL)
 Patent situation : owner of the rights
_ There are some changes:
 GENIVI initiative to enable Linux for automotive
 MeeGo/Tizen platform for In-Vehicle information
_ Our idea: Using Android-based Linux-system


Yes We CAN
Klicken bearbeiten
Our Idea
_ Android is not just a technology but also a
complete eco-system (e.g. Android Market).
_ Integration of an Android-based head-unit
into automotive network (CAN).
_ Show the interaction with automotive
development tools (here: CANoe simulation).
_ Developing App: Control and visualization of
the charging process for electric vehicle.


Yes We CAN
Hardware Platform
_ Freescale i.MX51 EVK
_ Cortex A8@800 MHz
_ 512 MB DDR2
_ 7“ WVGA Touchscreen
_ Other peripherals as USB,
Ethernet, SD, …
_ No automotive interfaces
integrated on the eval
board.
_ Android patches by
Freescale.

Yes We CAN
CAN Interface
_ PEAK System PCAN
_ CAN-to-USB Adapter
_ USB 1.1 (2.0)
_ CAN Specification
2.0A/B
_ Linux-driver (GPL)
available for kernel 2.4-
3.0


Yes We CAN
Klicken bearbeiten
Socket-CAN
_ CAN Implementation for Linux-Kernel
 Project from Volkswagen Research
 Official part since Kernel 2.6.25
 Configuration via make menuconfig
_ BSD-Sockets API
 socket(), bind(), read(), write(), close()
_ CAN-Frame defined in <linux/can.h>
struct can_frame ping;
ping.can_id = 0x123;
ping.can_dlc = 1;
ping.data[0] = 0xFF;


Yes We CAN
Klicken bearbeiten
Native CANComLib Implementation
_ Shared library CANComLib (~ 200 LOC) encapsulates
socket functions like
 socket(), bind(), read(), write(), close()
_ Provides an easy-to-use interface to send and receive
CAN messages:
int initialize();
struct can_frame receive_can(struct can_filter filter);
void send_can(struct can_frame sendFrame);
int terminate();

_ Android applications call the native library by using
the Android NDK.

Yes We CAN

ELECTRIC VEHICLE CHARGING APP


Yes We CAN
Klicken bearbeiten
Vehicle-to-Grid Communication
_ The communication between EV and charging
station is based on ISO61851 and ISO15118.
_ Several services are defined
 Battery Charging
 Internet Access
 User-defined Service
_ App to initialize, to control and to visualize the
charging process based on ISO standards.


Yes We CAN
System Overview (Development)
Electric Vehicle
Touch Screen

Peak-Box

Head- Charging
USB
CAN-Netzwerk PC
Unit ECU Powerline Communication (PLC)

Freescale i.MX51

CANcaseXL
USB

PC

Residual Bus Simulation with CANoe


Yes We CAN
SystemKlicken bearbeiten
Overview (Components)


Yes We CAN
SystemKlicken bearbeiten
Overview (Bus Simulation)


Yes We CAN

RESULTS


Yes We CAN
Statechart UI -- Welcome
tm Zustandsmaschine

Initial

Lade-Applikation starten

Start

Unbekannte Ladesäule angeschlossen

Dienst
Authentifizierung
Ladeparameter
Ladetarife

Ladeparameter eingegeben

Laden

Ladevorgang manuell beendet | Ladeziel erreicht

Ladeziel erreicht

Lade-Applikation beendet

Final

Yes We CAN
Statechart UI -- Parameter
tm Zustandsmaschine

Initial


Start


Dienst
Authentifizierung
Ladeparameter
Ladetarife


Laden


Ladeziel erreicht


Final

Yes We CAN
Statechart UI -- Charging
tm Zustandsmaschine

Initial


Start


Dienst
Authentifizierung
Ladeparameter
Ladetarife


Laden


Ladeziel erreicht


Final

Yes We CAN
Statechart UI -- Charging ended
tm Zustandsmaschine

Initial


Start


Dienst
Authentifizierung
Ladeparameter
Ladetarife


Laden


Ladeziel erreicht


Final

Yes We CAN

CONCLUSION


Yes We CAN
Klicken bearbeiten
Conclusion
_ How to enable Android-System to
communicate with automotive CAN network.
_ Approach can be transferred to other domains
using CAN e.g. automation.
_ Product would require deeper integration of
the components (e.g. CAN controller).
_ Future Trends:
 Using multicore and/or virtualization to combine
Android and RTOS on same hardware (CPU).


Yes We CAN
Bye Klicken bearbeiten

_ Thank you very much for your attention!


Yes We CAN
Klicken bearbeiten
Contact Information
Prof. Dr.-Ing. Michael Uelschen
University of Applied Sciences Osnabrück
Faculty Engineering and Computer Sciences
Laboratory for Computer Engineering
Barbarastraße 16, 49076 Osnabrück (Germany)

Postal Address : P.O. Box 1940, 49009 Osnabrück
m.uelschen@hs-osnabrueck.de
Tel.: +49 (0)541 / 969 3885
Room: SI0212


Android for Automotive - Yes We CAN

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Android for Automotive - Yes We CAN

Similaire à Android for Automotive - Yes We CAN (20)

Plus de Droidcon Berlin

Plus de Droidcon Berlin (20)

Dernier

Dernier (20)

Android for Automotive - Yes We CAN