Building an EV Charging Reference Implementation with EVerest.pptx

The U.S. Joint Office of Energy and Transportation (Joint Office) will use LF Energy’s EVerest project to build an open source reference implementation for electric vehicle (EV) charging infrastructure. EVerest is an open source project with the goal of developing and maintaining an open source software stack for EV charging stations. It is a modular framework for EV charging, consisting of multiple modules which can be configured and customized for any necessary use case. EVerest manages communications around energy between the car, local energy generation, batteries, adjacent chargers, power grids, cloud backend and payment systems, and the user, including on a mobile phone. EVerest was originated by PIONIX GmbH and contributed to LF Energy in early 2022.

This webinar discusses how the collaborative development model offered by open source and the neutral governance structure provided by LF Energy will speed the adoption of EVs and decarbonization of transportation in the United States compared to relying on proprietary technologies by:
-Enabling development and deployment to happen at an accelerated rate
-Increasing customizability for different use cases
-Offering long-term maintainability
-Avoiding vendor-lock in while enabling a commercial support ecosystem
-Ensuring high levels of security

1. Building an EV Charging Reference Implementation with EVerest K. Shankari - Joint Office of Energy & Transportation Alex Thornton - LF Energy Marco Möller - PIONIX

2. LF Energy

3. What is open source? A n approach to building technology that can be viewed, changed, and shared according to a permissive licence

4. Open source powers nearly all modern technology ~80% open source for undifferentiated foundation ~20% for strategic added value

5. Open source powers nearly all modern technology Cars Phones S upercomputers Stock exchanges Nuclear submarines Telecom networks Mars helicopter Starlink Much much more ~80% open source for undifferentiated foundation ~20% for strategic added value

6. ~80% open source Automotive Grade Linux ~20% Subaru’s custom code

7. Open source is a competitive advantage The most competitive, innovative companies in the world collaborate on open source to realize strategic advantages

8. Open source is secure Open source is more secure than closed, proprietary solutions due to transparency and speed to patch vulnerabilities

9. Benefits of open source for EV infrastructure Speed of innovation Security Long-term maintainability Interoperability Customizability

10. LF Energy accelerates the energy transition by building communities to develop open technologies and standards.

11. Building large, thriving, sustainable communities Neutrality A neutral host foundation for intellectual property (IP) Governance Governance and community help Resources Events, community, marketing, training, CI/build infrastructure Growth Build momentum within the LF community thousands of global members Funds Ability to raise and manage funds (optional) Experience Colleagues who share deep open source experience

12. Building large, thriving, sustainable communities Certification Over 90,000 open source technologists and leaders from around the globe gather at Linux Foundation events annually to share ideas, learn and collaborate Legal Training Events Developer Marketing Application Security We manage IP for the world's most important tech and have some of the world's top source legal team in house We have trained millions of students through free and paid online training, online skills certification, and on site e-learning We have designed and implemented both software and hardware testing and certification programs We have the largest share of voice of any open source foundation and a proven method to build large scale developer programs In addition to massive peer review, our projects our regularly audited and pen tested. We offer bug bounties, dependency analysis, and code scanning. Developer Operations We host the infrastructure that develops the world's largest software communities and provide release mgmts., IT ops and support

13. LF Energy 30+ projects covering generation to grid edge 75+ members, including utilities, Big Tech, technology vendors, and more

14. Summary Open source is a way of accelerating innovation by collaborating on foundational technology The most secure, competitive, and innovative organizations in the world use open source to their strategic advantage LF Energy builds open source communities to accelerate the energy transition

15. The Joint Office of Energy & Transportation

16. U.S. National Blueprint for Transportation Decarbonization https://www.energy.gov/eere/us-national-blueprint-transportation-decarbonization-joint-strategy-transform-transportation

17. The Biden Administration is prioritizing building a network of 500,000 chargers by 2030 Since President Biden took office, the number of publicly available charging ports has grown by 75%. Currently the US has more than 168,000 public charging ports 1 in every 10 vehicles sold is an EV driveelectric.gov

18. driveelectric.gov Infrastructure Investment & Jobs Act (IIJA) Programs Supported by the Joint Office The Joint Office provides unifying guidance , technical assistance , and analysis to support the following programs: National Electric Vehicle Infrastructure (NEVI) Formula Program (U.S. DOT)  $5 billion for states to build a national electric vehicle (EV) charging network along corridors, including $148 million awarded to repair and replace non-operational chargers. Charging & Fueling Infrastructure Discretionary Grant Program (U.S. DOT)  $2.5 billion in community and corridor grants for EV charging, as well as hydrogen, natural gas, and propane fueling infrastructure Low-No Emissions Grants Program for Transit (U.S. DOT) $5.6 billion in support of low- and no-emission transit bus deployments Clean School Bus Program (U.S. EPA) $5 billion in support of electric school bus deployments

19. The Joint Office and EVerest

20. Charging experience is a barrier to electrification Reliability of Open Public Electric Vehicle Direct Current Fast Chargers – David Remel, Carleen Cullen, Mary Bryan, Gustavo Cezar, https://ssrn.com/abstract=4077554 or http://dx.doi.org/10.2139/ssrn.4077554 NYTimes: A Frustrating Hassle Holding Electric Cars Back: Broken Chargers Owners of battery-powered cars sometimes struggle to refuel on longer trips because public chargers don’t work or malfunction while cars are plugged in. https://www.nytimes.com/2022/08/16/business/energy-environment/electric-vehicles-broken-chargers.html

21. Feb 28, 2024: New NEVI standards take effect driveelectric.gov Charger ISO 15118-2, including plug and charge https://www.ecfr.gov/current/title-23/chapter-I/subchapter-G/part-680 OCPP 2.0.1 OCPI 2.2.1 Improved cyber security encrypted connections, certificate management and public keys (PKI) Smart Charging support charging profiles grid schedule, time of use tariff Display messages, enhanced authentication, …

22. Software challenges: interoperability and reliability Current State Picture The current state of electric vehicle charging is unreliable with fragmented customer experiences. Future State Vision With robust software implementations charging stations can provide a seamless plug and play experience today and accelerate future technologies. Joint Office Unique Position The Joint Office can provide market signals and technological support in accordance with the Minimum Standards (CFR 680). EV Ecosystem Review Networking Different Implementations of the Same Standard Asynchronous Software Updates Handshake Failures Software Related Pain Points Errors caused by non-deterministic interactions are not tested in point-in-time testivals Non-happy paths Charging ecosystem components have slightly different implementations Disjointed Standards Proprietary implementations often lack end-to-end debugging capabilities Troubleshooting Consistent Trouble- Shooting

23. Reference implementation: fix both challenges EV container EVSE container CSMS container CSMS_OCPP_ref EVSE_OCPP_ref EVSE_ISO_ref EV_ISO_ref Automated, simulated failures (chaos) Reliability Interoperability Different Implementations of the Same Standard Asynchronous Software Updates Networking Handshake Failures Linus’ law “Given enough eyeballs, all bugs are shallow” Eric Raymond, The Cathedral and the Bazaar

24. EVerest community Why EVerest? Federal policy Shared governance Long-term maintenance M-16-21 Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software Aug 8, 2016 https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf “ LF Energy builds open source communities to accelerate the energy transition” “Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer.” Acceptance Criteria for moving to the Graduated Stage in LFE https://wiki.lfenergy.org/display/HOME/Technical+Project+Lifecycle#TechnicalProjectLifecycle - OEMs - Station manufacturers - Charging networks - Academia - Public agencies - Testing - Implementation - Integration - Prototyping - Analysis

25. Due diligence: Dockerized, one-line demos curl https://raw.githubusercontent.com/everest/everest-demo/main/demo-iso15118-2-dc.sh | bash More demos, including CSMS integration using OCPP, at: https://github.com/everest/everest-demo

26. Governance ; code contributions; seeding community Looking for US early adopters 🇺🇸 We will help you with integration and create a blueprint for those who follow

27. Accelerate Electrification through New Requirements and Technical Assistance driveelectric.gov NEVI, CFI Funding ⇾ requirements February 28th, 2024 ISO 15118-2 OCPP 2.0.1 OCPI 2.2.1 Improved user experience Technical support New features, Better testing, Improved documentation Early adopters, Community creation

28. History of EVerest creation and technical architecture

29. sources: https://www.businessinsider.com/electric-car-charging-reliability-broken-stations-ev-2022-5 https://www.electrive.net/2022/11/04/jede-zehnte-ladesaeule-ist-ausser-betrieb/ https://www.heise.de/news/Zuverlaessigkeit-von-Ladesaeulen-fuer-Elektroautos-Deutschland-nur-im-Mittelfeld-7327854.html Make every EV charger work with every EV variant and all connected apps and cloud software. THE PROBLEM T oday, 10-25% of charging sessions fail!

30. 2.5 billion+ vehicle s Cars, trucks, buses, motorcycles, boats Multiple brands, models , and configurations Different operating systems and firmwares sources: https://www.businessinsider.com/electric-car-charging-reliability-broken-stations-ev-2022-5 https://www.electrive.net/2022/11/04/jede-zehnte-ladesaeule-ist-ausser-betrieb/ https://www.heise.de/news/Zuverlaessigkeit-von-Ladesaeulen-fuer-Elektroautos-Deutschland-nur-im-Mittelfeld-7327854.html 3 billion+ EV chargers AC/DC, Home / Workplace / Fleet, Slow/Fast, V2G, PnC Multiple brands, models, versions Different firmwares, Cloud apps, mobile apps With the growth of the market this problem is getting extremely hard and charger manufactures can’t keep up … and the complexity is growing quickly estimation for an electric future

31. DC SAE J2847/2 DIN70121 GB/T DC 2025 OCPP 1.6 OCPP 2.0.1 OCPP 2.1 OCPP 1.6 Security wp. OCPP 2.0 AC IEC 61851-1:2011/ GB/T AC ISO15118-2 / -3 2010 2015 2020 IEC 61851-1:2017 more… CHAdeMO 1.0 ChaoJi / CHAdeMO 3.0 CHAdeMO 2.0 CHAdeMO 1.1 ChaoJi HPC CHAdeMO 3.1 -20 MCS V2G ISO15118-20 Plug ‘n Charge IEE2030.5 (SEP 2.0) Grid SAE J2847/3 Sunspec OpenADR 3.0 OpenADR 2.0a OpenADR 2.0b IEC 62746-10-1 SAEJ3072 Tesla SWCAN ChargeX MREC (minimum required error codes) … to be continued… J1772:2009 V2H OCPP 1.6 Plug&Charge Other Matter EEBus ZVT German Eichrecht / Metering Calibration Cloud ISO15118-8 WiFi The universe is expanding...

32. ‹#› https://xkcd.com/927/ A new standard is not a solution A shared codebase (de-facto-std) is!

33. All starts with correct IP Strategy Licence Option: Commercial Licence: No community GPL only: No proprietary IP / USPs protection Dual license: GPL + commercial No proprietary IP / USPs protection No community MIT / BSD (entirely, or only for core components): Community No limitation to commercial usage 3rd party contributors threaten by patent trolls Apache 2.0 Community could contribute No limitation to commercial usage Protection against patent trolls Collaboration across industry currently happens by standardization committees ⇒ slow & buggy Collaboration on code would also provide standardization ⇒ fast our Licence :

34. And so it began… 2024 2021 f ounded 02/2021 2022 announces EVerest as its latest project + EVerest Source code published 12.01.2022 2016-201 9 First idea of improving EV charging ecosystem Q3/2020 PIONIX founders Exit MAVinci to Intel TODAY joins EVerest TSC US JOET and Qwello join EVerest TSC PIONIX founde rs 2020 EVerest achieves “ early adoption ” stage within LF Energy 1st “EVerest summit” conference launch AM62-EVSE-DEV w/ EVerest support Beagleboard & Seeedstudio launch reCharger SECC based on EVerest Chargebyte integrates EVerest into charge controllers Open Source Conference @ OCA PlugFest EVerest Summit North America PIONIX board member OCA 2023

35. DC SAE J2847/2 DIN70121 GB/T DC 2025 OCPP 1.6 OCPP 2.0.1 OCPP 2.1 OCPP 1.6 Security wp. OCPP 2.0 AC IEC 61851-1:2011/ GB/T AC ISO15118-2 / -3 2010 2015 2020 IEC 61851-1:2017 more… CHAdeMO 1.0 ChaoJi / CHAdeMO 3.0 CHAdeMO 2.0 CHAdeMO 1.1 ChaoJi HPC CHAdeMO 3.1 -20 MCS V2G ISO15118-20 Plug ‘n Charge IEE2030.5 (SEP 2.0) Grid SAE J2847/3 Sunspec OpenADR 3.0 OpenADR 2.0a OpenADR 2.0b IEC 62746-10-1 SAEJ3072 Tesla SWCAN ChargeX MREC (minimum required error codes) … to be continued… J1772:2009 V2H OCPP 1.6 Plug&Charge Other Matter EEBus ZVT German Eichrecht / Metering Calibration Cloud ISO15118-8 WiFi EVerest has got you covered von Standards

36. Microservice architecture Typical architecture found in many commercial solutions for EV charger software Each module is a separate Linux process Use publish/subscribe pattern (e.g. MQTT) for communication between modules Module A Interface 1: Charger Commands: set_max_current(float ampere); Variables: float energy_charged; Module B call commands (with return value) async event: energy_charged = 5.23kWh MQTT, D-Bus, …

37. Module APIs / MQTT topics Excel : Hard coded topic paths on MQTT, human readable documentation Excel sheet MQTT topics MQTT does not standardize on data formats Are dependencies met? What if a module requires multiple instances of another module? What if topic path changes? → hard to maintain and configure Schemata : Machine readable definition of module interfaces, dependencies and data types Automatic dependency checking (with versioning) Auto generate human readable documentation Native C ++17 support, JS, P ython, Rust to abstract communication Auto complete for C++, compile time type safety Typical implementation EVerest Framework VS.

38. Build a simple AC Wallbox with ISO 15118 and OCPP https://youtu.be/iUKniRe4PKA

39. Build a simple AC Wallbox Step 1 of 7 One charging connector Charging logic and session Orchestrates all other modules access to this one connector EvseManager

40. Build a simple AC Wallbox Step 2 of 7 Hardware driver: CP, Relais, RCD Board support

41. Build a simple AC Wallbox Step 3 of 7 Minimal configuration, more advanced possible Energy manager

42. Build a simple AC Wallbox Step 4 of 7 Pure C++ ISO15118-2/DIN70121 done ISO15118-20 in beta EXI + SLAC Real World Compatible: Cross tested like crazy to as many cars as possible and implemented car bug workarounds Add ISO15118-2 PN532TokenProvider

43. Build a simple AC Wallbox Step 5 of 7 Token providers (output tokens) and token validators (can check if token is valid) RFID (new module) Plug&Charge Autocharge (EvseManager also has a token provider interface for EVCCID) Auth manager needs EvseV2G

44. Build a simple AC Wallbox Step 6 of 7 OCPP 1.6/ 2.0.1 module Powermeter (may also support German Eichrecht) System module supports e.g. reboot/firmware update etc via OCPP Add Cloud backend EvseV2G

45. Build a simple AC Wallbox Step 7 of 7 (display app, mobile phone app) Add API for ext. applications EvseV2G

46. Build a simple AC Wallbox Completed! Now EVerest is ready to run for your ISO15118 / OCPP ready AC wallbox! EvseV2G

47. Advanced config DC Charging The two ports share: EnergyManager (load balancing) OCPP (shown as two connectors in backend) API (App will see two ports) Adding a second DC port to the charging station EvseV2G EvseV2G

48. Software in the loop simulation (SIL) Running EVerest without HW or a car Run complete EVerest on your laptop - load simulated EVSE hardware as well as car simulation Simulates Control Pilot signal and ISO15118 between simulated car and evse Test complex scenario with multiple chargers etc. Use Node Red for quick UIs for development purposes EvseV2G

49. ↪ l ibOCPP, libevse-security ↪ l ibSlac, l ibfsm https://github.com/EVerest 32 public modules 34 Repositories 720k lines of Code easily extendable EVerest is a module system AND a huge set of supporting libraries ↪ libiso15118, ext-openv2g, ext-switchev-iso15118 ↪ tinyModbusRTU EvseV2G

50. Ecosystem emerging (more under NDA ;-) + many under NDA and from the community EVerest compatibility & projects e.g. ~30 clouds cross-tested E-Mobility Service Providers & Utilities One Stack to Charge them all! Charging Station OEMs Component Suppliers RWTH 🎓 Fraunhofer ISE 🎓 THU 🎓 Maker , Hacker & Enthusiasts Marmara University 🎓 KASTEL / KIT 🎓 Project “Beans” Project “Fish” Project “Asparagus” Standardization bodies EVerest TSC >>20 industrial projects Academia & Research

51. Community interaction is exploding 2023: massive growth >424 leads engaged with EVerest >44 contributor organizations in EVerest Community discussions growing 10x y/y Contributions growing 7x y/y GitHub activity 4.5x y/y EVerest within the LF Energy project peers 2024: Breakdown in Working Groups to enable further growth Car Communication Cloud Communication EVerest Framework & Tools CI/CD and Testing General and Q&A https://insights.lfx.linuxfoundation.org/foundation/lfenergy/overview?project=everest&repository=

52. Beautiful modular microservice architecture & middleware Many protocols included: OCPP 1.6 (all) / 2.0.1 / 2.1 ( basics ) ISO 15118-2(AC+DC) (ISO 15118-20 beta ) DC-BiDi: SAE J2847/2 DIN SPEC 70121 IEC 61851 / SAE J1772 ModBus Sunspec MQTT CCS1, CCS2, NACS/Tesla Many language bindings: C++ 17, Rust, Python, JavaScript Seamless buildings blocks for all use cases Software (& Hardware) in the Loop Simulations - develop on single laptop NodeRed integration for rapid prototyping Opt. local energy management Opt. user interface available (Flutter based) Well tested: Automated & manual tests, testivals, codescanning Tech Overview & Example Configurations Simple AC or DC Charger SW-in-the-loop testing Site Energy Mgmt AC+DC Hybrid Charger Deeply integrated HW reference designs available: CPU s supported & tested so far: Raspberry Pi CM4 AM6X Sitara NXP i.MX6 / i.MX8 … most LINUX capable systems OS supported & tested so far: Yocto: (thud) dunfell hardknott kirkstone Debian / Ubuntu OpenSuse Arch Fedora Other Linux distributions Always up-to-date : Online updates / OTA, secure boot , multiple redundant partitions Visual Configuration Editor Example configurations: Distributed charging park CP 1 pay term CP 2

53. The Joint Office and LF Energy - How you can get involved

54. How you can get involved EVerest documentation for details on mailing lists, group chats and working group meetings - everest.github.io LF Energy website ( lfenergy.org ) to get involved ( lfenergy.org/about/get-involved/ ) in the broader community Apply to be a JO supported early adopter, Email: [email protected] or [email protected] Stay tuned for upcoming webinars about other open EV projects

55. Q&A