Difference between revisions of "Driver ID Specs"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 16: | Line 16: | ||
Send a driver identification code to FW via RS232(mini HDMI Port) that will be logged and attached to events header. | Send a driver identification code to FW via RS232(mini HDMI Port) that will be logged and attached to events header. | ||
+ | Generate audio notification if the identification needs to be done. | ||
− | == Hardware Requirements == | + | Generate audio notification if the serial connection between reader and Idrive X1P was lost. |
+ | |||
+ | == Hardware Requirements == | ||
+ | |||
+ | * RS232 connection using Idrive X1P external connector - mini HDMI; | ||
+ | * 5V power connection using Idrive X1P external connector - mini HDMI; | ||
== Software Requirements == | == Software Requirements == |
Latest revision as of 15:41, 25 September 2013
Introduction
Driver ID component is a Idrive X1P accessory that provides driver identification based on iButton key and a one wire protocol reader.
Overall Description
Driver ID component will contain the following:
* iButton key(http://www.maximintegrated.com/products/ibutton/ibuttons/)
* Idrive designed one wire protocol key reader using an Atmel xxx micro-controller. * Idrive designed PCB * Idrive designed micro-controller software.
System Features
Send a driver identification code to FW via RS232(mini HDMI Port) that will be logged and attached to events header.
Generate audio notification if the identification needs to be done.
Generate audio notification if the serial connection between reader and Idrive X1P was lost.
Hardware Requirements
- RS232 connection using Idrive X1P external connector - mini HDMI;
- 5V power connection using Idrive X1P external connector - mini HDMI;