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
We Installed max charge limit is 16A using MaxChargeProfile OCPP message.
When Phase switching is enabled, when the device is switched and charging in 1phase, if the new charging limit of more than 4.4KW is sent from OCPP using TxProfile, the device allows charging even with more than 20A on single phase instead of limiting to 16A.
Everest should limit the charge limit to 16A when phase switching from 1 to 3 or 3 to 1 phases.
Set max charge profile to 16A
Enable automatic phase switching
Send TX profile having power greater than 4.4 KW
Check the PWM value in logs, it should be greater than value of 16A
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
We Installed max charge limit is 16A using MaxChargeProfile OCPP message.
When Phase switching is enabled, when the device is switched and charging in 1phase, if the new charging limit of more than 4.4KW is sent from OCPP using TxProfile, the device allows charging even with more than 20A on single phase instead of limiting to 16A.
Everest should limit the charge limit to 16A when phase switching from 1 to 3 or 3 to 1 phases.
Please find attached screenshot for reference
charging-core-024-16022509.log


EVerest Domain
Energy Management, OCPP1.6, OCPP
Affected EVerest Module
OCPP, Automatic phase switching
To Reproduce
Set max charge profile to 16A
Enable automatic phase switching
Send TX profile having power greater than 4.4 KW
Check the PWM value in logs, it should be greater than value of 16A
Anything else?
No response
The text was updated successfully, but these errors were encountered: