SAE J1924-2000 pdf download OEM/Vendor Interface Specification for Vehicle Electronic Programming Stations
1. Scope—The purpose of the SAE Information Report is to address the method of loading vehicle electronic controllers with chassis and customer specific parameters. This specification shall establish an interface definition. The interface definition must be mutually agreeable to truck OEMs and vendors. The purpose of this specification is not to answer the large protocol issues raised by systems such as GM’s MAP. 1.1 SAE Standard—In the future, SAE may use this specification as a basis for an OEMNendor interface specification standard.
2. References There are no referenced publications specified herein.
3. Programming System
3.1 Plant System—Each OEM will create its own system of programming vehicle control modules. This specification only addresses the programming station setup and the OEM/vendor intertace. It does not suggest any specifies concerning the OEM’s manufacturing system or production facilities.
3.2 Station Setup
3.2.1 PROPOSE~ S’ra’riorv—The link between the OEM computer and the vendor interface tool is RS232c. The OEM host communications port shall support the 9 pin standard. The OEM host computer may have multiple ports or one common port. The common port is possible if the OEM provides an external switch. See the example in Figure 1 .
3.2.2 PROPOSE~ So~wARE—The OEM production line PC shall execute an OEM production line program and the vendor communications programs. The OEM program shall gather customer and chassis specific parameter information from its manufacturing system and invoke the vendor program. The vendor program shall download the parameters via the host computer’s communications port to the vehicle control module. The vendor program shall also return parameter verification and warranty data to the OEM program. The vendors shall supply the communication program to the OEMs as an executable program file (.exe). See example in Figure 2.
3.2.3 FuTUaE DiRECTioN—The OEMs want to phase out vendor tools used on the production line. In the future, an ATA communications card will replace the vendor interface tools. The OEMs intend to evolve to one ATA/ SAE communications card which will plug into the host computer. This card will replace the vendor interface tools. The OEMs anticipate that the definition process will begin in the Spring of 1989. This should lead to a production line prototype in the early 1 990s.
4. Inferface Files
4.1 File Characteristics—Each interface file is an ASCII text file with multiple records. An end of line marker terminates each record and delimiters separate each field. A maximum character count limits the length of each field. If a larger field is needed, a field may contain a file name pointing to a separate file. An end of file marker terminates the file.
4.1.1 TExT Fi~E FoRM,aT—The record fields may contain any printable (20H to 7EH) ASCII characters except the field delimiter. The comma shall delimit record fields and a carriage return line feed shall terminate each record. A control-Z shall mark the end of file.
SAE J1924-2000 pdf download
PS:Thank you for your support!
