This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Communication Between Plug-In Vehicles and Off-Board DC Chargers
- Ground Vehicle Standard
- J2847/2_201504
- Revised
Downloadable datasets available
Annotation ability available
Sector:
Issuing Committee:
Language:
English
Scope
This SAE Recommended Practice SAE J2847-2 establishes requirements and specifications for communication between Plug-in Electric Vehicle (PEV) and the DC Off-board charger. Where relevant, this document notes, but does not formally specify, interactions between the vehicle and vehicle operator.
This document applies to the off-board DC charger for conductive charging, which supplies DC current to the Rechargable Energy Storage System (RESS) of the electric vehicle through a SAE J1772™ coupler. Communications will be on the SAE J1772 Pilot line for PLC communication. The details of PowerLine Communications (PLC) are found in SAE J2931/4.
The specification supports DC energy transfer via Forward Power Flow (FPF) from source to vehicle.
SAE has published multiple documents relating to PEV and vehicle-to-grid interfaces. The various document series are listed below, with a brief explanation of each.
Figure 1.1 shows the sequencing of these documents and their primary function (e.g., the J2836 and J2847/1 documents start with Smart Charging, J2836 and J2847/2 then adds DC charging, etc.). The intent is to have subsequent slash sheets complement each other as more functions and features are included. The /6 series of documents add wireless charging items not already included in the proceeding slash sheets. These are all then included in Interoperability in SAE J2953 and security in SAE J2931/7. J3072 then includes the PEV to grid requirements for Vehicle to Grid (V2G) power and communication to match J2836/3 Use Cases.
The summary of documents for DC Charging is then as follows:
-
SAE J1772™ is the PEV to EVSE systems document and includes the system and timing diagrams for DC Charging
-
SAE J2836/2™ starts with the Use Cases for DC Charging communications
-
SAE J2847/2 then transforms these Use Case requirements into the signals and messages
-
SAE J2931/1 is where the Protocol requirements are placed for all PEV communications
-
SAE J2931/4 is used for the PLC communication requirements for DC Charging since it is only a wired median
-
SAE J2953/1 is the Interoperability requirements
-
SAE J2953/2 is the Interoperability procedure and plan
-
SAE J2931/7 includes the security
Rationale
SAE J2847/2 provides messages for DC energy transfer. The updated version in August, 2012 was aligned with the DIN SPEC 70121 Candidate 2 and additions to J1772™ for DC charging, published October, 2012. This revision will include results from implementation and changes not included in the previous version. This will also include effects from DC discharging or Reverse Power Flow to off-board equipment that expands on J2847/3 for AC energy flow off the vehicle, and other Distributed Energy Resource functions that is being developed from the use cases in J2836/3™, published January, 2013.
Recommended Content
| Ground Vehicle Standard | Digital Communications for Plug-in Electric Vehicles |
| Ground Vehicle Standard | Broadband PLC Communication for Plug-in Electric Vehicles |
Topic
Data Sets - Support Documents
| Title | Description | Download |
|---|---|---|
| Unnamed Dataset 1 | ||
| Unnamed Dataset 2 | ||
| Unnamed Dataset 3 | ||
| Unnamed Dataset 4 | ||
| Unnamed Dataset 5 | ||
| Unnamed Dataset 6 | ||
| Unnamed Dataset 7 | ||
| Unnamed Dataset 8 | ||
| Unnamed Dataset 9 | ||
| Unnamed Dataset 10 | ||
| Unnamed Dataset 11 | ||
| Unnamed Dataset 12 | ||
| Table 1 | Semantics for EVSESupportedEnergyTransferType | |
| Unnamed Dataset 14 | ||
| Table 2 | Semantics and type definition for EVErrorCodeType | |
| Unnamed Dataset 16 | ||
| Unnamed Dataset 17 | ||
| Unnamed Dataset 18 | ||
| Unnamed Dataset 19 | ||
| Table 3 | Semantics & Types of Elements in the isolationLevelType | |
| Table 4 | Semantics and Type Definition for EVSEStatusCodeType | |
| Unnamed Dataset 22 | ||
| Unnamed Dataset 23 | ||
| Unnamed Dataset 24 | ||
| Table 5 | Semantics and Type Definition for PhysicalValueType | |
| Unnamed Dataset 26 | ||
| Unnamed Dataset 27 | ||
| Unnamed Dataset 28 | ||
| Unnamed Dataset 29 | ||
| Unnamed Dataset 30 | ||
| Unnamed Dataset 31 | ||
| Table 7 | Semantics and Type Definition for SelectedServiceType | |
| Unnamed Dataset 33 | ||
| Unnamed Dataset 34 | ||
| Unnamed Dataset 35 | ||
| Unnamed Dataset 36 | ||
| Unnamed Dataset 37 | ||
| Unnamed Dataset 38 | ||
| Unnamed Dataset 39 | ||
| Unnamed Dataset 40 | ||
| Unnamed Dataset 41 | ||
| Unnamed Dataset 42 | ||
| Unnamed Dataset 43 | ||
| Unnamed Dataset 44 | ||
| Unnamed Dataset 45 | ||
| Unnamed Dataset 46 | ||
| Unnamed Dataset 47 | ||
| Unnamed Dataset 48 | ||
| Unnamed Dataset 49 | ||
| Unnamed Dataset 50 | ||
| Unnamed Dataset 51 | ||
| Unnamed Dataset 52 | ||
| Unnamed Dataset 53 | ||
| Unnamed Dataset 54 | ||
| Unnamed Dataset 55 | ||
| Table 8 | EVCC and SECC Timers, Timeouts, Performance Times | |
| Table 9 | EVCC and SECC Message Timeouts and Performance times | |
| Unnamed Dataset 58 | ||
| Unnamed Dataset 59 | ||
| Table 10 | EVCC and SECC Communication Session Timing Parameters | |
| Table 11 | EVCC and SECC Communication Session Timing Parameter Values | |
| Unnamed Dataset 62 | ||
| Unnamed Dataset 63 | ||
| Table 12 | Semantics and Type Definition for a V2G Message | |
| Table 13 | Semantics and Type Definition for a V2G Message Header | |
| Unnamed Dataset 66 | ||
| Unnamed Dataset 67 | ||
| Unnamed Dataset 68 | ||
| Unnamed Dataset 69 | ||
| Unnamed Dataset 70 | ||
| Unnamed Dataset 71 | ||
| Unnamed Dataset 72 | ||
| Unnamed Dataset 73 | ||
| Unnamed Dataset 74 | ||
| Unnamed Dataset 75 | ||
| Unnamed Dataset 76 | ||
| Table B1 | Signals Table | |
| Table C1 | Response code correlation matrix | |
| Unnamed Dataset 79 | ||
| Table F1 | A-Data.request service primitive | |
| Table F2 | A-Data.indication service primitive | |
| Table F3 | A-Data.confirmation service primitive | |
| Table F4 | A-Data.response service primitive |
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.