Puh, da habe ich die OCPP-Spezifikation wohl falsch interpretiert. Fortan schicke ich nun immer ein startSchedule in SetChargingProfile.
Diese zwei Messages...
14:39:18.729 INFO OCPP: Sent following message to warp2-22p6: SetChargingProfile: {
"connectorId": 0,
"csChargingProfiles": {
"chargingProfileId": 256,
"stackLevel": 0,
"chargingProfilePurpose": "TxDefaultProfile",
"chargingProfileKind": "Absolute",
"chargingSchedule": {
"startSchedule": "2023-07-06T00:00:00Z",
"chargingRateUnit": "A",
"chargingSchedulePeriod": [
{
"startPeriod": 0,
"limit": 6
}
]
}
}
}
14:39:18.733 INFO OCPP: Sent following message to warp2-22p6: SetChargingProfile: {
"connectorId": 0,
"csChargingProfiles": {
"chargingProfileId": 1,
"stackLevel": 0,
"chargingProfilePurpose": "ChargePointMaxProfile",
"chargingProfileKind": "Absolute",
"chargingSchedule": {
"startSchedule": "2023-07-06T00:00:00Z",
"chargingRateUnit": "A",
"chargingSchedulePeriod": [
{
"startPeriod": 0,
"limit": 8
}
]
}
}
}
... führen nun wie erwartet zu:
2023-07-06 14:44:18,034 Evaluating charging profiles
2023-07-06 14:44:18,034 ChargePointMaxProfiles[0] applied.
2023-07-06 14:44:18,034 Connector 1
2023-07-06 14:44:18,045 TxDefaultProfiles[0] applied
2023-07-06 14:44:18,045 Profile evaluation done. Distributing limit
2023-07-06 14:44:18,055 Currents distributed:
2023-07-06 14:44:18,056 ConnID Allowed Phases MinRate
2023-07-06 14:44:18,066 0 8.000 3 0.000
2023-07-06 14:44:18,067 1 6.000 3 0.000
Vielen Dank!