Yes we can

1,305 views
1,194 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,305
On SlideShare
0
From Embeds
0
Number of Embeds
480
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Yes we can

  1. 1. Android for Automotive – Yes We CAN Michael Uelschen, Ralph Rakers Hochschule Osnabrück
  2. 2. Titelmasterformat durchYes We CAN Klicken bearbeitenOverview_ 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
  3. 3. Yes We CAN INTRODUCTIONdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 3
  4. 4. Titelmasterformat durchYes We CAN Klicken bearbeitenDistributed 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.droidcon.2012 | A Android for Automotive | Uelschen, Rakers 4
  5. 5. Titelmasterformat durchYes We CAN Klicken bearbeitenController 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.droidcon.2012 | A Android for Automotive | Uelschen, Rakers 5
  6. 6. Titelmasterformat durch Yes We CAN Klicken bearbeiten CAN Message (Data Frame)1 11 1 1 1 4 0-64 16 2 7SOF Ident RTR IDE r. DLC Data Field CRC ACK EOFType 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. droidcon.2012 | A Android for Automotive | Uelschen, Rakers 6
  7. 7. Yes We CAN INNOVATION CYCLE DILEMMAdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 7
  8. 8. Titelmasterformat durchYes We CAN Klicken bearbeitenInnovation Cycles -- Examples1. CAN Bus: 10 years  Development by BOSCH started in 1983  Introduction to Mercedes S-class in 1991  Introduction to lower-mid segment cars in 20012. Apple iPod: 1 year  Introduced in 2001  5th generation introduced in 2005  Innovation cycle shorter than 1 year3. Mobile phone: < 1 year  New devices every 6 months or lessdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 8
  9. 9. Yes We CANConsumer vs. Automotive DomainConsumer 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 Systemdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 9
  10. 10. Yes We CAN OUR APPROACHdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 10
  11. 11. Titelmasterformat durchYes We CAN Klicken bearbeitenLinux 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-systemdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 11
  12. 12. Titelmasterformat durchYes We CAN Klicken bearbeitenOur 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.droidcon.2012 | A Android for Automotive | Uelschen, Rakers 12
  13. 13. Yes We CANHardware 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.droidcon.2012 | A Android for Automotive | Uelschen, Rakers 13
  14. 14. Yes We CANCAN 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.0droidcon.2012 | A Android for Automotive | Uelschen, Rakers 14
  15. 15. Titelmasterformat durchYes We CAN Klicken bearbeitenSocket-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;droidcon.2012 | A Android for Automotive | Uelschen, Rakers 15
  16. 16. Titelmasterformat durchYes We CAN Klicken bearbeitenNative 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.droidcon.2012 | A Android for Automotive | Uelschen, Rakers 16
  17. 17. Yes We CAN ELECTRIC VEHICLE CHARGING APPdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 17
  18. 18. Titelmasterformat durchYes We CAN Klicken bearbeitenVehicle-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.droidcon.2012 | A Android for Automotive | Uelschen, Rakers 18
  19. 19. Yes We CANSystem 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 CANoedroidcon.2012 | A Android for Automotive | Uelschen, Rakers 19
  20. 20. Titelmasterformat durchYes We CANSystemKlicken bearbeiten Overview (Components)droidcon.2012 | A Android for Automotive | Uelschen, Rakers 20
  21. 21. Titelmasterformat durchYes We CANSystemKlicken bearbeiten Overview (Bus Simulation)droidcon.2012 | A Android for Automotive | Uelschen, Rakers 21
  22. 22. Yes We CAN RESULTSdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 22
  23. 23. Yes We CAN Statechart UI -- Welcometm 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 droidcon.2012 | A Android for Automotive | Uelschen, Rakers 23
  24. 24. Yes We CAN Statechart UI -- Parametertm 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 droidcon.2012 | A Android for Automotive | Uelschen, Rakers 24
  25. 25. Yes We CAN Statechart UI -- Chargingtm 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 droidcon.2012 | A Android for Automotive | Uelschen, Rakers 25
  26. 26. Yes We CAN Statechart UI -- Charging endedtm 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 droidcon.2012 | A Android for Automotive | Uelschen, Rakers 26
  27. 27. Yes We CAN CONCLUSIONdroidcon.2012 | A Android for Automotive | Uelschen, Rakers 27
  28. 28. Titelmasterformat durchYes We CAN Klicken bearbeitenConclusion_ 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).droidcon.2012 | A Android for Automotive | Uelschen, Rakers 28
  29. 29. Titelmasterformat durchYes We CANBye Klicken bearbeiten_ Thank you very much for your attention!droidcon.2012 | A Android for Automotive | Uelschen, Rakers 29
  30. 30. Titelmasterformat durchYes We CAN Klicken bearbeitenContact InformationProf. Dr.-Ing. Michael UelschenUniversity of Applied Sciences OsnabrückFaculty Engineering and Computer SciencesLaboratory for Computer EngineeringBarbarastraße 16, 49076 Osnabrück (Germany)Postal Address : P.O. Box 1940, 49009 Osnabrückm.uelschen@hs-osnabrueck.deTel.: +49 (0)541 / 969 3885Room: SI0212droidcon.2012 | A Android for Automotive | Uelschen, Rakers 30

×