1、SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirelyvoluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefro
2、m, is the sole responsibility of the user.”SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.Copyright 2003 Society of Automotive Engineers, Inc.All rights reserved. No part of this
3、 publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying,recording, or otherwise, without the prior written permission of SAE.TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)Tel: 724-776-4970 (o
4、utside USA)Fax: 724-776-0790Email: custsvcsae.orgSAE WEB ADDRESS: http:/www.sae.orgSURFACEVEHICLERECOMMENDEDPRACTICESAE J2571ISSUEDJAN2003Issued 2003-01Advanced Driver Interface Systems for Commercial Vehicle OperationsForewordIn recent years there have been significant new developments in the area
5、of driver interface systemsand software for those systems. The aim of these developments has been to offer the driver better informationfrom a central display or displays, and to take advantage of new developments in personal computing, graphicaluser interfaces and audio interfaces in order to enhan
6、ce safety and productivity in a commercial vehicle. Thesedevelopments are also driven by new Intelligent Transportation System (ITS) technologies, like Global PositioningSatellites, satellite communications, real time traffic information, automated tolls and collections, terrestrialwireless infrastr
7、ucture, and so on. In addition, the commonality of standardized, on-board digital networks (e.g.,SAE J1939) linking vehicle subsystems, also makes a single or limited number of driver interfaces possible, and inmost cases preferable.With professional drivers in commercial vehicle operations the act
8、of driving the vehicle is mixed with therequirements for which the vehicle is employed, such as hauling goods to a designated stop. The delivery processoftentimes requires the driver to be cognizant of customer requirements (e.g., schedules), and may requirefrequent directions to unfamiliar location
9、s. Among others, these potential distractions include receiving real-timeinstructions over a radio or cell phone, and glancing at paper maps. Advanced driver interface systems have thecapability to remove or mitigate these unavoidable distractions. For example, digital messages stored in a devicecan
10、 replace wireless voice communications, which in many cases, must be committed to memory or written. Also,digital navigation can replace paper maps with commercial vehicle-relevant routes, simplified images, and simpletextual or spoken instructions. Non-job related distractions, like adjusting an en
11、tertainment system, can be madesafer with voice activated commands.This SAE Recommended Practice does not apply to traditional driver interface technologies, including gauges,gauge clusters or indicator lights. 1. ScopeThis SAE Recommended Practice defines an architecture, including operating modes,
12、 in which anadvanced driver interface system and related software exist. It also provides reference to a set of FederalHighway Administration approved guidelines for human factors characteristics of such systems and relatedsoftware.1.1 PurposeThis document is meant to aid the developer of advanced d
13、river interface systems and relatedsoftware for commercial vehicle operations in understanding the general architecture in which an advanceddriver interface system is placed, as well as provide some limited guidance in developing informationpresentation to the driver. This document has cited specifi
14、c sections of The Human Factors Design Guidelinesfor Advanced Traveler Information Systems (ATIS) and Commercial Vehicle Operations, published by theUnited States Department of Transportations Federal Highway Administration. The specific guidelines citedare those thought to provide the most applicab
15、le assistance for developers of advanced driver interfacesystems and software for professional drivers.SAE SAE J2571 Issued JAN2003-2-2. References2.1 Applicable PublicationsThe following publications form a part of this specification to the extent specifiedherein. Unless otherwise indicated, the la
16、test version of SAE publications shall apply.2.1.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1587Joint SAE/TMC Electronic Data Interchange Between Microcomputer Systems in Heavy DutyVehicle ApplicationsSAEJ1708Serial Data Communications Between Microc
17、omputer Systems in Heavy Duty VehicleApplicationsSAE J1939Recommended Practice for a Serial Control and Communication Vehicle NetworkSAE J1939/71Vehicle Application Layer2.1.2 IEEE PUBLICATIONSAvailable from IEEE, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331.IEEE 1455Dedicated Short Range
18、 Communications 2.1.3 US DEPT. OF T RANSPORTATION, FEDERAL HIGHWAY ADMINISTRATION PUBLICATIONAvailable from U. S.Department of Transportation, 400 7th Street, S.W., Washington, DC 20590. Telephone: 202-366-4000.Website: www.its.dot.gov(FHWA-RD-98-057). Human Factors Design Guidelines for Advanced Tr
19、aveler Information Systems(ATIS) and Commercial Vehicle Operations (CVO)3. DefinitionsCVO Commercial Vehicle OperationsITS Intelligent Transportation SystemsATIS Advanced Traveler Information SystemsFHWA Federal Highway Administration4. Architecture of Advanced Driver Interface SystemsAn advanced dr
20、iver interface system has thecapability to present information to the driver from multiple sources and receive commands from the driver formultiple purposes. An advanced driver interface system can be an autonomous computing device with thecapability to run complex software, or can be the combinatio
21、n of a terminal device acting as the front end of anumber of autonomous intelligent devices on, or even off of the vehicle. Therefore it is important toacknowledge a structure of which the driver interface system shall be an integral part. Figure 1 illustrates thestructure of an advanced driver inte
22、rface system.FIGURE 1STRUCTURE OF ADVANCED DRIVER INTERFACE SYSTEM.4.1 The Front-End of an advanced driver interface system is that portion available to the driver. It consists of theinterfacing hardware, such as the display, keypad, touch-screen, audio circuitry, etc. It also consists of thesoftwar
23、e applications which present information to the driver, allow the driver to act upon that information, orsimply allow the driver to apply commands and messages through the driver interface system to other systemson or off of the vehicle. This document is primarily concerned with the front end. The f
24、ront end entails theHuman Factors elements.SAE SAE J2571 Issued JAN2003-3-4.2 The Back-End of an advanced driver interface system is the electronic interface to systems/devices externalto the advanced driver interface system. These include the diagnostic and control networks (SAE J1708, SAEJ1939), o
25、ff-board communications networks such as satellite or terrestrial wireless networks, video input oraudio input/output, or any of a number of possible electronic interconnections. This document draws thedevelopers attention to a number of sources of guidelines and recommended practices. These include
26、 theSAE J1939, SAE J1708, and SAE J1587. Also included are others such as IEEE 1455 specification fordedicated short range communications. Some electronic interface protocols are proprietary, such as certainwireless data networks. It is important to note that within the advanced driver interface sys
27、tem is includedsoftware operating on external devices using the advanced driver interface system for their own driverinterface requirements. 4.3 The Information Manager is at the core of the advanced driver interface system, and includes the messagemanagement rules that are applied to the informatio
28、n available to the driver. This document does not outlineany rules for the developer other than those required by mode control (see Section 5) or by documents cited asreference material. It is assumed that the developers of advanced driver interface systems or softwareapplications for those systems
29、shall use good judgement in designing their information manager software, andshall use applicable information management rules that might be subsequently developed by SAE.5. Operating ModesTwo operating modes shall exist for an advanced driver interface system. These twomodes are Parked mode and Not
30、-parked mode. Required within the advanced driver interface system is amechanism for indicating to software applications which of these two operating modes the driver interfacesystem is currently in. This mechanism shall enable software applications to operate in an unlimited or limitedfashion, depe
31、nding on which of the two modes is enabled. Primary responsibility for determining whether asoftware application can be operated safely during Not-parked mode rests with the software applicationdeveloper. The software application developer, with input from customers, safety experts, and otherrespons
32、ible parties, shall use the advanced driver interface systems mode indication mechanism to allow full,limited or non-use of the application under Not-parked mode. This document shall not impede a provider of anadvanced driver interface system from locking out software applications from operating dur
33、ing Not-parkedmode that have not received certification from the advanced driver interface system provider.5.1 Not-Parked ModeThis is the mode of operation during the time the vehicle is in motion or imminent motion.In this mode, application software running on an advanced driver interface system sh
34、all be such that the use ofthe software shall not detract from the safe operation of the vehicle. The advanced driver interface systemshall determine when the vehicle is in Not-parked mode and shall output an indication to software applicationsthat this is the current mode.5.2 Parked ModeThis is the
35、 mode of operation during the time that the vehicle is stopped and not in a state ofimpending motion, for example, where the operator has placed the vehicle transmission in PARK, or in neutralwith the parking brake set, or in gear with the engine off. In this mode, application software running on an
36、advanced driver interface system shall not be required to take into consideration the restrictions of motion orimminent motion of the vehicle.5.3 Optional Modes of OperationA provider of an advanced driver interface system may choose to haveadditional modes of operation. One example would be a Stand
37、by mode, where the operator is allowed to stopthe vehicle to enable use of the advanced driver interface system beyond that allowed while the vehicle is inmotion. Another example would be a Diagnostic/repair mode that enables a service person to operate thevehicle for the purpose of diagnostics and
38、repair. If such modes exist, the advanced driver interface devicemust indicate to the application software when these optional modes are active. In the case of a diagnostic/repair mode, either the software application or the advanced driver interface system shall provide for a meansto allow only aut
39、horized service personnel to enter this mode.SAE SAE J2571 Issued JAN2003-4-6. Human Factors Criteria for Advanced Driver Interface SystemsIt is recommended that the developersof advanced driver interface systems, and application software for such systems, follow the guidelinesreferenced as follows,
40、 which are cited from the publication Human Factors Design Guidelines for AdvancedTraveler Information Systems (ATIS) and Commercial Vehicle Operations (CVO). These guidelines werepublished in September 1998 by the US Dept. of Transportation, Federal Highway Administration (FHWA-RD-98-057). For purp
41、oses of this document, a series of specific sections of the FHWA Guidelines are outlined asfollows. It is up to each advanced driver interface system developer and application software developer todetermine how these guidelines are interpreted and applied. It is recommended the developer read the en
42、tireFHWA guidelines document to place into context the importance of each specific guideline. Listed as followsare those guidelines that merit the particular attention of developers of advanced driver interface systems forprofessional drivers in commercial vehicle operations.6.1 ATIS Display Guideli
43、nes1. Symbol Contrast (pages 3-2 through 3-3)2. Symbol Height (pages 3-4 through 3-5)3. Symbol Luminance Uniformity (pages 3-6 through 3-7)4. Symbol Font (pages 3-8 through 3-9)5. Symbol Width to Height Ratio (pages 3-10 through 3-11)6. Symbol Stroke Width to Height Ratio (pages 3-12 through 3-13)7.
44、 Symbol Spacing (pages 3-14 through 3-15)8. Symbol Color (pages 3-16 through 3-17)9. Selection of Colors for Coding Visual Displays (pages 3-18 through 3-19)10. Use of Color Coding (pages 3-20 through 3-21)11. Color Contrast (pages 3-22 through 3-23)12. Sensor Modality for Presenting ATIS/CVO Messag
45、es (pages 3-24 through 3-25)13. Auditory Message Length (pages 3-26 through 3-27)14. Complexity of ATIS Information (3-28 through 3-29)15. Symbol Versus Text Presentation of ATIS/CVO Messages (pages 3-30 through 3-31)16. Message Styles (pages 3-32 through 3-33)17. General Guidelines for User Interfa
46、ce Design (pages 3-42 through 3-43)18. General Guidelines for ATIS Messages (pages 3-44 through 3-45)19. Use of Alerts for ATIS Messages (pages 3-46 through 3-47)6.2 ATIS Control Guidelines1. Selection of Control Type (pages 4-2 through 4-3)2. Control Movement Compatibility (pages 4-4 through 4-5)3.
47、 Control Coding (pages 4-6 through 4-7)4. Selection of Keyboards for ATIS Devices (pages 4-8 through 4-9)5. Design of Speech-based Controls (pages 4-10 through 4-11)6. Providing Destination Preview Capability (pages 4-12 through 4-13)SAE SAE J2571 Issued JAN2003-5-6.3 Routing and Navigation Guidelin
48、es 1. Timing of Auditory Navigation Information (pages 5-4 through 5-5)2. Color Coding of Traffic Flow Information (pages 5-6 through 5-7)3. Clear Depiction of Route On Electronic Maps (pages 5-16 through 5-17)4. Presentation of Route and Destination Selection Information (pages 5-22 through 5-23)5.
49、 Presentation of Dynamic Route Selection Information (pages 5-24 through 5-25)6. Presentation of Route Guidance Information (pages 5-26 through 5-27)7. Presentation of Lane Position Information (pages 5-28 through 5-29)8. Presentation of Toll Collection Information (pages 5-30 through 5-31)9. Presentation of Route Incident Information (pages 5-32 through 5-33)6.4 Motorist Services Guidelines1. Presentation of Preference and Directory Information (pages 6-4 through 6-5)2. Presentation of Destination Coordination Information (pages 6-6 through 6-7)3. The Message Transfe
