You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ The standard OCPP configuration persistency has to be handled by the user applic
67
67
| Firmware Management | Support for firmware update management and diagnostic log file download | Actual file download/upload as well as firmware installation must be handled by the user application in the callbacks provided by **Open OCPP**|
68
68
| Local Auth List Management | Features to manage the local authorization list in Charge Points | None |
69
69
| Reservation | Support for reservation of a Charge Point. | None |
70
-
| Smart Charging | Support for basic Smart Charging, for instance using control pilot | GetCompositeSchedule is not supported for now in Chare Point role |
70
+
| Smart Charging | Support for basic Smart Charging, for instance using control pilot | GetCompositeSchedule is not supported for now in Charge Point role |
71
71
| Remote Trigger | Support for remote triggering of Charge Point initiated messages | None |
72
72
73
73
### Supported OCPP configuration keys
@@ -86,7 +86,7 @@ In the "Owner" column, "S" means that the configuration key behavior is handled
86
86
| ConnectionTimeOut | S | None |
87
87
| ConnectorPhaseRotation | S | None |
88
88
| ConnectorPhaseRotationMaxLength | S | None |
89
-
| GetConfigurationMaxKeys | S | Must be set to the sum of OCPP configuration keys count (99) + user application configuration keys count to allow to export all the configuration in 1 message |
89
+
| GetConfigurationMaxKeys | S | Must be set to the sum of OCPP configuration keys count (49) + user application configuration keys count to allow to export all the configuration in 1 message |
90
90
| HeartbeatInterval | S | Heartbeat are only sent if no messages have been exchanged since HeartbeatInterval seconds |
91
91
| LightIntensity | U | None |
92
92
| LocalAuthorizeOffline | S | None |
@@ -139,10 +139,9 @@ In the "Owner" column, "S" means that the configuration key behavior is handled
139
139
* 2 : TLS with HTTP Basic Authentication
140
140
* 3 : TLS with Client Side Certificates
141
141
142
-
The OCPP use cases to dynamically switch between Security Profiles is not implemented yet.
143
-
Only the automatic reconnexion when the **AuthorizationKey** parameter has been modified is implemented.
144
-
145
-
To switch between Security Profiles, the user application will have to : stop the stack, modify the connexion parameters, restart the stack.
142
+
In Charge Point role, the stack will automatically disconnect and then reconnect to the Central System after one of the following parameters has been modified :
143
+
***AuthorizationKey**
144
+
***Security Profile**
146
145
147
146
#### Security events
148
147
@@ -159,6 +158,13 @@ In Charge Point role, the user application can generate custom security events a
159
158
160
159
**Open OCPP** support this feature for both Charge Point and Central System roles.
161
160
161
+
#### Certificate management messages
162
+
163
+
**Open OCPP** support this feature for both Charge Point and Central System roles.
164
+
165
+
The actual storage of the certificates and their keys must be done by the user application.
166
+
167
+
**Open OCPP** provides callbacks and helper classes to ease certificate manipulation and installation.
Copy file name to clipboardExpand all lines: examples/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ The following examples are available :
6
6
*[Quick start Central System example](./quick_start_centralsystem/README.md)
7
7
*[Quick start Charge Point example](./quick_start_chargepoint/README.md)
8
8
*[Remote Charge Point example](./remote_chargepoint/README.md)
9
+
*[Security Charge Point example](./security_chargepoint/README.md)
9
10
10
11
How to run the examples:
11
12
* Customize the *config.ini* file of the selected example with the URL of the Central System and the other connection parameters has well has the OCPP configuration keys
0 commit comments