NASTF Equipment Committee Report

1
NASTF EquipmentCommittee Report

• November 5, 2003
• Las Vegas Nevada
• Committee Chairman Charlie Gorman
• http//www.etools.org/i4a/pages\index.cfm?pageid2
  131

2
Matrix Update

• Companies that have not provided
  emissions-related and non-emissions-related scan
  tool information
• 1.9 is a very small part of the vehicle
  population and represents a significant
  improvement since March 03

3
Matrix update

• Summary sheet is updated and accurate
• Individual OEM matrices need some work
• In some cases only licensees can evaluate
  information and we dont know who they are.
• Some OEM information is low priority due to
  market size, especially now that more and more
  info is available
• Even with larger OEMs We dont always know what
  systems have changed for 2004.

4
Matrix update

• We ask that each OEM update their own matrix
  whenever new information is provided.
• This is safe because matrix accuracy can always
  be challenged through the equipment committee
  channel or through the use of the complaint form.

5
Reprogramming

• New Tracking Matrix approved by the NASTF
  Equipment Committee
• A blank version that can be used as a template is
  available by using the following link
• http//www.etools.org/i4a/pages/index.cfm?pageid2
  048

6
SAE J2534 Diagram
Special thanks to Ford for permission to use this
graphic. Note Not all OEMs will use the
Internet as a calibration download source
7
Focus

• Focus is to capture existing means for updating
  "any and all" reprogrammable or reconfigurable
  vehicle modules.
• Reporting should not be limited to
• J2534 compliant modules
• the six NASTF systems (engine, trans, ABS,
  airbag, HVAC cruise)
• 1996 and newer systems.
• The intent is to capture all needs at once in
  order to develop hardware to support field
  reprogramming of all modules.

8
Reprogramming Matrix
9
Whats different from scan tool info

• three main factors that make the Reprogramming
  Matrix different from the Data Stream Matrix.
• SAE J2534 Standard
• Not all reprogramming functions are the same.
• Reprogramming requires a PC and OEM software in
  addition to vehicle communications.

10
System Identification Section
11
Two kinds of reprogramming
In this section each vehicle manufacturer should
list any module programming functions other than
those that are accomplished through complete
program downloads. This includes setting of
customer preferences, variant coding, module
configuration, data entry (VIN, odometer
readings, pinion factor, etc.).
12
Two kinds of reprogramming
In this section vehicle manufacturers should
report on systems with capabilities to initially
program (load) or reprogram a module.
13
Is the module reprogrammable?
Does dealer equipment have the capability to
reconfigure, set-up, initially program or
reprogram this module (Y, N)? This is valuable
information to technicians. If a module is not
reprogrammable by a dealer, there is no need to
complain about the lack of this information. If
the module in question is not reprogrammable by
any repair entity, reprogramming is not an
available tool.
14
Data Stream Info Available?
If Dealer Equipment can reprogram or reconfigure
this module, make appropriate entry for hardware
protocol used
15
Software and Calibrations Available?
If Dealer Equipment can reprogram or reconfigure
this module, make appropriate entry for
distribution of software and calibrations.
16
SAE J2534 Update

• Holly Pugliese
• U.S. EPA

17
J2534 Update

• The point of J2534 is to provide the aftermarket
  with one device that works with ANY OEM
  application to reprogram a vehicle
• First version of J2534 finalized in Feb of 02
• Vehicle manufacturers and interface manufacturers
  have been working together to make compatible
  programming applications and hardware

18
Issues and Concerns

• Currently there is no tool or interface that is
  100 compliant
• Interpretations of v 2.02 of J2534 have led to
  vehicle and interface manufacturers implementing
  different solutions
• Some vehicle manufacturers have reprogramming
  applications that work with a single interface,
  but not with other interfaces
• Some vehicle manufacturers have programming
  applications that work with interfaces from
  multiple manufacturers for some protocols, but
  not all

19
Working Toward Resolution

• Version 2.02 currently under revision
• Updated version to be balloted in December
• OEMs and tool companies have been given ample
  opportunity to provide comment
• Committee has incorporated to the extent possible
  all of the OEM input received
• EPA expects the updated version will address
  these issues and that compliant tools and
  interfaces will be available soon

20
Next Steps

• Get the scan tool matrix updated to everyones
  satisfaction.
• Send copy of master reprogramming matrix to each
  OEM. Set a goal of January 5, 2004 for
  completion of the matrix.