You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the OCPP 1.6 spec (section 3.13.1, pg 20) ChargePointMaxProfile can only be set at Charge Point ConnectorId 0. Additionally, it should limit the power or current to be shared by all connectors of the Charge Point. What I have experienced is that ChargePointMaxProfile is currently being applied in a per connector basis and not shared by all connectors.
If I set a limit of 5000 W, the total load is 10000 W:
Perhaps more important is to check if the same occurs with MicroOcpp.
The text was updated successfully, but these errors were encountered:
True, good finding! I missed that part completely when creating the Simulator. It needs an additional internal load balancer to handle ChargePointMaxProfiles.
This indeed reflects the behavior of the MicroOcpp core library. MicroOcpp does not come with an internal load balancer, but assumes that the host firmware implements it (which would be the Simulator here). I definitely need to point that out in the documentation there too, thanks for the reminder.
Hello, thanks again for this amazing tool.
As per the OCPP 1.6 spec (section 3.13.1, pg 20)
ChargePointMaxProfile
can only be set at Charge Point ConnectorId 0. Additionally, it should limit the power or current to be shared by all connectors of the Charge Point. What I have experienced is thatChargePointMaxProfile
is currently being applied in a per connector basis and not shared by all connectors.If I set a limit of 5000 W, the total load is 10000 W:
![image](https://private-user-images.githubusercontent.com/5142420/330121624-6b79b1cf-58b5-44e4-ba14-d124b493df13.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzI0MzcsIm5iZiI6MTczOTMzMjEzNywicGF0aCI6Ii81MTQyNDIwLzMzMDEyMTYyNC02Yjc5YjFjZi01OGI1LTQ0ZTQtYmExNC1kMTI0YjQ5M2RmMTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTJUMDM0ODU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZWMzZWU2OTllZjFjYjIyMWEyZjk1ODcwOWIxNjNmODAzYzMxYjc0NmMyNzRmMzcxNTliMzg0YWNlYTVjMDFiOSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.6MmU82u_FelY27RoNYIgM0r164nC9Pz0w6zgPm_UwWY)
Perhaps more important is to check if the same occurs with MicroOcpp.
The text was updated successfully, but these errors were encountered: