nos- / steve

SteVe - Steckdosenverwaltung

Introduction

SteVe was developed at the RWTH Aachen University and means Steckdosenverwaltung, namely socket administration in German. The aim of SteVe is to support the deployment and popularity of electric mobility, so it is easy to install and to use. SteVe provides basic functions for the administration of charge points, user data, and RFID cards for user authentication and was tested successfully in operation.

SteVe is considered as an open platform to implement, test and evaluate novel ideas for electric mobility, like authentication protocols, reservation mechanisms for charge points, and business models for electric mobility. SteVe is distributed under GPL and is free to use. If you are going to deploy SteVe we are happy to see the logo on a charge point.

Charge Point Support

Electric charge points using the following OCPP versions are supported:

• OCPP1.2S
• OCPP1.5S
• OCPP1.2J
• OCPP1.5J

We have successfully tested SteVe with charge points manufactured by EBG and Mennekes. If your charge point also works well with SteVe, please let us know! We will update the list.

System Requirements

SteVe requires

• JDK 8 (both Oracle JDK and OpenJDK are supported)
• Maven
• At least MySQL 5.6.4 (MariaDB 10.0 or later works as well) as database

to build and run.

SteVe is designed to run standalone, a java servlet container / web server (e.g. Apache Tomcat), is not required.

Configuration and Installation

1. Database preparation:

   The following MySQL statements can be used as database initialization (adjust according to your setup):

   CREATE DATABASE stevedb CHARACTER SET utf8 COLLATE utf8_unicode_ci;
   GRANT ALL PRIVILEGES ON stevedb.* TO 'steve'@'localhost' IDENTIFIED BY 'changeme';
   GRANT SELECT ON mysql.proc TO 'steve'@'localhost' IDENTIFIED BY 'changeme';
   

2. Download and extract tarball:

   You can download and extract the SteVe releases using the following commands (replace X.X.X with the desired version number):

   wget https://github.com/RWTH-i5-IDSG/steve/archive/steve-X.X.X.tar.gz
   tar xzvf steve-X.X.X.tar.gz
   cd steve-X.X.X
   

3. Configure SteVe before building:

   The basic configuration is defined in main.properties:

   • You must change database configuration
   • You must change the host to the correct IP address of your server
   • You must change web interface credentials
   • You can access the application via HTTPS, by enabling it and setting the keystore properties

   For advanced configuration please see the Configuration wiki

4. Build SteVe:

   To compile SteVe simply use Maven. A runnable jar file containing the application and configuration will be created in the subdirectory steve/target.

   # mvn package
   

5. Run SteVe:

   To start the application run (please do not run SteVe as root):

   # java -jar target/steve-X.X.X.jar
   

First Steps

After SteVe has successfully started, you can access the web interface using the configured credentials under:

http://<your-server-ip>:<port>/steve/manager

The default port number is 8080.

Add a charge point

1. In order for SteVe to accept messages from a charge point, the charge point must first be registered. To add a charge point to SteVe select Data Management >> Charge Points >> Add. Enter the ChargeBox ID configured in the charge point and confirm.

2. The charge points must be configured to communicate with following addresses. Depending on the OCPP version of the charge point, SteVe will automatically route messages to the version-specific implementation.

   • SOAP: http://<your-server-ip>:<port>/steve/services/CentralSystemService
   • WebSocket/JSON: ws://<your-server-ip>:<port>/steve/websocket/CentralSystemService/<chargeBoxId>

As soon as a heartbeat is received, you should see the status of the charge point in the SteVe Dashboard.

Have fun!

Screenshots

1. Home
2. Connector Status
3. Data Management - Charge Points
4. Data Management - Users
5. Data Management - OCPP Tags
6. Data Management - Reservations
7. Data Management - Transactions
8. Operations - OCPP v1.2
9. Operations - OCPP v1.5
10. Settings

Are you having issues?

See the FAQ

steve's Issues

Adaption of the comunicationprotocol SteVe <--> NKT-Chargepoint // Anpassung des Kommunikationsprotokolls SteVe <--> NKT-Ladesäule

Beim Vergleich der Tests zwischen

SteVe <--> Ladesäulensimulator
SteVe <--> realer NKT-Ladesäule

ist im Wiresharkmitschnitt aufgefallen, das die NKT-Säule im Gegensatz zur Simulation u.a. den Namespace "ns1" (im Head sowie auch im Body) ihres SOAP-Authentifizierungspaketes verwendet.

Im Branch custom-ns-prefix wurden zwar bereits einige dieser Unterschiede angeglichen, allerdings wird der ns1-Namespace bisher nur im Header aber noch nicht im Body berücksichtigt.

Für die weitere Arbeit ist es erforderlich, das dies weiterverfolgt und der spezielle Namensraum überall verwendet wird.