Generate OCPP 2.1 public draft messages #845

hikinggrass · 2024-10-23T14:22:01Z

Describe your changes

First draft of changes needed to include 2.1 messages. At the moment this contains certain (arguably a bit hacky) code generator changes to generate new 2.1 messages in their own namespace, while changing 2.0.1 message definitions based on the 2.1 schemas. Here we need a bit more fine-grained handling

Issue ticket number and link

Checklist before requesting a review

I have performed a self-review of my code
I have made corresponding changes to the documentation
If OCPP 2.0.1: I have updated the OCPP 2.0.1 status document
I read the contribution documentation and made sure that my changes meet its requirements

Signed-off-by: Kai-Uwe Hermann <[email protected]>

…more Signed-off-by: Kai-Uwe Hermann <[email protected]>

Signed-off-by: Kai-Uwe Hermann <[email protected]>

…rator Signed-off-by: Kai-Uwe Hermann <[email protected]>

…c-draft-messages # Conflicts: # include/ocpp/v201/messages/Get15118EVCertificate.hpp # lib/ocpp/v201/profile.cpp # src/code_generator/common/generate_cpp.py

hikinggrass · 2024-10-23T14:24:13Z

include/ocpp/v201/charge_point_callbacks.hpp

@@ -74,8 +74,8 @@ struct Callbacks {
    /// \return True if evse is reserved for the given id token / group id token, false if it is reserved for another
    ///         one.
    ///
-    std::function<bool(const int32_t evse_id, const CiString<36> idToken,
-                       const std::optional<CiString<36>> groupIdToken)>
+    std::function<bool(const int32_t evse_id, const CiString<255> idToken,


This isn't really a backwards-compatible change in the 2.1 schemas. Changes like this happened in a few different messages/types and need case-by-case handling. Either by adding additional conversion functions or different message generation for 2.0.1 and 2.1

Should be ok to accept larger tokens here. This is only an issue if e.g. OCTT tests for OCPP2.0.1 if we accept larger tokens.

hikinggrass · 2024-10-23T14:26:26Z

include/ocpp/v201/messages/Authorize.hpp

@@ -19,7 +19,7 @@ namespace v201 {
 struct AuthorizeRequest : public ocpp::Message {
    IdToken idToken;
    std::optional<CustomData> customData;
-    std::optional<CiString<5500>> certificate;
+    std::optional<CiString<10000>> certificate;


This could probably be reported via FieldLength variable for the AuthorizeRequest.certificate instance which should make this change backwards-compatible with 2.0.1

hikinggrass · 2024-10-23T14:27:40Z

include/ocpp/v201/messages/Get15118EVCertificate.hpp

@@ -20,8 +20,10 @@ namespace v201 {
 struct Get15118EVCertificateRequest : public ocpp::Message {
    CiString<50> iso15118SchemaVersion;
    CertificateActionEnum action;
-    CiString<5600> exiRequest;
+    CiString<11000> exiRequest;


Adding a FieldLength variable for Get15118EVCertificateRequest.exiRequest should make this backwards-compatible with 2.0.1

hikinggrass · 2024-10-23T14:28:29Z

include/ocpp/v201/messages/GetCertificateStatus.hpp

@@ -40,7 +40,7 @@ struct GetCertificateStatusResponse : public ocpp::Message {
    GetCertificateStatusEnum status;
    std::optional<CustomData> customData;
    std::optional<StatusInfo> statusInfo;
-    std::optional<CiString<5500>> ocspResult;
+    std::optional<CiString<18000>> ocspResult;


Adding a FieldLength variable for GetCertificateStatusResponse.ocspResult should make this backwards-compatible with 2.0.1

hikinggrass · 2024-10-23T14:29:03Z

include/ocpp/v201/messages/InstallCertificate.hpp

@@ -18,7 +18,7 @@ namespace v201 {
 /// \brief Contains a OCPP InstallCertificate message
 struct InstallCertificateRequest : public ocpp::Message {
    InstallCertificateUseEnum certificateType;
-    CiString<5500> certificate;
+    CiString<10000> certificate;


Adding a FieldLength variable for InstallCertificateRequest.certificate should make this backwards-compatible with 2.0.1

hikinggrass · 2024-10-23T14:29:32Z

include/ocpp/v201/messages/PublishFirmware.hpp

@@ -17,7 +17,7 @@ namespace v201 {

 /// \brief Contains a OCPP PublishFirmware message
 struct PublishFirmwareRequest : public ocpp::Message {
-    CiString<512> location;
+    CiString<2000> location;


Adding a FieldLength variable for PublishFirmwareRequest.location should make this backwards-compatible with 2.0.1

hikinggrass · 2024-10-23T14:29:46Z

include/ocpp/v201/messages/PublishFirmwareStatusNotification.hpp

@@ -19,8 +19,9 @@ namespace v201 {
 struct PublishFirmwareStatusNotificationRequest : public ocpp::Message {
    PublishFirmwareStatusEnum status;
    std::optional<CustomData> customData;
-    std::optional<std::vector<CiString<512>>> location;
+    std::optional<std::vector<CiString<2000>>> location;


Adding a FieldLength variable for PublishFirmwareStatusNotificationRequest.location should make this backwards-compatible with 2.0.1

hikinggrass · 2024-10-23T14:30:50Z

include/ocpp/v201/messages/TransactionEvent.hpp

    std::optional<std::vector<MeterValue>> meterValue;
    std::optional<bool> offline;
    std::optional<int32_t> numberOfPhasesUsed;
-    std::optional<int32_t> cableMaxCurrent;
+    std::optional<float> cableMaxCurrent;


This isn't strictly backwards compatible with 2.0.1 and probably needs additional handling

This change doesnt seem to make a lot of sense. In transaction_event_req we could continue to use an int and make an implicit cast to float

We should make sure that the float is serialized to an int in 2.0.1 when transmitting to the CSMS.

hikinggrass · 2024-10-23T14:32:58Z

include/ocpp/v201/ocpp_types.hpp

 struct AdditionalInfo {
-    CiString<36> additionalIdToken;
+    CiString<255> additionalIdToken;


TODO: find out implications for backwards compatibility with 2.0.1

Our best chance is to allow 255 here since we can then try to send to the CSMS. If the CSMS can handle it - fine. If it cant, we have at least tried and the CSMS will likely respond with a CALLERROR

hikinggrass · 2024-10-23T14:33:06Z

include/ocpp/v201/ocpp_types.hpp

@@ -34,8 +64,8 @@ void from_json(const json& j, AdditionalInfo& k);
 std::ostream& operator<<(std::ostream& os, const AdditionalInfo& k);

 struct IdToken {
-    CiString<36> idToken;
-    IdTokenEnum type;
+    CiString<255> idToken;


TODO: find out implications for backwards compatibility with 2.0.1

Our best chance is to allow 255 here since we can then try to send to the CSMS. If the CSMS can handle it - fine. If it cant, we have at least tried and the CSMS will likely respond with a CALLERROR

hikinggrass · 2024-10-23T14:33:14Z

include/ocpp/v201/ocpp_types.hpp

@@ -54,7 +84,7 @@ struct OCSPRequestData {
    CiString<128> issuerNameHash;
    CiString<128> issuerKeyHash;
    CiString<40> serialNumber;
-    CiString<512> responderURL;
+    CiString<2000> responderURL;


TODO: find out implications for backwards compatibility with 2.0.1

Same argument like with the id token. Lets allow the larger value here.

hikinggrass · 2024-10-23T14:33:22Z

include/ocpp/v201/ocpp_types.hpp

@@ -69,7 +99,7 @@ std::ostream& operator<<(std::ostream& os, const OCSPRequestData& k);

 struct MessageContent {
    MessageFormatEnum format;
-    CiString<512> content;
+    CiString<1024> content;


TODO: find out implications for backwards compatibility with 2.0.1

Allow since its from CSMS

hikinggrass · 2024-10-23T14:34:44Z

include/ocpp/v201/ocpp_types.hpp

    std::optional<CustomData> customData;
+    std::optional<float> limit;


TODO: find out implications for backwards compatibility with 2.0.1
This was required in 2.0.1 and is optional now in 2.1

Thats ok as long as we make sure that we always set this limit for v201 (which we do because it was required before).

hikinggrass · 2024-10-23T14:35:13Z

include/ocpp/v201/ocpp_types.hpp

@@ -285,7 +893,7 @@ void from_json(const json& j, CertificateHashDataChain& k);
 std::ostream& operator<<(std::ostream& os, const CertificateHashDataChain& k);

 struct LogParameters {
-    CiString<512> remoteLocation;
+    CiString<2000> remoteLocation;


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:36:04Z

include/ocpp/v201/ocpp_types.hpp

+    std::optional<CiString<50>> signingMethod;
+    std::optional<CiString<2500>> publicKey;


TODO: find out implications for backwards compatibility with 2.0.1
These two fields were required in 2.0.1 and are now optional in 2.1

Here we should implement different handling for 2.0.1 and 2.1 in the respective message handling

hikinggrass · 2024-10-23T14:37:08Z

include/ocpp/v201/ocpp_types.hpp

+    float energyAmount;
+    float evMinCurrent;
+    float evMaxCurrent;
+    float evMaxVoltage;


TODO: find out implications for backwards compatibility with 2.0.1
type change from int to float

Accept the change. We dont have any handling in libocpp with this type. We should implement different handling for 2.0.1 and 2.1 and make sure that the float is serialized to an int in 2.0.1 when transmitting to the CSMS.

hikinggrass · 2024-10-23T14:37:38Z

include/ocpp/v201/ocpp_types.hpp

+    float evMaxCurrent;
+    float evMaxVoltage;
    std::optional<CustomData> customData;
-    std::optional<int32_t> energyAmount;
-    std::optional<int32_t> evMaxPower;
+    std::optional<float> evMaxPower;
+    std::optional<float> evEnergyCapacity;
+    std::optional<float> energyAmount;


TODO: find out implications for backwards compatibility with 2.0.1
type change from int to float

Accept the change. We dont have any handling in libocpp with this type. We should implement different handling for 2.0.1 and 2.1 and make sure that the float is serialized to an int in 2.0.1 when transmitting to the CSMS.

hikinggrass · 2024-10-23T14:38:15Z

include/ocpp/v201/ocpp_types.hpp

    CiString<255> key;
    VPNEnum type;
    std::optional<CustomData> customData;
-    std::optional<CiString<20>> group;
+    std::optional<CiString<50>> group;


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:38:31Z

include/ocpp/v201/ocpp_types.hpp

    int32_t messageTimeout;
+    CiString<2000> ocppCsmsUrl;


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:38:42Z

include/ocpp/v201/ocpp_types.hpp

@@ -890,7 +1992,7 @@ void from_json(const json& j, SetMonitoringResult& k);
 std::ostream& operator<<(std::ostream& os, const SetMonitoringResult& k);

 struct SetVariableData {
-    CiString<1000> attributeValue;
+    CiString<2500> attributeValue;


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:39:00Z

include/ocpp/v201/ocpp_types.hpp

@@ -943,7 +2132,7 @@ void from_json(const json& j, Transaction& k);
 std::ostream& operator<<(std::ostream& os, const Transaction& k);

 struct Firmware {
-    CiString<512> location;
+    CiString<2000> location;


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:39:30Z

include/ocpp/v201/types.hpp

+namespace ChargingLimitSourceEnumStringType {
+inline const CiString<20> EMS = "EMS";
+inline const CiString<20> OTHER = "Other";
+inline const CiString<20> SO = "SO";
+inline const CiString<20> CSO = "CSO";
+} // namespace ChargingLimitSourceEnumStringType
+
+namespace IdTokenEnumStringType {
+inline const CiString<20> Value = "Value";
+inline const CiString<20> Central = "Central";
+inline const CiString<20> DirectPayment = "DirectPayment";
+inline const CiString<20> eMAID = "eMAID";
+inline const CiString<20> EVCCID = "EVCCID";
+inline const CiString<20> ISO14443 = "ISO14443";
+inline const CiString<20> ISO15693 = "ISO15693";
+inline const CiString<20> KeyCode = "KeyCode";
+inline const CiString<20> Local = "Local";
+inline const CiString<20> MacAddress = "MacAddress";
+inline const CiString<20> NEMA = "NEMA";
+inline const CiString<20> NoAuthorization = "NoAuthorization";
+inline const CiString<20> VIN = "VIN";
+} // namespace IdTokenEnumStringType


TODO: move this to constants.hpp

hikinggrass · 2024-10-23T14:40:17Z

lib/ocpp/v201/charge_point.cpp

@@ -792,7 +792,7 @@ std::optional<std::string> ChargePoint::get_evse_transaction_id(int32_t evse_id)
    return evse.get_transaction()->transactionId.get();
 }

-AuthorizeResponse ChargePoint::validate_token(const IdToken id_token, const std::optional<CiString<5500>>& certificate,
+AuthorizeResponse ChargePoint::validate_token(const IdToken id_token, const std::optional<CiString<10000>>& certificate,


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:40:29Z

lib/ocpp/v201/charge_point.cpp

@@ -1929,8 +1929,8 @@ bool ChargePoint::is_evse_reserved_for_other(EvseInterface& evse, const IdToken&
        const ConnectorStatusEnum status =
            evse.get_connector(static_cast<int32_t>(i))->get_effective_connector_status();
        if (status == ConnectorStatusEnum::Reserved) {
-            const std::optional<CiString<36>> groupIdToken =
-                group_id_token.has_value() ? group_id_token.value().idToken : std::optional<CiString<36>>{};
+            const std::optional<CiString<255>> groupIdToken =


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:40:36Z

lib/ocpp/v201/charge_point.cpp

@@ -2113,7 +2113,7 @@ void ChargePoint::notify_report_req(const int request_id, const std::vector<Repo
    }
 }

-AuthorizeResponse ChargePoint::authorize_req(const IdToken id_token, const std::optional<CiString<5500>>& certificate,
+AuthorizeResponse ChargePoint::authorize_req(const IdToken id_token, const std::optional<CiString<10000>>& certificate,


TODO: find out implications for backwards compatibility with 2.0.1

hikinggrass · 2024-10-23T14:41:34Z

lib/ocpp/v201/profile.cpp

@@ -102,7 +102,7 @@ void period_entry_t::init(const DateTime& in_start, int in_duration, const Charg
    const auto start_tp = std::chrono::floor<seconds>(in_start.to_time_point());
    start = std::move(DateTime(start_tp + seconds(in_period.startPeriod)));
    end = std::move(DateTime(start_tp + seconds(in_duration)));
-    limit = in_period.limit;
+    limit = in_period.limit.value_or(0); // FIXME


TODO: find out implications for backwards compatibility with 2.0.1
(limit became optional)

hikinggrass · 2024-10-23T14:41:58Z

lib/ocpp/v201/profile.cpp

+    } else if (candidate_period.limit.has_value()) {
        const auto charge_point_max_phases = candidate_period.numberPhases.value_or(default_number_phases);

        const auto period_max_phases = prevailing_period.numberPhases.value_or(default_number_phases);
        adjusted_period.numberPhases = std::min(charge_point_max_phases, period_max_phases);

        if (current_charging_rate_unit_enum == ChargingRateUnitEnum::A) {
-            if (candidate_period.limit < prevailing_period.limit) {
-                adjusted_period.limit = candidate_period.limit;
+            if (candidate_period.limit.value() < prevailing_period.limit.value_or(DEFAULT_LIMIT_AMPS)) {
+                adjusted_period.limit = candidate_period.limit.value();
            }
        } else {
-            const auto charge_point_limit_per_phase = candidate_period.limit / charge_point_max_phases;
-            const auto period_limit_per_phase = prevailing_period.limit / period_max_phases;
+            const auto charge_point_limit_per_phase = candidate_period.limit.value() / charge_point_max_phases;
+            const auto period_limit_per_phase = prevailing_period.limit.value_or(0) / period_max_phases; // FIXME



TODO: find out implications for backwards compatibility with 2.0.1
(limit became optional)

Still a lot of failures, likely from the extension/modification if ChargingSchedulePerios (limit becoming optional) Signed-off-by: Kai-Uwe Hermann <[email protected]>

Signed-off-by: Kai-Uwe Hermann <[email protected]>

…c-draft-messages # Conflicts: # lib/ocpp/v201/charge_point.cpp # lib/ocpp/v201/smart_charging.cpp # tests/lib/ocpp/v201/mocks/smart_charging_handler_mock.hpp # tests/lib/ocpp/v201/test_charge_point.cpp Signed-off-by: Kai-Uwe Hermann <[email protected]>

Signed-off-by: Kai-Uwe Hermann <[email protected]>

This was broken in an earlier attempt to adapt it to the optional "limit" Signed-off-by: Kai-Uwe Hermann <[email protected]>

Signed-off-by: Kai-Uwe Hermann <[email protected]>

…c-draft-messages # Conflicts: # lib/ocpp/v201/profile.cpp # tests/lib/ocpp/v201/test_charge_point.cpp # tests/lib/ocpp/v201/test_composite_schedule.cpp # tests/lib/ocpp/v201/test_database_handler.cpp # tests/lib/ocpp/v201/test_profile.cpp Signed-off-by: Kai-Uwe Hermann <[email protected]>

Signed-off-by: Kai-Uwe Hermann <[email protected]>

…c-draft-messages Signed-off-by: Kai-Uwe Hermann <[email protected]>

Pietfried · 2024-11-14T11:30:03Z

include/ocpp/v201/charge_point_callbacks.hpp

@@ -74,8 +74,8 @@ struct Callbacks {
    /// \return True if evse is reserved for the given id token / group id token, false if it is reserved for another
    ///         one.
    ///
-    std::function<bool(const int32_t evse_id, const CiString<36> idToken,
-                       const std::optional<CiString<36>> groupIdToken)>
+    std::function<bool(const int32_t evse_id, const CiString<255> idToken,


Should be ok to accept larger tokens here. This is only an issue if e.g. OCTT tests for OCPP2.0.1 if we accept larger tokens.

Pietfried · 2024-11-14T11:36:38Z

include/ocpp/v201/messages/TransactionEvent.hpp

    std::optional<std::vector<MeterValue>> meterValue;
    std::optional<bool> offline;
    std::optional<int32_t> numberOfPhasesUsed;
-    std::optional<int32_t> cableMaxCurrent;
+    std::optional<float> cableMaxCurrent;


This change doesnt seem to make a lot of sense. In transaction_event_req we could continue to use an int and make an implicit cast to float

We should make sure that the float is serialized to an int in 2.0.1 when transmitting to the CSMS.

Pietfried · 2024-11-14T11:43:42Z

include/ocpp/v201/ocpp_types.hpp

 struct AdditionalInfo {
-    CiString<36> additionalIdToken;
+    CiString<255> additionalIdToken;


Our best chance is to allow 255 here since we can then try to send to the CSMS. If the CSMS can handle it - fine. If it cant, we have at least tried and the CSMS will likely respond with a CALLERROR

Pietfried · 2024-11-14T11:44:56Z

include/ocpp/v201/ocpp_types.hpp

@@ -34,8 +64,8 @@ void from_json(const json& j, AdditionalInfo& k);
 std::ostream& operator<<(std::ostream& os, const AdditionalInfo& k);

 struct IdToken {
-    CiString<36> idToken;
-    IdTokenEnum type;
+    CiString<255> idToken;


Our best chance is to allow 255 here since we can then try to send to the CSMS. If the CSMS can handle it - fine. If it cant, we have at least tried and the CSMS will likely respond with a CALLERROR

Pietfried · 2024-11-14T11:46:00Z

include/ocpp/v201/ocpp_types.hpp

@@ -54,7 +84,7 @@ struct OCSPRequestData {
    CiString<128> issuerNameHash;
    CiString<128> issuerKeyHash;
    CiString<40> serialNumber;
-    CiString<512> responderURL;
+    CiString<2000> responderURL;


Same argument like with the id token. Lets allow the larger value here.

Pietfried · 2024-11-14T12:11:32Z

include/ocpp/v201/ocpp_types.hpp

@@ -890,7 +1992,7 @@ void from_json(const json& j, SetMonitoringResult& k);
 std::ostream& operator<<(std::ostream& os, const SetMonitoringResult& k);

 struct SetVariableData {
-    CiString<1000> attributeValue;
+    CiString<2500> attributeValue;


Pietfried · 2024-11-14T12:11:44Z

include/ocpp/v201/ocpp_types.hpp

@@ -943,7 +2132,7 @@ void from_json(const json& j, Transaction& k);
 std::ostream& operator<<(std::ostream& os, const Transaction& k);

 struct Firmware {
-    CiString<512> location;
+    CiString<2000> location;


Pietfried · 2024-11-14T12:13:31Z

lib/ocpp/v201/charge_point.cpp

@@ -792,7 +792,7 @@ std::optional<std::string> ChargePoint::get_evse_transaction_id(int32_t evse_id)
    return evse.get_transaction()->transactionId.get();
 }

-AuthorizeResponse ChargePoint::validate_token(const IdToken id_token, const std::optional<CiString<5500>>& certificate,
+AuthorizeResponse ChargePoint::validate_token(const IdToken id_token, const std::optional<CiString<10000>>& certificate,


Pietfried · 2024-11-14T12:13:45Z

lib/ocpp/v201/charge_point.cpp

@@ -1929,8 +1929,8 @@ bool ChargePoint::is_evse_reserved_for_other(EvseInterface& evse, const IdToken&
        const ConnectorStatusEnum status =
            evse.get_connector(static_cast<int32_t>(i))->get_effective_connector_status();
        if (status == ConnectorStatusEnum::Reserved) {
-            const std::optional<CiString<36>> groupIdToken =
-                group_id_token.has_value() ? group_id_token.value().idToken : std::optional<CiString<36>>{};
+            const std::optional<CiString<255>> groupIdToken =


Pietfried · 2024-11-14T12:14:03Z

lib/ocpp/v201/charge_point.cpp

@@ -2113,7 +2113,7 @@ void ChargePoint::notify_report_req(const int request_id, const std::vector<Repo
    }
 }

-AuthorizeResponse ChargePoint::authorize_req(const IdToken id_token, const std::optional<CiString<5500>>& certificate,
+AuthorizeResponse ChargePoint::authorize_req(const IdToken id_token, const std::optional<CiString<10000>>& certificate,


tests/lib/ocpp/v201/test_profile.cpp

Signed-off-by: Piet Gömpel <[email protected]>

hikinggrass added 7 commits October 7, 2024 18:44

Fix code generator to include manual fixes for 2.0.1 VariableAttribute

1abd2bb

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Fix code generator to remove superfluous ; after DateTime conversions

780572c

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Remove SecurityEvent enum from code generator since it is no enum any…

70e7dd7

…more Signed-off-by: Kai-Uwe Hermann <[email protected]>

1.6: retrieveDateTime in SignedUpdateFirmware.firmware is not optional

dd95a43

Signed-off-by: Kai-Uwe Hermann <[email protected]>

WIP: generate 2.0.1 messages from 2.1 draft schemas

a882867

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Generate OCPP 2.1 messages from draft schemas with modified code gene…

17b736e

…rator Signed-off-by: Kai-Uwe Hermann <[email protected]>

Merge remote-tracking branch 'origin/main' into feature/ocpp2.1-publi…

0492085

…c-draft-messages # Conflicts: # include/ocpp/v201/messages/Get15118EVCertificate.hpp # lib/ocpp/v201/profile.cpp # src/code_generator/common/generate_cpp.py

hikinggrass commented Oct 23, 2024

View reviewed changes

hikinggrass added 12 commits October 24, 2024 18:56

Fix compilation of smart charging tests

59d1361

Still a lot of failures, likely from the extension/modification if ChargingSchedulePerios (limit becoming optional) Signed-off-by: Kai-Uwe Hermann <[email protected]>

Attempt to fix unchecked optional access in calculate_composite_schedule

a3e730f

Signed-off-by: Kai-Uwe Hermann <[email protected]>

More fixes for smart charging tests

ab4f806

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Additional fixes

cb9e57e

Signed-off-by: Kai-Uwe Hermann <[email protected]>

ctest: output on failure

ada40cb

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Fix composite schedule calculation

03e55cd

This was broken in an earlier attempt to adapt it to the optional "limit" Signed-off-by: Kai-Uwe Hermann <[email protected]>

clang-format

2f0d9f3

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Fix enum usage in tests for enums that turned into strings

5800478

Signed-off-by: Kai-Uwe Hermann <[email protected]>

FIXME: re-introduce default limit temporarily

4dfd843

Signed-off-by: Kai-Uwe Hermann <[email protected]>

Merge remote-tracking branch 'origin/main' into feature/ocpp2.1-publi…

b14ec4b

…c-draft-messages Signed-off-by: Kai-Uwe Hermann <[email protected]>

Pietfried reviewed Nov 14, 2024

View reviewed changes

tests/lib/ocpp/v201/test_profile.cpp Show resolved Hide resolved

Update tests/lib/ocpp/v201/test_profile.cpp

06b4919

Signed-off-by: Piet Gömpel <[email protected]>

		std::optional<CustomData> customData;
		std::optional<float> limit;

		std::optional<CiString<50>> signingMethod;
		std::optional<CiString<2500>> publicKey;

Generate OCPP 2.1 public draft messages #845

Are you sure you want to change the base?

Generate OCPP 2.1 public draft messages #845

Conversation

hikinggrass commented Oct 23, 2024

Describe your changes

Issue ticket number and link

Checklist before requesting a review

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment