Ieee STD 1616a

IEEE Std 1616a"-2010
(Amendment to
EEE Std 1616-2004)
IEEE Standard for Motor VehicIe
Event Data Recorders (MVEDRs)
Amendment 1: MVEDR Connector
Lockout Apparatus (MVEDRCLA)
IEEE VehicuIar TechnoIogy Society
Sponsored by the
Land Transportation Committee
EEE
3 Park Avenue
New York, NY 10016-5997, USA
7 May 2010
1
6
1
6
a
T
M
Authorized licensed use limited to: ATENEO DE MANILA UNIVERSITY. Downloaded on February 06,2012 at 08:28:24 UTC from IEEE Xplore. Restrictions apply.
IEEE Std 1616a-2010
(Amendment to
IEEE Std 1616-2004)
IEEE Standard for Motor Vehicle
Sponsor
Land Transportation Committee
of the
IEEE Vehicular Technology Society
Approved 25 March 2010
IEEE-SA Standards Board

Abstract: This amendment adds information pertaining to motor vehicle event data recorder
connector lockout apparatus (MVEDRCLA) by revision.
Keywords: communication equipment, crash data, crash data recorder (CDR), data transfer,
data transmission, diagnostic link connector (DLC), diagnostic programs, diagnostic testing,
EEPROM, EEPROM data, electronic control unit (ECU), electronic equipment and components,
electronic scan tools, event data recorder (EDR), information exchange, litigation, nonvolatile
memory, nonvolatile memory data, OBD2 or OBDII, odometer clocking, odometer fraud,
odometer spun, odometer tampering, onboard network data security, power control module
(PCM) and/or electronic control unit (ECU) flashing, road vehicle components, road vehicle
engineering, road vehicles, SAE J1962 connectors, vehicle components, vehicle crash data,
vehicle identification number (VIN) tampering and/or theft

The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA

Copyright 2010 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 7 May 2010. Printed in the United States of America.

IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and Electronics
Engineers, Incorporated.

PDF: ISBN 978-0-7381-6253-9 STD96062
Print: ISBN 978-0-7381-6254-6 STDPD96062

IEEE prohibits discrimination, harassment and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of
the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus
development process, approved by the American National Standards Institute, which brings together volunteers
representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the
Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote
fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy
of any of the information or the soundness of any judgments contained in its standards.
Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other
damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly
resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document.
The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly
disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific
purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents
are supplied AS IS.
The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase,
market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint
expressed at the time a standard is approved and issued is subject to change brought about through developments in the
state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least
every five years for revision or reaffirmation, or every ten years for stabilization. When a document is more than five
years old and has not been reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to
conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are
cautioned to check to determine that they have the latest edition of any IEEE Standard.
In publishing and making this document available, the IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other
person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon his or
her independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the
advice of a competent professional in determining the appropriateness of a given IEEE standard.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to
specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate
action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is
important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason,
IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant
response to interpretation requests except in those cases where the matter has previously received formal consideration.
A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual
shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be
relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an
individual presenting information on IEEE standards shall make it clear that his or her views should be considered the
personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation
with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Recommendations to change the status of a stabilized standard should include a
rationale as to why a revision or withdrawal is required. Comments and recommendations on standards, and requests
for interpretations should be addressed to:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854
USA
Authorization to photocopy portions of any individual standard for internal or personal use is granted by The Institute
of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center.
To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood
Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for
educational classroom use can also be obtained through the Copyright Clearance Center.
iv
Copyright 2010 IEEE. All rights reserved.
Introduction
This introduction is not part of IEEE Std 1616a-2010, IEEE Standard for Motor Vehicle Event Data Recorders
(MVEDRs)Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA).
In the United States, an estimated 80 million motor vehicles already use some type of event-recording
equipment that collects not only acceleration and deceleration speed but also braking and steering data.
Proponents of standard data recorders hope the crash data they collect will be a useful complement to
accident information gathered from victims and eyewitnesses.
However, the implementation of event data recorders (EDRs) has not been without controversy. The
United States Department of Transportation (USDOT) Docket Management System (DMS) contains over
1000 submissions reflecting the pros and cons of a decade-long debate amongst automakers, government
regulators, safety and privacy advocates, and the public.
The National Highway Traffic Safety Administration (NHTSA) Rule on Event Data Recorders (49 CFR
563 [Bxx]) does not address issues generally within the realm of state law, such as the following:
a

The ownership of EDR data
How EDR data can be used/discovered in civil litigation
How EDR data may be used in criminal proceedings
Whether EDR data may be obtained by the police without a warrant
Whether EDR data may be developed into a driver-monitoring tool
The nature and extent that private parties will have or may contract for access to EDR data
These issues are being addressed by state legislatures. There are many types of recorders. Some
continuously record data, overwriting the previous few minutes until a crash stops them, and others are
activated by crash-like events (such as a sudden change of velocity or angular momentum) and continue to
record until the crash is over. EDRs can record whether or not brakes were used, the speed at the time of
impact, the steering angle, and whether seat belts were worn during the crash. While EDR information can
be useful in determining the cause of a crash, a lockout gives you the reassurance of knowing that you have
control of crash data. The "black box" will still work exactly as it is designed to. However, with a motor
vehicle event data recorder connector lockout apparatus (MVEDRCLA), the vehicle owner (and only the
vehicle owner) determine when and who sees the data and, thus, control how it is used. Ownership of EDR
data is a matter of state law. Generally, the owner of the vehicle is considered to be the rightful owner;
however, courts can subpoena crash data. Crash data can be used in civil and criminal court cases. This
amendment seeks to maintain privacy, prevent tampering, avoid odometer fraud, limit data access, and
enhance safety by using a MVEDRCLA.
While many vehicle purchasers are not aware these devices are in their vehicles, most are unaware of the
nature and potential use of the information collected by their EDR. Data collected by EDRs, without the
drivers knowledge, has been used in civil and criminal cases in several states and in Canada. At least one
automotive insurance company is considering basing policy rates on EDR data. Auto manufacturers could
use EDR data to void warranties. The possibilities are endless.
Several states have already passed laws requiring disclosure of the existence of an EDR in a vehicle, and
protection of a drivers privacy by requiring the owner's permission or a court order before downloading
the EDR data. It is generally agreed that the owner of a vehicle also owns the EDR data as they have
purchased the technology when they bought their vehicle. When consumers drive off the lot with a new car,
they own more than just the vehicle; they own the information their vehicle generates and stores.

a
The numbers in brackets correspond to those of the bibliography in Annex E.
v
A large ever-expanding market exists consisting of: Registered owners of over 243 million motor vehicles;
military vehicles and federal, state, county, and local government vehicles; vehicle OEMs and new car
dealerships that lease vehicles; automotive insurance companies that seek to prevent other parties from
access to data; automotive rental companies that cannot permit odometer tampering; institutional fleets
such as schools, colleges, and universities; business fleets include leasing, construction, plumbing, heating,
food distribution, shipping, utilities; and others such as police, fire, EMS, taxi, etc.
An NHTSA report [Bxx] notes:
Odometer fraud is the illegal practice of rolling back odometers to make it appear that vehicles
have lower mileage than they actually do. This has historically been considered a significant
problem for the American consumer. While any vehicle sold on the used car market could have
been the object of odometer tampering, the problem has been considered to be most prevalent
among late-model vehicles which have accumulated high mileage in a relatively short period of
time. Vehicles in fleets, such as lease fleets, rental fleets, or business company fleets typically
fall into this category. When sold on the used car market, vehicles whose odometers have been
rolled back, or "spun," can obtain artificially high prices, sincle a vehicle's odometer reading is a
key indicator of the condition, and hence the value, of the vehicle.
Notice to users
Laws and regulations
Users of these documents should consult all applicable laws and regulations. Compliance with the
provisions of this standard does not imply compliance to any applicable regulatory requirements.
Implementers of the standard are responsible for observing or referring to the applicable regulatory
requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in
compliance with applicable laws, and these documents may not be construed as doing so.
Copyrights
This document is copyrighted by the IEEE. It is made available for a wide variety of both public and
private uses. These include both use, by reference, in laws and regulations, and use in private self-
regulation, standardization, and the promotion of engineering practices and methods. By making this
document available for use and adoption by public authorities and private users, the IEEE does not waive
any rights in copyright to this document.
Updating of IEEE documents
Users of IEEE standards should be aware that these documents may be superseded at any time by the
issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect. In order to determine whether
a given document is the current edition and whether it has been amended through the issuance of
amendments, corrigenda, or errata, visit the IEEE Standards Association web site at
http://ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously.
For more information about the IEEE Standards Association or the IEEE standards development process,
visit the IEEE-SA web site at http://standards.ieee.org.
vi
Errata
Errata, if any, for this and all other standards can be accessed at the following URL:
http://standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL
for errata periodically.
Interpretations
Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/
index.html.
Patents
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence
or validity of any patent rights in connection therewith. A patent holder or patent applicant has filed a
statement of assurance that it will grant licenses under these rights without compensation or under
reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair
discrimination to applicants desiring to obtain such licenses. Other Essential Patent Claims may exist for
which a statement of assurance has not been received. The IEEE is not responsible for identifying Essential
Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope
of Patents Claims, or determining whether any licensing terms or conditions provided in connection with
submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-
discriminatory. Users of this standard are expressly advised that determination of the validity of any patent
rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information
may be obtained from the IEEE Standards Association.
Participants
At the time this amendment was submitted to the IEEE-SA Standards Board for approval, the Motor
Vehicle Event Data Recorder Connector Lockout Apparatus (MVEDRCLA) Working Group had the
following membership:
Thomas M. Kowalick, Chair
Anthony A. Huffman, Vice Chair
Matthew D. Smith, Secretary
Cheryl J. Whitford, Technical Editor

Michael Bender
Michael Geipel
Louis Horvath
Brian Kopp
Eric Ogilvie
Roh Seunghyun
William Rosenbluth
William Thompson
Eduardo Todt
Dmitri Varsanofiev
Chris Voeglie
Kimball Williams

The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.

John Barr
William Byrd
Keith Chow
Sourav Dutta
Andre Fournier
Randall Groves
Gloria Gwynne
Werner Hoelzl
Anthony Huffman
Piotr Karocki
Walter Keevil
Gerald L. Kolbe
Thomas Kowalick
Thomas Kurihara
Michael S. Newman

Robert Robinson
Seunghyun Roh
Bartien Sayogo
Gil Shultz
James E. Smith
Dmitri Varsanofiev
Kimball Williams
Oren Yuen
When the IEEE-SA Standards Board approved this amendment on 25 March 2010, it had the following
membership:
Robert M. Grow, Chair
Richard H. Hulett, Vice Chair
Steve M. Mills, Past Chair
Judith Gorman, Secretary

Karen Bartleson
Victor Berman
Ted Burse
Clint Chaplin
Andy Drozd
Alexander Gelman
Jim Hughes

Young Kyun Kim
Joseph L. Koepfinger*
John Kulick
David J. Law
Hung Ling
Oleg Logvinov
Ted Olsen

Ronald C. Petersen
Thomas Prevost
Jon Walter Rosdahl
Sam Sciacca
Mike Seavey
Curtis Siller
Don Wright
*Member Emeritus

Also included are the following nonvoting IEEE-SA Standards Board liaisons:

Satish Aggarwal, NRC Representative
Richard DeBlasio, DOE Representative
Michael Janezic, NIST Representative

Lisa Perry
IEEE Standards Program Manager, Document Development

Patricia Gerdon
IEEE Standards Program Manager, Technical Program Development

vii
viii
Contents
1. Overview ..................................................................................................................................................... 2
1.1 Scope .................................................................................................................................................... 2
1.2 Purpose ................................................................................................................................................. 2
1.3 General ................................................................................................................................................. 3
1.4 1.5 Standard structure ........................................................................................................................... 3
3. Definitions, acronyms, and abbreviations ................................................................................................... 4
3.1 Definitions ............................................................................................................................................ 4
3.2 Acronyms and abbreviations ................................................................................................................ 4
6. Output .......................................................................................................................................................... 5
6.14 MVEDRCLA Manual Lockout Device Protocol ................................................................................ 5
6.14.1 General ....................................................................................................................................... 5
6.14.2 Ease of access to an MVEDRCLA ............................................................................................ 5
6.14.3 Accessibility and control of an MVEDRCLA ........................................................................... 5
6.14.4 Locking and unlocking of an MVEDRCLA .............................................................................. 5
6.14.5 Keys and key codes .................................................................................................................... 5
6.14.6 Replacement keys or other opening devices .............................................................................. 6
6.14.7 Value-added components to an MVEDRCLA ........................................................................... 6
6.14.8 Vehicle operation with an MVEDRCLA ................................................................................... 6
9. Conformance ............................................................................................................................................... 6
Annex E (informative) Bibliography ............................................................................................................... 7

IEEE Standard for Motor Vehicle
IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or
environmental protection. Implementers of the standard are responsible for determining appropriate
safety, security, environmental, and health practices or regulatory requirements.
This IEEE document is made available for use subject to important notices and legal disclaimers.
These notices and disclaimers appear in all publications containing this document and may
be found under the heading Important Notice or Important Notices and Disclaimers
Concerning IEEE Documents. They can also be obtained on request from IEEE or viewed at
http://standards.ieee.org/IPR/disclaimers.html.
NOTEThe editing instructions contained in this corrigendum define how to merge the material contained
therein into the existing base standard and its amendments to form the comprehensive standard.
1

The editing instructions are shown in bold italic. Four editing instructions are used: change, delete, insert,
and replace. Change is used to make corrections in existing text or tables. The editing instruction specifies
the location of the change and describes what is being changed by using strikethrough (to remove old
material) and underscore (to add new material). Delete removes existing material. Insert adds new material
without disturbing the existing material. Insertions may require renumbering. If so, renumbering
instructions are given in the editing instruction. Replace is used to make changes in figures or equations by
removing the existing figure or equation and replacing it with a new one. Editing instructions, change
markings, and this NOTE will not be carried over into future editions because the changes will be
incorporated into the base standard.

1
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.
1
IEEE Std 1616a-2010
IEEE Standard for Motor Vehicle Event Data Recorders (MVEDRs)
Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)
2
1. Overview
1.1 Scope
Change the scope as follows:
Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store, and export data related to motor
vehicle predefined events in usage history. This standard defines a protocol for MVEDR output data
compatibility and export protocols of MVEDR data elements. This standard does not prescribe which
specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This
standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic
link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector
(DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or
within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to
permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions
status, maintenance, and/or repair. It is applicable to vehicles and their respective event data recorders for
all types of motor vehicles licensed to operate on public roadways, whether offered as original or
aftermarket equipment, whether stand-alone or integrated into the vehicle.
1.2 Purpose
Change the purpose as follows:
Many light-duty vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some
form of MVEDR. These systems, which are designed and produced by individual motor vehicle
manufacturers and component suppliers, are diverse in function and proprietary in nature, however, the
SAE J1962 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus
universally used to access event data recorder information.
2
Data access via the DLC can be accomplished
by using scan tools or microcomputers and network interfaces. This same DLC and network interface is
also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include
restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol
to protect against misuse of electronic tools which use the DLC to erase, modify or tamper with electronic
controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA
provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which will
act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to
emissions violations and theft of personal data. Adoption of this standard will therefore make the common
MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users.
The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data
output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of
the standard will therefore make MVEDR data more accessible and useful to end users.

2
The numbers in brackets correspond to those of the bibliography in Annex E.
IEEE Std 1616a-2010
Insert the following subclause 1.3 and renumber accordingly:
1.3 General
Crash information is critical to understanding causation leading up to the crash, occupant kinematics, and
vehicle performance during a crash, and post-crash events. Manufacturers, engineers, policy makers,
researchers, and others rely on crash information to improve vehicle design, shape regulatory policy,
develop injury criteria, detect vehicle defects, and resolve investigations and litigation. Motor vehicles have
markedly transitioned from mechanical machines with mechanical controls to highly technological vehicles
with integrated electronic systems and sensors. Modern automobiles generate, utilize, and analyze
electronic data to improve vehicle performance, safety, security, comfort, and emissions. Surrounding a
crash, capture of a subset of vehicle data on an MVEDR makes important information readily available for
medical responders, crash investigators, and researchers. The degree of societal benefit from MVEDRs is
directly related to the number of vehicles operating with an MVEDR and the ability to retrieve and utilize
these data. Having standardized data definitions and formats allows the capture of vehicle crash
information. This standard recognizes the value of improved crash information in improving the knowledge
of what happens before, during, and after a motor vehicle crash. Such insights will provide major benefits
to society and significantly improve the science of motor vehicle crashes.
The past four decades have witnessed an exponential increase in the number and sophistication of
electronic systems in vehicles. A vast increase in automotive electronic systems, coupled with related
memory storage technologies, has created an array of new safety engineering opportunities and subsequent
consumer acceptance challenges. Virtually every passenger car and light truck manufactured in or imported
to the North American market since model year 1996 includes an Environmental Protection Agency (EPA)
mandated DLC to allow access to engine and emissions diagnostic data. This onboard DLC (OBDII) is
regulated by the Code of Federal Regulations (CFR) (40 CFR 86.094-17(h) [Bxx]) and revisions for
subsequent model years. It is standardized by the Society of Automotive Engineers (SAE) Vehicle
Electrical Engineering Systems Diagnostic Standards Committee. The physical configuration of the output
plug is specified under SAE J1962-2002 [Bxx] and through the International Standards Organization under
ISO 15031-3:2004 [Bxx] and is increasingly used as an access point to other in-vehicle electronics systems,
subsystems, computers, sensors, actuators and an array of control modules including the air bag control
module. The onboard DLC is also used as a serial port to retrieve data elements from on-board systems,
subsystems, modules, devices and functions that collect and store data elements related to a vehicle crash
such as a restraint control module (RCM) and event data recorder (EDR). Thus, the onboard DLC provides
a portal for capture of an increasing volume of sophisticated sensor data regarding the operating condition,
operation and behavior of vehicles, and in particular the operation and behavior of vehicles involved in
crashes. Consumers continue to be interested in safety advancements but remain concerned about issues of
privacy, tampering, and misuse of vehicle crash data. It is important to protect a variety of crash-sensing
and diagnostic memory modules. Increasingly, data from these devices have been used in civil and criminal
court cases nationwide, including cases dealing with vehicular homicide in which speed was an issue. Thus,
this standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR
data elements and a protocol for an MVEDRCLA.
1.4 1.5 Standard structure
Change the seventh paragraph of subclause 1.5 as follows:
Clause 6, Output, defines common interfaces that may be utilized to extract MVEDR data and also details
the protocol for the MVEDRCLA.
3
IEEE Std 1616a-2010
3. Definitions, acronyms, and abbreviations
3.1 Definitions
Insert the following definitions in alphabetical order:
3.1.x connection: Two mated connectors or contacts.
3.1.x connector: Assembly of contact and housing, which terminates conductors for the purpose of
providing connection and disconnection to a suitable mating connector.
3.1.x connector lockout apparatus (CLA): Device or mechanism to secure a connector.
3.1.x contact: Conductive element in a connector (including means for cable attachment) that mates with a
corresponding element to provide an electrical path.
3.1.x high-security non-reproducible lock: A lock/key blank coded with serial numbers that is self-
certified by the OEM as "unpickable" by professional locksmith tools and not available to the public,
meaning that any duplication is by the original manufacturer.
3.1.x lock: Device or mechanism to secure an area.
3.1.x motor vehicle event data recorder connector lockout apparatus (MVEDRCLA): A device to
secure a connector from tampering.
3.1.x odometer: An instrument for measuring the distance traveled by a vehicle.
3.1.x odometer fraud: The illegal practice of rolling back an odometer to make it appear that a vehicle has
lower mileage than its actual mileage.
3.1.x tampering: Means to modify, remove, render inoperative, cause to be removed, or to make less
operative any device or element on a motor vehicle or motor vehicle power train, chassis, or body
components that results in altering Federal Vehicle Motor Safety Standards (FMVSSs).
3.1.x vehicle identification number (VIN) modification: Use of an electronic device connected to the
vehicle diagnostic link connector to modify the VIN to a value other than the number provided by the
original manufacturer of the vehicle.
3.2 Acronyms and abbreviations
Insert the following acronyms and abbreviations in alphabetical order:
ANSI American National Standard Institute
CLA connector lockout apparatus
MVEDRCLA motor vehicle event data recorder connector lockout apparatus
SCC Standards Coordinating Committee
4
IEEE Std 1616a-2010
5
6. Output
Insert subclause 6.14 as follows:
6.14 MVEDRCLA Manual Lockout Device Protocol
6.14.1 General
This protocol is applicable to all types and classes of motor vehicles that include MVEDRs. An
MVEDRCLA Manual Lockout Device Protocol is a method of operation for a device (the MVEDRCLA)
that holds the associated device (the DLC) inoperative to tampering unless a predetermined manual
function (key or coded signal) is performed to release the locking feature.
To install the MVEDRCLA, first find the OBDII port (SAE J1962 connector) on your vehicle. The location
of this port varies by manufacturer and model but all post 1996 vehicles are required to include this port.
The D-shaped OBDII port (SAE J1962 connector) will be located within 0.9144 m (3 ft) of the steering
wheel and should be easily accessible to a person in the driver's seat. If difficulty is experienced when
locating the OBDII port, look under the dashboard or in the dashboard area in front of the passenger seat.
Once the OBDII connector is found, plug the MVEDRCLA into itto prevent tampering. What the
MVEDRCLA does, essentially, is put a lock on the data recorder diagnostic port so one has control over
who accesses it. The MVEDRCLA may be removed for maintenance or inspection by reversing the
process.
6.14.2 Ease of access to an MVEDRCLA
Access to the vehicle MVEDRCLA shall not require a tool for the removal of an instrument panel cover,
connector cover, or any barriers.
6.14.3 Accessibility and control of an MVEDRCLA
MVEDRCLA security connectors designed to prevent data tampering, odometer fraud, VIN theft, or re-
engineering of vehicle networks shall be accessible and controlled by the vehicle owner and shall not
prevent emissions testing, vehicle maintenance, or repair of in-vehicle electronic systems, subsystems,
computers, sensors, actuators, or control modules, including the air bag control module.
6.14.4 Locking and unlocking of an MVEDRCLA
The owner shall control the means to lock and unlock the MVEDRCLA. The MVEDRCLA shall be
operational by either a mechanical lock or a mechanical-electrical lock via a coded signal.
6.14.5 Keys and key codes
MVEDRCLA keys shall be rated high security, non-reproducible other than by the OEM and shall be
coded with serial numbers. (See 3.1.x for the definition of high-security non-reproducible lock.) High-
security non-reproducible locks shall be self-certified by the OEM.
IEEE Std 1616a-2010
6
6.14.6 Replacement keys or other opening devices
OEMs of MVEDRCLAs shall provide the owner of the vehicle a means to receive a replacement key.
6.14.7 Value-added components to an MVEDRCLA
An MVEDRCLA may include a microchip memory component attached for storage of information
applicable to providing services to an operator of a motor vehicle. The microchip memory component may
include stored information such as timestamp, vehicle ownership, VIN, insurance, personal medical data,
and healthcare provider information.
6.14.8 Vehicle operation with an MVEDRCLA
Vehicles with an MVEDRCLA shall not change the normal physical and electrical operation of the vehicle
when attached to any external test equipment from that expected when the same equipment is attached
without an MVEDRCLA.
9. Conformance
Insert the following text as the last paragraph of Clause 9:
To claim conformance to the MVEDRCLA protocol, a product or service shall meet all of the mandatory
requirements defined by this standard. As part of the conformance claim, the implementation shall provide
a conformance statement that includes the means for the consumer to receive a replacement key or opening
device.
IEEE Std 1616a-2010
Annex E

(informative)

Bibliography
Change the following informative references and renumber accordingly:
[Bxx] ASTM E2493-07, Standard Guide for the Collection of Non-Volatile Memory Data in Evidentiary
Vehicle Electronic Control Units.
3

[Bxx] Code of Federal Regulations Title 40 Part 86.094-17(h), Protection of EnvironmentControl of
Emissions from New and In-Use Highway Vehicles and Engines.
4

[Bxx] Code of Federal Regulations Title 49 Part 563, TransportationEvent Data Recorders.
[Bxx] ISO 8092-2:2000, Road vehiclesConnections for on-board electrical wiring harnessesPart 2:
Definitions, test methods and general performance requirements.
[Bxx] ISO 9141-2:19941996, Road vehiclesDiagnostic systemsPart 2: CARB Carbo requirements for
interchange of digital information.
[Bxx] ISO 9141-2:1994/Amd 1:1996, Road vehiclesDiagnostic systemsPart 2: CARB requirements
for interchange of digital informationAmendment 1.
[Bxx] ISO 9141-3:1998, Road vehiclesDiagnostic systemsPart 3: Verification of the communication
between vehicle and OBD II scan tool.
[Bxx] ISO 14229-1:2006, Road vehiclesUnified diagnostic services (UDS)Part 1: Specification and
requirements.
[Bxx] ISO 14230-4:2000, Road vehiclesDiagnostic systemsKeyword Protocol 2000Part 4:
Requirements for emission-related systems.
[Bxx] ISO 15031-3:2004, Road vehiclesCommunication between vehicle and external equipment for
emissions-related diagnosticsPart 3: Diagnostic connector and related electrical circuits, specification
and use.
[Bxx] ISO 15031-4:2005, Road vehiclesCommunication between vehicle and external equipment for
emissions-related diagnosticsPart 4: External test equipment.
[Bxx] ISO 15765-4:2005, Road vehiclesDiagnostics on Controller Area Networks (CAN)Part 4:
Requirements for emissions-related systems.
[Bxx] ISO 16750-2:2010, Road vehiclesEnvironmental conditions and testing for electrical and
electronic equipmentPart 2: Electrical loads.

3
ASTM publications are available from the American Society for Testing and Materials, 100 Barr Harbor Drive, West
Conshohocken, PA 19428-2959, USA (http://www.astm.org/).
4
CFR publications are available from the U.S. Government Printing Office, 732 N. Capitol Street, Washington, DC 20401, USA
(http://www.gpo.gov/).
7
IEEE Std 1616a-2010
8
[Bxx] ISO 22900-1:2008, Road vehiclesModular vehicle communication interface (MVCI)Part 1:
Hardware design requirements.
[Bxx] ISO/CD 13400-1 (1 March 2010), Road VehiclesDiagnostic communication between test
equipement and vehicle over Internet protocolPart 1: General information and use-case definition.
equipement and vehicle over Internet protocolPart 2: Network and transport layer requirements and
services.
equipement and vehicle over Internet protocolPart 3: IEEE 802.3 based wired vehicle interface.
[Bxx] ISO/CD 14229-2 (28 March 2010), Road vehiclesUnified diagnostic services (UDS)Part 2:
Session layer services.
[Bxx] ISO/IEC 7498-1:1994, Information technologyOpen Systems InterconnectionBasic Reference
Model: The Basic Model.
[Bxx] ISO/IEC 10731:1994, Information technologyOpen Systems InterconnectionBasic Reference
ModelConventions for the definition of OSI services.
[Bxx] ISO/PAS 27145-1:2006, Road vehiclesImplementation of WWH-OBD communication
requirementsPart 1: General information and use case definition.
requirementsPart 2: Common emissions-related data dictionary.
requirementsPart 3: Common message dictionary.
requirementsPart 4: Connection between vehicle and test equipment.
[Bxx] NHTSA Report Number DOT HS 809 441, Preliminary Report: The Incidence Rate of Odometer
Fraud, April 2002.
5

[Bxx] SAE J1850-2001, Class B Data Communications Network Interface [OBD II, Not EU].
This standard defines a serial data protocol. There are two variants10.4 kbit/s (single-wire,
VPW) and 41.6 kbit/s (two-wire, PWM)that are mainly used by U.S. manufacturers, also known
as PCI (10.4K), Class 2 (10.4K), and SCP (41.6K).
[Bxx] SAE J1930-DA, Digital Annex, Electrical/Electronic Systems Diagnostic Terms, Definitions and
Abbreviations.
[Bxx] SAE J1962-2002, Diagnostic ConnectorEquivalent to ISO/DIS 15031-3:December 14, 2001.
This standard defines the physical connector used for the OBD-II interface.
[Bxx] SAE J1978-2002, OBD II Scan ToolEquivalent to ISO/DIS 15031-4:December 14, 2001.
This standard defines minimal operating standards for OBD-II scan tools.

5
Available at http://www.nhtsa.gov/Cars/rules/regrev/evaluate/809441.html.
IEEE Std 1616a-2010
9
[Bxx] SAE J1979-2002, E/E Diagnostic Test ModesEquivalent to ISO/DIS 15031-5:April 30, 3003
[emissions].
[Bxx] SAE J2012-2007, Diagnostic Trouble Code definitions.
[Bxx] SAE J2178/1-2004, Class B Data Communication Network MessagesPart 1: Detailed Header
Formats and Physical Address Assignments.
[Bxx] SAE J2178/2-2004, Class B Data Communication Network MessagesPart 2: Data Parameter
Definitions.
[Bxx] SAE J2178/3-2004, Class B Data Communication Network MessagesPart 3: Frame IDs for
Single-Byte Forms of Headers.
[Bxx] SAE J2178/4-2004, Class B Data Communication Network MessagesPart 4: Message Definitions
for Three Byte Headers.
[Bxx] SAE J2284/3-2010, High-Speed CAN (HSC) for Vehicle Applications at 500 KBPS.


Ieee STD 1616a

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ieee STD 1616a

Uploaded by

Copyright:

Available Formats

IEEE Std 1616a"-2010

You might also like