Resumen del contenido incluido en la página 1
CAN
Automotive Diagnostic Command Set User Manual
Automotive Diagnostic Command Set User Manual
December 2007
372139B-01
Resumen del contenido incluido en la página 2
Support Worldwide Technical Support and Product Information ni.com National Instruments Corporate Headquarters 11500 North Mopac Expressway Austin, Texas 78759-3504 USA Tel: 512 683 0100 Worldwide Offices Australia 1800 300 800, Austria 43 662 457990-0, Belgium 32 (0) 2 757 0020, Brazil 55 11 3262 3599, Canada 800 433 3488, China 86 21 5050 9800, Czech Republic 420 224 235 774, Denmark 45 45 76 26 00, Finland 358 (0) 9 725 72511, France 01 57 66 24 24, Germany 49 89 7413130, India 91 80 411900
Resumen del contenido incluido en la página 3
Important Information Warranty The media on which you receive National Instruments software are warranted not to fail to execute programming instructions, due to defects in materials and workmanship, for a period of 90 days from date of shipment, as evidenced by receipts or other documentation. National Instruments will, at its option, repair or replace software media that do not execute programming instructions if National Instruments receives notice of such defects during the warranty per
Resumen del contenido incluido en la página 4
Compliance Compliance with FCC/Canada Radio Frequency Interference Regulations Determining FCC Class The Federal Communications Commission (FCC) has rules to protect wireless communications from interference. The FCC places digital electronics into two classes. These classes are known as Class A (for use in industrial-commercial locations only) or Class B (for use in residential or commercial locations). All National Instruments (NI) products are FCC Class A products. Depending on where it
Resumen del contenido incluido en la página 5
Contents About This Manual Conventions ...................................................................................................................xi Related Documentation..................................................................................................xii Chapter 1 Introduction KWP2000 (Key Word Protocol 2000)...........................................................................1-1 Transport Protocol....................................................................
Resumen del contenido incluido en la página 6
Contents Visual C++ 6 ................................................................................................... 3-2 Other Programming Languages ...................................................................... 3-2 Debugging an Application............................................................................................. 3-3 Chapter 4 Using the Automotive Diagnostic Command Set Structure of the Automotive Diagnostic Command Set.............................................
Resumen del contenido incluido en la página 7
Contents ReadDTCByStatus.vi ......................................................................................5-48 ReadECUIdentification.vi ...............................................................................5-51 ReadMemoryByAddress.vi .............................................................................5-53 ReadStatusOfDTC.vi.......................................................................................5-55 RequestRoutineResultsByLocalIdentifier.vi................
Resumen del contenido incluido en la página 8
Contents Chapter 6 Automotive Diagnostic Command Set API for C Section Headings........................................................................................................... 6-1 Purpose............................................................................................................ 6-1 Format ............................................................................................................. 6-1 Input and Output ...................................................
Resumen del contenido incluido en la página 9
Contents ndTesterPresent ...............................................................................................6-71 ndWriteDataByLocalIdentifier........................................................................6-73 ndWriteMemoryByAddress ............................................................................6-75 UDS (DiagOnCAN) Services ........................................................................................6-77 ndUDSClearDiagnosticInformation.................
Resumen del contenido incluido en la página 10
About This Manual This manual provides instructions for using the Automotive Diagnostic Command Set. It contains information about installation, configuration, and troubleshooting, and also contains Automotive Diagnostic Command Set function reference for LabVIEW-based and C-based APIs. Conventions The following conventions appear in this manual: » The » symbol leads you through nested menu items and dialog box options to a final action. The sequence File»Page Setup»Options directs you to p
Resumen del contenido incluido en la página 11
About This Manual Related Documentation The following documents contain information that you might find helpful as you read this manual: • ANSI/ISO Standard 11898-1993, Road Vehicles—Interchange of Digital Information—Controller Area Network (CAN) for High-Speed Communication � CAN Specification Version 2.0, 1991, Robert Bosch GmbH., Postfach 106050, D-70049 Stuttgart 1 � CiA Draft Standard 102, Version 2.0, CAN Physical Layer for Industrial Applications � ISO 14229:1998(E), Road Vehicles,
Resumen del contenido incluido en la página 12
1 Introduction Diagnostics involve remote execution of routines, or services, on ECUs. To execute a routine, you send a byte string as a request to an ECU, and the ECU usually answers with a response byte string. Several diagnostic protocols such as KWP2000 and UDS standardize the format of the services to be executed, but those standards leave a large amount of room for manufacturer-specific extensions. A newer trend is the emission-related legislated OnBoard Diagnostics (OBD), which is m
Resumen del contenido incluido en la página 13
Chapter 1 Introduction Transport Protocol As KWP2000 uses messages of variable byte lengths, a transport protocol is necessary on layers with only a well defined (short) message length, such as CAN. The transport protocol splits a long KWP2000 message into pieces that can be transferred over the network and reassembles those pieces to recover the original message. KWP2000 runs on CAN on various transport protocols such as ISO TP (ISO 15765-2), TP 1.6, TP 2.0 (Volkswagen), and SAE J1939-21.
Resumen del contenido incluido en la página 14
Chapter 1 Introduction as second byte, and a ResponseCode as third byte. The only exception to this format is the negative response to an EscapeCode service; here, the third byte is an echo of the user-defined service code, and the fourth byte is the ResponseCode. The KWP2000 standard partly defines the ResponseCodes, but there is room left for manufacturer-specific extensions. For some of the ResponseCodes, KWP2000 defines an error handling procedure. Because both positive and negative re
Resumen del contenido incluido en la página 15
Chapter 1 Introduction Measurements Use the ReadDataByLocal/CommonIdentifier services to access ECU data in a way similar to a DAQ list. A Local/CommonIdentifier describes a list of ECU quantities that are then transferred from the ECU to the tester. The transfer can be either single value or periodic, with a slow, medium, or fast transfer rate. The transfer rates are manufacturer specific; you can use the SetDataRates service to set them, but this setting is manufacturer specific. Note The
Resumen del contenido incluido en la página 16
Chapter 1 Introduction UDS (Unified Diagnostic Services) The UDS protocol has become a de facto standard in automotive diagnostic applications. It is standardized as ISO 15765-3. UDS describes the implementation of various diagnostic services you can access through the protocol. As UDS uses messages of variable byte lengths, a transport protocol is necessary on layers with only a well defined (short) message length, such as CAN. The transport protocol splits a long UDS message into pieces t
Resumen del contenido incluido en la página 17
Chapter 1 Introduction Note Some parameters to both the Request and Positive Response Messages are optional. Each service defines these parameters. Also, the standard does not define all parameters. The Negative Response Message is usually a three-byte message: it has the Negative Response ServiceId (0x7F) as first byte, an echo of the original ServiceId as second byte, and a ResponseCode as third byte. The UDS standard partly defines the ResponseCodes, but there is room left for manufactur
Resumen del contenido incluido en la página 18
2 Installation and Configuration This chapter explains how to install and configure the Automotive Diagnostic Command Set. Installation This section discusses the Automotive Diagnostic Command Set installation for Microsoft Windows. Note You need administrator rights to install the Automotive Diagnostic Command Set on your computer. Follow these steps to install the Automotive Diagnostic Command Set software: 1. Insert the Automotive Diagnostic Command Set CD into the CD-ROM drive. 2. Open
Resumen del contenido incluido en la página 19
Chapter 2 Installation and Configuration Refer to Appendix A, Troubleshooting and Common Questions, of the NI-CAN User Manual for information about resolving hardware installation problems. When installation is complete, you can access the Automotive Diagnostic Command Set functions in your application development environment. LabVIEW Real-Time (RT) Configuration LabVIEW Real-Time (RT) combines easy-to-use LabVIEW programming with the power of real-time systems. When you use a National Instr
Resumen del contenido incluido en la página 20
3 Application Development This chapter explains how to develop an application using the Automotive Diagnostic Command Set API. Choosing the Programming Language The programming language you use for application development determines how to access the Automotive Diagnostic Command Set APIs. LabVIEW Automotive Diagnostic Command Set functions and controls are in the LabVIEW palettes. In LabVIEW, the Automotive Diagnostic Command Set palette is in the top-level NI Measurements palette. Chapter
