This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Energy Transfer System for Electric Vehicles - Part 2: Communication Requirements and Network Architecture
- Ground Vehicle Standard
- J2293/2_201402
- Stabilized
Downloadable datasets available
Annotation ability available
Sector:
Issuing Committee:
Language:
English
Scope
SAE J2293 establishes requirements for Electric Vehicles (EV) and the off-board Electric Vehicle Supply Equipment (EVSE) used to transfer electrical energy to an EV from an Electric Utility Power System (Utility) in North America. This document defines, either directly or by reference, all characteristics of the total EV Energy Transfer System (EV-ETS) necessary to insure the functional interoperability of an EV and EVSE of the same physical system architecture. The ETS, regardless of architecture, is responsible for the conversion of AC electrical energy into DC electrical energy that can be used to charge the Storage Battery of an EV, as shown in Figure 1.
The different physical ETS system architectures are identified by the form of the energy that is transferred between the EV and the EVSE, as shown in Figure 2. It is possible for an EV and EVSE to support more than one architecture.
This document does not contain all requirements related to EV energy transfer, as there are many aspects of an EV and EVSE that do not affect their interoperability. Specifically, this document does not deal with the characteristics of the interface between the EVSE and the Utility, except to acknowledge the Utility as the source of energy to be transferred to the EV.
The functional requirements for the ETS are described using a functional decomposition method. This is where requirements are successively broken down into simpler requirements and the relationships between requirements are captured in a graphic form. The requirements are written as the transformation of inputs into outputs, resulting in a model of the total system.
Each lowest level requirement is then allocated to one of four functional groups (FG) shown in Figure 2. These groups illustrate the variations of the three different system architectures, as the functions they represent will be accomplished either on an EV or within the EVSE, depending on the architecture. Physical requirements for the channels used to transfer the power and communicate information between the EV and the EVSE are then defined as a function of architecture. System architecture variations are referred to as follows:
-
a
Type A—Conductive AC System Architecture—J2293-1—6.2.1
-
b
Type B—Inductive System Architecture —J2293-1—6.2.2
-
c
Type C—Conductive DC System Architecture—J2293—6.2.3
The requirements model in Section 6 is not intended to dictate a specific design or physical implementation, but rather to provide a functional description of the system’s expected operational results. These results can be compared against the operation of any specific design. Validation against this document is only appropriate at the physical boundary between the EVSE and EV. See Section 8.
Rationale
This stabilized Recommended Practice documents for reference the historical state of energy transfer systems and communications for electric vehicles as they existed in 2008, as defined in SAE J1772 (per published version 11-1-2001) for conductive charging and SAE J1773 (per published version 11-1-1999) for inductive charging.
SAE J1772 continues to be updated to reflect the latest in conductive charging technology. See the latest available version of J1772.
SAE J1773 remains unchanged for inductive charging.
Documentation for the now-emerging “wireless” inductive charging systems will be published when available.
Grid power quality for supplying charging systems is covered in SAE document series J2894.
For state-of-the-art documentation on charging communications, refer to the SAE documents in the series J2836, J2847, J2931, and J2953.
Topic
Data Sets - Support Documents
| Title | Description | Download |
|---|---|---|
| Unnamed Dataset 1 | ||
| Unnamed Dataset 2 | ||
| TABLE 1 | SAE J2293-2 REQUIREMENT’S SCOPE | |
| TABLE 2 | SUPPORTED MESSAGE OPERATORS | |
| TABLE 3 | SUPPORTED MESSAGING SEQUENCES | |
| Unnamed Dataset 6 | ||
| TABLE 4 | DESCRIPTION OF APPLICATION MODES | |
| Unnamed Dataset 8 | ||
| TABLE 5 | ETS NETWORK MODES DT | |
| Unnamed Dataset 10 | ||
| Unnamed Dataset 11 | ||
| Unnamed Dataset 12 | ||
| Unnamed Dataset 13 | ||
| Unnamed Dataset 14 | ||
| Unnamed Dataset 15 | ||
| TABLE 6 | DETECT APPLICATION FAULT TEMPLATE CONTEXT FLOW SUBSTITUTIONS | |
| Unnamed Dataset 17 | ||
| TABLE 7 | MANAGE EVSE COMMUNICATIONS CONTEXT FLOW SUBSTITUTIONS | |
| Unnamed Dataset 19 | ||
| TABLE 8 | OFF-BOARD_EXT NETWORK MODES DT | |
| Unnamed Dataset 21 | ||
| Unnamed Dataset 22 | ||
| Unnamed Dataset 23 | ||
| Unnamed Dataset 24 | ||
| TABLE 9 | DETECT APPLICATION FAULT TEMPLATE CONTEXY FLOW SUBSTITUTIONS | |
| Unnamed Dataset 26 | ||
| TABLE 10 | MANAGE OFF-BOARD EXT COMMUNICATIONS CONTEXT FLOW SUBSTITUTIONS | |
| TABLE 11 | PAT 2.1P1 | |
| Unnamed Dataset 29 | ||
| TABLE 12 | SINGLE WIRE STATE ARBITRATION TABLE | |
| Unnamed Dataset 31 | ||
| TABLE 13 | DUAL WIRE STATE ARBITRATION TABLE | |
| Unnamed Dataset 33 | ||
| TABLE 14 | COUPLING STATE TABLE | |
| TABLE 15 | SAE J1772 - TYPE 1 MEDIA - EVSE NETWORK REQUIREMENTS | |
| TABLE 16 | SAE J1772 - TYPE 1 MEDIA - EVSE NETWORK REQUIREMENTS | |
| TABLE 17 | J1773 EVSE NETWORK REQUIREMENTS | |
| TABLE 18 | SAE J1772 - TYPE 1 MEDIA EV NETWORK REQUIREMENTS | |
| TABLE 19 | SAE J1772 - TYPE 2 MEDIA, EV NETWORK REQUIREMENTS | |
| TABLE 20 | SAE J1773 EV NETWORK REQUIREMENTS | |
| Unnamed Dataset 41 | ||
| Unnamed Dataset 42 | ||
| TABLE 21 | EV ETS NETWORK MODES DT | |
| Unnamed Dataset 44 | ||
| Unnamed Dataset 45 | ||
| Unnamed Dataset 46 | ||
| Unnamed Dataset 47 | ||
| TABLE 22 | DETECT APPLICATION FAULT TEMPLATE CONTEXT FLOW SUBSTITUTIONS | |
| Unnamed Dataset 49 | ||
| TABLE 23 | MANAGE EV ETS COMMUNICATIONS CONTEXT FLOW SUBSTITUTIONS | |
| TABLE 24 | INDICATE APP IS ACTIVE IN NODE PAT | |
| TABLE 25 | INDICATE APP IS ACTIVE IN NODE PAT | |
| Unnamed Dataset 53 | ||
| Unnamed Dataset 54 | ||
| Unnamed Dataset 55 | ||
| Unnamed Dataset 56 | ||
| Unnamed Dataset 57 | ||
| TABLE 26 | FUNCTION BIT DECODING TABLE | |
| Unnamed Dataset 59 | ||
| Unnamed Dataset 60 | ||
| TABLE 27 | FUNCTION BIT ENCODING | |
| Unnamed Dataset 62 | ||
| Unnamed Dataset 63 | ||
| Unnamed Dataset 64 | ||
| Unnamed Dataset 65 | ||
| Unnamed Dataset 66 | ||
| Unnamed Dataset 67 | ||
| Unnamed Dataset 68 | ||
| Unnamed Dataset 69 | ||
| Unnamed Dataset 70 | ||
| TABLE 28 | EVSE SOURCE ADDRESS SELECTION | |
| TABLE 29 | EVSE SOURCE ADDRESS SELECTION | |
| Unnamed Dataset 73 | ||
| Unnamed Dataset 74 | ||
| TABLE 30 | LAUNCH APP SERVICE REQUEST PAT | |
| Unnamed Dataset 76 | ||
| Unnamed Dataset 77 | ||
| TABLE 31 | MAINTAIN ETS APP STATE CONTEXT SUBSTITUTIONS | |
| Unnamed Dataset 79 | ||
| TABLE 32 | LAUNCH APP SERVICE REQUEST CONTEXT SUBSTITUTIONS | |
| Unnamed Dataset 81 | ||
| TABLE 33 | MAINTAIN APP SERVICE REQUEST ENABLE CONTEXT SUBSTITUTIONS | |
| Unnamed Dataset 83 | ||
| TABLE 34 | INDICATE APPLICATION IS ACTIVE CONTEXT FLOW SUBSTITUTIONS | |
| Unnamed Dataset 85 | ||
| Unnamed Dataset 86 | ||
| TABLE 35 | MANAGE APPLICATION SLAVE NODE COMMUNICATION TEMPLATE DATA DICTIONARY | |
| TABLE 36 | INDICATE APP IS ACTIVE IN NODE PAT | |
| Unnamed Dataset 89 | ||
| Unnamed Dataset 90 | ||
| Unnamed Dataset 91 | ||
| Unnamed Dataset 92 | ||
| TABLE 37 | LAUNCH APP STATE CONTEXT SUBSTITUTIONS | |
| Unnamed Dataset 94 | ||
| TABLE 38 | MAINTAIN APP SERVICE REQUEST CONTEXT SUBSTITUTIONS | |
| Unnamed Dataset 96 | ||
| TABLE 39 | LAUNCH APP STATE CONTEXT SUBSTITUTIONS | |
| Unnamed Dataset 98 | ||
| TABLE 40 | MANAGE APPLICATION MASTER NODE COMMUNICATION TEMPLATE DATA DICTIONARY | |
| Unnamed Dataset 100 | ||
| Unnamed Dataset 101 | ||
| Unnamed Dataset 102 | ||
| TABLE 41 | DETECT APPLICATION TRANSMITTER FAULT TEMPLATE DATA DICTIONARY | |
| TABLE 42 | SAE J2293-2 LAUNCH STRATEGIES | |
| TABLE 43 | LAUNCH MESSAGE TEMPLATE CONFIGURATION STORES | |
| TABLE 44 | TYPICAL VALUES FOR LAUNCH STRATEGIES | |
| Unnamed Dataset 107 | ||
| Unnamed Dataset 108 | ||
| Unnamed Dataset 109 | ||
| Unnamed Dataset 110 | ||
| Unnamed Dataset 111 | ||
| Unnamed Dataset 112 | ||
| Unnamed Dataset 113 | ||
| Unnamed Dataset 114 | ||
| Unnamed Dataset 115 | ||
| Unnamed Dataset 116 | ||
| Unnamed Dataset 117 | ||
| Unnamed Dataset 118 | ||
| Unnamed Dataset 119 | ||
| TABLE 45 | DATA DICTIONARY FOR LAUNCH MESSAGE TEMPLATE | |
| TABLE 46 | SAE J2293-2 RECEPTION STRATEGIES | |
| TABLE 47 | MAINTAIN PARAMETER TEPLATE CONFIGURATION STORES | |
| TABLE 48 | TYPICAL VALUES FOR RECEIVE STRATEGIES | |
| Unnamed Dataset 124 | ||
| Unnamed Dataset 125 | ||
| Unnamed Dataset 126 | ||
| Unnamed Dataset 127 | ||
| Unnamed Dataset 128 | ||
| Unnamed Dataset 129 | ||
| Unnamed Dataset 130 | ||
| Unnamed Dataset 131 | ||
| Unnamed Dataset 132 | ||
| Unnamed Dataset 133 | ||
| TABLE 49 | DEFAULTING EVENTS | |
| Unnamed Dataset 135 | ||
| Unnamed Dataset 136 | ||
| TABLE 50 | MAINTAIN PARAMETER TEMPLATE DATA DICTIONARY | |
| TABLE 51 | EVSE MESSAGE REQUIREMENT MATRIX | |
| TABLE 52 | EVSE MESSAGE REQUIREMENT MATRIX | |
| TABLE 53 | EXTERNAL MESSAGE REQUIREMENTS MATRIX | |
| Unnamed Dataset 141 | ||
| TABLE 54A | MESSAGE REQUIREMENTS PER ARCHITECTURE | |
| Unnamed Dataset 143 | ||
| TABLE 54B | MESSAGE REQUIREMENTS PER ARCHITECTURE | |
| Unnamed Dataset 145 | ||
| TABLE 54C | MESSAGE REQUIREMENTS PER ARCHITECTURE | |
| Unnamed Dataset 147 | ||
| TABLE 55 | PARAMETER PROCESS CALIBRATIONS | |
| TABLE 56 | MESSAGE LATENCY AND DATAFLOW CROSS REFERENCE | |
| TABLE 57 | REQUIREMENT ALLOCATION TO ARCHITECTURAL ELEMENTS AND INTERFACES | |
| TABLE 58 | DATA DICTIONARY | |
| TABLE 18 | ELECTRIC VEHICLE ENERGY TRANSFER SYSTEM (EV-ETS) PRN ASSIGNMENTS (PRNS C800–C8FF) | |
| Unnamed Dataset 153 | ||
| Unnamed Dataset 154 | ||
| Unnamed Dataset 155 | ||
| Unnamed Dataset 156 | ||
| TABLE AA | ||
| Unnamed Dataset 158 | ||
| TABLE XX | ELECTRIC VEHICLE ENERGY TRANSFER SYSTEM |
Issuing Committee
The Hybrid Technical Standards Committee reports to the Powertrain Systems Group of the Motor Vehicle Council. The Committee is responsible for developing and maintaining SAE Standards, Recommended Practices, and Information Reports related to the field of hybrid vehicle technology. The following topics are within the scope of this committee's work: ¿ safety aspects of hybrid systems in vehicles ¿ test procedures to establish the performance of hybrid systems and components ¿ nomenclature ¿ vehicle interface and serviceability requirements Participants in the SAE Hybrid Technical Standards Committee include OEMs, suppliers, consulting firms, government, and other interested parties.
Reference
* Redlines comparisons are available for those standards
listed in the Revision History that contain a radio button. A
redline comparison of the current version against a revision is
accomplished by selecting the radio button next to the standard and
then selecting 'compare'. At this time, Redline versions only exist
for some AMS standards. SAE will continue to add redline versioning
with ongoing updates to SAE MOBILUS.