SAE J 2461-2013 Vehicle Electronic Programming Stations (VEPS) System Specification for Win32《汽车电子编程站(VEPS)系统为Win32 ST段规格》.pdf

《SAE J 2461-2013 Vehicle Electronic Programming Stations (VEPS) System Specification for Win32《汽车电子编程站(VEPS)系统为Win32 ST段规格》.pdf》由会员分享，可在线阅读，更多相关《SAE J 2461-2013 Vehicle Electronic Programming Stations (VEPS) System Specification for Win32《汽车电子编程站(VEPS)系统为Win32 ST段规格》.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

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 entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there

2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2013 SAE International All rights reserved. No part of this p

3、ublication 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: +1 724-776-497

4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/J2461_201309 SURFACE VEHICLE RECOMMENDED PRACTICE J2461 SEP2013 Issued 1998-11 Re

5、vised 2013-09 Superseding J2461 MAR2010 Vehicle Electronic Programming Stations (VEPS) System Specification for Win32 RATIONALE Removed specific references to Windows versions. Removed self-reference to document in section 1.3.1. Update all RP1210B references to RP1210C. Reword reference to RP1210A

6、as an earlier RP1210 version. Replace all Windows and Microsoft related trademarks with a Registered mark . Reword the last paragraph in Section 1.4.3 to clarify its meaning. TABLE OF CONTENTS 1. SCOPE 2 1.1 Identification 2 1.2 Introduction . 2 1.3 Background . 3 1.3.1 WIN32 VEPS 3 1.3.2 DOS VEPS 3

7、 1.3.3 Electronics Impact . 3 1.3.4 SAE J2214 Features and SAE J2461 Change Summary. 3 2. REFERENCES 4 2.1 Applicable Documents 4 2.1.1 SAE Publications . 4 2.1.2 TMC Publications 4 3. ACRONYMS . 4 4. TRADEMARK ACKNOWLEDGMENTS 4 5. SYSTEM OVERVIEW . 4 5.1 System Objectives 5 5.2 VEPS Components . 5

8、5.2.1 OEM Shop Floor Program. 6 5.2.2 VCP . 6 5.2.3 TMC RP1210C 6 5.2.4 Parameter File . 6 5.2.5 Verification File 7 5.2.6 Definition File 7 5.3 Process Overview . 7 6. VENDOR COMPONENT PROGRAM (VCP) 9 6.1 Configuration . 9 6.1.1 Setup . 9 6.1.2 Home Directory . 9 6.1.3 Home Directory Example 9 6.2

9、Interfaces 10 6.2.1 Command Line Parameters 10 6.2.2 Exit Codes . 10 SAE INTERNATIONAL J2461 Revised SEP2013 Page 2 of 13 6.3 User Interface 10 7. NOTES 10 7.1 Marginal Indicia . 10 APPENDIX A PROGRAMMING EXAMPLES 12 FIGURE 1 TYPICAL VEPS USAGE . 5 FIGURE 2 VEPS COMPONENTS AND INTERFACES . 5 FIGURE

10、3 ARCHITECTURAL OVERVIEW - POTENTIAL COMMUNICATIONS INTERFACES . 6 FIGURE 4 OEM CREATES PARAMETER FILE 7 FIGURE 5 OEM STARTS THE VCP 7 FIGURE 6 VCP RETRIEVES INFORMATION FROM PARAMETER FILE . 7 FIGURE 7 VCP PROGRAMS VEHICLE ELECTRONICS 8 FIGURE 8 VCP SIGNALS PROGRAMMING RESULTS . 8 FIGURE 9 VCP RETU

11、RNS EXIT CODE 8 FIGURE 10 OEM PROGRAM READS EXIT CODE 9 FIGURE 11 OEM PROGRAM RETRIEVES INFORMATION FROM VERIFICATION FILE 9 FIGURE 12 VCP STATUS DIALOG BOXES . 11 TABLE 1 VCP EXIT CODES 10 1. SCOPE 1.1 Identification SAE J2461 specifies the recommended practices of a Vehicle Electronics Programming

12、 Stations (VEPS) architecture.in a Win32 environment. This system specification, SAE J2461, was a revision of the requirements for Vehicle Electronics Programming Stations (VEPS) set forth in SAE J2214, Vehicle Electronics Programming Stations (VEPS) System Specification for Programming Components a

13、t OEM Assembly Plants (Cancelled Jun 2004). The J2214 standard has been cancelled indicating that it is no longer needed or relevant. 1.2 Introduction SAE J2461 describes the application of the Win32 environment to the customization of programmable components assembled in OEM vehicles, where compone

14、nts provide a communication API such as TMC RP1210C. Because the customization is performed using both OEM-provided and vendor-provided software, the roles and responsibilities of the vendor and OEM elements must be defined to permit the development of common vendor software elements for all Origina

15、l Equipment Manufacturers (OEMs). SAE J2461 identifies the system resources of a Win32 computer between OEM and vendor components, the required elements comprising VEPS, and specifies the software interfaces needed between the OEM-supplied elements and the vendor-supplied elements. By maintaining ma

16、ny common elements with SAE J2214, an orderly transition from a MS-DOS based VEPS to a Win32 VEPS can be achieved. SAE J2286 is the software interface element of SAE J2214 that specifies the Vendor Component Program Data File Interface for OEM Assembly Operations. SAE J2286 will still be the Data Fi

17、le Interface used for the Win32 VEPS. TMC RP1210C describes the communication API used by the vendor programs. SAE INTERNATIONAL J2461 Revised SEP2013 Page 3 of 13 1.3 Background The OEMs typically are horizontally integrated. Each major vehicle component has multiple vendors who compete for compone

18、nt sales in OEM markets. Customer orders determine a set of components from this variety to meet the vehicles desired performance requirements. Customization and calibration of these components for the vehicles application necessitates the need for a standard method to perform this programming witho

19、ut causing the OEM to install special VEPS for each vendor component. Hence the existence of MS-DOS SAE J2214. As the need for more applications grow at OEM VEPS, a more flexible solution to the current RP is needed. Win32 SAE J2461 provides such a solution. 1.3.1 WIN32 VEPS SAE J2286 Vendor Compone

20、nt Program Data File Interface for OEM Assembly Operations TMC RP1210C Windows Communications API 1.3.2 DOS VEPS SAE J2214 Vehicle Electronic Programming Stations (VEPS) System Specification for Programming Components at OEM Assembly Plants (Cancelled Jun 2004) SAE J2286 Vendor Component Program Dat

21、a File Interface for OEM Assembly Operations SAE J1683 MS-DOS Interface for SAE J1708 Communications (Cancelled Jun 2004) SAE J1924 OEM/Vendor Interface Specification for Vehicle Electronic Programming Stations (Cancelled Aug 2000) 1.3.3 Electronics Impact The introduction of electronic control syst

22、ems for OEM vehicles such as diesel engines, transmissions, anti-lock brakes, etc. coincided with the introduction of new product features that were integrated within the systems controllers. As an example, features such as cruise control and road speed limiting require that controllers be calibrate

23、d with specific information related to the equipment installed on the vehicle such as tire size, rear axle ratio, and desired operating speeds. Programmable parameters identify the information items needed to calibrate the controllers. Parameter programming is accomplished through the use of the con

24、trollers data link. This programming function customizes controller performance to comply with the customers specified parameter changes. 1.3.4 SAE J2214 Features and SAE J2461 Change Summary SAE J2286 specifies a common interface format within an MS-DOS environment. Each parameters requirement for

25、an assembly job is entered as a record in an ASCII file specified as a parameter file. The parameter file is interpreted by a Vendor Component Program (VCP) that performs the specified programming via a common communication interface. The programming result for each parameter is reported as a record

26、 in the verification file. The definition and remarks files document the parameters that can be programmed in the Vendor Component. SAE J2461 retains the core architecture defined by SAE J2286, including the four defined files. Like SAE J2214, SAE J2461 defines that a common communication utility be

27、 used by the VCP to prevent the proliferation of Vendor Interface Tools required to support each programmable component under SAE J2214. The common communication interface used by SAE J2214 is SAE J1683. The common communication interface used by SAE J2461 is TMC RP1210C. SAE INTERNATIONAL J2461 Rev

28、ised SEP2013 Page 4 of 13 2. REFERENCES 2.1 Applicable Documents The following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest issue of SAE publications shall apply. 2.1.1 SAE Publications Available from SAE International, 400 Com

29、monwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org. SAE J2286 Vendor Component Program Data File Interface for OEM Assembly Operations 2.1.2 TMC Publications Available from the Technology and Maintenance Council, American

30、Trucking Associations, 2200 Mill Road, Alexandria, VA 22314, Tel: (703) 838-1700, . TMC RP1210C Windows Communication API 3. ACRONYMS ASCII American Standard Code for Information Interchange API Application Program Interface DI Data Item ECU Electronic Control Unit GUI Graphical User Interface MIS M

31、anagement Information Systems OEM Original Equipment ManufacturerPC Personal Computer RP Recommended Practice SAE SAE International SW Software STD StandardTMC Technology Maintenance Council VCP Vendor Component Program VEPS Vehicle Electronics Programming Station Win32 32 bit Windows 4. TRADEMARK A

32、CKNOWLEDGMENTS MS-DOS is a registered trademark of Microsoft, Inc. Win32 is a registered trademark of Microsoft, Inc. 5. SYSTEM OVERVIEW The requirements for Vehicle Electronics Programming Stations (VEPS) are discussed from a functional perspective in this section. SAE INTERNATIONAL J2461 Revised S

33、EP2013 Page 5 of 13 5.1 System Objectives SAE J2461 provides the system specification for the programming station illustrated in Figure 1. Objectives to be met by VEPS include: a. Customize electronically controlled components to the customers desires at vehicle OEM assembly plants. b. Provide posit

34、ive indications of programming results. c. Simplify communications with the vehicle network. d. Define Vendor Component Programs in such a manner that all component vendors can provide them to OEMs. Figure 1 illustrates the process of programming the electronic components of a vehicle at an OEM asse

35、mbly plant. The figure shows four assembly jobs progressing down the assembly line. Jobs 1 and 2 have been programmed. Job 3 is being programmed, and job 4 will be presented to the programming station. The station has identified that job 3 was presented to it for programming and initiated the progra

36、mming process. FIGURE 1 - TYPICAL VEPS USAGE 5.2 VEPS Components Figure 2 illustrates the computer programs and interfaces that comprise a typical VEPS. FIGURE 2 - VEPS COMPONENTS AND INTERFACES SAE INTERNATIONAL J2461 Revised SEP2013 Page 6 of 13 5.2.1 OEM Shop Floor Program The main purpose of the

37、 OEM Shop Floor Program is to identify the assembly job, extract parameter information (usually from the OEM Manufacturing System), format the parameter file, and invoke the VCP. The preceding steps represent the minimum requirements to support the execution of the VCP. The methods associated for su

38、pporting the VCP execution is left to each individual OEM to implement. 5.2.2 VCP The VCP is responsible for auditing the parameter values, programming the values into the vendors vehicle electronics, and reporting the programming results. The VCP only needs to support one component or family of com

39、ponents produced by an individual vendor. 5.2.3 TMC RP1210C This document describes a standardized interfaceTMCs RP1210C Windows Communication Application Program Interface (API)for personal computer (PC) to on-vehicle data link communications under the Microsoft Windows family of operating systems.

40、 See Figure 3. Technology Maintenance Council (TMC) established this Recommended Practice for vehicle ECU communication and control under the Microsoft Windows family of operating systems. Anyone is welcome to employ this RP in implementing software systems for ECU reprogramming and communication. T

41、his standard will use the generic reference RP1210 to allow backwards compatibility with older VEPS systems that have already been implemented using earlier RP1210 versions (RP1210A or RP1210B). FIGURE 3 - ARCHITECTURAL OVERVIEW - POTENTIAL COMMUNICATIONS INTERFACES 5.2.4 Parameter File SAE INTERNAT

42、IONAL J2461 Revised SEP2013 Page 7 of 13 The parameter file is produced by the OEM Shop Floor program. It contains all the particular vendors parameters that the OEM wishes to program for the immediate programming session. The parameter file format is defined by SAE J2286. 5.2.5 Verification File Th

43、e verification file is produced by the VCP. It contains records identifying the status of the VCP programming session. The verification file format is defined by SAE J2286. 5.2.6 Definition File The definition file is provided by the vendor. It contains records which describe the parameters supporte

44、d by the VCP, including default value, lower limit, upper limit, etc. The definition file format is defined by SAE J2286. The use of the definition file is optional to both the OEM shop floor program and the VCP. 5.3 Process Overview a. STEP 1The OEM shop floor program generates the parameter file t

45、o provide VCP with parameter programming information. See Figure 4. FIGURE 4 - OEM CREATES PARAMETER FILE b. STEP 2The OEM shop floor program invokes the VPC with optional command line arguments. The VCP runs as a separate Windows application. See Figure 5. FIGURE 5 - OEM STARTS THE VCP c. STEP 3The

46、 VCP parses the parameter files. The VCP locates the parameter file using the rules found in SAE J2286. See Figure 6. FIGURE 6 - VCP RETRIEVES INFORMATION FROM PARAMETER FILE SAE INTERNATIONAL J2461 Revised SEP2013 Page 8 of 13 d. STEP 4The VCP begins the communication session with the vendor compon

47、ent electronics via the TMC RP1210C Windows Communication API. Here the VCP reads, writes, and validates ECU data. If the OEM has enabled the VCP GUI, then the VCP gives visual feedback of the VEPS communication session. See Figure 7. FIGURE 7 - VCP PROGRAMS VEHICLE ELECTRONICS e. STEP 5The VCP crea

48、tes a verification file based on the path/name information. The status of the VEPS communications session, as well as the programming status of each parameter is written to the verification file. If the OEM has enabled the VCP GUI, then the VCP displays the VEPS communications results. See Figure 8.

49、 FIGURE 8 - VCP SIGNALS PROGRAMMING RESULTS f. STEP 6The VCP terminates. Upon termination, the VCP supplies an exit code. See Figure 9 and 6.2.2. FIGURE 9 - VCP RETURNS EXIT CODE SAE INTERNATIONAL J2461 Revised SEP2013 Page 9 of 13 g. STEP 7The OEM shop floor program reads the exit code to determine the status of the VEPS communications session. Optionally, the OEM shop floor program ca