WEBVTT 00:00.000 --> 00:07.000 Okay, thanks for being here. 00:07.000 --> 00:12.000 Today I want to talk about bi-directional charging. 00:12.000 --> 00:18.000 About the protocols, the challenges and the strategies we do in Evers. 00:18.000 --> 00:23.000 My name is Andreas. I'm working at Pionics on Evers. 00:24.000 --> 00:30.000 As I said, we will start what bi-directional charging is and why we should do it. 00:30.000 --> 00:34.000 Then some different charging and discharging strategies. 00:34.000 --> 00:38.000 And then we will have a look at the entire impact chain of it. 00:38.000 --> 00:43.000 And then I will give you some insights and Evers how we do energy management there. 00:43.000 --> 00:46.000 And then we will come to conclusion. 00:46.000 --> 00:51.000 So what is bi-directional charging? I guess you all know what charging is. 00:51.000 --> 00:53.000 And I guess you all know what this charging is. 00:53.000 --> 00:57.000 And if you put both together, you have bi-directional charging. 00:57.000 --> 01:01.000 So with this, why should we do it? 01:01.000 --> 01:04.000 That different reasons for it. 01:04.000 --> 01:06.000 At first, there was a climate change. 01:06.000 --> 01:14.000 This is why we have renewable energies with small producers and decentralized production. 01:14.000 --> 01:17.000 And this is why we need grip stabilization. 01:17.000 --> 01:21.000 For this, we can use electrical vehicles. 01:21.000 --> 01:28.000 And some personal motivations could be the price optimization during the charging. 01:28.000 --> 01:32.000 And you could also use your EVS emergency power supply. 01:32.000 --> 01:39.000 Or just use the EV as a big power bank, for example, at the camping ground. 01:39.000 --> 01:45.000 And then we will start with a very first charging strategy. 01:45.000 --> 01:52.000 For this, we need an electric vehicle with a certain minimal and maximal charging power. 01:52.000 --> 01:55.000 And a specific battery size. 01:55.000 --> 01:59.000 And the goal is to charge this EV as fast as possible. 01:59.000 --> 02:01.000 And strategy is okay. 02:01.000 --> 02:07.000 You just take as much as possible available power to charge the car. 02:07.000 --> 02:14.000 And in this scenario, we have an external restriction of charging power after 30 minutes. 02:14.000 --> 02:18.000 So you can see the result here. 02:18.000 --> 02:23.000 The green line, the charging power, which starts with 50 kilowatts. 02:23.000 --> 02:26.000 And then drops after 30 minutes to 20 kilowatts. 02:26.000 --> 02:29.000 Because of this external limit. 02:29.000 --> 02:34.000 And yeah, after 30 and half hours, the EV is full. 02:34.000 --> 02:37.000 And the charging session ends. 02:37.000 --> 02:41.000 So quite easy straight forward, strategy. 02:42.000 --> 02:50.000 The more complex one is the optimization of the PV produced energy consumption. 02:50.000 --> 02:54.000 And also with some other consumers in the local grid. 02:54.000 --> 03:01.000 For this, we need a photovoltaic system, which has certain peak power and daily energy yield. 03:01.000 --> 03:03.000 And the curve. 03:03.000 --> 03:10.000 So the most energy production will be around 12am. 03:10.000 --> 03:13.000 And again, we have a scenario. 03:13.000 --> 03:16.000 The arrival time is at 11 o'clock. 03:16.000 --> 03:23.000 We have a state of charge of 10 kilowatts and a max charging power of 20 kilowatts in this scenario. 03:23.000 --> 03:28.000 And goal is to use as much of the PV produced energy as possible. 03:28.000 --> 03:33.000 And strategy is that we calculate the left over at the grid connection points. 03:33.000 --> 03:37.000 So we have the PV production, subtract the other consumers. 03:37.000 --> 03:40.000 And with this left over power, we can charge. 03:40.000 --> 03:51.000 And if this left over power is negative, we can discharge this left over power to come to zero at the left over energy. 03:51.000 --> 03:57.000 So here, the result again in the upper left, you see the PV production in purple. 03:57.000 --> 04:00.000 And yellow, some random other consumers. 04:00.000 --> 04:03.000 And then bottom left, you see the left over energy. 04:03.000 --> 04:10.000 And you can see, until 11am, we have some import of energy in the beginning. 04:10.000 --> 04:12.000 And then some export of energy. 04:12.000 --> 04:15.000 And at 11am, it drops to zero. 04:15.000 --> 04:22.000 And this is because, which you can see in the upper right, the charging power starts at 11am. 04:22.000 --> 04:28.000 The PV arrives and starts to charge and brings this left over energy to zero. 04:28.000 --> 04:35.000 And at a certain time around 5pm, the EV starts even to discharge. 04:35.000 --> 04:40.000 Because the consumption is higher than the production. 04:40.000 --> 04:49.000 And we want to use the ones PV generated energy here. 04:49.000 --> 04:51.000 Yeah, there's also the energy market. 04:51.000 --> 04:57.000 And we could do some price optimization, but no time to explain a strategy here. 04:57.000 --> 05:00.000 But yeah, in general, we can support the grid. 05:00.000 --> 05:04.000 The grid can use the EV. 05:04.000 --> 05:11.000 And for this, we would give some restrictions, a minimal and maximal state of charge. 05:11.000 --> 05:20.000 And then the grid can design, decide when it is, when does it make sense to charge or discharge the EV. 05:20.000 --> 05:26.000 Now, I want to have a look at the entire impact chain of bidder to charging. 05:26.000 --> 05:29.000 I took this diagram from a research project. 05:29.000 --> 05:31.000 We are part of it. 05:31.000 --> 05:32.000 It's quite big. 05:32.000 --> 05:37.000 I made an easier version of for you, but it's important to have in mind. 05:37.000 --> 05:43.000 There are a lot of players in this system that are part of this. 05:43.000 --> 05:48.000 And first, we have a look at this section. 05:48.000 --> 05:53.000 So the communication between the EV and EV's E, which is standby. 05:53.000 --> 05:57.000 E is the O15, 118, E is O15, 118. 05:57.000 --> 06:01.000 And we already heard about it today. 06:01.000 --> 06:04.000 So it defines the procedure of charging session. 06:04.000 --> 06:12.000 And yeah, it provides then tooling for smart charging and also bidirectional charging. 06:12.000 --> 06:18.000 Here we have a quick overview about the features and the different versions of E is O15, 118. 06:18.000 --> 06:22.000 And you can see the dashed 20 version brings the features we need for bidirectional charging. 06:22.000 --> 06:27.000 So smart charging and pause and resume features. 06:27.000 --> 06:36.000 Yeah, then we have another area, the communication between the EV's E and the OCP back. 06:36.000 --> 06:41.000 And so for this, we use OCP to communicate. 06:41.000 --> 06:44.000 And there, again, we have different versions. 06:44.000 --> 06:51.000 And the new one, the 2.1, brings features for smart charging and the support for bidirectional charging. 06:51.000 --> 06:55.000 So also some necessary stuff here. 06:55.000 --> 07:02.000 And then here we have the local consumers and producers of energy. 07:02.000 --> 07:08.000 They can talk with each other via E-bass, for example. 07:08.000 --> 07:13.000 And E-bass also enables the interaction with the grid. 07:13.000 --> 07:19.000 And defines also the behavior of this devices in specific use cases. 07:19.000 --> 07:28.000 And now I want to dive more into errors and show you some internals. 07:28.000 --> 07:30.000 Again, some system architecture. 07:30.000 --> 07:32.000 This one is inside of errors. 07:32.000 --> 07:35.000 So the rectangles are our internals modules. 07:35.000 --> 07:38.000 The ovals are some external service. 07:38.000 --> 07:42.000 And the color purple means that this area is worked in progress. 07:42.000 --> 07:44.000 I want to break it down for you. 07:44.000 --> 07:47.000 On the left we see the communication to the EV. 07:47.000 --> 07:49.000 So here is a 15118. 07:49.000 --> 07:50.000 It doesn't point. 07:50.000 --> 07:52.000 We have the EV's E-Manager. 07:52.000 --> 07:53.000 We have the isomodule. 07:53.000 --> 07:55.000 We have the hardware driver. 07:55.000 --> 07:57.000 In this case, the gate driver. 07:57.000 --> 07:59.000 And the EV. 07:59.000 --> 08:04.000 On the right side, we have OCPP, which also does some authorization. 08:04.000 --> 08:08.000 This is not important right now for us. 08:08.000 --> 08:14.000 But it connects the EV's E-Manager to the OCPP back end. 08:14.000 --> 08:18.000 In the bottom right, we can see the E-E bus related stuff. 08:18.000 --> 08:21.000 This is connected to the energy manager. 08:21.000 --> 08:25.000 And we'll give some limits to charge and discharge. 08:25.000 --> 08:29.000 Yeah, the energy manager, how does it works? 08:29.000 --> 08:32.000 So even one lay down. 08:32.000 --> 08:35.000 It has a representation of the energy tree in it. 08:35.000 --> 08:39.000 So we have, in this case, two EV's E's. 08:39.000 --> 08:41.000 To connect us at one charging station. 08:41.000 --> 08:43.000 They each have a circuit breaker. 08:43.000 --> 08:48.000 And they share also a circuit breaker with 63 AMs in this case. 08:48.000 --> 08:56.000 And if one of these nodes wants to produce or consume more or less energy, 08:56.000 --> 08:58.000 it needs to make a request. 08:58.000 --> 09:01.000 And this root price is brought up to the energy manager. 09:01.000 --> 09:03.000 So following the green arrows. 09:03.000 --> 09:06.000 And then the energy manager asks some logic. 09:06.000 --> 09:10.000 And brings back down through the node and response 09:10.000 --> 09:15.000 with the distribution of the power consumption. 09:15.000 --> 09:20.000 Here, we can see the energy tree in this architecture. 09:20.000 --> 09:22.000 So in the bottom right, the energy manager. 09:22.000 --> 09:26.000 Then there's some limit control by E bus. 09:26.000 --> 09:29.000 Then some limit control by OCPP. 09:29.000 --> 09:35.000 And this is what can be used in the EV's E-Manager. 09:36.000 --> 09:39.000 So now we come to the conclusion. 09:39.000 --> 09:41.000 What are the today's problems? 09:41.000 --> 09:45.000 Yeah, the most EV's and EV's E-V-S-E's. 09:45.000 --> 09:49.000 Don't speak is 15118-20. 09:49.000 --> 09:57.000 So to address this issue, the one thing we do is testing the EV's in the field. 09:57.000 --> 10:01.000 And we have a nice repository with all the lock files. 10:01.000 --> 10:08.000 And with a nice table where you can have a look at which EV has which features. 10:08.000 --> 10:13.000 Then another problem is, okay, an open standard doesn't mean automatically 10:13.000 --> 10:15.000 that we have an open implementation. 10:15.000 --> 10:19.000 This is by ever's targets, exactly this. 10:19.000 --> 10:23.000 And it implements this protocols and standards 10:23.000 --> 10:25.000 or integrate existing ones. 10:25.000 --> 10:30.000 And in some cases like E bus, which comes with a lot of overhead, 10:30.000 --> 10:37.000 it's quite hard to just do a simple implementation by yourself. 10:37.000 --> 10:42.000 So we are all in already on the positive side on the Outlook side. 10:42.000 --> 10:44.000 We have open software. 10:44.000 --> 10:48.000 As I mentioned, Everest, which brings implementation for the, yeah, 10:48.000 --> 10:55.000 is of 15118 stuff and for the OCPP stuff for all the different versions. 10:55.000 --> 11:00.000 So on a good way there, and we have also some other open source projects. 11:00.000 --> 11:04.000 We already heard three of them today. 11:04.000 --> 11:08.000 And yeah, we have, for example, for E bus. 11:08.000 --> 11:13.000 We have a E bus, go library, which we couldn't integrate in Everest. 11:13.000 --> 11:18.000 We have Citroen Res on the OCPP back-and-site, Steve and Maeve. 11:18.000 --> 11:24.000 And we also need hardware to run this open software on. 11:24.000 --> 11:28.000 And there's already hardware that can do this. 11:28.000 --> 11:31.000 There are more than 10,000 chargers in the field, 11:31.000 --> 11:34.000 currently that already run Everest. 11:34.000 --> 11:39.000 And then we have, for example, the Phyres aboard, 11:39.000 --> 11:42.000 which is built in a very modular way. 11:42.000 --> 11:46.000 And I also bring a configuration of it. 11:46.000 --> 11:51.000 It is here in AC configuration, but the board is also designed to do DC 11:52.000 --> 11:55.000 and bi-directional charging. 11:55.000 --> 11:58.000 So, and it can, can run Everest. 11:58.000 --> 12:03.000 So, yeah, it is already available. 12:03.000 --> 12:07.000 Then we have the dashboard, as reference hardware. 12:07.000 --> 12:13.000 It is open hardware, it is already available, designed for AC and DC. 12:13.000 --> 12:16.000 At once Everest. 12:16.000 --> 12:19.000 Then we have the GAT board. 12:19.000 --> 12:23.000 I bought also one, which is more designed to do AC, 12:23.000 --> 12:27.000 but it is also possible to do some DC stuff there. 12:27.000 --> 12:31.000 Also, open hardware, and also already available. 12:31.000 --> 12:36.000 So, there we are on a good way on software and hardware. 12:36.000 --> 12:38.000 We're looking through the future. 12:38.000 --> 12:41.000 And last thing to say is, get involved. 12:41.000 --> 12:44.000 There are multiple open source projects you code country to. 12:44.000 --> 12:48.000 In our case, in Everest, we have open working group calls, 12:48.000 --> 12:52.000 where you can just join ask questions, bring in your ideas, 12:52.000 --> 12:54.000 and yeah, start contributing. 12:54.000 --> 12:56.000 And since there is no much time left, 12:56.000 --> 13:00.000 we can do a Q&A session in the hallway. 13:00.000 --> 13:02.000 Thanks. 13:02.000 --> 13:13.000 We have two minutes to do Q&A here. 13:13.000 --> 13:21.000 Can you talk about the bus as the way to talk building management system? 13:21.000 --> 13:23.000 That's not yours back, right? 13:23.000 --> 13:25.000 That's the else approach call. 13:25.000 --> 13:29.000 Make sure I don't do that, but I do do MQTT. 13:29.000 --> 13:31.000 Yeah. 13:31.000 --> 13:35.000 So, the bus is one way to do it. 13:35.000 --> 13:39.000 So you mean this slide, right? 13:39.000 --> 13:41.000 So the bus is one way. 13:42.000 --> 13:45.000 Yeah, something we are currently on it, 13:45.000 --> 13:48.000 because it's in Germany. 13:48.000 --> 13:52.000 It may be more spreaded to use ebus, 13:52.000 --> 13:56.000 but it's also a bit of clunky, 13:56.000 --> 14:02.000 and it's hard to say, 14:02.000 --> 14:05.000 if it's the best choice to do ebus, 14:05.000 --> 14:08.000 but we will see what the future brings. 14:09.000 --> 14:11.000 Yeah. 14:11.000 --> 14:12.000 Yeah. 14:20.000 --> 14:22.000 Sorry to do what with the battery? 14:22.000 --> 14:26.000 I don't exactly. 14:26.000 --> 14:36.000 So you don't kill the battery by just trying to get older. 14:36.000 --> 14:40.000 Do you want to prevent it from just charging the bus operation? 14:40.000 --> 14:44.000 Do you just keep the problem at the car? 14:44.000 --> 14:48.000 So the ease of 15 and 118, 14:48.000 --> 14:54.000 20 protocol will care about a correct charging and discharging. 14:54.000 --> 15:01.000 But of course, you will have some use of the battery 15:01.000 --> 15:05.000 and the battery will getting worse 15:05.000 --> 15:08.000 with the time as the same, 15:08.000 --> 15:12.000 if you would charge and discharge while driving. 15:12.000 --> 15:18.000 But yeah, this... 15:18.000 --> 15:20.000 The truth. 15:36.000 --> 15:39.000 Yeah. 15:39.000 --> 15:42.000 So thank you for attending. 15:42.000 --> 15:43.000 Time's up. 15:43.000 --> 15:45.000 Thank you.