Refine Your Search

Search Results

Viewing 1 to 3 of 3
Technical Paper

Electronics Integration Test Station Development Methods

2001-11-12
2001-01-2769
The methods used to cope with the simultaneous development of the Electronics Integration Test Station (EITS) hardware and software in conjunction with its Test Target hardware and software are reviewed. The EITS provides a system level test facility for conducting hardware-in-the-loop (HIL) evaluations on vehicle electronic control systems. The development methods feature, formal hardware and software requirements documentation, formal software development, an iterative build process, and electronic capture of test incidents for analysis, verification and problem resolution. The application of the software development environment including the requirements management tools, and object oriented design tools is discussed within the context of the development methodology.
Technical Paper

System Requirements for the Electronics Integration Test Station

2001-11-12
2001-01-2770
The system level requirements for the Electronics Integration Test Station (EITS) are reviewed. EITS provides capabilities for system level testing of a variety of heavy-duty vehicle electronic control module configurations. EITS provides a hardware-in-the-loop (HIL) test facility at the system level, permitting the development of integration experiments as individual control system modules are added to the complement of modules being tested. The evaluation needs, which drive system-level testing of control system performance for systems of heavy-duty vehicle electronic control modules, are discussed. Implementation issues leading to system level requirements are also discussed.
Technical Paper

Proposed Revisions to the J1924 Definition of Vehicle Electronic Programming Station [VEPS] for Programming Electronic Components at OEM Assembly Plants

1993-11-01
933013
The current practice for programming electronic control modules using SAE Recommended Practice J1708 permits each vendor to provide a unique hardware and software interface for his products. A standardized communications interface for J1708 communications at OEM Assembly Plants is needed to eliminate the impacts of the unique interfaces. Draft SAE Recommend Practice J2214, Vehicle Electronic Programming Stations [VEPS] System Specification for Programming J1708-capable components at OEM Assembly Plants is proposed to address these concerns and improve upon the file-based interface documented in SAE Information Report J1924, OEM/Vendor Interface Specification for Vehicle Electronic Programming Stations. J2214 references the proposed SAE Recommended Practice J1683, MS-DOS™ Interface for J1708 Communications to define the standard interface.
X