EvseCapability

@MapboxExperimental
object EvseCapability

OCPI Capability. The capabilities of an EVSE. Refer to this type in the OCPI GitHub repository for more details.

Types

Link copied to clipboard
annotation class Type

Retention policy for the EvseCapability.

Properties

Link copied to clipboard

The EVSE supports charging preferences.

Link copied to clipboard

The EVSE supports charging profiles.

Link copied to clipboard

EVSE has a payment terminal that supports chip cards.

Link copied to clipboard

EVSE has a payment terminal that supports contactless cards.

Link copied to clipboard

EVSE has a payment terminal that makes it possible to pay for charging using a credit card.

Link copied to clipboard

EVSE has a payment terminal that makes it possible to pay for charging using a debit card.

Link copied to clipboard
const val PED_TERMINAL: String

EVSE has a payment terminal with a pin-code entry device.

Link copied to clipboard

The EVSE can remotely be started/stopped.

Link copied to clipboard
const val RESERVABLE: String

The EVSE can be reserved.

Link copied to clipboard
const val RFID_READER: String

Charging at this EVSE can be authorized with an RFID token.

Link copied to clipboard

When a StartSession is received by this EVSE, the eMSP is required to add the optional c onnector_id field in the StartSession object.

Link copied to clipboard

This EVSE supports token groups, two or more tokens work as one, so that a session can be started with one token and stopped with another (handy when an EV driver has both a card and key-fob).

Link copied to clipboard
const val UNKNOWN: String

The capability of the EVSE is unknown.

Link copied to clipboard

Connectors have mechanical lock that can be requested by the eMSP to be unlocked.