Conference on Scalability and...
Transcript of Conference on Scalability and...
COTEVOS COncepts, capacities and methods for Testing EV systems and their interOperability within the Smartgrids
José Antonio López TECNALIA [email protected]
Bilbao, 22th October 2015 Tecnalia 1
IGREENGRID Conference on Scalability and Replicability
Why the need to test EV and EVSE grid integration
Current predictions state the amount of cars with an electric plug in will reach ~70-85% in 2030.
(This estimate includes HEV, PHEV and EV)
The given penetration of EVs (2015) is very
unlikely to cause car sourced grid errors but this can be expected to change as EVs roll out more and more.
Current evaluations show that grid failures will first occur locally on a low voltage grid level with relatively low penetration rates. Resulting in the in-ability of EVs to charge
ICE-Internal combustion engine, HEV – Hybrid Electric vehicle (optional plug), REEV – Range Extended electric vehicle, BEV – Battery electric vehicle, FCEV – Fuel cell electric vehicle Source: “Evolution, Electric Vehicles in Europe: gearing up for a new phase?” Amsterdam Roundtable Foundation and McKinsey & Company, April 2014
Tecnalia 2
COTEVOS towards the unified testing infrastructure
• The COTEVOS Reference Architecture aims to be a framework for the testing of: Interoperability is a product or system, whose interfaces are
completely understood, to work with other products or systems, present or future, without any restricted access or implementation
Conformance is how well something, such as a product or system, meets a specified standard
Tecnalia 3
COTEVOS towards the unified testing infrastructure
• Standards – IEC 61851 – ISO 15118 – IEC 62196 – …
• Protocols – OCPP – OCHP – OSCP – …
• Regulations – TOR (Technisch Organisatorische Richtlinie) – VDE AR-N 4105 – …
4
Source: The German Standardisation Roadmap
Tecnalia
aims to develop infrastructure to test
Conformance Interoperability
COTEVOS towards the unified testing infrastructure
Is standardization alone the solution? • Is simple testing against standards sufficient?
• Is it enough to build test infrastructure for the existing standards?
5
Interoperability contains a future view
Tecnalia
COTEVOS towards the unified testing infrastructure
• A very first step prior to defining a reference architecture is to look around what is already there
6
Tecnalia
The COTEVOS Reference Architecture – Describes all the actors and their interfaces of the current e-
mobility system
– Provides a context for use- and test-case definition
– Strong alignment with existing initiatives
– Layered approach enables a future evolution of the architecture as the e-mobility system develops
Tecnalia 7
COTEVOS towards the unified testing infrastructure
• COTEVOS Interface Reference Architecture – 3 “Layer” Topology (some topological similarity to the SGAM)
• Layer 1 - Actor/Interface Layer
• Layer 2 - Service/Function Layer
• Layer 3 - Physical/Test Stand Layer
Tecnalia 8
COTEVOS towards the unified testing infrastructure
COTEVOS – Reference Architecture Actor / Interface Layer
Tecnalia 9
• The Actor / Interface Layer of the COTEVOS RA includes:
– Actor definition • first definition in alignment with M/490
– Interface definition
• Based on standard and nonstandard interfaces
– All functionalities are covered, regardless of the actor which implements them.
COTEVOS – Reference Architecture Actor / Interface Layer
Tecnalia 10
EVSE Operator
EV
Energy Supplier
Flexibility Operator
Metering Operator
DSO EV User
EMSP Clearing house
EVSE
COTEVOS – Reference Architecture Service / Function Layer
OEM Service Actor
LEGEND
Grid Management Service
EVSE Operational Management Service
EV Battery Service
Energy Retailer Service
Charge Allocation Service
EV Flexibility Aggregation Service
Procurement Service
EVSE Management Service
Commercial Aggregation Service
Metering Service
EV Diagnostics & Maintenance
Charge Management Service
Clearinghouse Service
Contract & Billing Service
Identification Service
Charge Execution Service
User Preference Service
Authentication & Authorisation Service
Other Services (e.g. Navigation)
11
Tecnalia
• The Service / Function Layer of the COTEVOS RA includes: – Based on the idea that functions and actors are not always directly
coupled. Use-case depended coupling
– Allows a separation of concerns within the eMobility system
– resembles of the functional layer of SGAM
COTEVOS – Reference Architecture Service / Function Layer
12
COTEVOS Physical / Test Layer
• Different Implementations of the Reference Architecture
13 Connectedto grid
EVSEas DUT
TNO’s EV-IOP-Lab-In-A-Suitcase
EV simulator
Tecnalia
COTEVOS Reference Architecture
Emulated
EV user
EVSP OEM
Energy retailer
CH DSO
EVSEO
Real World
EVSE Grid EV
EMS
Charger / Inverter
Electrical/Physical
Router
EVuser sim
EVSP Sim.
OEM sim
Energy retailer
sim
CH sim
DSO sim.
EVSEO sim.
Message bus
GUI
Logging
Visualis-ation
Scenario Editor
…
… ...
Tecnalia 14
15
From Use Cases to Test Cases
• Round robin tests will be used for inter-laboratory comparison: first basic tests have been already performed
• Define test suites (like the WGI BAIOP) that cover a use case
• The test suite will consist of different test cases (steps) that need to conform to a specific standard e.g. – EV requests a charging schedule to EVSE (e.g. conform IEC15118) – EVSE operator sends the proposed charge profile to EVSE (e.g.
conform IEC15118)
16
28 test cases have been identified and they have been sorted into 6+1 groups
Test Cases aggrupation
+7 for wireless charging
17
Test Case examples
Part II Tecnalia’s implementation
Tecnalia 18
Tecnalia’s testing capabilities
Capabilities covered by Tecnalia
Emulated
EV user
EVSP OEM
Energy retailer
CH DSO
EVSEO
Real World
EVSE Grid EV
EMS
Charger / Inverter
Electrical/Physical
Router
EVuser sim
EVSP Sim.
OEM sim
Energy retailer
sim
CH sim
DSO sim.
EVSEO sim.
Message bus
GUI
Logging
Visualis-ation
Scenario Editor
…
… ...
Tecnalia Tecnalia
19
EV-EVSE testing platform illustration
Tecnalia 20
Testing EVSE charge
Grid
EMS
Electrical/Physical
Router
EVSEO sim.
Message bus
ISO 15118
Simulated
- OCPP
OCPP
- ISO 15118 authorization messages*
EVSP Sim.
CH sim
OCHP OCHP OCHP
EV 61851
Charger / Inverter
EVSE DUT
IEC 61851 Tecnalia
Lab2 Lab3
Tecnalia
1/3
* Comm. not defined in the standard (simulated process using CAs)
21
EV - Hardware
Tecnalia
Industrial PC ARK-2120L
2 x Classic FF 12 080 1
INSYS PowerLine GP
Switch EKI 2525
© Tecnalia + Arduino
DSIEC2f-EV32S-NC
Charger/Inverter XW4024-230-50
Link Pro Xanbus gateway
PP
CP
2/3
22
EV - Software
Tecnalia
• IEC 61851 • Charger/inverter (and related tools) software developed • State machine developed • © Tecnalia board + Arduino software. Interface finished • System integration + testing platform
• ISO/IEC 15118 • Implemented:
• SDP, TCP • ISO 15118 A1 and A2 Use cases • State machine triggers and events • EXI – XML and bindings with programming language • X509 certificates • DHCP support • System integration + testing platform
• Pending: • TLS
• Workarounds: • SLAC (part 3) not implemented. NMK must be manually assigned
3/3
23
Testing EV charge
Grid
EMS
Electrical/Physical
Router
EVSEO sim.
Message bus
ISO 15118
Simulated
- OCPP
OCPP
- ISO 15118 authorization messages*
EVSP Sim.
CH sim
OCHP OCHP OCHP
IEC 61851
EV 15118 DUT
EV 61851 DUT
EVSE
* Comm. not defined in the standard (simulated process using CAs)
Real World
CA
Lab2 Lab3
Tecnalia
1/3
Tecnalia
24
EVSE - Hardware 2/3
Tecnalia
Switch EKI 2528
DSIEC-M-EV32S
Industrial PC Xtrem n7000
© Tecnalia + Arduino INSYS PowerLine GP
(with SLAC)
Circutor CVM Mini
Schneider LC1D
PP
CP (with HLC) CP (pure)
To power grid To Tecnalia Internet Router
25
EVSE - Software
Tecnalia
• IEC 61851 • State machine developed • © Tecnalia board + Arduino software. Interface finished • System integration + testing platform
• ISO/IEC 15118 • Implemented:
• SDP, TCP • State machine triggers and events • EXI – XML and bindings with programming language • X509 certificates • DHCP server • ISO 15118 A1 and A2 Use cases • System integration + testing platform • Access to Internet (through the Tecnalia’s router)
• Pending: • TLS • Some messages (part 2) of the state machine
• OCPP integration. Some interesting operations
3/3
26
OCPP compliancy
Tecnalia
• Use of SoapUI internal API to perform predefined OCPP (v1.2, v1.5 and v2.0) tests
• Conformance testing for • For the EVSE Operator (Central System in OCPP) • For the EVSE
• Not defined the extent of the application • Proposed tests:
• SOAP messages testing (changing SOAP versions 1.2, 2.0) • Namespace changes • Headers • Communication tampering and stress testing • Test sequences
• Graphical interface
27
A real test case
Tecnalia
Watch testing video
Discussion
Bilbao, 22th October 2015