Page History

...

• Kevin: IMHO EV charging when the vehicle is connected to the charging station is totally in the scope of use cases and specifications defined by a consortium like the Open Charging Alliance. However there is a need to know the status of the EV battery charge when the vehicle is not connected
• Glenn: AKAIK the utilities request the status of EV battery charge for load balancing, I could bring an expert in the call to explain the EV/Power Utility communication use case for commercial vehicles as means possible inclusion by GENIVI in defining 'scope' for EV/Electrical Utility communication requirements - leading to the development of open specifications for broaded use of same.
• /TODO/ Geotab to provide an expert in this area to describe current use cases at Monday GENIVI call. (5:30 CET)
• Benjamin: in W3C VSS, there is a branch on battery capacity but it is empty up to now
  • https://github.com/GENIVI/vehicle_signal_specification/blob/master/spec/Drivetrain/BatteryManagement.vspec
• Gunnar: agreed, there is a need to complement VSS on this
• Gunnar: I agree that when the EV is connected to the charging station, this is not a use case for GENIVI, however when the vehicle is OTA, this is in scope of our CCS project
• Kevin: last week we at High Mobility open sourced all of our SDK with a unified set of APIs (based on data we got from BMW/Mercedes/... on the production projects), it might be good to look at data examples available at
  • charging data: https://github.com/highmobility/auto-api/blob/master/charging.yml
• Gunnar: IMHO we should rename this topic to EV management (i.e. something different than EV charging) since we do not overlap with the work on EV charging
• Guru: we need also to clarify how this topic fits with the EV battery management system
• EV charging docs (reminder) - useful links
  
  • OCCP: https://www.openchargealliance.org/downloads/
  • EV charging ecosystem overview: Electric_Vehicle_Charging_-_Definitions_and_Explanation_-_january_2019.pdf

...