How to handle battery packs?

[cyasing]

I am trying to simulate a battery pack for an electric vehicle. The battery pack needs to be subjected to a drive cycle of one of WLTC drive cycles. I am not able to understand how to use an array of cell models to a single drive cycle (instead of subjecting each cell to a drive cycle). This is to ensure that I am not just repeating the same simulation over and over, but is simultaneous as in real-life conditions.

I do see that there is a discussion for WLTC drive cycle here, but it is scaled for a single cell, which is not something that I want.

[cyasing]

It looks like there is another software developed by the PyBaMM team, liionpack, that uses PyBaMM to model a whole battery pack. I'll be trying that now.

[cyasing]

@TomTranter Did you find anything wrong with my approach? I have now updated my single cell script, data, and similarly, the battery script that works better than the previous one, at least at the cell level. The error of "constant current operations" still does not go away, however. Just saying if those are needed.

[TomTranter]

Sorry haven't looked yet. Will see on Monday

[cyasing]

Sorry haven't looked yet. Will see on Monday

Alright.

[TomTranter]

So liionpack supports drivecycles specifying current only

[cyasing]

So liionpack supports drivecycles specifying current only

Yeah, that makes sense.

[TomTranter]

Aligning liionpack more closely with PyBaMM functionality is on our roadmap and should be available in the near future. Sorry for the inconvenience. In the meantime that error message isn't the best as I see how it could have led you to think no drive cycles were possible at all

[TomTranter]

Have a look at the model.variables. You're going to have to be a bit more specific with that question. At which point are you trying to access them?

[cyasing]

I was planning on editing the protocols.py to add a case for power input. In a forked repository. I thought that might be better than writing a function in my original script, since I can stop that error from coming up that way.

[cyasing]

I was planning on editing the protocols.py to add a case for power input. In a forked repository. I thought that might be better than writing a function in my original script, since I can stop that error from coming up that way.

Do you think this is not optimal?

[TomTranter]

Please stop posting here and open an issue on the liionpack repo.

[cyasing]

Sorry about that, I thought I should continue here.