# OCPPLab Docs

> Operator documentation for OCPPLab — OCPP gateway, OCPI roaming, Dashboard product guides, and integrations.

Base: https://ocpplab.com/docs

## Guides

- [Concepts](https://ocpplab.com/docs/guides/getting-started/concepts): Core EV charging terms: CPO, eMSP, OCPP, OCPI, and how OCPPLab fits the stack.
- [Introduction](https://ocpplab.com/docs/guides/getting-started/introduction): What OCPPLab is — OCPP/OCPI gateways, multi-backend routing, and when to use these docs.
- [Quickstart](https://ocpplab.com/docs/guides/getting-started/quickstart): Get from zero to a connected charge point and a visible session in the Dashboard in under an hour.
- [Getting started](https://ocpplab.com/docs/guides/getting-started): How OCPPLab fits into an EV charging stack and where to go next.
- [Credentials endpoint](https://ocpplab.com/docs/guides/ocpi/2-1-1/credentials): OCPI 2.1.1 Credentials endpoint — Module Identifier: credentials
- [OCPI](https://ocpplab.com/docs/guides/ocpi/2-1-1/introduction): OCPI 2.1.1 OCPI — During implementation of OCPI 2.1, a number of bugs in the message definition were found.
- [CDRs module](https://ocpplab.com/docs/guides/ocpi/2-1-1/mod-cdrs): OCPI 2.1.1 CDRs module — Module Identifier: cdrs
- [Commands module](https://ocpplab.com/docs/guides/ocpi/2-1-1/mod-commands): OCPI 2.1.1 Commands module — Module Identifier: commands
- [Locations module](https://ocpplab.com/docs/guides/ocpi/2-1-1/mod-locations): OCPI 2.1.1 Locations module — Module Identifier: locations
- [Sessions module](https://ocpplab.com/docs/guides/ocpi/2-1-1/mod-sessions): OCPI 2.1.1 Sessions module — Module Identifier: sessions
- [Tariffs module](https://ocpplab.com/docs/guides/ocpi/2-1-1/mod-tariffs): OCPI 2.1.1 Tariffs module — Module Identifier: tariffs
- [Tokens module](https://ocpplab.com/docs/guides/ocpi/2-1-1/mod-tokens): OCPI 2.1.1 Tokens module — Module Identifier: tokens
- [smartcharging](https://ocpplab.com/docs/guides/ocpi/2-1-1/smart-charging): OCPI 2.1.1 smartcharging — TO BE DEFINED
- [Status codes](https://ocpplab.com/docs/guides/ocpi/2-1-1/status-codes): OCPI 2.1.1 Status codes — There are two types of status codes:
- [Business Object Name](https://ocpplab.com/docs/guides/ocpi/2-1-1/template-object-description): OCPI 2.1.1 Business Object Name — This is a template for object descriptions.
- [Terminology and Definitions](https://ocpplab.com/docs/guides/ocpi/2-1-1/terminology): OCPI 2.1.1 Terminology and Definitions — OCPI Open Charge Point Interface
- [Transport and format](https://ocpplab.com/docs/guides/ocpi/2-1-1/transport-and-format): OCPI 2.1.1 Transport and format — The OCPI protocol is based on HTTP and uses the JSON format. It follows a RESTful architecture for webservices where possible.
- [Types](https://ocpplab.com/docs/guides/ocpi/2-1-1/types): OCPI 2.1.1 Types — Case Insensitive String. Only printable ASCII allowed.
- [versionhistory](https://ocpplab.com/docs/guides/ocpi/2-1-1/version-history): OCPI 2.1.1 versionhistory — Copyright © 2014 – 2019 NKL. All rights reserved.
- [Version information endpoint](https://ocpplab.com/docs/guides/ocpi/2-1-1/version-information-endpoint): OCPI 2.1.1 Version information endpoint — This endpoint lists all the available OCPI versions and the corresponding URLs to
- [OCPI 2.1.1](https://ocpplab.com/docs/guides/ocpi/2-1-1): Index of the OCPI 2.1.1 specification modules and reference docs, each on its own page.
- [Credentials module](https://ocpplab.com/docs/guides/ocpi/2-2-1/credentials): OCPI 2.2.1 Credentials module — Module Identifier: credentials
- [OCPI](https://ocpplab.com/docs/guides/ocpi/2-2-1/introduction): OCPI 2.2.1 OCPI — In the OCPI Development Working Group at the EV Roaming Foundation we are always tracking unclarities in the specification and making changes to the specification document to fix…
- [CDRs module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-cdrs): OCPI 2.2.1 CDRs module — Module Identifier: cdrs
- [ChargingProfiles module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-charging-profiles): OCPI 2.2.1 ChargingProfiles module — Module Identifier: chargingprofiles
- [Commands module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-commands): OCPI 2.2.1 Commands module — Module Identifier: commands
- [HubClientInfo module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-hub-client-info): OCPI 2.2.1 HubClientInfo module — Module Identifier: hubclientinfo
- [Locations module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-locations): OCPI 2.2.1 Locations module — Module Identifier: locations
- [Sessions module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-sessions): OCPI 2.2.1 Sessions module — Module Identifier: sessions
- [Tariffs module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-tariffs): OCPI 2.2.1 Tariffs module — Module Identifier: tariffs
- [Tokens module](https://ocpplab.com/docs/guides/ocpi/2-2-1/mod-tokens): OCPI 2.2.1 Tokens module — Module Identifier: tokens
- [Status codes](https://ocpplab.com/docs/guides/ocpi/2-2-1/status-codes): OCPI 2.2.1 Status codes — There are two types of status codes:
- [Terminology and Definitions](https://ocpplab.com/docs/guides/ocpi/2-2-1/terminology): OCPI 2.2.1 Terminology and Definitions — The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and
- [Supported Topologies](https://ocpplab.com/docs/guides/ocpi/2-2-1/topology): OCPI 2.2.1 Supported Topologies — OCPI started as a bilateral protocol, for peer-to-peer communication.
- [Transport and format](https://ocpplab.com/docs/guides/ocpi/2-2-1/transport-and-format): OCPI 2.2.1 Transport and format — The OCPI protocol is based on HTTP and uses the JSON format. It follows a RESTful architecture for web services where possible.
- [Types](https://ocpplab.com/docs/guides/ocpi/2-2-1/types): OCPI 2.2.1 Types — Case Insensitive String. Only printable ASCII allowed.
- [versionhistory](https://ocpplab.com/docs/guides/ocpi/2-2-1/version-history): OCPI 2.2.1 versionhistory — Version History
- [Versions module](https://ocpplab.com/docs/guides/ocpi/2-2-1/version-information-endpoint): OCPI 2.2.1 Versions module — Type: Configuration Module
- [OCPI 2.2.1](https://ocpplab.com/docs/guides/ocpi/2-2-1): Index of the OCPI 2.2.1 specification modules, each on its own page with field tables, examples, and JSON Schemas.
- [OCPI credentials handshake](https://ocpplab.com/docs/guides/ocpi/credentials): Establish mutual OCPI credentials and versions with an eMSP or hub on OCPPLab.
- [OCPI roaming go-live](https://ocpplab.com/docs/guides/ocpi/roaming): Checklist to take OCPI roaming live: credentials, locations, sessions, and CDRs.
- [OCPI](https://ocpplab.com/docs/guides/ocpi): Roaming connectivity with OCPI 2.1.1 and 2.2.1 on OCPPLab.
- [Authorize](https://ocpplab.com/docs/guides/ocpp/1-6/actions/authorize): Before the owner of an electric vehicle can start or stop charging, the Charge Point has to authorize the operation. The Charge Point SHALL only supply energy after authorization. When stopping a T…
- [Boot Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/boot-notification): After start-up, a Charge Point SHALL send a request to the Central System with information about its configuration (e.g. version, vendor, etc.). The Central System SHALL respond to indicate whether…
- [Cancel Reservation](https://ocpplab.com/docs/guides/ocpp/1-6/actions/cancel-reservation): To cancel a reservation the Central System SHALL send a CancelReservation.req PDU to the Charge Point.
- [Certificate Signed](https://ocpplab.com/docs/guides/ocpp/1-6/actions/certificate-signed): CertificateSigned.req is sent by the Central System to the Charge Point to deliver a Charge Point client-side certificate that has been signed by a Certificate Authority. It is used in both certifi…
- [Change Availability](https://ocpplab.com/docs/guides/ocpp/1-6/actions/change-availability): Central System can request a Charge Point to change its availability. A Charge Point is considered available (operative) when it is charging or ready for charging. A Charge Point is considered unav…
- [Change Configuration](https://ocpplab.com/docs/guides/ocpp/1-6/actions/change-configuration): Central System can request a Charge Point to change configuration parameters. To achieve this, Central System SHALL send a ChangeConfiguration.req. This request contains a key-value pair, where key…
- [Clear Cache](https://ocpplab.com/docs/guides/ocpp/1-6/actions/clear-cache): Central System can request a Charge Point to clear its Authorization Cache. The Central System SHALL send a ClearCache.req PDU for clearing the Charge Point's Authorization Cache.
- [Clear Charging Profile](https://ocpplab.com/docs/guides/ocpp/1-6/actions/clear-charging-profile): If the Central System wishes to clear some or all of the charging profiles that were previously sent to the Charge Point, it SHALL use the ClearChargingProfile.req PDU.
- [Data Transfer (Charge Point → Central System)](https://ocpplab.com/docs/guides/ocpp/1-6/actions/data-transfer): If a Charge Point needs to send information to the Central System for a function not supported by OCPP, it SHALL use the DataTransfer.req PDU.
- [Delete Certificate](https://ocpplab.com/docs/guides/ocpp/1-6/actions/delete-certificate): To facilitate the management of the Charge Point's installed certificates, the Central System can request the Charge Point to delete a specific installed certificate by sending a DeleteCertificate…
- [Diagnostics Status Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/diagnostics-status-notification): Charge Point sends a notification to inform the Central System about the status of a diagnostics upload.
- [Extended Trigger Message](https://ocpplab.com/docs/guides/ocpp/1-6/actions/extended-trigger-message): ExtendedTriggerMessage is the OCPP 2.0.1 TriggerMessage ported back into OCPP 1.6 security extension. It was renamed from TriggerMessage because the original name conflicts with the OCPP 1.6 messag…
- [Firmware Status Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/firmware-status-notification): A Charge Point sends notifications to inform the Central System about the progress of the firmware update. The Charge Point SHALL send a FirmwareStatusNotification.req PDU for informing the Central…
- [Get Composite Schedule](https://ocpplab.com/docs/guides/ocpp/1-6/actions/get-composite-schedule): The Central System MAY request the Charge Point to report the Composite Charging Schedule by sending a GetCompositeSchedule.req PDU. The reported schedule, in the GetCompositeSchedule.conf PDU, is…
- [Get Configuration](https://ocpplab.com/docs/guides/ocpp/1-6/actions/get-configuration): To retrieve the value of configuration settings, the Central System SHALL send a GetConfiguration.req PDU to the Charge Point.
- [Get Diagnostics](https://ocpplab.com/docs/guides/ocpp/1-6/actions/get-diagnostics): Central System can request a Charge Point for diagnostic information. The Central System SHALL send a GetDiagnostics.req PDU for getting diagnostic information of a Charge Point with a location whe…
- [Get Installed Certificate Ids](https://ocpplab.com/docs/guides/ocpp/1-6/actions/get-installed-certificate-ids): To facilitate the management of the Charge Point's installed certificates, the Central System can request the Charge Point to send a list of installed certificates of a given type by sending a GetI…
- [Get Local List Version](https://ocpplab.com/docs/guides/ocpp/1-6/actions/get-local-list-version): In order to support synchronisation of the Local Authorization List, Central System can request a Charge Point for the version number of the Local Authorization List. The Central System SHALL send…
- [Get Log](https://ocpplab.com/docs/guides/ocpp/1-6/actions/get-log): The Central System can request a Charge Point to upload a log file (security log or diagnostics log) to a given location. The format of the log file is not prescribed.
- [Heartbeat](https://ocpplab.com/docs/guides/ocpp/1-6/actions/heartbeat): To let the Central System know that a Charge Point is still connected, a Charge Point sends a heartbeat after a configurable time interval.
- [Install Certificate](https://ocpplab.com/docs/guides/ocpp/1-6/actions/install-certificate): The Central System uses InstallCertificate.req to install a new root/CA certificate (Central System Root or Manufacturer Root) into the Charge Point's trust store. This is not for installing the Ch…
- [Log Status Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/log-status-notification): The Charge Point uses LogStatusNotification.req to inform the Central System about the progress of a log file upload that was started by GetLog.req. The CP sends one or more notifications during th…
- [Meter Values](https://ocpplab.com/docs/guides/ocpp/1-6/actions/meter-values): A Charge Point MAY sample the energy meter or other sensor/transducer hardware to provide extra information about its meter values. It is up to the Charge Point to decide when it will send meter va…
- [Remote Start Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/actions/remote-start-transaction): Central System can request a Charge Point to start a transaction by sending a RemoteStartTransaction.req. Upon receipt, the Charge Point SHALL reply with RemoteStartTransaction.conf and a status in…
- [Remote Stop Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/actions/remote-stop-transaction): Central System can request a Charge Point to stop a transaction by sending a RemoteStopTransaction.req to the Charge Point with the identifier of the transaction. Charge Point SHALL reply with Remo…
- [Reserve Now](https://ocpplab.com/docs/guides/ocpp/1-6/actions/reserve-now): A Central System can issue a ReserveNow.req to a Charge Point to reserve a connector for use by a specific idTag.
- [Reset](https://ocpplab.com/docs/guides/ocpp/1-6/actions/reset): The Central System SHALL send a Reset.req PDU for requesting a Charge Point to reset itself. The Central System can request a hard or a soft reset. Upon receipt of a Reset.req PDU, the Charge Point…
- [Security Event Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/security-event-notification): The Charge Point uses SecurityEventNotification.req to immediately inform the Central System of changes in system security. The Central System acknowledges receipt with SecurityEventNotification.conf.
- [Send Local List](https://ocpplab.com/docs/guides/ocpp/1-6/actions/send-local-list): Central System can send a Local Authorization List that a Charge Point can use for authorization of idTags. The list MAY be either a full list to replace the current list in the Charge Point or it…
- [Set Charging Profile](https://ocpplab.com/docs/guides/ocpp/1-6/actions/set-charging-profile): A Central System can send a SetChargingProfile.req to a Charge Point, to set a charging profile, in the following situations:
- [Sign Certificate](https://ocpplab.com/docs/guides/ocpp/1-6/actions/sign-certificate): The Charge Point uses SignCertificate.req to request that the Certificate Authority sign its public key into a Charge Point certificate. The Charge Point sends the public key in the form of a Certi…
- [Signed Firmware Status Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/signed-firmware-status-notification): The Charge Point uses SignedFirmwareStatusNotification.req to inform the Central System about the progress of a secure firmware update started by SignedUpdateFirmware.req. This message is the OCPP…
- [Signed Update Firmware](https://ocpplab.com/docs/guides/ocpp/1-6/actions/signed-update-firmware): The Central System uses SignedUpdateFirmware.req to instruct the Charge Point to download and install a digitally-signed firmware image. This message is the OCPP 2.0.1 UpdateFirmware ported into OC…
- [Start Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/actions/start-transaction): The Charge Point SHALL send a StartTransaction.req PDU to the Central System to inform about a transaction that has been started. If this transaction ends a reservation (see Reserve Now operation)…
- [Status Notification](https://ocpplab.com/docs/guides/ocpp/1-6/actions/status-notification): A Charge Point sends a notification to the Central System to inform the Central System about a status change or an error within the Charge Point.
- [Stop Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/actions/stop-transaction): When a transaction is stopped, the Charge Point SHALL send a StopTransaction.req PDU, notifying the Central System that the transaction has stopped.
- [Trigger Message](https://ocpplab.com/docs/guides/ocpp/1-6/actions/trigger-message): During normal operation, the Charge Point informs the Central System of its state and any relevant occurrences. If there is nothing to report the Charge Point will send at least a heartbeat at a pr…
- [Unlock Connector](https://ocpplab.com/docs/guides/ocpp/1-6/actions/unlock-connector): Central System can request a Charge Point to unlock a connector. To do so, the Central System SHALL send an UnlockConnector.req PDU.
- [Update Firmware](https://ocpplab.com/docs/guides/ocpp/1-6/actions/update-firmware): Central System can notify a Charge Point that it needs to update its firmware. The Central System SHALL send an UpdateFirmware.req PDU to instruct the Charge Point to install new firmware. The PDU…
- [OCPP 1.6 Actions](https://ocpplab.com/docs/guides/ocpp/1-6/actions): Index of all 39 OCPP 1.6 messages (actions), each with a full reference page.
- [TC_001_CS — Cold Boot Charge Point](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-001-cs): Cold Boot Charge Point (TC_001_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to startup the Charge Point and let it register itself at the Central System.
- [TC_001_CSMS — Cold Boot Charge Point](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-001-csms): Cold Boot Charge Point (TC_001_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to startup the Charge Point and let it register itself at the Central System.
- [TC_002_CS — Cold Boot Charge Point - Pending](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-002-cs): Cold Boot Charge Point - Pending (TC_002_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to delay the startup for a Charge Point. For example to set the correct configurations.
- [TC_003_CS — Regular Charging Session - Plugin First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-003-cs): Regular Charging Session - Plugin First (TC_003_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a Charging session.
- [TC_003_CSMS — Regular Charging Session - Plugin First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-003-csms): Regular Charging Session - Plugin First (TC_003_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a Charging session.
- [TC_004_1_CS — Regular Charging Session – Identification First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-004-1-cs): Regular Charging Session – Identification First (TC_004_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a Charging session.
- [TC_004_1_CSMS — Regular Charging Session – Identification First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-004-1-csms): Regular Charging Session – Identification First (TC_004_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a charging session.
- [TC_004_2_CS — Regular Charging Session – Identification First - ConnectionTimeOut](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-004-2-cs): Regular Charging Session – Identification First - ConnectionTimeOut (TC_004_2_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to make a connector available when it is not used.
- [TC_004_2_CSMS — Regular Charging Session – Identification First - ConnectionTimeOut](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-004-2-csms): Regular Charging Session – Identification First - ConnectionTimeOut (TC_004_2_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to make a connector available when it is not used.
- [TC_005_1_CS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-005-1-cs): EV Side Disconnected - StopTransactionOnEVSideDisconnect = true - (TC_005_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop the transaction when the cable is disconnected at EV s…
- [TC_005_1_CSMS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-005-1-csms): EV Side Disconnected - StopTransactionOnEVSideDisconnect = true - (TC_005_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop the transaction when the cable is disconnected at EV…
- [TC_005_2_CS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-005-2-cs): EV Side Disconnected - StopTransactionOnEVSideDisconnect = true - (TC_005_2_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop the transaction when the cable is disconnected at EV s…
- [TC_005_3_CS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = false -](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-005-3-cs): EV Side Disconnected - StopTransactionOnEVSideDisconnect = false - (TC_005_3_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to keep the transaction active, even when the cable is discon…
- [TC_007_CS — Regular Start Charging Session – Cached Id](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-007-cs): Regular Start Charging Session – Cached Id (TC_007_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction with an id stored in the Authorization cache.
- [TC_007_CSMS — Regular Start Charging Session – Cached Id](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-007-csms): Regular Start Charging Session – Cached Id (TC_007_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction with an id stored in the Authorization cache.
- [TC_008_CS — Regular Start Charging Session – Id in Local Authorization List](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-008-cs): Regular Start Charging Session – Id in Local Authorization List (TC_008_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to authorize a transaction using the Local Authorization List.
- [TC_010_CS — Remote Start Charging Session – Cable Plugged in First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-010-cs): Remote Start Charging Session – Cable Plugged in First (TC_010_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction remotely.
- [TC_010_CSMS — Remote Start Charging Session – Cable Plugged in First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-010-csms): Remote Start Charging Session – Cable Plugged in First (TC_010_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction remotely.
- [TC_011_1_CS — Remote Start Charging Session – Remote Start First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-011-1-cs): Remote Start Charging Session – Remote Start First (TC_011_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction remotely.
- [TC_011_1_CSMS — Remote Start Charging Session – Remote Start First](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-011-1-csms): Remote Start Charging Session – Remote Start First (TC_011_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction remotely.
- [TC_011_2_CS — Remote Start Charging Session – Time Out](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-011-2-cs): Remote Start Charging Session – Time Out (TC_011_2_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to set a connector back to available, after receiving a RemoteStartTransaction.req and…
- [TC_011_2_CSMS — Remote Start Charging Session – Time Out](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-011-2-csms): Remote Start Charging Session – Time Out (TC_011_2_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to set a connector back to available, after receiving a RemoteStartTransaction.req an…
- [TC_012_CS — Remote Stop Charging Session](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-012-cs): Remote Stop Charging Session (TC_012_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to remotely stop a transaction.
- [TC_012_CSMS — Remote Stop Charging Session](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-012-csms): Remote Stop Charging Session (TC_012_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to remotely stop a transaction.
- [TC_013_CS — Hard Reset Without transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-013-cs): Hard Reset Without transaction (TC_013_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to hard reset a Charge Point, while no transaction is active.
- [TC_013_CSMS — Hard Reset](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-013-csms): Hard Reset (TC_013_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to hard reset a Charge Point.
- [TC_014_CS — Soft Reset Without Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-014-cs): Soft Reset Without Transaction (TC_014_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to soft reset a Charge Point, while no transaction is active.
- [TC_014_CSMS — Soft Reset](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-014-csms): Soft Reset (TC_014_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to soft reset a Charge Point.
- [TC_015_CS — Hard Reset With Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-015-cs): Hard Reset With Transaction (TC_015_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to hard reset a Charge Point, while a transaction is active.
- [TC_016_CS — Soft Reset With Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-016-cs): Soft Reset With Transaction (TC_016_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to soft reset a Charge Point, while a transaction is active.
- [TC_017_1_CS — Unlock connector - no charging session running (Not fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-017-1-cs): Unlock connector - no charging session running (Not fixed cable) (TC_017_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to unlock a connector of a Charge Point.
- [TC_017_1_CSMS — Unlock connector - no charging session running (Not fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-017-1-csms): Unlock connector - no charging session running (Not fixed cable) (TC_017_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to unlock a connector of a Charge Point.
- [TC_017_2_CS — Unlock connector - no charging session running (Fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-017-2-cs): Unlock connector - no charging session running (Fixed cable) (TC_017_2_CS) — OCPP 1.6 OCTT compliance test. This scenario describes how to Charge Point should react to an UnlockConnector.req, when…
- [TC_017_2_CSMS — Unlock connector - no charging session running (Fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-017-2-csms): Unlock connector - no charging session running (Fixed cable) (TC_017_2_CSMS) — OCPP 1.6 OCTT compliance test. This scenario describes how to Charge Point should react to an UnlockConnector.req, whe…
- [TC_018_1_CS — Unlock Connector - With Charging Session (Not fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-018-1-cs): Unlock Connector - With Charging Session (Not fixed cable) (TC_018_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to unlock a connector of a Charge Point, while a transaction is ongoing.
- [TC_018_1_CSMS — Unlock Connector - With Charging Session (Not fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-018-1-csms): Unlock Connector - With Charging Session (Not fixed cable) (TC_018_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to unlock a connector of a Charge Point, while a transaction is ong…
- [TC_018_2_CS — Unlock Connector - With Charging Session (Fixed cable)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-018-2-cs): Unlock Connector - With Charging Session (Fixed cable) (TC_018_2_CS) — OCPP 1.6 OCTT compliance test. This scenario describes how to Charge Point should react to an UnlockConnector.req, when having…
- [TC_019_1_CSMS — Retrieve all configuration keys](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-019-1-csms): Retrieve all configuration keys (TC_019_1_CSMS) — OCPP 1.6 OCTT compliance test. The Central System is able to retrieve all available configuration keys.
- [TC_019_2_CSMS — Retrieve specific configuration key](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-019-2-csms): Retrieve specific configuration key (TC_019_2_CSMS) — OCPP 1.6 OCTT compliance test. The Central System is able to retrieve a specific configuration key.
- [TC_019_CS — Retrieve configuration](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-019-cs): Retrieve configuration (TC_019_CS) — OCPP 1.6 OCTT compliance test. The Central System is able to retrieve all available or specific configuration keys.
- [TC_021_CS — Change/set Configuration](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-021-cs): Change/set Configuration (TC_021_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to set the value of a configuration key.
- [TC_021_CSMS — Change/set Configuration](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-021-csms): Change/set Configuration (TC_021_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to set the value of a configuration key.
- [TC_023_1_CSMS — Start Charging Session – Authorize invalid](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-023-1-csms): Start Charging Session – Authorize invalid (TC_023_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to inform the Charge Point that the EV Driver is not Authorized to start a transact…
- [TC_023_2_CSMS — Start Charging Session – Authorize expired](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-023-2-csms): Start Charging Session – Authorize expired (TC_023_2_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to inform the Charge Point that the EV Driver is not Authorized to start a transact…
- [TC_023_3_CSMS — Start Charging Session – Authorize blocked](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-023-3-csms): Start Charging Session – Authorize blocked (TC_023_3_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to inform the Charge Point that the EV Driver is not Authorized to start a transact…
- [TC_023_CS — Start Charging Session – Authorize invalid](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-023-cs): Start Charging Session – Authorize invalid (TC_023_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to inform the Charge Point that the EV Driver is not Authorized to start a transaction.
- [TC_024_CS — Start Charging Session - Lock Failure](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-024-cs): Start Charging Session - Lock Failure (TC_024_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to report a connector lock failure.
- [TC_024_CSMS — Start Charging Session Lock Failure](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-024-csms): Start Charging Session Lock Failure (TC_024_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to report a connector lock failure.
- [TC_026_CS — Remote Start Charging Session – Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-026-cs): Remote Start Charging Session – Rejected (TC_026_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject a RemoteStartTransaction.req, when a transaction is already ongoing on the requ…
- [TC_026_CSMS — Remote Start Charging Session – Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-026-csms): Remote Start Charging Session – Rejected (TC_026_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject a RemoteStartTransaction.req.
- [TC_027_CS — Remote start transaction - connector id shall not be 0](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-027-cs): Remote start transaction - connector id shall not be 0 (TC_027_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject a RemoteStartTransaction.req on connectorId = 0.
- [TC_028_CS — Remote Stop Transaction – Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-028-cs): Remote Stop Transaction – Rejected (TC_028_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject a RemoteStopTransaction.req, when an unknown transactionId is given.
- [TC_028_CSMS — Remote Stop Transaction – Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-028-csms): Remote Stop Transaction – Rejected (TC_028_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject a RemoteStopTransaction.req, when an unknown transactionId is given.
- [TC_030_CS — Unlock Connector – Unlock Failure](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-030-cs): Unlock Connector – Unlock Failure (TC_030_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to report a connector lock failure.
- [TC_030_CSMS — Unlock Connector – Unlock Failure](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-030-csms): Unlock Connector – Unlock Failure (TC_030_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to report a connector lock failure.
- [TC_031_CS — Unlock Connector – Unknown Connector](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-031-cs): Unlock Connector – Unknown Connector (TC_031_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject an UnlockConnector.req, when an unknown connectorId is given.
- [TC_031_CSMS — Unlock Connector – Unknown Connector](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-031-csms): Unlock Connector – Unknown Connector (TC_031_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject an UnlockConnector.req, when an unknown connectorId is given.
- [TC_032_1_CS — Power failure boot charging point - configured to stop transaction(s) before going down](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-032-1-cs): Power failure boot charging point - configured to stop transaction(s) before going down (TC_032_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop all transactions before going do…
- [TC_032_1_CSMS — Power failure boot charging point-configured to stop transaction(s)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-032-1-csms): Power failure boot charging point-configured to stop transaction(s) (TC_032_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop all transactions, when a power failure occurred.
- [TC_032_2_CS — Power failure boot charging point-configured to stop transaction(s)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-032-2-cs): Power failure boot charging point-configured to stop transaction(s) (TC_032_2_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop transaction all transactions, when a power failure o…
- [TC_034_CS — Power Failure with Unavailable Status](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-034-cs): Power Failure with Unavailable Status (TC_034_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to persist the status of the connectors, when a power failure occurs.
- [TC_036_CS — Connection Loss During Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-036-cs): Connection Loss During Transaction (TC_036_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to cache meter values, when a connection loss occurred during a transaction.
- [TC_037_1_CS — Offline Start Transaction - Valid IdTag](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-037-1-cs): Offline Start Transaction - Valid IdTag (TC_037_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction, while being offline.
- [TC_037_1_CSMS — Offline Start Transaction - Valid IdTag](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-037-1-csms): Offline Start Transaction - Valid IdTag (TC_037_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction, while being offline.
- [TC_037_2_CS — Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = false](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-037-2-cs): Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = false (TC_037_2_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction, while being offline.
- [TC_037_3_CS — Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-037-3-cs): Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true (TC_037_3_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction, while being offline.
- [TC_037_3_CSMS — Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-037-3-csms): Offline Start Transaction - Invalid IdTag - StopTransactionOnInvalidId = true (TC_037_3_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start a transaction, while being offline.
- [TC_038_CS — Offline Stop Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-038-cs): Offline Stop Transaction (TC_038_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to stop a transaction, while the Charge Point is offline.
- [TC_039_CS — Offline Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-039-cs): Offline Transaction (TC_039_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to start and stop a transaction, while the Charge Point is offline.
- [TC_039_CSMS — Offline Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-039-csms): Offline Transaction (TC_039_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to start and stop a transaction, while the Charge Point is offline.
- [TC_040_1_CS — Configuration key - NotSupported](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-040-1-cs): Configuration key - NotSupported (TC_040_1_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject an unknown configuration key.
- [TC_040_1_CSMS — Configuration keys - NotSupported](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-040-1-csms): Configuration keys - NotSupported (TC_040_1_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject an unknown configuration key.
- [TC_040_2_CS — Configuratoin key - Invalid value](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-040-2-cs): Configuratoin key - Invalid value (TC_040_2_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject setting a configuration key, when an incorrect value is given.
- [TC_040_2_CSMS — Configuration keys - Invalid value](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-040-2-csms): Configuration keys - Invalid value (TC_040_2_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to reject setting a configuration key, when an incorrect value is given.
- [TC_041_CS — Fault Behavior](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-041-cs): Fault Behavior (TC_041_CS) — OCPP 1.6 OCTT compliance test. This scenario is used to refuse starting a transaction, when the Charge Point in fault state.
- [TC_042_1_CS — Get Local List Version (not supported)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-042-1-cs): Get Local List Version (not supported) (TC_042_1_CS) — OCPP 1.6 OCTT compliance test. The Central System can request a Charge Point for the version number of the Local Authorization List.
- [TC_042_1_CSMS — Get Local List Version (not supported)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-042-1-csms): Get Local List Version (not supported) (TC_042_1_CSMS) — OCPP 1.6 OCTT compliance test. The Central System can request a Charge Point for the version number of the Local Authorization List.
- [TC_042_2_CS — Get Local List Version (empty)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-042-2-cs): Get Local List Version (empty) (TC_042_2_CS) — OCPP 1.6 OCTT compliance test. The Central System can request a Charge Point for the version number of the Local Authorization List.
- [TC_042_2_CSMS — Get Local List Version (empty)](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-042-2-csms): Get Local List Version (empty) (TC_042_2_CSMS) — OCPP 1.6 OCTT compliance test. The Central System can request a Charge Point for the version number of the Local Authorization List.
- [TC_043_1_CS — Send Local Authorization List - NotSupported](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-1-cs): Send Local Authorization List - NotSupported (TC_043_1_CS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_1_CSMS — Send Local Authorization List - NotSupported](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-1-csms): Send Local Authorization List - NotSupported (TC_043_1_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_2_CS — Send Local Authorization List - VersionMismatch](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-2-cs): Send Local Authorization List - VersionMismatch (TC_043_2_CS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_3_CS — Send Local Authorization List - Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-3-cs): Send Local Authorization List - Failed (TC_043_3_CS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_3_CSMS — Send Local Authorization List - Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-3-csms): Send Local Authorization List - Failed (TC_043_3_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_4_CSMS — Send Local Authorization List - Full](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-4-csms): Send Local Authorization List - Full (TC_043_4_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_5_CSMS — Send Local Authorization List - Differential](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-5-csms): Send Local Authorization List - Differential (TC_043_5_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_043_CS — Send Local Authorization List](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-043-cs): Send Local Authorization List (TC_043_CS) — OCPP 1.6 OCTT compliance test. The Charge Point can authorize an EV driver based on a local list that is set by the Central System.
- [TC_044_1_CS — Firmware Update - Download and Install](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-044-1-cs): Firmware Update - Download and Install (TC_044_1_CS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is updated.
- [TC_044_1_CSMS — Firmware Update - Download and Install](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-044-1-csms): Firmware Update - Download and Install (TC_044_1_CSMS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is updated.
- [TC_044_2_CS — Firmware Update - Download Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-044-2-cs): Firmware Update - Download Failed (TC_044_2_CS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is being updated, but downloading the firmware fails.
- [TC_044_2_CSMS — Firmware Update - Download Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-044-2-csms): Firmware Update - Download Failed (TC_044_2_CSMS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is being updated, but downloading the firmware fails.
- [TC_044_3_CS — Firmware Update - Installation Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-044-3-cs): Firmware Update - Installation Failed (TC_044_3_CS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is being updated, but the installation fails.
- [TC_044_3_CSMS — Firmware Update - Installation Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-044-3-csms): Firmware Update - Installation Failed (TC_044_3_CSMS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is being updated, but the installation fails.
- [TC_045_1_CS — Get Diagnostics](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-045-1-cs): Get Diagnostics (TC_045_1_CS) — OCPP 1.6 OCTT compliance test. The Charge Point uploads a diagnostics log to a specified location based on a request of the Central System.
- [TC_045_1_CSMS — Get Diagnostics](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-045-1-csms): Get Diagnostics (TC_045_1_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point uploads a diagnostics log to a specified location based on a request of the Central System.
- [TC_045_2_CS — Get Diagnostics - Upload Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-045-2-cs): Get Diagnostics - Upload Failed (TC_045_2_CS) — OCPP 1.6 OCTT compliance test. When getting the diagnostics of a Charge Point, the upload of the log fails.
- [TC_045_2_CSMS — Get Diagnostics - Upload Failed](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-045-2-csms): Get Diagnostics - Upload Failed (TC_045_2_CSMS) — OCPP 1.6 OCTT compliance test. When getting the diagnostics of a Charge Point, the upload of the log fails.
- [TC_046_1_CS — Reservation of a Connector - Local start transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-046-1-cs): Reservation of a Connector - Local start transaction (TC_046_1_CS) — OCPP 1.6 OCTT compliance test. A Connector is reserved and a charging transaction takes place.
- [TC_046_2_CS — Reservation of a Connector - Remote start transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-046-2-cs): Reservation of a Connector - Remote start transaction (TC_046_2_CS) — OCPP 1.6 OCTT compliance test. A Connector is reserved and a charging transaction takes place.
- [TC_046_CSMS — Reservation of a Connector - Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-046-csms): Reservation of a Connector - Transaction (TC_046_CSMS) — OCPP 1.6 OCTT compliance test. A Connector is reserved and a charging transaction takes place.
- [TC_047_CS — Reservation of a Connector - Expire](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-047-cs): Reservation of a Connector - Expire (TC_047_CS) — OCPP 1.6 OCTT compliance test. A Connector is reserved, a charging transaction could take place, but the reservation is not used (in time)
- [TC_047_CSMS — Reservation of a Connector - Expire](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-047-csms): Reservation of a Connector - Expire (TC_047_CSMS) — OCPP 1.6 OCTT compliance test. A Connector is reserved, a charging transaction could take place, but the reservation is not used (in time)
- [TC_048_1_CS — Reservation of a Connector - Faulted](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-1-cs): Reservation of a Connector - Faulted (TC_048_1_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Faulted i…
- [TC_048_1_CSMS — Reservation of a Connector - Faulted](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-1-csms): Reservation of a Connector - Faulted (TC_048_1_CSMS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Faulted…
- [TC_048_2_CS — Reservation of a Connector - Occupied](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-2-cs): Reservation of a Connector - Occupied (TC_048_2_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Occupied…
- [TC_048_2_CSMS — Reservation of a Connector - Occupied](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-2-csms): Reservation of a Connector - Occupied (TC_048_2_CSMS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Occupi…
- [TC_048_3_CS — Reservation of a Connector - Unavailable](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-3-cs): Reservation of a Connector - Unavailable (TC_048_3_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Unava…
- [TC_048_3_CSMS — Reservation of a Connector - Unavailable](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-3-csms): Reservation of a Connector - Unavailable (TC_048_3_CSMS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Una…
- [TC_048_4_CS — Reservation of a Connector - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-4-cs): Reservation of a Connector - Rejected (TC_048_4_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Rejected…
- [TC_048_4_CSMS — Reservation of a Connector - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-048-4-csms): Reservation of a Connector - Rejected (TC_048_4_CSMS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Connector, but the reservation is not made, instead the status Reject…
- [TC_049_CS — Reservation of a Charge Point - Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-049-cs): Reservation of a Charge Point - Transaction (TC_049_CS) — OCPP 1.6 OCTT compliance test. A Charge Point / unspecified Connector is reserved and a charging transaction takes place.
- [TC_049_CSMS — Reservation of a Charge Point - Transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-049-csms): Reservation of a Charge Point - Transaction (TC_049_CSMS) — OCPP 1.6 OCTT compliance test. A Charge Point / unspecified Connector is reserved and a charging transaction takes place.
- [TC_050_1_CS — Reservation of a Charge Point - Faulted](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-050-1-cs): Reservation of a Charge Point - Faulted (TC_050_1_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Charge Point, but the reservation is not made, instead the status Fau…
- [TC_050_2_CS — Reservation of a Charge Point - Occupied](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-050-2-cs): Reservation of a Charge Point - Occupied (TC_050_2_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Charge Point, but the reservation is not made, instead the status Oc…
- [TC_050_3_CS — Reservation of a Charge Point - Unavailable](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-050-3-cs): Reservation of a Charge Point - Unavailable (TC_050_3_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Charge Point, but the reservation is not made, instead the status…
- [TC_050_4_CS — Reservation of a Charge Point - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-050-4-cs): Reservation of a Charge Point - Rejected (TC_050_4_CS) — OCPP 1.6 OCTT compliance test. The Central System attempts to reserve a Charge Point, but the reservation is not made, instead the status Re…
- [TC_051_CS — Cancel Reservation](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-051-cs): Cancel Reservation (TC_051_CS) — OCPP 1.6 OCTT compliance test. The Central System cancels an existing, not expired reservation.
- [TC_051_CSMS — Cancel Reservation](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-051-csms): Cancel Reservation (TC_051_CSMS) — OCPP 1.6 OCTT compliance test. The Central System cancels an existing, not expired reservation.
- [TC_052_CS — Cancel Reservation - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-052-cs): Cancel Reservation - Rejected (TC_052_CS) — OCPP 1.6 OCTT compliance test. The Central System tries to cancel reservation, but this request is rejected by the Charge Point.
- [TC_052_CSMS — Cancel Reservation - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-052-csms): Cancel Reservation - Rejected (TC_052_CSMS) — OCPP 1.6 OCTT compliance test. The Central System tries to cancel reservation, but this request is rejected by the Charge Point.
- [TC_053_CS — Use a reserved Connector with parentIdTag](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-053-cs): Use a reserved Connector with parentIdTag (TC_053_CS) — OCPP 1.6 OCTT compliance test. The Charge Point has been reserved and is used with a parentIdTag
- [TC_053_CSMS — Use a reserved Connector with parentIdTag](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-053-csms): Use a reserved Connector with parentIdTag (TC_053_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point has been reserved and is used with a parentIdTag
- [TC_054_CS — Trigger Message](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-054-cs): Trigger Message (TC_054_CS) — OCPP 1.6 OCTT compliance test. The Central System triggers a message from the Charge Point
- [TC_054_CSMS — Trigger Message](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-054-csms): Trigger Message (TC_054_CSMS) — OCPP 1.6 OCTT compliance test. The Central System triggers a message from the Charge Point
- [TC_055_CS — Trigger Message - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-055-cs): Trigger Message - Rejected (TC_055_CS) — OCPP 1.6 OCTT compliance test. The Central System triggers a message from the Charge Point, but the Charge Point rejects the message.
- [TC_055_CSMS — Trigger Message - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-055-csms): Trigger Message - Rejected (TC_055_CSMS) — OCPP 1.6 OCTT compliance test. The Central System triggers a message from the Charge Point, but the Charge Point rejects the message.
- [TC_056_CS —](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-056-cs): The Central System sets a default schedule for new transactions.
- [TC_056_CSMS — Central Smart Charging - TxDefaultProfile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-056-csms): Central Smart Charging - TxDefaultProfile (TC_056_CSMS) — OCPP 1.6 OCTT compliance test. The Central System sets a default schedule for new transactions.
- [TC_057_CS —](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-057-cs): The Central System sets a schedule for a running transaction.
- [TC_057_CSMS — Central Smart Charging - TxProfile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-057-csms): Central Smart Charging - TxProfile (TC_057_CSMS) — OCPP 1.6 OCTT compliance test. The Central System sets a schedule for a running transaction.
- [TC_058_1_CS — Central Smart Charging - No ongoing transaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-058-1-cs): Central Smart Charging - No ongoing transaction (TC_058_1_CS) — OCPP 1.6 OCTT compliance test. The Central System sets a schedule for a transaction (that is not running).
- [TC_058_2_CS — Central Smart Charging - Wrong transactionId](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-058-2-cs): Central Smart Charging - Wrong transactionId (TC_058_2_CS) — OCPP 1.6 OCTT compliance test. The Central System sets a schedule for a transaction (that is not running).
- [TC_059_CS — Remote Start Transaction with Charging Profile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-059-cs): Remote Start Transaction with Charging Profile (TC_059_CS) — OCPP 1.6 OCTT compliance test. The Central System starts a transaction on a Charge Point with a ChargingProfile
- [TC_059_CSMS — Remote Start Transaction with Charging Profile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-059-csms): Remote Start Transaction with Charging Profile (TC_059_CSMS) — OCPP 1.6 OCTT compliance test. The Central System starts a transaction on a Charge Point with a ChargingProfile
- [TC_060_CS — Remote Start Transaction with Charging Profile - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-060-cs): Remote Start Transaction with Charging Profile - Rejected (TC_060_CS) — OCPP 1.6 OCTT compliance test. The Central System tries to start a transaction on a Charge Point but this is rejected.
- [TC_061_CS — Clear Authorization Data in Authorization Cache](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-061-cs): Clear Authorization Data in Authorization Cache (TC_061_CS) — OCPP 1.6 OCTT compliance test. The Central System can clear the Authorization Cache of a Charge Point.
- [TC_061_CSMS — Clear Authorization Data in Authorization Cache](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-061-csms): Clear Authorization Data in Authorization Cache (TC_061_CSMS) — OCPP 1.6 OCTT compliance test. The Central System can clear the Authorization Cache of a Charge Point.
- [TC_062_CS — Data Transfer to a Charge Point](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-062-cs): Data Transfer to a Charge Point (TC_062_CS) — OCPP 1.6 OCTT compliance test. The Central System sends a vendor specific message to a Charge Point.
- [TC_064_CSMS — Data Transfer to a Central System](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-064-csms): Data Transfer to a Central System (TC_064_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point sends a vendor specific message to the Central System.
- [TC_066_CS — Get Composite Schedule](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-066-cs): Get Composite Schedule (TC_066_CS) — OCPP 1.6 OCTT compliance test. The Central System sends 3 ChargingProfiles to a Charge Point and then requests (and validates) the composite schedule.
- [TC_066_CSMS — Get Composite Schedule](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-066-csms): Get Composite Schedule (TC_066_CSMS) — OCPP 1.6 OCTT compliance test. The Central System requests a composite schedule.
- [TC_067_CS — Clear Charging Profile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-067-cs): Clear Charging Profile (TC_067_CS) — OCPP 1.6 OCTT compliance test. The Central Systems sets charging profiles and clears it.
- [TC_067_CSMS — Clear Charging Profile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-067-csms): Clear Charging Profile (TC_067_CSMS) — OCPP 1.6 OCTT compliance test. The Central Systems sets a Charging Profile and clears it.
- [TC_068_CS — Stop transaction - IdTag in StopTransaction matches IdTag in StartTransaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-068-cs): Stop transaction - IdTag in StopTransaction matches IdTag in StartTransaction (TC_068_CS) — OCPP 1.6 OCTT compliance test. The Charge Point stops a transaction when a card is swiped with the same i…
- [TC_069_CS — Stop transaction - ParentIdTag in StopTransaction matches ParentIdTag in StartTransaction](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-069-cs): Stop transaction - ParentIdTag in StopTransaction matches ParentIdTag in StartTransaction (TC_069_CS) — OCPP 1.6 OCTT compliance test. The Charge Point stops a transaction when a card is swiped wit…
- [TC_070_CS — Sampled Meter Values](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-070-cs): Sampled Meter Values (TC_070_CS) — OCPP 1.6 OCTT compliance test. The Charge Point is able to send different kinds of Sampled MeterValues with a certain interval. What MeterValues are to be sent an…
- [TC_071_CS — Clock-aligned Meter Values](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-071-cs): Clock-aligned Meter Values (TC_071_CS) — OCPP 1.6 OCTT compliance test. The Charge Point is able to send different kinds of Clock-aligned MeterValues with a certain interval. What MeterValues are t…
- [TC_072_CS — Stacking Charging Profiles](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-072-cs): Stacking Charging Profiles (TC_072_CS) — OCPP 1.6 OCTT compliance test. The Central System sends 2 ChargingProfiles to a Charge Point and then requests (and validates) the composite schedule.
- [TC_073_CS — Update Charge Point Password for HTTP Basic Authentication](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-073-cs): Update Charge Point Password for HTTP Basic Authentication (TC_073_CS) — OCPP 1.6 OCTT compliance test. The Central System can configure a new password for HTTP Basic Authentication, the Central Sy…
- [TC_073_CSMS — Update Charge Point Password for HTTP Basic Authentication](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-073-csms): Update Charge Point Password for HTTP Basic Authentication (TC_073_CSMS) — OCPP 1.6 OCTT compliance test. The Central System can configure a new password for HTTP Basic Authentication, the Central…
- [TC_074_CS — Update Charge Point Certificate by request of Central System](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-074-cs): Update Charge Point Certificate by request of Central System (TC_074_CS) — OCPP 1.6 OCTT compliance test. The tool shall take on the role of both Central System and Certificate Authority Server. Wh…
- [TC_074_CSMS — Update Charge Point Certificate by request of Central System](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-074-csms): Update Charge Point Certificate by request of Central System (TC_074_CSMS) — OCPP 1.6 OCTT compliance test. When SUT Charge Point, the tool shall take on the role of both Central System and Certifi…
- [TC_075_1_CS — Install a certificate on the Charge Point - ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-075-1-cs): Install a certificate on the Charge Point - ManufacturerRootCertificate (TC_075_1_CS) — OCPP 1.6 OCTT compliance test. The Central System requests the Charge Point to install a new manufacturer roo…
- [TC_075_1_CSMS — Install a certificate on the Charge Point - ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-075-1-csms): Install a certificate on the Charge Point - ManufacturerRootCertificate (TC_075_1_CSMS) — OCPP 1.6 OCTT compliance test. The Central System requests the Charge Point to install a new Manufacturer r…
- [TC_075_2_CS — Install a certificate on the Charge Point - CentralSystemRootCertificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-075-2-cs): Install a certificate on the Charge Point - CentralSystemRootCertificate (TC_075_2_CS) — OCPP 1.6 OCTT compliance test. The Central System requests the Charge Point to install a new Central System…
- [TC_075_2_CSMS — Install a certificate on the Charge Point - CentralSystemRootCertificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-075-2-csms): Install a certificate on the Charge Point - CentralSystemRootCertificate (TC_075_2_CSMS) — OCPP 1.6 OCTT compliance test. The Central System requests the Charge Point to install a new Central Syste…
- [TC_076_CS — Delete a specific certificate from the Charge Point](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-076-cs): Delete a specific certificate from the Charge Point (TC_076_CS) — OCPP 1.6 OCTT compliance test. To facilitate the management of the Charge Point’s installed certificates, a method of deleting an i…
- [TC_076_CSMS — Delete a specific certificate from the Charge Point](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-076-csms): Delete a specific certificate from the Charge Point (TC_076_CSMS) — OCPP 1.6 OCTT compliance test. To facilitate the management of the Charge Point’s installed certificates, a method of deleting an…
- [TC_077_CS — Invalid ChargePointCertificate Security Event](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-077-cs): Invalid ChargePointCertificate Security Event (TC_077_CS) — OCPP 1.6 OCTT compliance test. The Charge Point notifies the Central System of an invalid certificate. The tool shall take on the role of…
- [TC_077_CSMS — Invalid ChargePointCertificate Security Event](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-077-csms): Invalid ChargePointCertificate Security Event (TC_077_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point notifies the Central System of an invalid certificate.
- [TC_078_CS — Invalid CentralSystemCertificate Security Event](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-078-cs): Invalid CentralSystemCertificate Security Event (TC_078_CS) — OCPP 1.6 OCTT compliance test. The Charge Point notifies the Central System of an invalid certificate.
- [TC_078_CSMS — Invalid CentralSystemCertificate Security Event](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-078-csms): Invalid CentralSystemCertificate Security Event (TC_078_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point notifies the Central System of an invalid certificate.
- [TC_079_CS — Get Security Log](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-079-cs): Get Security Log (TC_079_CS) — OCPP 1.6 OCTT compliance test. The Charge Point uploads a security log to a specified location based on a request of the Central System.
- [TC_079_CSMS — Get Security Log](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-079-csms): Get Security Log (TC_079_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point uploads a security log to a specified location based on a request of the Central System.
- [TC_080_CS — Secure Firmware Update](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-080-cs): Secure Firmware Update (TC_080_CS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is updated in a secure way.
- [TC_080_CSMS — Secure Firmware Update](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-080-csms): Secure Firmware Update (TC_080_CSMS) — OCPP 1.6 OCTT compliance test. The firmware of a Charge Point is updated in a secure way.
- [TC_081_CS — Secure Firmware Update - Invalid Signature](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-081-cs): Secure Firmware Update - Invalid Signature (TC_081_CS) — OCPP 1.6 OCTT compliance test. The Charge Point validates the Signature and deems it invalid.
- [TC_081_CSMS — Secure Firmware Update - Invalid Signature](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-081-csms): Secure Firmware Update - Invalid Signature (TC_081_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point validates the Signature and deems it invalid.
- [TC_082_CS —](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-082-cs): The Central System sets a default schedule for a currently ongoing transaction.
- [TC_083_CS — Upgrade security profile](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-083-cs): Upgrade security profile (TC_083_CS) — OCPP 1.6 OCTT compliance test. The Central System can upgrade the connection using a higher Security Profile, the Central System can send a new value for the…
- [TC_083_CSMS — Upgrade Charge Point Security Profile - Accepted](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-083-csms): Upgrade Charge Point Security Profile - Accepted (TC_083_CSMS) — OCPP 1.6 OCTT compliance test. The Central System can upgrade the connection using a higher Security Profile, the Central System can…
- [TC_084_CS — Downgrade security profile - Rejected](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-084-cs): Downgrade security profile - Rejected (TC_084_CS) — OCPP 1.6 OCTT compliance test. The Central System can upgrade the connection using a higher Security Profile. It is not possible to downgrade to…
- [TC_085_CS — Basic Authentication - Valid username/password combination](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-085-cs): Basic Authentication - Valid username/password combination (TC_085_CS) — OCPP 1.6 OCTT compliance test. The Charge Point uses Basic authentication to authenticate itself to the Central System, when…
- [TC_085_CSMS — Basic Authentication - Valid username/password combination](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-085-csms): Basic Authentication - Valid username/password combination (TC_085_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point uses Basic authentication to authenticate itself to the Central System, wh…
- [TC_086_CS — TLS - server-side certificate - Valid certificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-086-cs): TLS - server-side certificate - Valid certificate (TC_086_CS) — OCPP 1.6 OCTT compliance test. The Central System uses a server-side certificate to identify itself to the Charge Point, when using s…
- [TC_086_CSMS — TLS - server-side certificate - Valid certificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-086-csms): TLS - server-side certificate - Valid certificate (TC_086_CSMS) — OCPP 1.6 OCTT compliance test. The Central System uses a server-side certificate to identify itself to the Charge Point, when using…
- [TC_087_CS — TLS - Client-side certificate - valid certificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-087-cs): TLS - Client-side certificate - valid certificate (TC_087_CS) — OCPP 1.6 OCTT compliance test. The Charge Point uses a client-side certificate to identify itself to the Central System, when using s…
- [TC_087_CSMS — TLS - Client-side certificate - valid certificate](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases/tc-087-csms): TLS - Client-side certificate - valid certificate (TC_087_CSMS) — OCPP 1.6 OCTT compliance test. The Charge Point uses a client-side certificate to identify itself to the Central System, when using…
- [OCPP 1.6 Test Cases](https://ocpplab.com/docs/guides/ocpp/1-6/test-cases): Index of all 178 OCPP 1.6 OCTT compliance test cases (102 Charge Point + 76 CSMS).
- [OCPP 1.6](https://ocpplab.com/docs/guides/ocpp/1-6): Simulating OCPP 1.6 chargers — core messages, transaction flow, and the configuration keys that matter for testing.
- [Authorize](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/authorize): The Charging Station sends AuthorizeRequest to the CSMS to obtain authorization for an idToken before starting (or stopping) a transaction. OCPP 2.0.1 also supports authorization of EV Contract Cer…
- [Boot Notification](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/boot-notification): After (re)boot, the Charging Station sends BootNotificationRequest to the CSMS containing the boot reason and Charging Station identification (vendor, model, serial, firmware, modem, …).
- [Cancel Reservation](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/cancel-reservation): The CSMS sends CancelReservationRequest to cancel an active reservation on the Charging Station. The CS replies with status Accepted if a reservation matching reservationId exists; otherwise Rejected.
- [Certificate Signed](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/certificate-signed): The CSMS sends CertificateSignedRequest to deliver a signed PEM-encoded X.509 certificate (with sub-CA chain when applicable) to the Charging Station. The certificate is the result of the CSR previ…
- [Change Availability](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/change-availability): The CSMS sends ChangeAvailabilityRequest to set the operational status of either the whole Charging Station (when evse is omitted) or a specific EVSE/connector (when evse is provided) to Operative…
- [Clear Cache](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/clear-cache): The CSMS sends ClearCacheRequest to ask the Charging Station to clear its Authorization Cache. The CS replies with Accepted if it executed the request, otherwise Rejected.
- [Clear Charging Profile](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/clear-charging-profile): The CSMS sends ClearChargingProfileRequest to remove either a specific charging profile (by chargingProfileId) or a selection of profiles matching evseId, stackLevel, and/or chargingProfilePurpose.
- [Clear Display Message](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/clear-display-message): The CSMS sends ClearDisplayMessageRequest to ask the Charging Station to remove a previously-configured display message identified by id.
- [Clear Variable Monitoring](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/clear-variable-monitoring): The CSMS sends ClearVariableMonitoringRequest to remove one or more variable monitors, identified by their monitor id. The CS replies with one ClearMonitoringResultType per requested id.
- [Cleared Charging Limit](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/cleared-charging-limit): The Charging Station sends ClearedChargingLimitRequest to inform the CSMS that an externally-set charging limit (e.g. from EMS, SO/DSO, or local controller) has been cleared/released, so the CS is…
- [Cost Updated](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/cost-updated): The CSMS sends CostUpdatedRequest to push the current running total cost of an ongoing transaction to the Charging Station. The CS uses this value to update its display for the EV driver.
- [Customer Information](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/customer-information): The CSMS sends CustomerInformationRequest to:
- [Data Transfer (Charging Station → CSMS)](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/data-transfer): When the Charging Station needs to send vendor-specific information to the CSMS for functionality not covered by OCPP, it uses DataTransferRequest. The vendorId identifies the vendor-specific imple…
- [Delete Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/delete-certificate): The CSMS sends DeleteCertificateRequest to remove a specific installed certificate from the Charging Station. The target certificate is identified by its hash data (CertificateHashDataType).
- [OCPP 2.0.1 Part 2 — Errata v2.0](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/errata): OCPP 2.0.1 OCPP 2.0.1 Part 2 — Errata v2.0 message reference.
- [Firmware Status Notification](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/firmware-status-notification): The Charging Station sends FirmwareStatusNotificationRequest to inform the CSMS about the progress of a firmware update started by UpdateFirmwareRequest (L01: signed firmware; L02: legacy non-signe…
- [Get Base Report](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-base-report): The CSMS sends GetBaseReportRequest to ask the Charging Station for a base Device Model report — typically ConfigurationInventory (writable variables), FullInventory (everything), SummaryInventory…
- [Get Certificate Status](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-certificate-status): The Charging Station sends GetCertificateStatusRequest to ask the CSMS for the OCSP status of an ISO 15118 / V2G-related certificate. This is typically used during EV authorization with contract ce…
- [Get Charging Profiles](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-charging-profiles): The CSMS sends GetChargingProfilesRequest to ask the Charging Station to report the charging profiles it currently has installed. The CS responds with GetChargingProfilesResponse(status) and then d…
- [Get Composite Schedule](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-composite-schedule): The CSMS sends GetCompositeScheduleRequest to ask the Charging Station for the composite schedule that results from combining all currently active charging profiles, local limits, and (where applic…
- [Get Display Messages](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-display-messages): The CSMS sends GetDisplayMessagesRequest to ask the Charging Station to report its currently-configured display messages. Filters by id, priority, and state narrow the result. The actual message da…
- [Get Installed Certificate Ids](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-installed-certificate-ids): The CSMS sends GetInstalledCertificateIdsRequest to ask the Charging Station for an overview of installed certificates. Multiple certificate types can be requested in a single message; when certifi…
- [Get Local List Version](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-local-list-version): The CSMS sends GetLocalListVersionRequest to retrieve the current version number of the Charging Station's Local Authorization List.
- [Get Log](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-log): The CSMS sends GetLogRequest to ask the Charging Station to upload a log file (security or diagnostics) to a remote location. The CS responds with GetLogResponse(status, filename?) and then sends p…
- [Get Monitoring Report](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-monitoring-report): The CSMS sends GetMonitoringReportRequest to ask the Charging Station to report which monitors are currently configured for given components / variables. Filtering is by monitoringCriteria (up to 3…
- [Get Report](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-report): The CSMS sends GetReportRequest to ask the Charging Station for a custom Device Model report — narrower than GetBaseReport. Filtering is by componentCriteria (up to 4) and/or by an explicit list of…
- [Get Transaction Status](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-transaction-status): The CSMS sends GetTransactionStatusRequest to ask the Charging Station whether transaction-related messages are still queued for delivery. When transactionId is provided, only messages for that spe…
- [Get Variables](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get-variables): The CSMS sends GetVariablesRequest to read one or more Device Model Variables synchronously. The response contains the result for each requested variable: actual/target/min/max value, attribute typ…
- [Get 15118 EV Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/get15118-ev-certificate): When an ISO 15118 vehicle selects the CertificateInstallation (M01) or CertificateUpdate (M02) service, the Charging Station forwards the EV's CertificateInstallationReq to the CSMS encapsulated in…
- [Heartbeat](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/heartbeat): This use case describes a way to let the CSMS know the Charging Station is still connected: a Charging Station sends a heartbeat after a configurable time interval. Depending on the configuration…
- [Install Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/install-certificate): The CSMS sends InstallCertificateRequest to install a root/CA certificate (V2G, MO, CSMS, or Manufacturer root) into the Charging Station's trust store.
- [Log Status Notification](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/log-status-notification): The Charging Station sends LogStatusNotificationRequest to inform the CSMS about the progress of a log file upload that was started by GetLogRequest. The CS sends one or more notifications during t…
- [Meter Values](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/meter-values): The Charging Station sends MeterValuesRequest to deliver one or more sampled meter readings not related to a transaction. For meter values inside a transaction, the CS uses TransactionEvent instead…
- [Notify Charging Limit](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-charging-limit): The Charging Station sends NotifyChargingLimitRequest to communicate to the CSMS a charging limit that was set by an external system (e.g. EMS, SO/DSO, Local Controller) — not by the CSMS via SetCh…
- [Notify Customer Information](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-customer-information): After the CSMS sends CustomerInformationRequest (with report = true), the Charging Station replies with one or more NotifyCustomerInformationRequest messages containing the requested customer data…
- [Notify Display Messages](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-display-messages): After the CSMS sends GetDisplayMessagesRequest, the Charging Station replies with one or more NotifyDisplayMessagesRequest messages containing the matching display messages. The report can be split…
- [Notify EV Charging Needs](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-ev-charging-needs): When an EV connects via ISO 15118 and communicates its charging needs, the Charging Station forwards those needs to the CSMS using NotifyEVChargingNeedsRequest. This enables Central Smart Charging…
- [Notify EV Charging Schedule](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-ev-charging-schedule): When the EV (via ISO 15118) calculates its own charging schedule and provides it to the Charging Station, the CS forwards that schedule to the CSMS via NotifyEVChargingScheduleRequest. This is typi…
- [Notify Event](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-event): The Charging Station sends NotifyEventRequest to deliver Device Management monitoring events to the CSMS. Each event corresponds to a Component / Variable / VariableMonitoring triple where a config…
- [Notify Monitoring Report](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-monitoring-report): After the CSMS sends GetMonitoringReportRequest, the Charging Station replies with one or more NotifyMonitoringReportRequest messages containing the requested monitor configurations. Long reports a…
- [Notify Report](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/notify-report): After the CSMS sends GetBaseReportRequest or GetReportRequest, the Charging Station delivers the resulting Device Model report as a sequence of NotifyReportRequest messages. Each carries a chunk of…
- [OCPP-J — JSON over WebSockets](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/ocpp-j): OCPP 2.0.1 OCPP-J — JSON over WebSockets message reference.
- [Publish Firmware Status Notification](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/publish-firmware-status-notification): When a Local Controller has been asked to publish a firmware file (via PublishFirmwareRequest, used in setups with a Local Controller acting as firmware mirror for downstream Charging Stations), it…
- [Publish Firmware](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/publish-firmware): The CSMS sends PublishFirmwareRequest to a Local Controller (acting as Charging Station in the OCPP topology) instructing it to download a firmware file from a URI and republish it locally — so dow…
- [Report Charging Profiles](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/report-charging-profiles): After the CSMS sends GetChargingProfilesRequest, the Charging Station reports the matching installed charging profiles using one or more ReportChargingProfilesRequest messages. The report can be sp…
- [Request Start Transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/request-start-transaction): The CSMS sends RequestStartTransactionRequest to ask the Charging Station to start a transaction. OCPP 2.0.1 replaces the OCPP 1.6 RemoteStartTransaction with this message and adds:
- [Request Stop Transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/request-stop-transaction): The CSMS sends RequestStopTransactionRequest to ask the Charging Station to stop an ongoing transaction. The CS replies with Accepted/Rejected and, if accepted, drives the transaction to a normal s…
- [Reservation Status Update](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/reservation-status-update): The Charging Station sends ReservationStatusUpdateRequest to inform the CSMS that a previously-made reservation has ended without being used (either because it expired, or because it became unusabl…
- [Reserve Now](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/reserve-now): The CSMS sends ReserveNowRequest to ask the Charging Station to reserve an EVSE (or any EVSE matching connectorType) for a specific idToken until expiryDateTime.
- [Reset](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/reset): The CSMS sends ResetRequest to ask the Charging Station (or a specific EVSE) to perform a reset. OCPP 2.0.1 changes the reset semantics from Soft/Hard to Immediate vs OnIdle:
- [Security Event Notification](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/security-event-notification): The Charging Station sends SecurityEventNotificationRequest to inform the CSMS of a security-related event. The CSMS acknowledges with SecurityEventNotificationResponse (no body).
- [Send Local List](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/send-local-list): The CSMS sends SendLocalListRequest to update the Charging Station's Local Authorization List. The update may be Full (replace) or Differential (apply changes).
- [Set Charging Profile](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-charging-profile): The CSMS sends SetChargingProfileRequest to install a charging profile on the Charging Station. The profile applies to a specific EVSE — evseId = 0 carries an overall limit for the whole Charging S…
- [Set Display Message](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-display-message): The CSMS sends SetDisplayMessageRequest to configure a display message on the Charging Station — either a generic message (O01), a message tied to a specific transaction (O02), or a replacement of…
- [Set Monitoring Base](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-monitoring-base): The CSMS sends SetMonitoringBaseRequest to set the base monitoring configuration on the Charging Station — i.e. which set of monitors is active by default (All, FactoryDefault, or HardWiredOnly).
- [Set Monitoring Level](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-monitoring-level): The CSMS sends SetMonitoringLevelRequest to configure the severity threshold below which the Charging Station reports monitoring events. Only events with severity ≤ severity are sent.
- [Set Network Profile](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-network-profile): The CSMS sends SetNetworkProfileRequest to configure or update a network connection profile in a specific configuration slot on the Charging Station. The profile contains the CSMS URL, OCPP version…
- [Set Variable Monitoring](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-variable-monitoring): The CSMS sends SetVariableMonitoringRequest to install one or more monitors on Device Model variables. Each monitor specifies the threshold/delta value, a type (UpperThreshold, LowerThreshold, Delt…
- [Set Variables](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/set-variables): The CSMS sends SetVariablesRequest to write one or more Device Model variable attributes synchronously. The Charging Station returns one SetVariableResultType per variable, indicating success/failu…
- [Sign Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/sign-certificate): The Charging Station sends SignCertificateRequest to ask the CSMS (and ultimately the Certificate Authority) to sign its public key into a certificate. The public key is delivered as a Certificate…
- [Status Notification](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/status-notification): The Charging Station sends StatusNotificationRequest to inform the CSMS about a change of connector status (Available, Occupied, Reserved, Unavailable, Faulted).
- [Transaction Event](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/transaction-event): TransactionEventRequest is the single message used in OCPP 2.0.1 to report the entire lifecycle of a transaction — replacing OCPP 1.6's StartTransaction, StopTransaction, and transaction-related Me…
- [Trigger Message](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/trigger-message): The CSMS sends TriggerMessageRequest to ask the Charging Station to send a CS-initiated message on demand — typically used when the CSMS suspects its view of the CS state is stale (e.g. firmware up…
- [Unlock Connector](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/unlock-connector): The CSMS sends UnlockConnectorRequest to ask the Charging Station to unlock a specific connector. Used to help an EV driver whose cable retention has malfunctioned. If a transaction is in progress…
- [Unpublish Firmware](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/unpublish-firmware): The CSMS sends UnpublishFirmwareRequest to a Local Controller (acting as Charging Station in the OCPP topology) to remove a previously-published firmware file. The file is identified by its MD5 che…
- [Update Firmware](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions/update-firmware): The CSMS sends UpdateFirmwareRequest to instruct the Charging Station to download and install new firmware. OCPP 2.0.1 unifies the OCPP 1.6 UpdateFirmware and SignedUpdateFirmware into a single mes…
- [OCPP 2.0.1 Actions](https://ocpplab.com/docs/guides/ocpp/2-0-1/actions): Index of all 66 OCPP 2.0.1 messages (actions), each with a full reference page.
- [TC_A_01_CS — Basic Authentication - Valid username/password combination](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-01-cs): Basic Authentication - Valid username/password combination (TC_A_01_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses Basic authentication to authenticate itself to the CSMS, when us…
- [TC_A_01_CSMS — Basic Authentication - Valid username/password combination](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-01-csms): Basic Authentication - Valid username/password combination (TC_A_01_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses Basic authentication to authenticate itself to the CSMS, when…
- [TC_A_02_CSMS — Basic Authentication - Username does not equal ChargingStationId](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-02-csms): Basic Authentication - Username does not equal ChargingStationId (TC_A_02_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses Basic authentication to authenticate itself to the CSMS…
- [TC_A_03_CSMS — Basic Authentication - Invalid password](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-03-csms): Basic Authentication - Invalid password (TC_A_03_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses Basic authentication to authenticate itself to the CSMS, when using security prof…
- [TC_A_04_CS — TLS - server-side certificate - Valid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-04-cs): TLS - server-side certificate - Valid certificate (TC_A_04_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS uses a server-side certificate to identify itself to the Charging Station, when using secu…
- [TC_A_04_CSMS — TLS - server-side certificate - Valid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-04-csms): TLS - server-side certificate - Valid certificate (TC_A_04_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS uses a server-side certificate to identify itself to the Charging Station, when using se…
- [TC_A_05_CS — TLS - server-side certificate - Invalid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-05-cs): TLS - server-side certificate - Invalid certificate (TC_A_05_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS uses a server-side certificate to identify itself to the Charging Station, when using se…
- [TC_A_06_CS — TLS - server-side certificate - TLS version too low](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-06-cs): TLS - server-side certificate - TLS version too low (TC_A_06_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS uses a server-side certificate to identify itself to the Charging Station, when using se…
- [TC_A_06_CSMS — TLS - server-side certificate - TLS version too low](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-06-csms): TLS - server-side certificate - TLS version too low (TC_A_06_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS uses a server-side certificate to identify itself to the Charging Station, when using…
- [TC_A_07_CS — TLS - Client-side certificate - valid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-07-cs): TLS - Client-side certificate - valid certificate (TC_A_07_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses a client-side certificate to identify itself to the CSMS, when using secu…
- [TC_A_07_CSMS — TLS - Client-side certificate - valid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-07-csms): TLS - Client-side certificate - valid certificate (TC_A_07_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses a client-side certificate to identify itself to the CSMS, when using se…
- [TC_A_08_CSMS — TLS - Client-side certificate - Invalid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-08-csms): TLS - Client-side certificate - Invalid certificate (TC_A_08_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station uses a client-side certificate to identify itself to the CSMS, when using…
- [TC_A_09_CS — Update Charging Station Password for HTTP Basic Authentication - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-09-cs): Update Charging Station Password for HTTP Basic Authentication - Accepted (TC_A_09_CS) — OCPP 2.0.1 OCTT compliance test. This test case defines how to use the BasicAuthPassword, the password used…
- [TC_A_09_CSMS — Update Charging Station Password for HTTP Basic Authentication - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-09-csms): Update Charging Station Password for HTTP Basic Authentication - Accepted (TC_A_09_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case defines how to use the BasicAuthPassword, the password use…
- [TC_A_10_CS — Update Charging Station Password for HTTP Basic Authentication - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-10-cs): Update Charging Station Password for HTTP Basic Authentication - Rejected (TC_A_10_CS) — OCPP 2.0.1 OCTT compliance test. This test case defines how to use the BasicAuthPassword, the password used…
- [TC_A_10_CSMS — Update Charging Station Password for HTTP Basic Authentication - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-10-csms): Update Charging Station Password for HTTP Basic Authentication - Rejected (TC_A_10_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case defines how to use the BasicAuthPassword, the password use…
- [TC_A_11_CS — Update Charging Station Certificate by request of CSMS - Success - Charging Station Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-11-cs): Update Charging Station Certificate by request of CSMS - Success - Charging Station Certificate (TC_A_11_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to u…
- [TC_A_11_CSMS — Update Charging Station Certificate by request of CSMS - Success - Charging Station Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-11-csms): Update Charging Station Certificate by request of CSMS - Success - Charging Station Certificate (TC_A_11_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to…
- [TC_A_14_CS — Update Charging Station Certificate by request of CSMS - Invalid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-14-cs): Update Charging Station Certificate by request of CSMS - Invalid certificate (TC_A_14_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to update its charging…
- [TC_A_14_CSMS — Update Charging Station Certificate by request of CSMS - Invalid certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-14-csms): Update Charging Station Certificate by request of CSMS - Invalid certificate (TC_A_14_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to update its chargin…
- [TC_A_15_CS — Update Charging Station Certificate by request of CSMS - SignCertificateRequest Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-15-cs): Update Charging Station Certificate by request of CSMS - SignCertificateRequest Rejected (TC_A_15_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to update i…
- [TC_A_19_CS — Upgrade Charging Station Security Profile - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-19-cs): Upgrade Charging Station Security Profile - Accepted (TC_A_19_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station, to increase the security profil…
- [TC_A_19_CSMS — Upgrade Charging Station Security Profile - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-19-csms): Upgrade Charging Station Security Profile - Accepted (TC_A_19_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station, to increase the security prof…
- [TC_A_20_CS — Upgrade Charging Station Security Profile - No valid CSMSRootCertificate installed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-20-cs): Upgrade Charging Station Security Profile - No valid CSMSRootCertificate installed (TC_A_20_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to change the connectionData at the Charging Stat…
- [TC_A_21_CS — Upgrade Charging Station Security Profile - No valid ChargingStationCertificate installed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-21-cs): Upgrade Charging Station Security Profile - No valid ChargingStationCertificate installed (TC_A_21_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to change the connectionData at the Chargi…
- [TC_A_22_CS — Upgrade Charging Station Security Profile - Downgrade security profile - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-22-cs): Upgrade Charging Station Security Profile - Downgrade security profile - Rejected (TC_A_22_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to change the connectionData at the Charging Stati…
- [TC_A_23_CS — Update Charging Station Certificate by request of CSMS - CertificateSignedRequest Timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-a-23-cs): Update Charging Station Certificate by request of CSMS - CertificateSignedRequest Timeout (TC_A_23_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to update…
- [TC_B_01_CS — Cold Boot Charging Station - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-01-cs): Cold Boot Charging Station - Accepted (TC_B_01_CS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information about the Charging Station…
- [TC_B_01_CSMS — Cold Boot Charging Station - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-01-csms): Cold Boot Charging Station - Accepted (TC_B_01_CSMS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information about the Charging Statio…
- [TC_B_02_CS — Cold Boot Charging Station - Pending](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-02-cs): Cold Boot Charging Station - Pending (TC_B_02_CS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information about the Charging Station t…
- [TC_B_02_CSMS — Cold Boot Charging Station - Pending](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-02-csms): Cold Boot Charging Station - Pending (TC_B_02_CSMS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information about the Charging Station…
- [TC_B_03_CS — Cold Boot Charging Station - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-03-cs): Cold Boot Charging Station - Rejected (TC_B_03_CS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information about the Charging Station…
- [TC_B_06_CS — Get Variables - single value](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-06-cs): Get Variables - single value (TC_B_06_CS) — OCPP 2.0.1 OCTT compliance test. Get the value of one of the required variables of OCPPCommCtrlr
- [TC_B_06_CSMS — Get Variables - single value](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-06-csms): Get Variables - single value (TC_B_06_CSMS) — OCPP 2.0.1 OCTT compliance test. Get the value of two of the required variables of OCPPCommCtrlr
- [TC_B_07_CS — Get Variables - multiple values](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-07-cs): Get Variables - multiple values (TC_B_07_CS) — OCPP 2.0.1 OCTT compliance test. Get the value of two required variables
- [TC_B_07_CSMS — Get Variables - multiple values](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-07-csms): Get Variables - multiple values (TC_B_07_CSMS) — OCPP 2.0.1 OCTT compliance test. Get the value of two of the required variables of OCPPCommCtrlr
- [TC_B_08_CS — Get Variables - limit to maximum number of values](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-08-cs): Get Variables - limit to maximum number of values (TC_B_08_CS) — OCPP 2.0.1 OCTT compliance test. Do not return more variables than supported by MaxItemsPerMessageGetVariables.
- [TC_B_09_CS — Set Variables - single value](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-09-cs): Set Variables - single value (TC_B_09_CS) — OCPP 2.0.1 OCTT compliance test. Set the value of one of the required variables of OCPPCommCtrlr
- [TC_B_09_CSMS — Set Variables - single value](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-09-csms): Set Variables - single value (TC_B_09_CSMS) — OCPP 2.0.1 OCTT compliance test. Set the value of one of the required variables of OCPPCommCtrlr
- [TC_B_10_CS — Set Variables - multiple values](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-10-cs): Set Variables - multiple values (TC_B_10_CS) — OCPP 2.0.1 OCTT compliance test. Set the value of two required variables
- [TC_B_10_CSMS — Set Variables - multiple values](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-10-csms): Set Variables - multiple values (TC_B_10_CSMS) — OCPP 2.0.1 OCTT compliance test. Set the value of two of the required variables of OCPPCommCtrlr
- [TC_B_11_CS — Set Variables - invalidly formatted values](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-11-cs): Set Variables - invalidly formatted values (TC_B_11_CS) — OCPP 2.0.1 OCTT compliance test. Set the value of two of the required variables of OCPPCommCtrlr
- [TC_B_12_CS — Get Base Report - ConfigurationInventory](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-12-cs): Get Base Report - ConfigurationInventory (TC_B_12_CS) — OCPP 2.0.1 OCTT compliance test. CSMS requests a ConfigurationInventory base report.
- [TC_B_12_CSMS — Get Base Report - ConfigurationInventory](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-12-csms): Get Base Report - ConfigurationInventory (TC_B_12_CSMS) — OCPP 2.0.1 OCTT compliance test. CSMS requests a ConfigurationInventory base report.
- [TC_B_13_CS — Get Base Report - FullInventory](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-13-cs): Get Base Report - FullInventory (TC_B_13_CS) — OCPP 2.0.1 OCTT compliance test. CSMS requests a FullInventory base report.
- [TC_B_13_CSMS — Get Base Report - FullInventory](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-13-csms): Get Base Report - FullInventory (TC_B_13_CSMS) — OCPP 2.0.1 OCTT compliance test. CSMS requests a FullInventory base report.
- [TC_B_15_CS — Get Base Report - Not Supported base report](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-15-cs): Get Base Report - Not Supported base report (TC_B_15_CS) — OCPP 2.0.1 OCTT compliance test. CSMS requests a base report that is not supported.
- [TC_B_20_CS — Reset Charging Station - Without ongoing transaction - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-20-cs): Reset Charging Station - Without ongoing transaction - OnIdle (TC_B_20_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset itself by…
- [TC_B_20_CSMS — Reset Charging Station - Without ongoing transaction - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-20-csms): Reset Charging Station - Without ongoing transaction - OnIdle (TC_B_20_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset itself b…
- [TC_B_21_CS — Reset Charging Station - With Ongoing Transaction - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-21-cs): Reset Charging Station - With Ongoing Transaction - OnIdle (TC_B_21_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset itse…
- [TC_B_21_CSMS — Reset Charging Station - With Ongoing Transaction - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-21-csms): Reset Charging Station - With Ongoing Transaction - OnIdle (TC_B_21_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset it…
- [TC_B_22_CS — Reset Charging Station - With Ongoing Transaction - Immediate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-22-cs): Reset Charging Station - With Ongoing Transaction - Immediate (TC_B_22_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset i…
- [TC_B_22_CSMS — Reset Charging Station - With Ongoing Transaction - Immediate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-22-csms): Reset Charging Station - With Ongoing Transaction - Immediate (TC_B_22_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset…
- [TC_B_23_CS — Reset Charging Station - Unavailable persists reset](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-23-cs): Reset Charging Station - Unavailable persists reset (TC_B_23_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset itself by sending a…
- [TC_B_25_CS — Reset EVSE - Without ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-25-cs): Reset EVSE - Without ongoing transaction (TC_B_25_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset an EVSE by sending a ResetReque…
- [TC_B_25_CSMS — Reset EVSE - Without ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-25-csms): Reset EVSE - Without ongoing transaction (TC_B_25_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset an EVSE by sending a ResetReq…
- [TC_B_26_CS — Reset EVSE - With Ongoing Transaction - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-26-cs): Reset EVSE - With Ongoing Transaction - OnIdle (TC_B_26_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset an EVSE by sendi…
- [TC_B_26_CSMS — Reset EVSE - With Ongoing Transaction - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-26-csms): Reset EVSE - With Ongoing Transaction - OnIdle (TC_B_26_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset an EVSE by sen…
- [TC_B_27_CS — Reset EVSE - With Ongoing Transaction - Immediate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-27-cs): Reset EVSE - With Ongoing Transaction - Immediate (TC_B_27_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset an EVSE by se…
- [TC_B_27_CSMS — Reset EVSE - With Ongoing Transaction - Immediate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-27-csms): Reset EVSE - With Ongoing Transaction - Immediate (TC_B_27_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to reset an EVSE by…
- [TC_B_28_CS — Reset EVSE - Not Supported](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-28-cs): Reset EVSE - Not Supported (TC_B_28_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset an EVSE by sending a ResetRequest while it is…
- [TC_B_29_CS — Reset EVSE - With ongoing transaction - Not Supported](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-29-cs): Reset EVSE - With ongoing transaction - Not Supported (TC_B_29_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can request the Charging Station to reset an EVSE by sending…
- [TC_B_30_CS — Cold Boot Charging Station - Pending/Rejected - SecurityError](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-30-cs): Cold Boot Charging Station - Pending/Rejected - SecurityError (TC_B_30_CS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information abo…
- [TC_B_30_CSMS — Cold Boot Charging Station - Pending/Rejected - SecurityError](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-30-csms): Cold Boot Charging Station - Pending/Rejected - SecurityError (TC_B_30_CSMS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information a…
- [TC_B_31_CSMS — Cold Boot Charging Station - Pending/Rejected - TriggerMessage](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-31-csms): Cold Boot Charging Station - Pending/Rejected - TriggerMessage (TC_B_31_CSMS) — OCPP 2.0.1 OCTT compliance test. The booting mechanism allows a Charging Station to provide some general information…
- [TC_B_32_CS — Get Variables - Unknown component](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-32-cs): Get Variables - Unknown component (TC_B_32_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a GetVariablesRequest to retrieve values from device model variables at the Charging Station.
- [TC_B_33_CS — Get Variables - Unknown variable](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-33-cs): Get Variables - Unknown variable (TC_B_33_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a GetVariablesRequest to retrieve values from device model variables at the Charging Station.
- [TC_B_34_CS — Get Variables - Not supported attribute type](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-34-cs): Get Variables - Not supported attribute type (TC_B_34_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a GetVariablesRequest to retrieve values from device model variables at the Charging St…
- [TC_B_35_CS — Set Variables - Unknown component](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-35-cs): Set Variables - Unknown component (TC_B_35_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a SetVariablesRequest to set values from device model variables at the Charging Station.
- [TC_B_36_CS — Set Variables - Unknown variable](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-36-cs): Set Variables - Unknown variable (TC_B_36_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a SetVariablesRequest to set values from device model variables at the Charging Station.
- [TC_B_37_CS — Set Variables - Not supported attribute type](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-37-cs): Set Variables - Not supported attribute type (TC_B_37_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a SetVariablesRequest to set values from device model variables at the Charging Station.
- [TC_B_39_CS — Set Variables - Read-only](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-39-cs): Set Variables - Read-only (TC_B_39_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can use a SetVariablesRequest to set values from device model variables at the Charging Station.
- [TC_B_41_CS — Reset Charging Station - With multiple ongoing transactions - OnIdle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-41-cs): Reset Charging Station - With multiple ongoing transactions - OnIdle (TC_B_41_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS can remotely request the Charging Station to…
- [TC_B_42_CSMS — Set new NetworkConnectionProfile - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-42-csms): Set new NetworkConnectionProfile - Accepted (TC_B_42_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station. For instance in preparation of a migra…
- [TC_B_43_CS — Set new NetworkConnectionProfile - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-43-cs): Set new NetworkConnectionProfile - Rejected (TC_B_43_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station. For instance in preparation of a migrati…
- [TC_B_44_CSMS — Set new NetworkConnectionProfile - Failed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-44-csms): Set new NetworkConnectionProfile - Failed (TC_B_44_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station. For instance in preparation of a migrati…
- [TC_B_45_CS — Migrate to new ConnectionProfile - Success - Same CSMS Root](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-45-cs): Migrate to new ConnectionProfile - Success - Same CSMS Root (TC_B_45_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station. For instance in preparat…
- [TC_B_46_CS — Migrate to new ConnectionProfile - Fallback mechanism - Same CSMS Root](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-46-cs): Migrate to new ConnectionProfile - Fallback mechanism - Same CSMS Root (TC_B_46_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station. For instance…
- [TC_B_47_CS — Migrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-47-cs): Migrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per (TC_B_47_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Statio…
- [TC_B_49_CS — Migrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-49-cs): Migrate to new ConnectionProfile - Fallback after NetworkProfileConnectionAttempts per (TC_B_49_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Statio…
- [TC_B_50_CS — Migrate to new ConnectionProfile - Success - New CSMS Root - New CSMS](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-50-cs): Migrate to new ConnectionProfile - Success - New CSMS Root - New CSMS (TC_B_50_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS updates the connection details on the Charging Station. For instance i…
- [TC_B_51_CS — Status change during offline period - > Offline Threshold](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-51-cs): Status change during offline period - > Offline Threshold (TC_B_51_CS) — OCPP 2.0.1 OCTT compliance test. A Charging Station sends a notification to the CSMS to inform the CSMS about a Connector st…
- [TC_B_52_CS — Status change during offline period - < Offline Threshold](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-52-cs): Status change during offline period - < Offline Threshold (TC_B_52_CS) — OCPP 2.0.1 OCTT compliance test. A Charging Station sends a notification to the CSMS to inform the CSMS about a Connector st…
- [TC_B_53_CS — Get Base Report - Test mandatory DM variables via FullInventory](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-53-cs): Get Base Report - Test mandatory DM variables via FullInventory (TC_B_53_CS) — OCPP 2.0.1 OCTT compliance test. CSMS requests a FullInventory base report.
- [TC_B_57_CS — Network Reconnection - After connection loss](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-b-57-cs): Network Reconnection - After connection loss (TC_B_57_CS) — OCPP 2.0.1 OCTT compliance test. When the connection is lost, the Charging Station SHALL try to reconnect. When reconnecting, the Chargin…
- [TC_C_02_CS — Local start transaction - Authorization Invalid/Unknown](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-02-cs): Local start transaction - Authorization Invalid/Unknown (TC_C_02_CS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at t…
- [TC_C_02_CSMS — Local start transaction - Authorization Invalid/Unknown](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-02-csms): Local start transaction - Authorization Invalid/Unknown (TC_C_02_CSMS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at…
- [TC_C_04_CS — Local Stop Transaction - Different idToken](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-04-cs): Local Stop Transaction - Different idToken (TC_C_04_CS) — OCPP 2.0.1 OCTT compliance test. The EV Driver is able to stop an ongoing transaction, by locally presenting his IdToken.
- [TC_C_05_CS — Local start transaction - Authorization invalid - Cable lock](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-05-cs): Local start transaction - Authorization invalid - Cable lock (TC_C_05_CS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first…
- [TC_C_06_CS — Local start transaction - Authorization Blocked](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-06-cs): Local start transaction - Authorization Blocked (TC_C_06_CS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at the CSMS…
- [TC_C_06_CSMS — Local start transaction - Authorization Blocked](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-06-csms): Local start transaction - Authorization Blocked (TC_C_06_CSMS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at the CSM…
- [TC_C_07_CS — Local start transaction - Authorization Expired](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-07-cs): Local start transaction - Authorization Expired (TC_C_07_CS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at the CSMS…
- [TC_C_07_CSMS — Local start transaction - Authorization Expired](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-07-csms): Local start transaction - Authorization Expired (TC_C_07_CSMS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at the CSM…
- [TC_C_08_CS — Authorization through authorization cache - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-08-cs): Authorization through authorization cache - Accepted (TC_C_08_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction while the Chargi…
- [TC_C_08_CSMS — Authorization through authorization cache - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-08-csms): Authorization through authorization cache - Accepted (TC_C_08_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction while the Char…
- [TC_C_09_CS — Authorization through authorization cache - Invalid & Not Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-09-cs): Authorization through authorization cache - Invalid & Not Accepted (TC_C_09_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction wh…
- [TC_C_10_CS — Authorization through authorization cache - Blocked](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-10-cs): Authorization through authorization cache - Blocked (TC_C_10_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction while the Chargin…
- [TC_C_11_CS — Authorization through authorization cache - Expired](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-11-cs): Authorization through authorization cache - Expired (TC_C_11_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction while the Chargin…
- [TC_C_12_CS — Authorization through authorization cache - Invalid & Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-12-cs): Authorization through authorization cache - Invalid & Accepted (TC_C_12_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction while…
- [TC_C_13_CS — Authorization through authorization cache - Accepted but cable not connected yet.](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-13-cs): Authorization through authorization cache - Accepted but cable not connected yet. (TC_C_13_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a…
- [TC_C_15_CS — Authorization through authorization cache - StopTxOnInvalidId = false, MaxEnergyOnInvalidId > 0](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-15-cs): Authorization through authorization cache - StopTxOnInvalidId = false, MaxEnergyOnInvalidId > 0 (TC_C_15_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authori…
- [TC_C_16_CS — Authorization through authorization cache - StopTxOnInvalidId = true](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-16-cs): Authorization through authorization cache - StopTxOnInvalidId = true (TC_C_16_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction…
- [TC_C_17_CS — Authorization through authorization cache - StopTxOnInvalidId = false](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-17-cs): Authorization through authorization cache - StopTxOnInvalidId = false (TC_C_17_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction…
- [TC_C_18_CS — Authorization through authorization cache - StopTxOnInvalidId = true, MaxEnergyOnInvalidId > 0](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-18-cs): Authorization through authorization cache - StopTxOnInvalidId = true, MaxEnergyOnInvalidId > 0 (TC_C_18_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authoriz…
- [TC_C_20_CSMS — Authorization through authorization cache - Invalid](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-20-csms): Authorization through authorization cache - Invalid (TC_C_20_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is authorized to start a transaction while the Charg…
- [TC_C_26_CS — Offline Authorization - Unknown Id](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-26-cs): Offline Authorization - Unknown Id (TC_C_26_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station is allowed to allow starting a transaction for unknown idTokens when offline and configured t…
- [TC_C_32_CS — Store Authorization Data in the Authorization Cache - Persistent over reboot](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-32-cs): Store Authorization Data in the Authorization Cache - Persistent over reboot (TC_C_32_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores a rec…
- [TC_C_33_CS — Store Authorization Data in the Authorization Cache - Update on AuthorizeResponse](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-33-cs): Store Authorization Data in the Authorization Cache - Update on AuthorizeResponse (TC_C_33_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores…
- [TC_C_34_CS — Store Authorization Data in the Authorization Cache - Update on TransactionResponse](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-34-cs): Store Authorization Data in the Authorization Cache - Update on TransactionResponse (TC_C_34_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously store…
- [TC_C_36_CS — Store Authorization Data in the Authorization Cache - AuthCacheCtrlr.LocalPreAuthorize = false](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-36-cs): Store Authorization Data in the Authorization Cache - AuthCacheCtrlr.LocalPreAuthorize = false (TC_C_36_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonom…
- [TC_C_37_CS — Clear Authorization Data in Authorization Cache - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-37-cs): Clear Authorization Data in Authorization Cache - Accepted (TC_C_37_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores a record of previously…
- [TC_C_37_CSMS — Clear Authorization Data in Authorization Cache - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-37-csms): Clear Authorization Data in Authorization Cache - Accepted (TC_C_37_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores a record of previousl…
- [TC_C_38_CS — Clear Authorization Data in Authorization Cache - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-38-cs): Clear Authorization Data in Authorization Cache - Rejected (TC_C_38_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores a record of previously…
- [TC_C_38_CSMS — Clear Authorization Data in Authorization Cache - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-38-csms): Clear Authorization Data in Authorization Cache - Rejected (TC_C_38_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores a record of previousl…
- [TC_C_39_CS — Authorization by GroupId - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-39-cs): Authorization by GroupId - Success (TC_C_39_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how a Charging Station can authorize an action for an EV Driver based on GroupId information…
- [TC_C_39_CSMS — Authorization by GroupId - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-39-csms): Authorization by GroupId - Success (TC_C_39_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how a Charging Station can authorize an action for an EV Driver based on GroupId informati…
- [TC_C_41_CS — Authorization by GroupId - Success with Authorization Cache](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-41-cs): Authorization by GroupId - Success with Authorization Cache (TC_C_41_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how a Charging Station can authorize an action for an EV Driver bas…
- [TC_C_42_CS — Authorization by GroupId - Not stopped by GroupId](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-42-cs): Authorization by GroupId - Not stopped by GroupId (TC_C_42_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how a Charging Station can authorize an action for an EV Driver based on Grou…
- [TC_C_44_CS — Authorization by GroupId - Invalid status with Authorization Cache](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-44-cs): Authorization by GroupId - Invalid status with Authorization Cache (TC_C_44_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how a Charging Station can authorize an action for an EV Dri…
- [TC_C_45_CS — Authorization by GroupId - Master pass - Not able to start transaction + groupId](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-45-cs): Authorization by GroupId - Master pass - Not able to start transaction + groupId (TC_C_45_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how a Charging Station can authorize an action…
- [TC_C_46_CS — Store Authorization Data in the Authorization Cache - AuthCacheLifeTime](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-46-cs): Store Authorization Data in the Authorization Cache - AuthCacheLifeTime (TC_C_46_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the Charging Station autonomously stores a record o…
- [TC_C_47_CS — Stop Transaction with a Master Pass - With UI - All transactions](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-47-cs): Stop Transaction with a Master Pass - With UI - All transactions (TC_C_47_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how somebody with a Master Pass (User) can stop (selected) ong…
- [TC_C_47_CSMS — Stop Transaction with a Master Pass - With UI - All transactions](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-47-csms): Stop Transaction with a Master Pass - With UI - All transactions (TC_C_47_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how somebody with a Master Pass (User) can stop (selected) o…
- [TC_C_48_CS — Stop Transaction with a Master Pass - With UI - With UI - Specific transactions](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-48-cs): Stop Transaction with a Master Pass - With UI - With UI - Specific transactions (TC_C_48_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how somebody with a Master Pass (User) can stop…
- [TC_C_48_CSMS — Stop Transaction with a Master Pass - With UI - With UI - Specific transactions](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-48-csms): Stop Transaction with a Master Pass - With UI - With UI - Specific transactions (TC_C_48_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how somebody with a Master Pass (User) can st…
- [TC_C_49_CS — Stop Transaction with a Master Pass - Without UI](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-49-cs): Stop Transaction with a Master Pass - Without UI (TC_C_49_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how somebody with a Master Pass (User) can stop (selected) ongoing transaction…
- [TC_C_49_CSMS — Stop Transaction with a Master Pass - Without UI](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-49-csms): Stop Transaction with a Master Pass - Without UI (TC_C_49_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how somebody with a Master Pass (User) can stop (selected) ongoing transacti…
- [TC_C_56_CS — Local start transaction - Authorization Unknown](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-56-cs): Local start transaction - Authorization Unknown (TC_C_56_CS) — OCPP 2.0.1 OCTT compliance test. When a Charging Station needs to charge an EV, it needs to authorize the EV Driver first at the CSMS…
- [TC_C_57_CS — Authorization through authorization cache - AuthCacheDisablePostAuthorize](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-c-57-cs): Authorization through authorization cache - AuthCacheDisablePostAuthorize (TC_C_57_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver can be authorized to start a tra…
- [TC_E_01_CS — Start transaction options - PowerPathClosed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-01-cs): Start transaction options - PowerPathClosed (TC_E_01_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be c…
- [TC_E_01_CSMS — Start transaction options - PowerPathClosed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-01-csms): Start transaction options - PowerPathClosed (TC_E_01_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be…
- [TC_E_02_CS — Start transaction options - EnergyTransfer](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-02-cs): Start transaction options - EnergyTransfer (TC_E_02_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be co…
- [TC_E_02_CSMS — Start transaction options - EnergyTransfer](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-02-csms): Start transaction options - EnergyTransfer (TC_E_02_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be…
- [TC_E_03_CS — Local start transaction - Cable plugin first - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-03-cs): Local start transaction - Cable plugin first - Success (TC_E_03_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of id…
- [TC_E_03_CSMS — Local start transaction - Cable plugin first - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-03-csms): Local start transaction - Cable plugin first - Success (TC_E_03_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of…
- [TC_E_04_CS — Local start transaction - Authorization first - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-04-cs): Local start transaction - Authorization first - Success (TC_E_04_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of i…
- [TC_E_04_CSMS — Local start transaction - Authorization first - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-04-csms): Local start transaction - Authorization first - Success (TC_E_04_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of…
- [TC_E_05_CS — Local start transaction - Authorization first - Cable plugin timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-05-cs): Local start transaction - Authorization first - Cable plugin timeout (TC_E_05_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR presen…
- [TC_E_06_CS — Local Stop Transaction - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-06-cs): Local Stop Transaction - Accepted (TC_E_06_CS) — OCPP 2.0.1 OCTT compliance test. The EV Driver is able to stop an ongoing transaction, by locally presenting an IdToken.
- [TC_E_07_CS — Stop transaction options - PowerPathClosed - Local stop](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-07-cs): Stop transaction options - PowerPathClosed - Local stop (TC_E_07_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop po…
- [TC_E_07_CSMS — Stop transaction options - PowerPathClosed - Local stop](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-07-csms): Stop transaction options - PowerPathClosed - Local stop (TC_E_07_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop…
- [TC_E_08_CS — Stop transaction options - EnergyTransfer stopped - StopAuthorized](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-08-cs): Stop transaction options - EnergyTransfer stopped - StopAuthorized (TC_E_08_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start…
- [TC_E_08_CSMS — Stop transaction options - EnergyTransfer stopped - StopAuthorized](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-08-csms): Stop transaction options - EnergyTransfer stopped - StopAuthorized (TC_E_08_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction star…
- [TC_E_09_CS — Start transaction options - EVConnected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-09-cs): Start transaction options - EVConnected (TC_E_09_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be confi…
- [TC_E_09_CSMS — Start transaction options - EVConnected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-09-csms): Start transaction options - EVConnected (TC_E_09_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be con…
- [TC_E_10_CS — Start transaction options - Authorized - Local](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-10-cs): Start transaction options - Authorized - Local (TC_E_10_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to b…
- [TC_E_10_CSMS — Start transaction options - Authorized - Local](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-10-csms): Start transaction options - Authorized - Local (TC_E_10_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to…
- [TC_E_11_CS — Start transaction options - DataSigned](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-11-cs): Start transaction options - DataSigned (TC_E_11_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be config…
- [TC_E_11_CSMS — Start transaction options - DataSigned](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-11-csms): Start transaction options - DataSigned (TC_E_11_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be conf…
- [TC_E_12_CS — Start transaction options - ParkingBayOccupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-12-cs): Start transaction options - ParkingBayOccupied (TC_E_12_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to b…
- [TC_E_12_CSMS — Start transaction options - ParkingBayOccupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-12-csms): Start transaction options - ParkingBayOccupied (TC_E_12_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to…
- [TC_E_13_CS — Start transaction options - Authorized - Remote](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-13-cs): Start transaction options - Authorized - Remote (TC_E_13_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to…
- [TC_E_14_CS — Stop transaction options - EVDisconnected - Charging Station side](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-14-cs): Stop transaction options - EVDisconnected - Charging Station side (TC_E_14_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start a…
- [TC_E_14_CSMS — Stop transaction options - EVDisconnected - Charging Station side](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-14-csms): Stop transaction options - EVDisconnected - Charging Station side (TC_E_14_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start…
- [TC_E_15_CS — Stop transaction options - StopAuthorized - Local](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-15-cs): Stop transaction options - StopAuthorized - Local (TC_E_15_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points t…
- [TC_E_15_CSMS — Stop transaction options - StopAuthorized - Local](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-15-csms): Stop transaction options - StopAuthorized - Local (TC_E_15_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points…
- [TC_E_16_CS — Stop transaction options - Deauthorized - Invalid idToken](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-16-cs): Stop transaction options - Deauthorized - Invalid idToken (TC_E_16_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop…
- [TC_E_16_CSMS — Stop transaction options - Deauthorized - Invalid idToken](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-16-csms): Stop transaction options - Deauthorized - Invalid idToken (TC_E_16_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and sto…
- [TC_E_17_CS — Stop transaction options - Deauthorized - EV side disconnect](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-17-cs): Stop transaction options - Deauthorized - EV side disconnect (TC_E_17_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and st…
- [TC_E_17_CSMS — Stop transaction options - Deauthorized - EV side disconnect](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-17-csms): Stop transaction options - Deauthorized - EV side disconnect (TC_E_17_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and…
- [TC_E_19_CS — Stop transaction options - ParkingBayUnoccupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-19-cs): Stop transaction options - ParkingBayUnoccupied (TC_E_19_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to…
- [TC_E_19_CSMS — Stop transaction options - ParkingBayUnoccupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-19-csms): Stop transaction options - ParkingBayUnoccupied (TC_E_19_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points t…
- [TC_E_20_CS — Stop transaction options - EVDisconnected - EV side (able to charge IEC 61851-1 EV)](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-20-cs): Stop transaction options - EVDisconnected - EV side (able to charge IEC 61851-1 EV) (TC_E_20_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the t…
- [TC_E_20_CSMS — Stop transaction options - EVDisconnected - EV side (able to charge IEC 61851-1 EV)](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-20-csms): Stop transaction options - EVDisconnected - EV side (able to charge IEC 61851-1 EV) (TC_E_20_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the…
- [TC_E_21_CS — Stop transaction options - StopAuthorized - Remote](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-21-cs): Stop transaction options - StopAuthorized - Remote (TC_E_21_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points…
- [TC_E_21_CSMS — Stop transaction options - StopAuthorized - Remote](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-21-csms): Stop transaction options - StopAuthorized - Remote (TC_E_21_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop point…
- [TC_E_22_CS — Stop transaction options - EnergyTransfer stopped - SuspendedEV](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-22-cs): Stop transaction options - EnergyTransfer stopped - SuspendedEV (TC_E_22_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and…
- [TC_E_22_CSMS — Stop transaction options - EnergyTransfer stopped - SuspendedEV](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-22-csms): Stop transaction options - EnergyTransfer stopped - SuspendedEV (TC_E_22_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start a…
- [TC_E_24_CS — Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is true](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-24-cs): Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is true (TC_E_24_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station can behave in several different ways wh…
- [TC_E_25_CS — Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is false](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-25-cs): Disconnect cable on EV-side - Deauthorize transaction - UnlockOnEVSideDisconnect is false (TC_E_25_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station can behave in several different ways w…
- [TC_E_26_CS — Disconnect cable on EV-side - Suspend transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-26-cs): Disconnect cable on EV-side - Suspend transaction (TC_E_26_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station can behave in several different ways when the cable is disconnected at the EV…
- [TC_E_26_CSMS — Disconnect cable on EV-side - Suspend transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-26-csms): Disconnect cable on EV-side - Suspend transaction (TC_E_26_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station can behave in several different ways when the cable is disconnected at the E…
- [TC_E_27_CS — Disconnect cable on EV-side - Suspend transaction - Fixed cable connection timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-27-cs): Disconnect cable on EV-side - Suspend transaction - Fixed cable connection timeout (TC_E_27_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station can behave in several different ways when the…
- [TC_E_28_CS — Check Transaction status - TransactionId unknown](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-28-cs): Check Transaction status - TransactionId unknown (TC_E_28_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find out whether there are queued tra…
- [TC_E_29_CS — Check Transaction status - Transaction with id ongoing - with message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-29-cs): Check Transaction status - Transaction with id ongoing - with message in queue (TC_E_29_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find ou…
- [TC_E_29_CSMS — Check Transaction status - Transaction with id ongoing - with message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-29-csms): Check Transaction status - Transaction with id ongoing - with message in queue (TC_E_29_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find…
- [TC_E_30_CS — Check Transaction status - Transaction with id ongoing - without message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-30-cs): Check Transaction status - Transaction with id ongoing - without message in queue (TC_E_30_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find…
- [TC_E_30_CSMS — Check Transaction status - Transaction with id ongoing - without message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-30-csms): Check Transaction status - Transaction with id ongoing - without message in queue (TC_E_30_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to fi…
- [TC_E_31_CS — Check Transaction status - Transaction with id ended - with message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-31-cs): Check Transaction status - Transaction with id ended - with message in queue (TC_E_31_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find out…
- [TC_E_31_CSMS — Check Transaction status - Transaction with id ended - with message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-31-csms): Check Transaction status - Transaction with id ended - with message in queue (TC_E_31_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find ou…
- [TC_E_32_CS — Check Transaction status - Transaction with id ended - without message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-32-cs): Check Transaction status - Transaction with id ended - without message in queue (TC_E_32_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find o…
- [TC_E_33_CS — Check Transaction status - Without transactionId - with message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-33-cs): Check Transaction status - Without transactionId - with message in queue (TC_E_33_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find out whet…
- [TC_E_33_CSMS — Check Transaction status - Without transactionId - with message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-33-csms): Check Transaction status - Without transactionId - with message in queue (TC_E_33_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find out wh…
- [TC_E_34_CS — Check Transaction status - Without transactionId - without message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-34-cs): Check Transaction status - Without transactionId - without message in queue (TC_E_34_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find out w…
- [TC_E_34_CSMS — Check Transaction status - Without transactionId - without message in queue](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-34-csms): Check Transaction status - Without transactionId - without message in queue (TC_E_34_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the status of a transaction and to find out…
- [TC_E_35_CS — Stop transaction options - PowerPathClosed - Remote stop](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-35-cs): Stop transaction options - PowerPathClosed - Remote stop (TC_E_35_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop p…
- [TC_E_37_CS — Stop transaction options - PowerPathClosed - EV side disconnect](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-37-cs): Stop transaction options - PowerPathClosed - EV side disconnect (TC_E_37_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and…
- [TC_E_38_CS — Local start transaction - EV not ready](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-38-cs): Local start transaction - EV not ready (TC_E_38_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of identification. Bo…
- [TC_E_38_CSMS — Local start transaction - EV not ready](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-38-csms): Local start transaction - EV not ready (TC_E_38_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of identification…
- [TC_E_39_CS — Stop transaction options - Deauthorized - timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-39-cs): Stop transaction options - Deauthorized - timeout (TC_E_39_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points t…
- [TC_E_39_CSMS — Stop transaction options - Deauthorized - timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-39-csms): Stop transaction options - Deauthorized - timeout (TC_E_39_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR present a form of ident…
- [TC_E_40_CS — Offline Behaviour - Connection loss during transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-40-cs): Offline Behaviour - Connection loss during transaction (TC_E_40_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station queues TransactionEvent messages to inform the CSMS that a transaction oc…
- [TC_E_41_CS — Retry sending transaction message when failed - Max retry count reached](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-41-cs): Retry sending transaction message when failed - Max retry count reached (TC_E_41_CS) — OCPP 2.0.1 OCTT compliance test. There are situations/issues why a CSMS might not accept a transaction related…
- [TC_E_42_CS — Retry sending transaction message when failed - Success before reaching the max retry count](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-42-cs): Retry sending transaction message when failed - Success before reaching the max retry count (TC_E_42_CS) — OCPP 2.0.1 OCTT compliance test. There are situations/issues why a CSMS might not accept a…
- [TC_E_43_CS — Offline Behaviour - Transaction during offline period](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-43-cs): Offline Behaviour - Transaction during offline period (TC_E_43_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station queues TransactionEvent messages to inform the CSMS that a transaction occ…
- [TC_E_44_CS — Offline Behaviour - Stop transaction during offline period](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-44-cs): Offline Behaviour - Stop transaction during offline period (TC_E_44_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station queues TransactionEvent messages to inform the CSMS that a transactio…
- [TC_E_45_CS — Offline Behaviour - Stop transaction during offline period - Same GroupId](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-45-cs): Offline Behaviour - Stop transaction during offline period - Same GroupId (TC_E_45_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station queues TransactionEvent messages to inform the CSMS th…
- [TC_E_50_CS — Retry sending transaction message when failed - Max retry count reached - CallError](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-50-cs): Retry sending transaction message when failed - Max retry count reached - CallError (TC_E_50_CS) — OCPP 2.0.1 OCTT compliance test. There are situations/issues why a CSMS might not accept a transac…
- [TC_E_51_CS — Retry sending transaction message when failed - Success before reaching the max retry count - CallError](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-51-cs): Retry sending transaction message when failed - Success before reaching the max retry count - CallError (TC_E_51_CS) — OCPP 2.0.1 OCTT compliance test. There are situations/issues why a CSMS might…
- [TC_E_52_CS — Local start transaction - Authorization first - DisableRemoteAuthorization](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-52-cs): Local start transaction - Authorization first - DisableRemoteAuthorization (TC_E_52_CS) — OCPP 2.0.1 OCTT compliance test. When DisableRemoteAuthorization is set to true, the Charging Station will…
- [TC_E_53_CSMS — Reset Sequence Number - CSMS accepting seqNo = 0 at start of transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-53-csms): Reset Sequence Number - CSMS accepting seqNo = 0 at start of transaction (TC_E_53_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.0.1 Edition 2 recommends that seqNo starts at 0 for every transacti…
- [TC_E_54_CS — Stop transaction options - EVDisconnected - EV side (not able to charge IEC 61851-1 EV)](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-e-54-cs): Stop transaction options - EVDisconnected - EV side (not able to charge IEC 61851-1 EV) (TC_E_54_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x has a flexible transaction mechanism that allows t…
- [TC_F_01_CS — Remote start transaction - Cable plugin first](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-01-cs): Remote start transaction - Cable plugin first (TC_F_01_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR wait for/trigger a RequestSta…
- [TC_F_01_CSMS — Remote start transaction - Cable plugin first](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-01-csms): Remote start transaction - Cable plugin first (TC_F_01_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first connect the EV and EVSE OR wait for/trigger a RequestS…
- [TC_F_02_CS — Remote start transaction - Remote start first - AuthorizeRemoteStart is true](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-02-cs): Remote start transaction - Remote start first - AuthorizeRemoteStart is true (TC_F_02_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first wait for/trigger a Reques…
- [TC_F_02_CSMS — Remote start transaction - Remote start first - AuthorizeRemoteStart is true](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-02-csms): Remote start transaction - Remote start first - AuthorizeRemoteStart is true (TC_F_02_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first wait for/trigger a Requ…
- [TC_F_03_CS — Remote start transaction - Remote start first - AuthorizeRemoteStart is false](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-03-cs): Remote start transaction - Remote start first - AuthorizeRemoteStart is false (TC_F_03_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first wait for/trigger a Reque…
- [TC_F_03_CSMS — Remote start transaction - Remote start first - AuthorizeRemoteStart is false](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-03-csms): Remote start transaction - Remote start first - AuthorizeRemoteStart is false (TC_F_03_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first wait for/trigger a Req…
- [TC_F_04_CS — Remote start transaction - Remote start first - Cable plugin timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-04-cs): Remote start transaction - Remote start first - Cable plugin timeout (TC_F_04_CS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first wait for/trigger a RequestStartTr…
- [TC_F_04_CSMS — Remote start transaction - Remote start first - Cable plugin timeout](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-04-csms): Remote start transaction - Remote start first - Cable plugin timeout (TC_F_04_CSMS) — OCPP 2.0.1 OCTT compliance test. OCPP 2.x.x allows an EV driver to either first wait for/trigger a RequestStart…
- [TC_F_05_CS — Remote unlock Connector - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-05-cs): Remote unlock Connector - With ongoing transaction (TC_F_05_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS can be requested to sent an UnlockConnectorRequest to the ch…
- [TC_F_06_CS — Remote unlock Connector - Without ongoing transaction - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-06-cs): Remote unlock Connector - Without ongoing transaction - Accepted (TC_F_06_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS can be requested to sent an UnlockConnectorReq…
- [TC_F_06_CSMS — Remote unlock Connector - Without ongoing transaction - Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-06-csms): Remote unlock Connector - Without ongoing transaction - Accepted (TC_F_06_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS can be requested to sent an UnlockConnectorR…
- [TC_F_07_CS — Remote unlock Connector - Without ongoing transaction - No cable connected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-07-cs): Remote unlock Connector - Without ongoing transaction - No cable connected (TC_F_07_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS can be requested to sent an UnlockCo…
- [TC_F_08_CS — Remote stop transaction - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-08-cs): Remote stop transaction - Success (TC_F_08_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to stop a charging session remotely by sending a RequestStopTransactionRequest to the Charging Sta…
- [TC_F_09_CS — Remote stop transaction - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-09-cs): Remote stop transaction - Rejected (TC_F_09_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to stop a charging session remotely by sending a RequestStopTransactionRequest to the Charging St…
- [TC_F_10_CS — Remote unlock Connector - Without ongoing transaction - UnknownConnector](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-10-cs): Remote unlock Connector - Without ongoing transaction - UnknownConnector (TC_F_10_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS can be requested to sent an UnlockConn…
- [TC_F_11_CS — Trigger message - MeterValues - Specific EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-11-cs): Trigger message - MeterValues - Specific EVSE (TC_F_11_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the…
- [TC_F_11_CSMS — Trigger message - MeterValues - Specific EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-11-csms): Trigger message - MeterValues - Specific EVSE (TC_F_11_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request t…
- [TC_F_12_CS — Trigger message - MeterValues - All EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-12-cs): Trigger message - MeterValues - All EVSE (TC_F_12_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CSMS…
- [TC_F_12_CSMS — Trigger message - MeterValues - All EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-12-csms): Trigger message - MeterValues - All EVSE (TC_F_12_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CS…
- [TC_F_13_CS — Trigger message - TransactionEvent - Specific EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-13-cs): Trigger message - TransactionEvent - Specific EVSE (TC_F_13_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the reques…
- [TC_F_13_CSMS — Trigger message - TransactionEvent - Specific EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-13-csms): Trigger message - TransactionEvent - Specific EVSE (TC_F_13_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the requ…
- [TC_F_14_CS — Trigger message - TransactionEvent - All EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-14-cs): Trigger message - TransactionEvent - All EVSE (TC_F_14_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the…
- [TC_F_14_CSMS — Trigger message - TransactionEvent - All EVSE](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-14-csms): Trigger message - TransactionEvent - All EVSE (TC_F_14_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request t…
- [TC_F_15_CS — Trigger message - LogStatusNotification - Idle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-15-cs): Trigger message - LogStatusNotification - Idle (TC_F_15_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request th…
- [TC_F_15_CSMS — Trigger message - LogStatusNotification - Idle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-15-csms): Trigger message - LogStatusNotification - Idle (TC_F_15_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request…
- [TC_F_16_CS — Trigger message - LogStatusNotification - Uploading](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-16-cs): Trigger message - LogStatusNotification - Uploading (TC_F_16_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the reque…
- [TC_F_17_CS — Trigger message - FirmwareStatusNotification - Specific EVSE not relevant](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-17-cs): Trigger message - FirmwareStatusNotification - Specific EVSE not relevant (TC_F_17_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated…
- [TC_F_18_CS — Trigger message - FirmwareStatusNotification - Idle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-18-cs): Trigger message - FirmwareStatusNotification - Idle (TC_F_18_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the reque…
- [TC_F_18_CSMS — Trigger message - FirmwareStatusNotification - Idle](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-18-csms): Trigger message - FirmwareStatusNotification - Idle (TC_F_18_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the req…
- [TC_F_19_CS — Trigger message - FirmwareStatusNotification - Downloading](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-19-cs): Trigger message - FirmwareStatusNotification - Downloading (TC_F_19_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In th…
- [TC_F_20_CS — Trigger message - Heartbeat](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-20-cs): Trigger message - Heartbeat (TC_F_20_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CSMS indicates wh…
- [TC_F_20_CSMS — Trigger message - Heartbeat](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-20-csms): Trigger message - Heartbeat (TC_F_20_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CSMS indicates…
- [TC_F_23_CS — Trigger message - StatusNotification - Specific EVSE - Available](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-23-cs): Trigger message - StatusNotification - Specific EVSE - Available (TC_F_23_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages…
- [TC_F_23_CSMS — Trigger message - StatusNotification - Specific EVSE - Available](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-23-csms): Trigger message - StatusNotification - Specific EVSE - Available (TC_F_23_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated message…
- [TC_F_24_CS — Trigger message - StatusNotification - Specific EVSE - Occupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-24-cs): Trigger message - StatusNotification - Specific EVSE - Occupied (TC_F_24_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages…
- [TC_F_24_CSMS — Trigger message - StatusNotification - Specific EVSE - Occupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-24-csms): Trigger message - StatusNotification - Specific EVSE - Occupied (TC_F_24_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages…
- [TC_F_26_CS — Trigger message - BootNotification - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-26-cs): Trigger message - BootNotification - Rejected (TC_F_26_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the…
- [TC_F_27_CS — Trigger message - NotImplemented](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-27-cs): Trigger message - NotImplemented (TC_F_27_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CSMS indicat…
- [TC_F_27_CSMS — Trigger message - NotImplemented](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-f-27-csms): Trigger message - NotImplemented (TC_F_27_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS can request a Charging Station to send Charging Station-initiated messages. In the request the CSMS indic…
- [TC_G_01_CS — Connector status Notification - Available to Occupied](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-01-cs): Connector status Notification - Available to Occupied (TC_G_01_CS) — OCPP 2.0.1 OCTT compliance test. A Charging Station sends a notification to the CSMS to inform the CSMS about a Connector status…
- [TC_G_02_CS — Connector status Notification - Occupied to Available](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-02-cs): Connector status Notification - Occupied to Available (TC_G_02_CS) — OCPP 2.0.1 OCTT compliance test. A Charging Station sends a notification to the CSMS to inform the CSMS about a Connector status…
- [TC_G_03_CS — Change Availability EVSE - Operative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-03-cs): Change Availability EVSE - Operative to inoperative (TC_G_03_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of on…
- [TC_G_03_CSMS — Change Availability EVSE - Operative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-03-csms): Change Availability EVSE - Operative to inoperative (TC_G_03_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of…
- [TC_G_04_CS — Change Availability EVSE - Inoperative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-04-cs): Change Availability EVSE - Inoperative to operative (TC_G_04_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of on…
- [TC_G_04_CSMS — Change Availability EVSE - Inoperative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-04-csms): Change Availability EVSE - Inoperative to operative (TC_G_04_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of…
- [TC_G_05_CS — Change Availability Charging Station - Operative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-05-cs): Change Availability Charging Station - Operative to inoperative (TC_G_05_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS requests the Charging Station to change the ava…
- [TC_G_05_CSMS — Change Availability Charging Station - Operative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-05-csms): Change Availability Charging Station - Operative to inoperative (TC_G_05_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS requests the Charging Station to change the a…
- [TC_G_06_CS — Change Availability Charging Station - Inoperative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-06-cs): Change Availability Charging Station - Inoperative to operative (TC_G_06_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS requests the Charging Station to change the ava…
- [TC_G_06_CSMS — Change Availability Charging Station - Inoperative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-06-csms): Change Availability Charging Station - Inoperative to operative (TC_G_06_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS requests the Charging Station to change the a…
- [TC_G_07_CS — Change Availability Connector - Operative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-07-cs): Change Availability Connector - Operative to inoperative (TC_G_07_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability…
- [TC_G_07_CSMS — Change Availability Connector - Operative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-07-csms): Change Availability Connector - Operative to inoperative (TC_G_07_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availabilit…
- [TC_G_08_CS — Change Availability Connector - Inoperative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-08-cs): Change Availability Connector - Inoperative to operative (TC_G_08_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability…
- [TC_G_08_CSMS — Change Availability Connector - Inoperative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-08-csms): Change Availability Connector - Inoperative to operative (TC_G_08_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availabilit…
- [TC_G_09_CS — Change Availability EVSE - Operative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-09-cs): Change Availability EVSE - Operative to operative (TC_G_09_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of one…
- [TC_G_10_CS — Change Availability EVSE - Inoperative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-10-cs): Change Availability EVSE - Inoperative to inoperative (TC_G_10_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of…
- [TC_G_11_CS — Change Availability EVSE - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-11-cs): Change Availability EVSE - With ongoing transaction (TC_G_11_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of on…
- [TC_G_11_CSMS — Change Availability EVSE - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-11-csms): Change Availability EVSE - With ongoing transaction (TC_G_11_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of…
- [TC_G_12_CS — Change Availability Charging Station - Operative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-12-cs): Change Availability Charging Station - Operative to operative (TC_G_12_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS requests the Charging Station to change the avail…
- [TC_G_13_CS — Change Availability Charging Station - Inoperative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-13-cs): Change Availability Charging Station - Inoperative to inoperative (TC_G_13_CS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the CSMS requests the Charging Station to change the a…
- [TC_G_14_CS — Change Availability Charging Station - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-14-cs): Change Availability Charging Station - With ongoing transaction (TC_G_14_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availa…
- [TC_G_14_CSMS — Change Availability Charging Station - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-14-csms): Change Availability Charging Station - With ongoing transaction (TC_G_14_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the avai…
- [TC_G_15_CS — Change Availability Connector - Operative to operative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-15-cs): Change Availability Connector - Operative to operative (TC_G_15_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability of…
- [TC_G_16_CS — Change Availability Connector - Inoperative to inoperative](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-16-cs): Change Availability Connector - Inoperative to inoperative (TC_G_16_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availabilit…
- [TC_G_17_CS — Change Availability Connector - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-17-cs): Change Availability Connector - With ongoing transaction (TC_G_17_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability…
- [TC_G_17_CSMS — Change Availability Connector - With ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-17-csms): Change Availability Connector - With ongoing transaction (TC_G_17_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availabilit…
- [TC_G_18_CS — Change Availability EVSE - state persists across reboot](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-18-cs): Change Availability EVSE - state persists across reboot (TC_G_18_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availability o…
- [TC_G_19_CS — Change Availability Connector - state persists across reboot](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-19-cs): Change Availability Connector - state persists across reboot (TC_G_19_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the availabil…
- [TC_G_20_CSMS — Connector status Notification - Lock Failure](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-20-csms): Connector status Notification - Lock Failure (TC_G_20_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case describes how the EV Driver is prevented from starting a charge session at the Charging…
- [TC_G_21_CS — Change Availability Charging Station - state persists across reboot](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-g-21-cs): Change Availability Charging Station - state persists across reboot (TC_G_21_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers how the CSMS requests the Charging Station to change the av…
- [TC_J_01_CS — Clock-aligned Meter Values - No transaction ongoing](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-01-cs): Clock-aligned Meter Values - No transaction ongoing (TC_J_01_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide…
- [TC_J_01_CSMS — Clock-aligned Meter Values - No transaction ongoing](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-01-csms): Clock-aligned Meter Values - No transaction ongoing (TC_J_01_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provid…
- [TC_J_02_CS — Clock-aligned Meter Values - Transaction ongoing](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-02-cs): Clock-aligned Meter Values - Transaction ongoing (TC_J_02_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide inf…
- [TC_J_02_CSMS — Clock-aligned Meter Values - Transaction ongoing](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-02-csms): Clock-aligned Meter Values - Transaction ongoing (TC_J_02_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide i…
- [TC_J_03_CS — Clock-aligned Meter Values - EventType Ended](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-03-cs): Clock-aligned Meter Values - EventType Ended (TC_J_03_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide informa…
- [TC_J_03_CSMS — Clock-aligned Meter Values - EventType Ended](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-03-csms): Clock-aligned Meter Values - EventType Ended (TC_J_03_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide infor…
- [TC_J_04_CS — Clock-aligned Meter Values - Signed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-04-cs): Clock-aligned Meter Values - Signed (TC_J_04_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information abou…
- [TC_J_04_CSMS — Clock-aligned Meter Values - Signed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-04-csms): Clock-aligned Meter Values - Signed (TC_J_04_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information ab…
- [TC_J_06_CS — Clock-aligned Meter Values - No Meter Values during transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-06-cs): Clock-aligned Meter Values - No Meter Values during transaction (TC_J_06_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware…
- [TC_J_07_CS — Sampled Meter Values - EventType Started - EVSE known](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-07-cs): Sampled Meter Values - EventType Started - EVSE known (TC_J_07_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provid…
- [TC_J_07_CSMS — Sampled Meter Values - EventType Started - EVSE known](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-07-csms): Sampled Meter Values - EventType Started - EVSE known (TC_J_07_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to prov…
- [TC_J_08_CS — Sampled Meter Values - Context Transaction.Begin - EVSE not known](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-08-cs): Sampled Meter Values - Context Transaction.Begin - EVSE not known (TC_J_08_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardwa…
- [TC_J_08_CSMS — Sampled Meter Values - Context Transaction.Begin - EVSE not known](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-08-csms): Sampled Meter Values - Context Transaction.Begin - EVSE not known (TC_J_08_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hard…
- [TC_J_09_CS — Sampled Meter Values - EventType Updated](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-09-cs): Sampled Meter Values - EventType Updated (TC_J_09_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information…
- [TC_J_09_CSMS — Sampled Meter Values - EventType Updated](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-09-csms): Sampled Meter Values - EventType Updated (TC_J_09_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide informati…
- [TC_J_10_CS — Sampled Meter Values - EventType Ended](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-10-cs): Sampled Meter Values - EventType Ended (TC_J_10_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information a…
- [TC_J_10_CSMS — Sampled Meter Values - EventType Ended](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-10-csms): Sampled Meter Values - EventType Ended (TC_J_10_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information…
- [TC_J_11_CS — Sampled Meter Values - Signed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-11-cs): Sampled Meter Values - Signed (TC_J_11_CS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information about its…
- [TC_J_11_CSMS — Sampled Meter Values - Signed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-j-11-csms): Sampled Meter Values - Signed (TC_J_11_CSMS) — OCPP 2.0.1 OCTT compliance test. The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information about it…
- [TC_K_38_CS — Remote start transaction with charging profile - Ignore chargingProfile](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-k-38-cs): Remote start transaction with charging profile - Ignore chargingProfile (TC_K_38_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sets a TxProfile on a specific EVSE inside a RequestStartTransaction…
- [TC_L_01_CS — Secure Firmware Update - Installation successful](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-01-cs): Secure Firmware Update - Installation successful (TC_L_01_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by…
- [TC_L_01_CSMS — Secure Firmware Update - Installation successful](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-01-csms): Secure Firmware Update - Installation successful (TC_L_01_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware b…
- [TC_L_02_CS — Secure Firmware Update - InstallScheduled](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-02-cs): Secure Firmware Update - InstallScheduled (TC_L_02_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sending…
- [TC_L_02_CSMS — Secure Firmware Update - InstallScheduled](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-02-csms): Secure Firmware Update - InstallScheduled (TC_L_02_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sendi…
- [TC_L_03_CS — Secure Firmware Update - DownloadScheduled](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-03-cs): Secure Firmware Update - DownloadScheduled (TC_L_03_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sendin…
- [TC_L_03_CSMS — Secure Firmware Update - DownloadScheduled](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-03-csms): Secure Firmware Update - DownloadScheduled (TC_L_03_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by send…
- [TC_L_04_CSMS — Secure Firmware Update - RevokedCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-04-csms): Secure Firmware Update - RevokedCertificate (TC_L_04_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sen…
- [TC_L_05_CS — Secure Firmware Update - InvalidCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-05-cs): Secure Firmware Update - InvalidCertificate (TC_L_05_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sendi…
- [TC_L_05_CSMS — Secure Firmware Update - InvalidCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-05-csms): Secure Firmware Update - InvalidCertificate (TC_L_05_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sen…
- [TC_L_06_CS — Secure Firmware Update - InvalidSignature](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-06-cs): Secure Firmware Update - InvalidSignature (TC_L_06_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sending…
- [TC_L_06_CSMS — Secure Firmware Update - InvalidSignature](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-06-csms): Secure Firmware Update - InvalidSignature (TC_L_06_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sendi…
- [TC_L_07_CS — Secure Firmware Update - DownloadFailed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-07-cs): Secure Firmware Update - DownloadFailed (TC_L_07_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sending a…
- [TC_L_07_CSMS — Secure Firmware Update - DownloadFailed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-07-csms): Secure Firmware Update - DownloadFailed (TC_L_07_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sending…
- [TC_L_08_CS — Secure Firmware Update - InstallVerificationFailed or InstallationFailed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-08-cs): Secure Firmware Update - InstallVerificationFailed or InstallationFailed (TC_L_08_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and in…
- [TC_L_08_CSMS — Secure Firmware Update - InstallVerificationFailed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-08-csms): Secure Firmware Update - InstallVerificationFailed (TC_L_08_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware…
- [TC_L_09_CSMS — Secure Firmware Update - InstallationFailed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-09-csms): Secure Firmware Update - InstallationFailed (TC_L_09_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sen…
- [TC_L_10_CS — Secure Firmware Update - AcceptedCanceled](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-10-cs): Secure Firmware Update - AcceptedCanceled (TC_L_10_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sending…
- [TC_L_10_CSMS — Secure Firmware Update - AcceptedCanceled](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-10-csms): Secure Firmware Update - AcceptedCanceled (TC_L_10_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sendi…
- [TC_L_11_CS — Secure Firmware Update - Unable to cancel](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-11-cs): Secure Firmware Update - Unable to cancel (TC_L_11_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sending…
- [TC_L_11_CSMS — Secure Firmware Update - Unable to cancel](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-11-csms): Secure Firmware Update - Unable to cancel (TC_L_11_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and install a new firmware by sendi…
- [TC_L_12_CS — Secure Firmware Update - Unable to download/install firmware with ongoing transaction -](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-12-cs): Secure Firmware Update - Unable to download/install firmware with ongoing transaction - (TC_L_12_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely…
- [TC_L_13_CS — Secure Firmware Update - Unable to download/install firmware with ongoing transaction -](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-13-cs): Secure Firmware Update - Unable to download/install firmware with ongoing transaction - (TC_L_13_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely…
- [TC_L_13_CSMS — Secure Firmware Update - Unable to download/install firmware with ongoing transaction -](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-13-csms): Secure Firmware Update - Unable to download/install firmware with ongoing transaction - (TC_L_13_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securel…
- [TC_L_14_CS — Secure Firmware Update - Unable to install firmware with ongoing transaction -](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-14-cs): Secure Firmware Update - Unable to install firmware with ongoing transaction - (TC_L_14_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download…
- [TC_L_15_CS — Secure Firmware Update - Unable to install firmware with ongoing transaction -](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-15-cs): Secure Firmware Update - Unable to install firmware with ongoing transaction - (TC_L_15_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download…
- [TC_L_16_CS — Secure Firmware Update - Able to update firmware with ongoing transaction](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-16-cs): Secure Firmware Update - Able to update firmware with ongoing transaction (TC_L_16_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and i…
- [TC_L_18_CS — Secure Firmware Update - Missing firmware signing certificate and signature](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-l-18-cs): Secure Firmware Update - Missing firmware signing certificate and signature (TC_L_18_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to securely download and…
- [TC_M_01_CS — Install CA certificate - CSMSRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-01-cs): Install CA certificate - CSMSRootCertificate (TC_M_01_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificates using the InstallCe…
- [TC_M_01_CSMS — Install CA certificate - CSMSRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-01-csms): Install CA certificate - CSMSRootCertificate (TC_M_01_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificates using the Install…
- [TC_M_02_CS — Install CA certificate - ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-02-cs): Install CA certificate - ManufacturerRootCertificate (TC_M_02_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificates using the I…
- [TC_M_02_CSMS — Install CA certificate - ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-02-csms): Install CA certificate - ManufacturerRootCertificate (TC_M_02_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificates using the…
- [TC_M_05_CSMS — Install CA certificate - Failed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-05-csms): Install CA certificate - Failed (TC_M_05_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificates using the InstallCertificateRe…
- [TC_M_07_CS — Install CA certificate - Rejected - Certificate invalid](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-07-cs): Install CA certificate - Rejected - Certificate invalid (TC_M_07_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificates using th…
- [TC_M_09_CS — Install CA certificate - AdditionalRootCertificateCheck - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-09-cs): Install CA certificate - AdditionalRootCertificateCheck - Rejected (TC_M_09_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to install new Root CA certificat…
- [TC_M_12_CS — Retrieve certificates from Charging Station - CSMSRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-12-cs): Retrieve certificates from Charging Station - CSMSRootCertificate (TC_M_12_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging Station usi…
- [TC_M_13_CS — Retrieve certificates from Charging Station - ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-13-cs): Retrieve certificates from Charging Station - ManufacturerRootCertificate (TC_M_13_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging Sta…
- [TC_M_13_CSMS — Retrieve certificates from Charging Station - ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-13-csms): Retrieve certificates from Charging Station - ManufacturerRootCertificate (TC_M_13_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging S…
- [TC_M_17_CS — Retrieve certificates from Charging Station - CSMSRootCertificate & ManufacturerRootCertificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-17-cs): Retrieve certificates from Charging Station - CSMSRootCertificate & ManufacturerRootCertificate (TC_M_17_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates install…
- [TC_M_18_CS — Retrieve certificates from Charging Station - All certificateTypes](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-18-cs): Retrieve certificates from Charging Station - All certificateTypes (TC_M_18_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging Station us…
- [TC_M_18_CSMS — Retrieve certificates from Charging Station - All certificateTypes](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-18-csms): Retrieve certificates from Charging Station - All certificateTypes (TC_M_18_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging Station…
- [TC_M_19_CS — Retrieve certificates from Charging Station - No matching certificate found](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-19-cs): Retrieve certificates from Charging Station - No matching certificate found (TC_M_19_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging S…
- [TC_M_19_CSMS — Retrieve certificates from Charging Station - No matching certificate found](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-19-csms): Retrieve certificates from Charging Station - No matching certificate found (TC_M_19_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to retrieve the certificates installed at the Charging…
- [TC_M_20_CS — Delete a certificate from a Charging Station - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-20-cs): Delete a certificate from a Charging Station - Success (TC_M_20_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to delete an installed certificate using the…
- [TC_M_20_CSMS — Delete a certificate from a Charging Station - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-20-csms): Delete a certificate from a Charging Station - Success (TC_M_20_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to delete an installed certificate using th…
- [TC_M_21_CSMS — Delete a certificate from a Charging Station - Failed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-21-csms): Delete a certificate from a Charging Station - Failed (TC_M_21_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to delete an installed certificate using the…
- [TC_M_22_CS — Delete a certificate from a Charging Station - No matching certificate found](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-22-cs): Delete a certificate from a Charging Station - No matching certificate found (TC_M_22_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to delete an installed…
- [TC_M_23_CS — Delete a certificate from a Charging Station - Unable to delete the Charging Station Certificate](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-23-cs): Delete a certificate from a Charging Station - Unable to delete the Charging Station Certificate (TC_M_23_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to…
- [TC_M_30_CS — Install CA certificate - AdditionalRootCertificateCheck - Reconnect using new CSMS Root - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-30-cs): Install CA certificate - AdditionalRootCertificateCheck - Reconnect using new CSMS Root - Success (TC_M_30_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station to…
- [TC_M_31_CS — Install CA certificate - AdditionalRootCertificateCheck - Reconnect using new CSMS Root - Fallback](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-m-31-cs): Install CA certificate - AdditionalRootCertificateCheck - Reconnect using new CSMS Root - Fallback (TC_M_31_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS is able to request the Charging Station t…
- [TC_N_25_CS — Retrieve Log Information - Diagnostics Log - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-25-cs): Retrieve Log Information - Diagnostics Log - Success (TC_N_25_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. The…
- [TC_N_25_CSMS — Retrieve Log Information - Diagnostics Log - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-25-csms): Retrieve Log Information - Diagnostics Log - Success (TC_N_25_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. Th…
- [TC_N_26_CS — Retrieve Log Information - Diagnostics Log - Upload failed](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-26-cs): Retrieve Log Information - Diagnostics Log - Upload failed (TC_N_26_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station…
- [TC_N_27_CS — Get Customer Information - Accepted + data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-27-cs): Get Customer Information - Accepted + data (TC_N_27_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to retrieve IdToken customer information, for example to…
- [TC_N_27_CSMS — Get Customer Information - Accepted + data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-27-csms): Get Customer Information - Accepted + data (TC_N_27_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to retrieve IdToken customer information, for example t…
- [TC_N_28_CS — Get Customer Information - Accepted + no data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-28-cs): Get Customer Information - Accepted + no data (TC_N_28_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to retrieve IdToken customer information, for example…
- [TC_N_28_CSMS — Get Customer Information - Accepted + no data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-28-csms): Get Customer Information - Accepted + no data (TC_N_28_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to retrieve IdToken customer information, for exampl…
- [TC_N_29_CSMS — Get Customer Information - Not Accepted](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-29-csms): Get Customer Information - Not Accepted (TC_N_29_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to retrieve IdToken customer information, but the Charging…
- [TC_N_30_CS — Clear Customer Information - Clear and report + data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-30-cs): Clear Customer Information - Clear and report + data (TC_N_30_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) IdToken customer inform…
- [TC_N_30_CSMS — Clear Customer Information - Clear and report + data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-30-csms): Clear Customer Information - Clear and report + data (TC_N_30_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) IdToken customer info…
- [TC_N_31_CS — Clear Customer Information - Clear and report + no data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-31-cs): Clear Customer Information - Clear and report + no data (TC_N_31_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) IdToken customer inf…
- [TC_N_31_CSMS — Clear Customer Information - Clear and report + no data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-31-csms): Clear Customer Information - Clear and report + no data (TC_N_31_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) IdToken customer i…
- [TC_N_32_CS — Clear Customer Information - Clear and no report](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-32-cs): Clear Customer Information - Clear and no report (TC_N_32_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) IdToken customer informatio…
- [TC_N_32_CSMS — Clear Customer Information - Clear and no report](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-32-csms): Clear Customer Information - Clear and no report (TC_N_32_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear IdToken customer information, for exampl…
- [TC_N_34_CSMS — Retrieve Log Information - Rejected](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-34-csms): Retrieve Log Information - Rejected (TC_N_34_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. The CSMS can reques…
- [TC_N_35_CS — Retrieve Log Information - Security Log - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-35-cs): Retrieve Log Information - Security Log - Success (TC_N_35_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. The CSM…
- [TC_N_35_CSMS — Retrieve Log Information - Security Log - Success](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-35-csms): Retrieve Log Information - Security Log - Success (TC_N_35_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. The C…
- [TC_N_36_CS — Retrieve Log Information - Second Request](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-36-cs): Retrieve Log Information - Second Request (TC_N_36_CS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. The CSMS can re…
- [TC_N_36_CSMS — Retrieve Log Information - Second Request](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-36-csms): Retrieve Log Information - Second Request (TC_N_36_CSMS) — OCPP 2.0.1 OCTT compliance test. This test case covers the functionality of getting log information from a Charging Station. The CSMS can…
- [TC_N_62_CS — Clear Customer Information - Clear and report - customerIdentifier](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-62-cs): Clear Customer Information - Clear and report - customerIdentifier (TC_N_62_CS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) raw custo…
- [TC_N_62_CSMS — Clear Customer Information - Clear and report - customerIdentifier](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-n-62-csms): Clear Customer Information - Clear and report - customerIdentifier (TC_N_62_CSMS) — OCPP 2.0.1 OCTT compliance test. The CSMS sends a message to the Charging Station to clear (and retrieve) raw cus…
- [TC_P_01_CS — Data Transfer to the Charging Station - Rejected / Unknown VendorId / Unknown MessageId](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-p-01-cs): Data Transfer to the Charging Station - Rejected / Unknown VendorId / Unknown MessageId (TC_P_01_CS) — OCPP 2.0.1 OCTT compliance test. The DataTransfer message to send information for functions th…
- [TC_P_02_CSMS — Data Transfer to the CSMS - Rejected / Unknown VendorId / Unknown MessageId](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-p-02-csms): Data Transfer to the CSMS - Rejected / Unknown VendorId / Unknown MessageId (TC_P_02_CSMS) — OCPP 2.0.1 OCTT compliance test. The DataTransfer message to send information for functions that are not…
- [TC_P_03_CS — CustomData - Receive custom data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-p-03-cs): CustomData - Receive custom data (TC_P_03_CS) — OCPP 2.0.1 OCTT compliance test. Checks if the CS is able to receive custom data.
- [TC_P_03_CSMS — CustomData - Receive custom data](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases/tc-p-03-csms): CustomData - Receive custom data (TC_P_03_CSMS) — OCPP 2.0.1 OCTT compliance test. Checks if the CSMS is able to receive custom data.
- [OCPP 2.0.1 Test Cases](https://ocpplab.com/docs/guides/ocpp/2-0-1/test-cases): Index of all 365 OCPP 2.0.1 OCTT compliance test cases (230 Charge Point + 135 CSMS).
- [OCPP 2.0.1](https://ocpplab.com/docs/guides/ocpp/2-0-1): Simulating OCPP 2.0.1 chargers — the device model, TransactionEvent, security profiles, and variable reporting.
- [Connect a charger](https://ocpplab.com/docs/guides/ocpp/connect-charger): Point a charge point at the OCPPLab OCPP endpoint and verify BootNotification through a test session.
- [Connecting to your CPMS](https://ocpplab.com/docs/guides/ocpp/connecting-to-your-cpms): Point OCPPLab at your own Charge Point Management System — URLs, identities, security profiles, and troubleshooting.
- [Simulating a charger](https://ocpplab.com/docs/guides/ocpp/simulating-a-charger): Model a full charging session end to end — boot, status transitions, authorization, transaction, and meter values.
- [OCPP](https://ocpplab.com/docs/guides/ocpp): Connect and operate charge points over OCPP 1.6 and 2.0.1 with the OCPPLab gateway.
- [Architecture](https://ocpplab.com/docs/guides/platform/architecture): High-level OCPPLab architecture for OCPP, OCPI, data, and Dashboard.
- [Authorizations](https://ocpplab.com/docs/guides/platform/dashboard/authorizations): idTag and remote-start authorization outcomes for OCPP stations in the Dashboard.
- [Charge sessions](https://ocpplab.com/docs/guides/platform/dashboard/charge-sessions): OCPP charge sessions in Dashboard: energy, stop reasons, and how to open a test session.
- [Create a charger](https://ocpplab.com/docs/guides/platform/dashboard/create-charger): Tutorial: open the Create charger sheet and fill every field — identity, access, location, OCPP version, brand, model, and connectors.
- [Logs](https://ocpplab.com/docs/guides/platform/dashboard/logs): Explore charger and protocol messages in the Dashboard when diagnosing OCPP issues.
- [Managed chargers](https://ocpplab.com/docs/guides/platform/dashboard/managed-chargers): Fleet inventory of OCPP charge points: connection state, filters, and how to add a charger.
- [Observability](https://ocpplab.com/docs/guides/platform/dashboard/observability): Dashboard health hub and webhook automation: callbacks and delivery logs with screenshots.
- [OCPP map](https://ocpplab.com/docs/guides/platform/dashboard/ocpp-map): Geographic map of managed OCPP stations for dispatch and site context.
- [Operations home](https://ocpplab.com/docs/guides/platform/dashboard/operations-home): Dashboard home dashboard: Online, Offline, Stale, and Never connected counts plus connection exceptions.
- [Proxy](https://ocpplab.com/docs/guides/platform/dashboard/proxy): OCPP proxy in Dashboard: backends, chargers, routes, live sessions, and wire logs with screenshots.
- [Roaming](https://ocpplab.com/docs/guides/platform/dashboard/roaming): OCPI roaming in Dashboard: partners, partner operations, sync jobs, business details, map, and OCPI data modules with screenshots.
- [Tokens](https://ocpplab.com/docs/guides/platform/dashboard/tokens): Local RFID and token inventory used for OCPP authorization in the Dashboard.
- [Workspace](https://ocpplab.com/docs/guides/platform/dashboard/workspace): Account preferences, security, teams, business details, billing, usage, audit logs, and OAuth in the Dashboard.
- [Dashboard](https://ocpplab.com/docs/guides/platform/dashboard): Operator UI for OCPPLab: sidebar areas, page map, and tutorials with product screenshots.
- [Multi-backend routing](https://ocpplab.com/docs/guides/platform/proxy-routing): Route chargers to two CPMS backends, dual-run during migration, and cut over without changing field firmware.
- [Webhooks](https://ocpplab.com/docs/guides/platform/webhooks): Receive OCPPLab events in your own billing, CRM, or automation systems.
- [OCPPLab product](https://ocpplab.com/docs/guides/platform): Dashboard multi-page operator guides, architecture, and webhooks for the OCPPLab product.
- [Charger will not connect](https://ocpplab.com/docs/guides/troubleshooting/charger-will-not-connect): Diagnose OCPP WebSocket failures when a charge point never boots, drops immediately, or never sends BootNotification to OCPPLab.
- [OCPI handshake failures](https://ocpplab.com/docs/guides/troubleshooting/ocpi-handshake-failures): Diagnose OCPI versions and credentials exchange failures between OCPPLab and an eMSP or hub.
- [Troubleshooting](https://ocpplab.com/docs/guides/troubleshooting): Failure-mode landings for charger connections, OCPP sessions, and OCPI credentials handshakes on OCPPLab.

## Reference

- [Reference overview](https://ocpplab.com/docs/reference)

## Related

- [llms-full.txt](https://ocpplab.com/docs/llms-full.txt)
- [API alias llms.txt](https://ocpplab.com/docs/api/llms.txt)