OCPP.Core
OCPP.Core is an OCPP (Open ChargePoint Protocol) server written in .NET 10. It includes a management Web-UI for administration of charge points and charge tokens (RFID-Token)
Status
It currently supports OCPP1.6J, 2.0 and 2.1.
OCPP.Core is currently used with 6 KEBA P30c/x charge points operating in a load management and OCPP1.6J.
Here’s a report of the first real live experiences from 2021.
The OCPP-Server currently handles the following messages:
OCPP V1.6
Messages from the charge point (processed):
- BootNotification
- Heartbeat
- Authorize
- StartTransaction
- StopTransaction
- MeterValues
- StatusNotification
- DataTransfer
Commands to the charge point (via API / Management-UI):
- RemoteStartTransaction
- RemoteStopTransaction
- Reset
- UnlockConnector
- SetChargingProfile
- ClearChargingProfile
- GetConfiguration
- ChangeConfiguration
OCPP V2.0 and V2.1
Messages from the charge point (processed):
- BootNotification
- Heartbeat
- Authorize
- TransactionEvent
- MeterValues
- StatusNotification
- DataTransfer
- NotifyReport (answer to GetBaseReport)
Messages from the charge point that are accepted, but not processed further (content in the log or in the EventLog of the charge point):
- LogStatusNotification
- FirmwareStatusNotification
- ClearedChargingLimit
- NotifyChargingLimit
- NotifyEVChargingSchedule
- SecurityEventNotification (EventLog)
- NotifyEvent (EventLog)
Messages from the charge point for functions the server doesn’t offer - answered as the specification requires and noted in the EventLog:
- SignCertificate (Rejected)
- Get15118EVCertificate (Failed)
- GetCertificateStatus (Failed)
- NotifyEVChargingNeeds (Rejected, OCPP 2.1: NoChargingProfile)
Answers to requests the server never sends - accepted and noted in the EventLog:
- ReservationStatusUpdate
- NotifyMonitoringReport
- ReportChargingProfiles
- NotifyCustomerInformation
- NotifyDisplayMessages
- PublishFirmwareStatusNotification
Commands to the charge point (via API / Management-UI):
- RequestStartTransaction
- RequestStopTransaction
- Reset
- UnlockConnector
- SetChargingProfile
- ClearChargingProfile
- GetVariables
- GetBaseReport
- SetVariables
All other messages from a charge point are rejected (CALLERROR “NotSupported”) and noted in the EventLog of the charge point, so you can see when a charge point sends messages the server doesn’t support.
Management Web-UI
The Web-UI is localized in English and German. It has an overview page with all charge stations and their availabilty.
Every charge point (or connector!) is displayed as a tile with status information. If a car is charging the tile is red and shows the duration. If the charge station sends data about the current power and state of charge (SoC) itis displayed in the footer of the tile. Our KEBA devices e.g. are only sending the main meter value :-(
If you click on a charge point/connector tile you get a list of the latest transactions and can download them as CSV.
The Web-UI has two different roles. A normal user can see the charge points and transactions (screenshots above). An Administrator can also create and edit the charge stations, charge tags, connectors and can also manage user accounts.
Multi connector behavior
At first, I didn’t pay much attention to multiple connectors. Charge points with multiple connectors are not very common. But then we got the charge points in our home installed and it turned out that our devices (with load management) operate as a single charge point with a connector for each charge point (see here).
I added multi connector support with V1.1. When the server receives an OCPP message with a connector number (status & transaction messages) the OCPP server dynamically builds a list of connectors in the database (table “ConnectorStatus”). Admin users can see this list and can optionally configure custom names.
This results in different scenarios for displaying charge points:
- A charge point without known connectors
=> display charge point with its name
- A charge point with one known connector without a specific name
=> display one charge point with the charge point name
- A charge point with 2+ connectors without specific names
=> display each connector with a default name “charge point name:connector no.”
If a connector has a name specified this name overrides the charge point name or default scheme (see above). This allows you to define custom names for every connector (like left / right).
System Requirements
OCPP.Core is written in .NET 8 and therefore runs on different plattforms. I also installed it in Azure for testing purposes.
The storage is based on the EntityFramework-Core and supports different databases. The project contains script for SQL-Server (SQL-Express) and SQLite.
Build, Configuration and Installation
The steps to build, configure and install OCPP.Core are described here in Detail.
Testing it…
Web-UI
Open the configured URL in a browser. The debug URL in the project is “http://localhost:8082/”.
You should see the login screen. Enter the configured admin account.
Open the “Administration” menu and create a chargepoint with ID “station42” and a charge tag.
Administration menu:
Create new chargepoint:
Optionally, you can add authentication data for this chargepoint: Username/Password for basic authentication and/or a certificate thumbprint for a client certificate.
When you’re editing a chargepoint you can send restart or unlock commands to the chargepoint here.
Create new charge tag:
The Web-UI is localized in English and German language
OCPP-Server
An easy way to test the OCPP-Server are simulators:
Attention: Both simulators have minor and major bugs in certain actions. That’s why I modified them both and included copies in this project.
There also is an extended version of the 1.6 simulator with two connectors:
Open one of the simulators in the browser and enter “ws://localhost:8081/OCPP/station42” as the central station URL.
“station42” is the ID of the chargepoint you created in the previous step.
Enter the charge tag ID you entered before as “Tag”.
Click “Connect”
Now the simulator hopefully show a success message at the bottom.
When you start a transaction and refresh the Web-UI you should see the corresponding status in the charge point tiles.
评论