OCPP

Examples for Setting Charging Profiles

TxDefaultProfile

{ "connectorId": "0", "csChargingProfiles": { "chargingProfileId": 1, "stackLevel": 1, "chargingProfilePurpose": "TxDefaultProfile", "chargingProfileKind": "Recurring", "recurrencyKind": "Daily", "chargingSchedule": { "startSchedule": "2021-01-01T00:00:00Z", "chargingRateUnit": "A", "chargingSchedulePeriod": [ { "startPeriod": 0, "limit": 15 }, { "startPeriod": 72000, "limit": 30 }, { "startPeriod": 79200, "limit": 25 } ] } } }

 

ChargePointMaxProfile

{ "connectorId": 0, "csChargingProfiles": { "chargingProfileId": 1, "stackLevel": 1, "chargingProfilePurpose": "ChargePointMaxProfile", "chargingProfileKind": "Absolute", "chargingSchedule": { "chargingRateUnit": "A", "chargingSchedulePeriod": [ { "startPeriod": 0, "limit": 15 } ], "startSchedule": "2022-04-28T21:02:00Z" } } }

AllowOfflineTxForUnknownId

Required/Optional: Optional

Accessibility: Read/write

Type: Boolean

Default value: False

Description:

  • If this key exists, the Charge Point supports Unknown Offline Authorization.
  • If the key is any form of TRUE, then Unknown Offline Authorization is enabled.

AuthorizationCacheEnabled

Required/Optional: Optional

Accessibility: Read

Type: Boolean

Default value: False

Description:

  • If this key exists, the Charge Point supports an Authorization Cache.
  • If this key is any form of TRUE, the Authorization Cache is enabled.

AuthorizeRemoteTxRequests

Required/Optional: Required

Accessibility: Read/Write

Type: Boolean

Default value: True

Description: Whether a remote request to start a transaction in the form of a RemoteStartTransaction.req message should be authorized beforehand like a local action to start a transaction.

ChargingScheduleAllowedChargingRateUnit

Required/Optional: Required

Accessibility: Read

Type: Comma-separated list

Default value: Current

Description: A list of supported quantities for use in a ChargingSchedule. Allowed values: 'Current' and 'Power'.

ChargingScheduleMaxPeriods

Required/Optional: Required

Accessibility: Read

Type: Integer

Default value: 24

Description: Maximum number of periods that may be defined per ChargingSchedule.

ClockAlignedDataInterval

Required/Optional: Required

Accessibility: Read/write

Type: Integer

Default value: 900

Description: Represents the size (in seconds) of the per-day aggregation intervals of clock-aligned data. For example, a value of 900 means that every day is broken into 96 15-minute (900 seconds) intervals.

 

When clock aligned data is being transmitted, the interval in question is identified by the start time and (optional) duration interval value, represented according to the ISO8601 standard. All "per-period" data (e.g. energy readings) should be accumulated (for "flow" type measurands such as energy), or averaged (for other values) across the entire interval (or partial interval, at the beginning or end of a charging session), and transmitted (if so enabled) at the end of each interval, bearing the interval start time timestamp. A value of "0" (numeric zero), by convention, is to be interpreted to mean that no clock-aligned data should be transmitted.

ConnectionTimeOut

Required/Optional: Required

Accessibility: Read/write

Type: Integer (in seconds)

Default value: 25

Description: Interval (from successful authorization) until charging session is canceled due to failure of EV user to correctly insert the charging cable.

ConnectorPhaseRotation

Required/Optional: Required

Type: Comma-separated list

Description: The phase rotation per connector relative to the connector's energy meter (or, if absent, the grid connection).

Possible values per connector are:

  • NotApplicable (for Single phase or DC Charge Points)
  • Unknown (not yet known)
  • RST (Standard Reference Phasing)
  • RTS (Reversed Reference Phasing)
  • SRT (Reversed 240 degree rotation)
  • STR (Standard 120 degree rotation)
  • TRS (Standard 240 degree rotation)
  • TSR (Reversed 120 degree rotation)
  • R = Phase 1 (L1)
  • S = Phase 2 (L2)
  • T = Phase 1 (L3)

If known, the Charge Point MAY also report the phase rotation between the grid connection and the main energymeter by using index number Zero.

Values are reported as a comma-separated list, formatted: 0.RST, 1.RST, 2.RTS.

GetConfigurationMaxKeys

Required/Optional: Required

Accessibility: Read

Type: Integer

Default value: 36

Description: Maximum number of requested configuration keys in a GetConfiguration.req PDU.

HeartbeatInterval

Required/Optional: Required

Accessibility: Read/write

Type: Integer (in seconds)

Default value: 60

Description: Interval of inactivity (no OCPP exchanges) with central system after which the Charge Point should send a Heartbeat.req PDU.

LocalAuthorizeOffline

Required/Optional: Required

Accessibility: Read/write

Type: Boolean

Default value: True

Description: Whether the Charge Point, when offline, will start a transaction for locally-authorized identifiers.

LocalPreAuthorize

Required/Optional: Required

Accessibility: Read/write

Type: Boolean

Default value: True

Description: Whether the Charge Point, when online, will start a transaction for locally-authorized identifiers without waiting for or requesting an Authorize.conf from the Central System.

MaxEnergyOnInvalidId

Required/Optional: Optional

Accessibility: Read/write

Type: Integer (in Wh)

Default value: 0

Description: Maximum energy in Wh delivered when an identifier is invalidated by the Central System after start of a transaction.

MeterValuesAlignedData

Required/Optional: Optional

Accessibility: Read/write

Type: CSL

Default value: "Energy.Active.Import.Register"

Description: Clock-aligned measurand(s) to be included in a MeterValues.req PDU, every ClockAlignedDataInterval seconds.

MeterValueSampleInterval

Required/Optional: Optional

Accessibility: Read/write

Type: Integer (in seconds)

Default value: 90

Description: Interval between sampling of metering (or other) data, intended to be transmitted by "MeterValues" PDUs.

For charging session data (ConnectorId>0), samples are acquired and transmitted periodically at this interval from the start of the charging transaction.

A value of "0" (numeric zero), by convention, is to be interpreted to mean that no sampled data should be transmitted.

MeterValuesSampledData

Required/Optional: Required

Accessibility: Read/write

Type: CSL

Default value: "Energy.Active.Import.Register,Voltage,Current.Import,Power.Active.Import,Temperature,Frequency,Power.Factor"

Description: Sampled measurands to be included in a MeterValues.req PDU, every MeterValueSampleInterval seconds.

Where applicable, the Measurand is combined with the optional phase; for instance: Voltage.L1 Default: "Energy.Active.Import.Register".

NumberOfConnectors

Required/Optional: Required

Accessibility: Read

Type: Integer

Default value: 1

Description: The number of physical charging connectors of this Charge Point.

ReserveConnectorZeroSupported

Required/Optional: Optional

Accessibility: Read/write

Type: Boolean

Default value: True

Description: If this configuration key is present and set to TRUE,. then the Charge Point supports reservations on connector 0.

ResetRetries

Required/Optional: Required

Accessibility: Read/write

Type: Integer (in number of attempts)

Default value: 3

Description: Number of times to retry an unsuccessful reset of the Charge Point.

StopTransactionOnEVSideDisconnect

Required/Optional: Required

Accessibility: Read/write

Type: Boolean

Default value: True

Description: When set to true, the Charge Point SHALL administratively stop the transaction when the cable is unplugged from the EV.

StopTransactionOnInvalidId

Required/Optional: Required

Accessibility: Read/write

Type: Boolean

Default value: True

Description: Whether the Charge Point will stop an ongoing transaction when it receives a non-Accepted authorization status in a StartTransaction.conf for this transaction.

StopTxnAlignedData

Required/Optional: Required

Accessibility: Read/write

Type: Comma-separated list

Default value: "Energy.Active.Import.Register"

Description: Clock-aligned periodic measurand(s) to be included in the TransactionData element of a StopTransaction.req MeterValues.req PDU for every ClockAlignedDataInterval of the charging session.

StopTxnSampledData

Required/Optional: Optional

Accessibility: Read/write

Type: Comma-separated list

Description: Maximum number of items in a StopTxnAlignedData Configuration Key.

StopTxnSampledDataMaxLength

Required/Optional: Optional

Accessibility: Read

Type: 0

Description: Maximum number of items in a StopTxnSampledData Configuration Key

SupportedFeatureProfiles

Required/Optional: Required

Accessibility: Read

Type: Comma-separated list

Default value: Core

Description: A list of supported Feature Profiles.

Possible values:

  • Core
  • FirmwareManagement
  • LocalAuthListManagement
  • Reservation
  • SmartCharging
  • RemoteTrigger

SupportedFeatureProfilesMaxLength

Required/Optional: Optional

Accessibility: Read

Default value: 1

Description: Maximum number of items in a SupportedFeatureProfiles Configuration Key.

TransactionMessageAttempts

Required/Optional: Required

Accessibility: Read/write

Type: Integer (in number of times)

Default value: 1

Description: How often the Charge Point should try to submit a transaction-related message when the Central System fails to process it.

TransactionMessageRetryInterval

Required/Optional: Required

Accessibility: Read/write

Type: Integer (in seconds)

Default value: 0

Description: How long the Charge Point should wait before resubmitting a transaction-related message that the Central System failed to process.

UnlockConnectorOnEVSideDisconnect

Required/Optional: Required

Accessibility: Read/write

Type: Boolean

Default value: True

Description: When set to true, the Charge Point SHALL unlock the cable on the Charge Point side when the cable is unplugged at the EV.

WebSocketPingInterval

Required/Optional: Optional

Accessibility: Read

Type: Integer (in seconds)

Default value: 60

Description: Only relevant for websocket implementations:

  • 0 disables client side websocket Ping/Pong. In this case there is either no ping/pong or the server initiates the ping and client responds with Pong.

  • Positive values are interpreted as number of seconds between pings.

  • Negative values are not allowed. ChangeConfiguration is expected to return a REJECTED result.