Proposal Rev.

01

Development
Proposals
for
Unified Car Sharing/Trip Terminal

Jan. 2014
목차

1. Scope
2. Block diagram
3. Operating & Service Processing
4. Developing Itinerary
5. Cost Analysis for Man-Power
6. Cost Analysis for Proto Production
7. Issues

Reference. OBD-II signal protocols

-2-
1. Scope

 Embedded Linux H/W  Micro Controller Used

 ARM926EJ Base  32Bit Risc Micro COntroller
 RAM : Mobile DDR2  RAM : Mobile DDR2
 Flash : Serial Flash or NAND Flash)  Flash : Internal Flash and RAM)
 USB : Host 1.1 Full Speed and Device 2.0  USB : Master or Device
 UART : 2 Port  UART : 6 Port
 Ethernet : 10/100Mbps  Ethernet : 10/100Mbps

 Peripherals
 GPS Receiver (Galileo/GLONASS)
 WCDMA 3G Interface (for KT)
 Wifi 802.11b/g/n
 Blackbox HD
 RFID Card Reader (Additional Parts)
 USB 1.1, 2.0 (Optional)
 Bluetooth (Optional)
 Peripherals
 GPS Receiver (Galileo/GLONASS)
 WCDMA 3G Interface (for KT)
 RFID Card Reader (Additional Parts)
 USB 1.1, 2.0 (Optional)
 Bluetooth (Optional)

 Car Interface  Car Interface

 OBD Interface (KOBD/EODB etc.)  OBD Interface (KOBD/EODB etc.)
 Power Interface  Power Interface

-3-
 2. Block Diagram

For Linux Only

RFID Blackbox
Reader

Development USB
Optional
Objective
For Linux Only
UART GPS
WiFi Satellite
Embedded 802.11b/g/n
(K)OBD
Interface
UART Linux
or
UART
MiCOM GPS
USB Optional Receiver

Cellular

-4-
3. Operating & Service Processing

Blackbox

GPS
RFID Image Satellite
Reader &
Inf Event
or
ma ing
ti on os ition
P a
Dat

Unified
Terminal
Sensing (from OBD)
• Status of Start
• Batt. Voltage

ro st n
nt ue tio • Fuel Guage
lD &
Co Req ma

a
• Total Travel
at
r

Cellular
fo

• Sensing Data etc…

In

Information Controls
• User Data • Door Lock/Unlock
Server
• GPS Data • Starting ON/OFF
• Image & Event • Vehicle Horn
• Status of Start • Trunk ON/OFF
• Batt. Voltage
• Fuel Guage
• Total Travel
• Sensing Data

-5-
4. Development Itinerary

Weekly Schedule
Itinerary
Item Remarks
Step W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13

Feasibility 　 　 　 　 　 　 　 　 　 　 　
Schematic Design 　 　 　 　 　 　 　 　 　 　
Component Purchase 　 　 　 　 　 　 　 　 　
H/W Artwork 　 　 　 　 　 　 　 　 　 　
PCB Production 　 　 　 　 　 　 　 　 　 　 　
PBA Assembly 　 　 　 　 　 　 　 　 　 　 　 　
Test 　 　 　 　 　 　 　 　
Feasibility 　 　 　 　 　 　 　 　 　 　 　
Linux Kernal Parts (for Linux)
　
RTOS Parts (For Micom)
GPS Interface 　 　 　 　 　 　 　 　 　 　 　

S/W Device RFID Reader Interface 　 　 　 　 　 　 　 　 　 　 　

Driver Blackbox Interface 　 　 　 　 　 　 　 　 　 　
PGM
Wifi Interface 　 　 　 　 　 　 　 　
ODB Interface
Intraction with Server(in KT) 　 　 　 　 　 　 　 　 　
Interlock Test 　 　 　 　 　 　 　 　 　
System
Check & Backup 　 　 　 　 　 　 　 　 　 　 　
Apparatus (Mockup or Molding) 　 　 　 　 　 　
Report & Review 　 　 　 　 　 　 　 　 　 　 　 　 　
Note : For Linux For Micom Variables Only Linux

-6-
5. Cost Analysis for Man-Power

Man Month [MM] Cost [10K ₩]

Remarks
Item Position Job Months Total Per Total
Monthly
Linux Micom Linux Micom 1-MM Linux Micom 　

Admin. Director . Project Management 0.2 3.0 2.10 0.6 0.42 1,000 600 420 　

. Schematic Design
High . Component Survey 1.0 3.0 2.10 3.0 2.10 850 2,550 1,785 　
. Function Test

H/W
. H/W Assitante
. Component Purchasing
MiD 0.3 3.0 2.10 0.9 0.63 400 360 252 　
. Production
. Quality Control

. Linux Porting
S/W High . Device Driver Programming 1.0 3.0 2.10 3.0 2.10 600 1,800 1,260 　
. Test & Function Verify

Grand Total (3-Months) 2.5 - - 7.5 5.25 - 5,310 3,717 　

-7-
6. Cost Analysis for Proto Production

Cost [10K ₩]
Item Job Step Q'ty Remarks
U/P T/P

. PCB Artwork 1 250 250

Sample
. PCB Production 1 60 60
(10 ea)
H/W
Sample
. PBA Assembly 1 100 100
(10 ea)

stock
. Component 10 20 200
Problem ???

Grand Total (3-Months) 610 　

-8-
7. Issues

No
Issue Target Discussion & Finalize Remarks
.

1 개발완료시점 기간고려 ( 약 3 개월 )

2 Target Price 130( 천원 ) : Mi- PBA Ass’y 제외

com Linux 시 30% Up
3 WCDMA M2M server 운용현황 ?

- 동영상 처리 초당 Frame 수 ?
4 - Event 영상 화질 ? Black Box 관련
- Channel 2 채널 ?
5 Sample 비용 분담

사별 역할 분담

6 양산 방법 결정

7 기타 OBD Protocol?

-9-
 Reference. OBD-II signal protocols

There are five signaling protocols that are permitted with the OBD-II interface. Most vehicles implement only one of the protocols. It is
often possible to deduce the protocol used based on which pins are present on the J1962 connector:battery ground) and pin 16 (bat -
tery positive).
SAE J1850 PWM (pulse-width modulation) — 41.6 kB/sec, stan- ISO 14230 KWP2000 (Keyword Protocol 2000)
dard of the Ford Motor Company) pin 7: K-line
pin 2: Bus+ pin 15: L-line (optional)
pin 10: Bus– Physical layer identical to ISO 9141-2
High voltage is +5 V Data rate 1.2 to 10.4 kBaud
Message length is restricted to 12 bytes, including CRC Message may contain up to 255 bytes in the data field
Employs a multi-master arbitration scheme called 'Carrier ISO 15765 CAN (250 kBit/s or 500 kBit/s). The CAN protocol was devel-
Sense Multiple Access with Non-Destructive Arbitration' (C- oped by Bosch for automotive and industrial control. Unlike other OBD pro-
SMA/NDA) tocols, variants are widely use outside of the automotive industry. While it
SAE J1850 VPW (variable pulse width) — 10.4/41.6 kB/sec, stan- did not meet the OBD-II requirements for U.S. vehicles prior to 2003, as of
dard of General Motors) 2008 all vehicles sold in the US are required to implement CAN as one of
pin 2: Bus+ their signaling protocols.
Bus idles low pin 6: CAN High
High voltage is +7 V pin 14: CAN Low
Decision point is +3.5 V
Message length is restricted to 12 bytes, including CRC Note.
Employs CSMA/NDA All OBD-II pin outs use the same connector, but different pins are
ISO 9141-2. This protocol has an asynchronous serial data rate of used with the exception of pin 4 (battery ground) and pin 16 (battery
10.4 kBaud. It is somewhat similar to RS-232; however, the signal positive).
levels are different, and communications happens on a single, bidi-
rectional line without additional handshake signals. ISO 9141-2 is
primarily used in Chrysler, European, and Asian vehicles.
pin 7: K-line
pin 15: L-line (optional)
UART signaling
K-line idles high, with a 510 ohm resistor to V batt
The active/dominant state is driven low with an open-collec-
tor driver.
Message length is Max 260Bytes. Data field MAX 255.

-10-