130 likes | 328 Views
DRIVERTECH'S STAKE IN THE CONSORTIUM. 1. DT-2000 and DT-800m Driver Interface Computers 2. DriverTech Driving Mode Application (Software). 1. DT-2000 and DT-800m Driver Interface Computers. A. Windows CE Operating System B. Multiple 10 (Multiple RS-232 and Parallel Ports)
E N D
DRIVERTECH'S STAKE IN THE CONSORTIUM 1. DT-2000 and DT-800m Driver Interface Computers 2. DriverTech Driving Mode Application (Software)
1. DT-2000 and DT-800m Driver Interface Computers A. Windows CE Operating System B. Multiple 10 (Multiple RS-232 and Parallel Ports) C. Interface to J1708 and J1939 Data Buses D. VGA Color Display E. Two PCMCIA Slots F. Audio Processing Circuit
2. DriverTech Driving Mode Application A. Hard-coded driver interface software B. HTML support for dynamic form creation C. Remote Command Message (RCM) D. Raster Map Navigation E. Load Tendering Module F. Satellite and Terrestrial Wireless Connectivity
SAE Truck and Bus ITS Committee'sDriver Interface Task Force Scope Statement: To define a series of methods for interaction, including a messaging structure between the electronic computing systems of a vehicle and the operator of that vehicle. Focus is on the limitations on what interactions are permitted, rather than defining each possible interaction.
Operating Modes 1. Driving Mode • Restricted Software • Determined by Truck Motion and Other Factors • Driving Safety Is Paramount 2. Stopped Mode • Open Computing Environment • Driving Safety Is Not a Factor 3. Diagnostic Mode • Driving Safety is Important • System Diagnosis is Paramount
Vehicle On-board computer On-board computer Third party app Third party app Driver Driver Interface Vehicle Driver Interface
* * * * * PwrTrn (?) (1939) • OPERATOR • TECHNICIAN • OTHER IDB (?) APP 1 COMM 1 DISPLAY 1 APP 2 COMM 2 APP 3 DISP 2 APP 4 (No Comm) DEVICE / APP APP 4 DISP 3 COMM 4 • Various displays (physical) possible • Highly integrated (DISP 1) w/Multiple Apps. & Comms. • ‘Terminal’ type, w/App from some other device • Stand alone, single App w/Comms • Apps w/no Network Comms (phone book, etc.) • Various interface definitions needed • App to display • App to App • IDB to App • Other net (1939?) to Apps • Display to operator • Different roles of the ‘operator’, moving, stop, service
Screen Object Screen area object Button object Virtual ITS Toll Virtual ITS Weight ITS Comms Driver Button and screen drivers Screen driver(s) Comms Xpndr Buttons & scanner, & Deboynoe VGA Video Card ITS Systems ITS Open Onboard System Architecture (Page 1 of 2) Application Application Application Application Application Application Application Application Application Application Layer GUI Screen Object Button object Vehicle Component Layer Button object Screen Area object Button object Voice interaction not shown Hardware Abstraction Layer Kernel/Driver/Bios Hardware - open bus Front End Back End
ITS Open Onboard System Architecture (Page 2 of 2) Application Application Home Screen(s) Startup Screen Vehicle Object Driver Object Virtual Engine Object Transmission Object Brakes Object Vehicle Location Object Vehicle ID Object Trailer Object (ID) Trailer Brakes Trailer Reefer Dispatch Mailbox Wife Mailbox Driver created Mailbox Virtual Comms Object J1587 Mailbox Object J1939 Mailbox Object GPS Object Inertial Nav Object Task Manager Comms Driver Driver ID System Driver J1939 Driver J1587 Driver GPS Receiver Driver INS Driver J1587 Xcvr J1939 Xcvr System/ Vehicle ID Chip GPS Rovr Inertial Nav Sys Comms Xcvr Driver ID System
3. Information Presented 1. Max Info Processing Capability (a point) Emergency Only Maintenance Info Any Data 2. Information Available/Time 4. Information Management (Rules)