OCPP 1.8.0

Implemented cloud-support for ChargingProfile purpose type 'TxProfile'

Caveats:

• TxProfile functionality limited to online chargers
• No stacking support for TxProfile
• Only absolute schedule type is supported
• Prior behaviour of ChargePointMaxProfile and TxDefaultProfile remains unchanged
• Schedules (periods and limits) created by TxDefaultProfile are not removed/reset and can interfere with TxProfile limits. In case of conflicts, attempt to clear these limits and re-apply TxProfile.

FAQs/Remarks:

This is a best effort implementation for ChargingProfile of type TxProfile meaning we support a basic implementation that does not cover all hardened scenarios.

Due to the cloud proxy architecture, the resulting current limits set by TxProfile requests will be propagated to the chargers as soon as they appear online, and the scheduled period is relevant. We will forward the request to the chargers and retry up to 3 times.

There could be other current limits competing with the TxProfile for example through an API call (a non-OCPP path) to the same charger with different current limits or limits set by an external/local energy management device. In this case the lowest limit takes precedence. Multiple chargers on the same circuit can use their load balancing functionality and therefore the effect might not be what the TxProfile limits intended.

We will continue to monitor and improve this feature but are aware that the direct OCPP implementation path is superior and has less issues to a cloud proxy implementation.

Examples can be found Here