NREL is a national laboratory of the U.S. Department of Energy, Office of Energy Efficiency and Renewable Energy, operated by the Alliance for Sustainable Energy, LLC.

Demonstrating PLC over J1772

During PEV Charging for

Application at Military Microgrids

Mike Simpson Mike.Simpson@NREL.gov Team Members:

Myungsoo Jun

Mike Kuss

Tony Markel (lead) 28 June 2012

This presentation does not contain any proprietary, confidential, or otherwise restricted information.

2

Agenda

• NREL Electric Vehicle Grid Integration

(EVGI) Background

• SPIDERS and Military Microgrids

• Proposed Messaging for bi-directional

vehicle charging (V2x)

• Power Line Communications (PLC)

Hardware Implementation

• Lessons Learned

• Next Steps

3

What is Electric Vehicle Grid Integration (EVGI)?

4

SPIDERS: JCTD • Smart Power Infrastructure Demonstration for

Energy Reliability and Security (SPIDERS)

– Joint Command Technology Demonstration (JCTD)

• NORTHCOM + PACOM

– Demonstrate:

• Cyber-security of electric grid

• Smart Grid technologies & applications

• Islanded micro-grid

• Demand-side management

• Redundant back-up power systems

• Integration of distributed/intermittent renewables

• Fort Carson: “Triple Net Zero” Installation

– Currently have 2-MW Solar array on-base

• Demo-ing several other RE tech on-site

– Project goal is to demonstrate:

• Large-scale renewables

• Smart micro-grid

• Vehicle-to-Grid (V2G) with Plug-in Electric Vehicles (PEVs)

Smith Newton Electric Truck; NREL PIX 17631

5

SPIDERS PEV Charge Interface

Representative Block Diagram, TARDEC Dia

gra

m c

ou

rte

sy D

ea

n M

cG

rew

, TA

RD

EC

6

SAE J2847/3 Message Initialization Procedure

Black text is in original 2847/1 and 2847/2

Red text is proposed for 2847/3

Pilot=

State B

Pilot= State C or D

AND

Vehicle Ready = TRUE

Fault

Initialization

· EVSE/PEV exchange

operating limits

· PEV locks connector

· EVSE performs Internal

Isolation Monitoring

Energy Transfer

· PEV continuously monitors HV

isolation

· PEV controls current level request

· EVSE transfers energy per PEV

Request

Disconnected

Shutdown/1

· PEV requests zero current

· PEV waits for safe voltage level

Not Ready

· EVSE prompts user to

disconnect

· EVSE disables current

flow

· PEV ensures that

connector is unlocked

Connector =

Unlocked

Pilot = State B

Charge Complete = 1

Fault

Pilot=

State A

(disconnected)

Precharge

· EVSE enables HV DC output

· PEV requests voltage and small

current

· EVSE controls to PEV request

· PEV waits for voltage to match ESS

· EVSE sends Grid Control request if

V2G capable

· PEV acknowledges Grid Control

request (or denies/ignores)

Voltages matched AND

Grid Control = 0

(PEV closes contactor)

Fault

Fault

Isolation Monitoring

· EVSE may continue to check

isolation on its side of the PEV

contactor

· PEV monitors isolation on its

side of the contactor

Connector = Locked AND

Charger Status = Isolation Monitoring Active

Vehicle Ready = TRUE

AND

Connector = Locked

(to restart charging)

Fault

Fault

Shutdown/2

· PEV performs welded checks

· PEV opens contactor

· PEV unlocks connector

Contactor =

Opened

Fault

PreV2G

· PEV sends kWh Avail, Min/Max I, kWh

requested & departure time, VehID

· EVSE sends EVSE ID, returns EV data

(handshake)

· IF handshake success = 1, PEV Status =

“V2G” ELSE PEV Status = “Energy xfer”

Voltages Matched AND

Grid Control = 1

Voltages matched AND

PEV Status = “Energy xfer”

V2G

· EVSE continuously monitors HV isolation

· PEV isolation monitor not active

· EVSE controls current level request –

EVSE transfers current within PEV-

defined limits (EVSE will disconnect from

aggregator in the event of low SOC and

imminent departure by setting Grid

Control = 0)

Voltages matched AND

PEV Status = “V2G”

Digital comm timeout

> 10T OR

V/I outside PEV-defined limits

Fault OR

Pilot=State B

Charge Complete = 1

· UI prompts driver before exiting, e.g. “Leaving

around 4:30pm today?”

àIf no explicit confirmation, Grid Control = 1

EVSE-Aggregator

· Aggregator pings EVSEs for the

following data: Min/Max Power, Energy

available, Energy request

· Aggregator sends kW command to

each EVSE (based on utility command

and proprietary scheduling algorithms)

7

Suggested Messages (adapted from J2847/2)

Variable Description [suggested XML variable name if applicable] Units From—To Standard

Ecap PEV Energy Storage System (ESS) capacity [EVEnergyCapacity] kWh PEV-EVSE J2847/2

SOC ESS State-of-Charge (SOC) [EVRESSSOC] PEV-EVSE J2847/2

Emin Minimum allowable depth-of-discharge [kWhAvailable] kWh Calculated by EVSE J2847/2

x PEV kWh request [EVEnergyRequest] kWh PEV-EVSE-Agg J2847/2

X Aggregated PEV Energy available for charging (regulation down) MWh Agg-Utility Rules vary; e.g., CAISO; CEC Rule 21

α PEV energy available (for V2G) [kWhAvailable] kWh PEV-EVSE-Agg J2847/1

А Aggregated PEV energy available for discharging (regulation up) MWh by Agg-Utility Rules vary; e.g., CAISO; CEC Rule 21

Pmin_nom PEV-EVSE-defined max discharge rate kW PEV-EVSE 2847/2

Pmin EVSE-calculated min power rate based on energy trajectory kW EVSE-Agg 2847/1

Pmax; ū PEV-EVSE-defined max charge rate kW PEV-EVSE-Agg 2847/2

Pmin_agg Aggregated minimum power output capability MW Agg-Utility Rules vary; e.g., CAISO; CEC Rule 21

Pmax_agg Aggregated minimum power output capability MW Agg-Utility Rules vary; e.g., CAISO; CEC Rule 21

Pagg Power command from Grid Operator (GO) to Aggregator (Agg) MW Utility-Agg Rules vary; e.g., CAISO; CEC Rule 21

PFagg Power factor command from the GO to the aggregator Utility-Agg Rules vary; e.g., CAISO; CEC Rule 21

PEVSE Power command from the aggregator to each EVSE kW Agg-EVSE J2847/1

PFEVSE Power factor command from the aggregator to an EVSE Agg-EVSE J2847/1

t Time now J2847/2

TETD Estimated time of departure PEV-EVSE J2847/2

THTD Hours til departure hours calculated by EVSE J2847/2

EF Energy forecast (time-dependent array) kWh calculated by EVSE J2847/2

e Error between energy forecast and actual energy in ESS kWh calculated by EVSE J2847/1

n Vehicle index (aggregator) calculated by Agg J2847/1

N Number of PEVs connected to aggregator J2847/1

Black text is in original 2847/1 and 2847/2. Red text denotes new or proposed options. Blue text denotes calculated values that do not require

communication among entities. Messages slated to be integrated with Aeych LLC & others proposed changes (6/2012)

8

V2G Relevant Variables

• Minimize message count to avoid discrepancies between PEV and charge controller or aggregator

• Minimize required bandwidth

• Utilize existing J2847/2 messages

• Provide operational flexibility

Note: ACE = Area Control Error

9

Simultaneous PEV Charging and PLC Communications of PEV State via EVSE

Photo Credit: Mike Simpson, NREL

10

PEV CAN-bus

Serial

USB

Custom

J1772 control pilot

DB9 M

DB9 F

J1772 Connector

Deutch Connector

Bare Wire

Connection

On-board Power

Electronics

Cables

Connectors

EVSE

Pilot Line In

Display

Development

Board + CPU Display

PEV–PLC Test Setup

PLC

Module

Development

Board + CPU

PLC

Module

11

PC display PLC

communications

module wired to

J1772 pilot line

Connections

to Vehicle

CAN bus

J2847 Message Test Platform Vehicle

Development board

deployed to translate CAN

into J2847 messages Photo Credit: Mike Simpson, NREL

12

Communications

flowing through

vehicle, through

J1772 connection

PC display

PLC communications

module

receiving/translating

signals

Clipper Creek CS40

Level 2 EVSE (with

PLC flowing through

pilot line)

J2847 Message Test Platform Infrastructure

Development board

deployed to translate CAN

into and control EVSE Photo Credit: Mike Simpson, NREL

13

Planned Next Steps

• Test all messages

• Integrate DC bi-directional charging with stationary battery and J1772 Combo Connector

• Integrate DC bi-directional charging with Smith Newton electric vehicle

• Demonstrate grid services

– Frequency regulation

– Peak shaving

• Integrate development board functionality into HomePlug Green PHY hardware

Special thanks to: Our sponsor —

• Merrill Smith, Office of Electricity, U.S.

Department of Energy

Project collaborators —

• Dean McGrew, TARDEC

• Azure Dynamics

Questions?