Difference between revisions of "Driver ID Specs"
Jump to navigation
Jump to search
(Created page with "== Introduction == == Overall Description == == System Features == == Other Nonfunctional Requirements ==") |
|||
| Line 1: | Line 1: | ||
== Introduction == | == 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 == | == Overall Description == | ||
| + | |||
| + | Driver ID component will be build using a iButton key(http://www.maximintegrated.com/products/ibutton/ibuttons/) | ||
| + | |||
== System Features == | == System Features == | ||
| + | |||
| + | Send a driver identification code to FW via RS232(mini HDMI Port) that will be logged and attached to events header. | ||
| + | |||
| + | |||
| + | == Hardware Requirements == | ||
| + | |||
| + | == Software Requirements == | ||
| + | |||
== Other Nonfunctional Requirements == | == Other Nonfunctional Requirements == | ||
Revision as of 10:00, 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 be build using a iButton key(http://www.maximintegrated.com/products/ibutton/ibuttons/)
System Features
Send a driver identification code to FW via RS232(mini HDMI Port) that will be logged and attached to events header.