sae pev communication task force status -...

PEV/EVSE Communication SAE Task Force Status

IWC Meeting

3/28/2012Rich Scholer - SAE Communication Task

Force Status1

Outline

• Background

• PLC Status

• Additional Document Status


Force Status2

BackgroundMajor Documents and Functions


Force Status3

1. J2836™ - Use Cases (establishes requirements)

ISO/IEC 15118-1

2. J2847 – Messages, diagrams, etc. (derived from

the use case requirements)

ISO/IEC 15118-2

3. J2931 – Communication Requirements

ISO/IEC 15118-3

4. J2953 – Interoperability

ISO/IEC 15118-4


Force Status4

Summation of SAE Communication StandardsJ2836™ – General info (use cases)

Dash 1 – Utility programs *

Dash 2 – Off-board charger communications*

Dash 3 – Reverse Energy Flow

Dash 4 – Diagnostics

Dash 5 – Customer to PEV and HAN/NAN

Dash 6 – Wireless charging/discharging

J2953– Interoperability

Dash 1 – General Requirements

Dash 2 – Testing and Cert

Dash 3 –

• * Published

J2847– Detailed info (messages)

Dash 1 – Utility programs *

Dash 2 – Off-board charger communications *

Dash 3 – Reverse Energy Flow

Dash 4 – Diagnostics

Dash 5 – Customer to PEV and HAN/NAN

Dash 6 – Wireless charging/discharging

J2931– Protocol (Requirements)

Dash 1 – General Requirements*

Dash 2 – InBand Signaling (control Pilot)

Dash 3 – NB OFDM PLC over pilot or mains

Dash 4 – BB OFDM PLC over pilot or mains

Dash 5 – Telematics

Dash 6 – DSRC/RFID (wireless charging)

Dash 7 - Security


Force Status5

J2931/7 Security

J2953/1 Interoperability, J2953/2 Test Procedures

Document Interaction

Utility Programs

DC Charging

Reverse Power

Flow

Diagnostics

Customer to

PEV and

HAN/NAN

Wireless Power

Flow

Use Cases Requirements Protocol

BB OFDM (PLC)

Telematics

DSRC

(& RFID)

Basis

J2836/1™ J2847/1

J2931/1J2836/2™ J2847/2

J2836/3™ J2847/3

J2836/4™ J2847/4

J2931/4

J2836/5™ J2847/5 J2931/5

J2836/6™ J2847/6 J2931/6

PLC Development steps

1. Establish Requirements (publish J2931/1)2. PLC System Diagram (make a picture)3. Generate Test Plan and Lab Setup (EPRI & ANL)4. Review Test Report results (SAE Meeting)5. Establish Timeline


Force Status6


Force Status7

System Architecture (Utility Messages)

EVSE

Com modulePEV

Com modulePLC

ESI

PLC

EUMD

CANZigBee

SEP 1.x to SEP 2.0 Migration Unit

(if needed) ESI Dependent

SEP 2.0 SEP 1.x or 2.0

J1772™

Control

Pilot

SEP 1.x to

SEP 2.0

ZigBee

PLC ZigBee

• Fundamental case

– Highest expected usage


Force Status8

Actual Lab Set-up (ANL)

PLC Test Status• March 21-22, 2012 Task Force Meeting

– During this meeting, each of the requirements identified in J2931/1 were voted on for a Pass, Fail or Unknown/Untested position from both attendees and WebEx participants.

– We agreed to move forward with HP GP as the single PLC technology for DC Charging and Utility messages between the PEV and EVSE.

– A decision was also taken to discontinue any testing of other technologies (G3, FSK).

– We are continuing to coordinate effort with the ISO/IEC Project Team 4 testing


Force Status9

PLC Test Status (cont)Two requirements need additional testing.

• RelComm4 is the effect of consumer network on PEV network, and this showed conflicting results between EPRI and ANL. – We identified differences as updated firmware of PL16 modules, and

corset type.

– The action item was taken for ANL to retest with the EPRI boards, use the coupling cap variation along with a common cordset.

• DCComm.6, the shared network requirement, is the combined effect of both Utility and DC charging messages with the effects of the consumer network. – This solution requires Qualcomm to provide new firmware fixes so that

this requirement can be successfully met. It was decided that the testing will be carried out within two-three weeks at ANL and EPRI.


Force Status10

Timeline


Force Status11

Jan Feb Mar Apr May Jun Jul Aug

SAE PLC Test (EPRI, ANL, PNNL)

SAE Task Force Topic - DC Charging

J2847/2 (DC Charging)

J2931/1 (Stack info)

J2931/4 (PLC Protocol)

SAE Hybrid Committee Ballot - DC Charging

J2847/2 (DC Charging) J2847/2

J2931/1, 4 J2931

SAE Formatting

J2847/2 (DC Charging) J2847/2

J2931/1, 4 J2931

Publish J2931 doc(s) Techical Information Reports (TIR)

MVC Ballot - DC Charging (J2847/2 only) J2847/2

Publish J2847/2 Recommended Practice (RP)

2012

Additional Document Status


Force Status12

Document StatusUtility & DC Charging

• Reopened J2847/1 – Utility messages

– Dan Mepham is adding SEP2 info

• Reopened J2847/2 – DC Charging

– Doug Oliver is adding messages to harmonize with IEC

– Moving sequence diagrams into J1772™

• Reopened J2931/1 – Protocol Requirements

– Slav Berezin is adding Communication Stack sections


Force Status13

Document Status (cont)• J2836/3™ – PEV as Distributed Energy Resource

(DER) (formerly known as Reverse Power Flow)

– Hank McGlynn – developing use cases for PEV communicating as a DER device

– Grid connected operation as a DER (V2G)• PEV connects through EVSE to a live grid (which can be

islanded) – current source

• On-board or eternal inverter (J2847/2 to be updated to allow for reverse DC flow into external inverter)

• Inverter must fully comply with IEEE 1547 - exceptions to be deferred until next version (e.g. IEEE 1547.4 microgrids and IEEE 1547.8)


Force Status14

J2836/3™ (cont)

– Off-grid operation of PEV as a power (voltage) source (V2L, V2H, and V2V)

• On-board inverter sets and regulates voltage and frequency for loads

• Loads plug into a vehicle power panel with NEMA outlets (not via EVSE)

• For V2H the connection to the home must be through a UL1008 transfer switch

• High level communication not required for PEV as sole source of off-grid power (defer load sharing with other power sources until next version)


Force Status15

Document Status (cont)• J2847/3 will follow J2836/3™ effort and use the

J2847/1 SEP2-based approach• SEP2 provides basic DER functionality

• SEP2 will need to be updated for IEEE 1547.8 advanced DER modes

• J2836/4™ - Diagnostics - J2847/4 to follow

– Mike Muller is preparing for EVSE standard functions and diagnostics.

• J2836/5™ - Telematics – J2847/5 to follow

– Venkatesh Donthy is collecting HAN/NAN use cases for customer to HAN interactions

– Consumer and Utility Network expanded cases and synchronizations


Force Status16

Wireless Charging – Use Cases


Force Status17

• J2836/6™ - Wireless Charging - Mark Klerer – Coordinating the completion of use cases with the

requirements from J2954 (EVSE and alignment)

– Created second draft with input from J2954 members• Covers Use Cases

– Wireless EV Charger (WEVC) Discovery

– Vehicle Alignment

– Charging Control: Initiation, Power Transfer, Termination

– Monitoring and Diagnostics

• Emergency Shutdown

– Where possible reuse concepts and procedures from conductive charging applications


Force Status18

Wireless Charging Use Case Diagram


Force Status19

J2847/6 & J2931/6

• J2847/6 Messages for Wireless Charging– Draft to be created to meet requirements from Use

Cases in J2836/6: First Draft expected begining May

• J2931/6 Communications Protocol– DSRC to be used as protocol between Base Unit and

Vehicle Unit (EVSE) to be worked in cooperation with J2735 (First Draft end of April)

– RFID to be used to assist in vehicle alignment. Configuration to be defined by J2954. (Expected by end of May)

Interoperability and Security

• J2953/1– Cliff Fietzek restarted monthly meetings

• J2931/7– Hina Chaudhry is coordinating input from SGIP

CSWG and others• Incorporating NIST 7628 guidelines to map out different

domains and defining corresponding threats and risks

• Future focus will be on different security policies and controls recommendation to mitigate the threats thus identified


Force Status20

The End

Questions?


Force Status21