Medinilla is a charging station management system backend built on top of ASP .NET Core. It aims to be a comprehensive, modular platform upon which you can build EV charging solutions.
Currently implemented OCPP messages:
- Boot Notification
- Heartbeat
- Security Event
- Authorize
- Transaction Event
The most fundamental idea behind the architectural decisions on this project was scalability, and fault tolerance. The core logic of Medinilla runs in Akka Actors, which are assigned per-client connection.
One thing to note is that response to websockets is dispatched on the thread pool directly, since we don’t expect it to grow that much (us sending data back to a ws is essentially ‘fire-and-forget’).
Currently detailed, OCPP Basic Implementation (as per docs):
Use cases to be implemented:
Use cases to be implemented:
Use cases to be implemented:
Use cases to be implemented (one of):
Use cases to be implemented:
- E01 (one of S1-S6)
- E02
- E03
- E05
- E06 (one of S1-S6)
- E07
- E08
- One of E09, E10, E11, E12, E13
Use cases to be implemented:
Use cases to be implemented:
Use cases to be implemented:
Use cases to be implemented:
Some of the future features in the pipeline for Medinilla are:
- [✓]
Transaction Graphs. These are an optimized way of computing transaction consumption, by generating and keeping track of a graph with sampled values based on measurand, context, etc. – Link to README - Custom hardware logic plugin. Despite OCPP being a comprehensive protocol, firmware implementations vary significantly in practice. Medinilla will offer plug-and-play modules for extending or modifying OCPP event handlers, allowing users to either build firmware-specific plugins or reuse existing ones from the community.
- HTTP Hooks. Users can inject custom logic in the pipeline by wiring their own implementation. We send events to your endpoint. You consume them.
Actions have been implemented using the following Charging Station emulators: