Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Protocols


OCCP 1.5 SOAPno

OCPP 1.5 JSONno

OCCP 1.6 SOAPyes

OCPP 1.6 JSONyes
Operations Initiated by Charge Point

Authorizeyes

Boot Notificationyes

DataTransferyes

DiagnosticsStatusNotificationyes

FirmwareStatusNotificationyes

HeartBeatyes

MeterValuesyes

StartTransactionyes

StatusNotificationyes

StopTransactionyes
Operations Initiated by Central System

CancelReservationyes

ChangeAvailabilityyes

ChangeConfigurationyes

ClearCacheyes

ClearCharging Profileyes

DataTransferyes

GetCompositeScheduleno

GetConfigurationyes

GetDiagnoticsyes

GetLocalListVersionyes

RemoteStartTransactionyes

RemoteStopTransactionyes

ReserveNowno

Resetyes

SendLocalListyes

SetChargingProfileyes

UnlockConnectoryes

UpdateFirmwareyes
Security issues

support of the (optional) use of TLS in OCPP 1.5?no

support of the (optional) use of TLS in OCPP 1.6?yes (in development)

used TLS version in OCPP 1.6yes (in development)

maximum key length in OCPP 1.6yes (in development)

validation of server protocolsyes

support of SFTP for firmware updatesyes (we will support SSL)

individual credentials per Charge Point (per default)no
Configuration Profiles

Support of Core Profileyes

AllowOfflineTxForUnknownIdyes

AuthorizationCacheEnabledyes

BlinkRepeatno (is using different approach)

LightIntensityno (is using light sensor)

MaxEnergyOnInvalidIdno (does not allow to start on invalid id)

MeterValuesAlignedDataMaxLengthyes

MeterValuesSampledDataMaxLengthyes

MinimumStatusDurationno

ConnectorPhaseRotationMaxLengthno (we use other settings)

StopTxnAlignedDataMaxLengthno

StopTxnSampledDataMaxLengthno

SupportedFeatureProfilesMaxLengthyes

WebSocketPingIntervalyes

Support of Local Auth List Management Profileyes

ConnectorSwitch3to1PhaseSupportedno

Support of Smart Charging Profileyes

ConnectorSwitch3to1PhaseSupportedno
  • No labels