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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ This implementation is based on the following libraries :
60
60
61
61
As of this version :
62
62
63
-
* All the messages defined in the OCPP 1.6 edition 2 protocol have been implemented except GetCompositeSchedule for Charge Point role
63
+
* All the messages defined in the OCPP 1.6 edition 2 protocol have been implemented
64
64
* All the configuration keys defined in the OCPP 1.6 edition 2 protocol have been implemented for the Charge Point role
65
65
* All the messages defined in the OCPP 1.6 security whitepaper edition 2 have been implemented
66
66
* All the messages defined in the Using ISO 15118 Plug & Charge with OCPP 1.6 Application Note v1.0 have been implemented
@@ -93,7 +93,7 @@ The standard OCPP configuration persistency has to be handled by the user applic
93
93
| 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**|
94
94
| Local Auth List Management | Features to manage the local authorization list in Charge Points | None |
95
95
| Reservation | Support for reservation of a Charge Point. | None |
96
-
| Smart Charging | Support for basic Smart Charging, for instance using control pilot | GetCompositeSchedule is not supported for now in Charge Point role |
96
+
| Smart Charging | Support for basic Smart Charging, for instance using control pilot | GetCompositeSchedule is not supported for connector 0 in Charge Point role |
97
97
| Remote Trigger | Support for remote triggering of Charge Point initiated messages | None |
0 commit comments