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
noticing consistent 5-6% offset between "CP current setpoint" as sent by EVSE via CP vs. actual current drawn by EV OBC.
e.g. setpoint to charge = 16A, actual current drawn = 15.3A.
the same offset is present whether in SOLAR / SMART / NORMAL mode
also noticed that "MAINS L1" seems to be within 0.1A of "SET CURRENT".
is it possible that PWM correction is evaluated against "MAINS L1" instead of against "EV L1" ?
Describe the bug
noticing consistent 5-6% offset between "CP current setpoint" as sent by EVSE via CP vs. actual current drawn by EV OBC.
e.g. setpoint to charge = 16A, actual current drawn = 15.3A.
the same offset is present whether in SOLAR / SMART / NORMAL mode
also noticed that "MAINS L1" seems to be within 0.1A of "SET CURRENT".
is it possible that PWM correction is evaluated against "MAINS L1" instead of against "EV L1" ?
Upload your config
raw.json
Upload a debug log
To Reproduce
see above: always present
Expected behavior
actual current drawn by EV ~ EVSE current setpoint
Screenshots
![image](https://private-user-images.githubusercontent.com/99096767/327521254-52222438-dad8-4334-a76b-2b07480cbf02.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM5MDQ4NTQsIm5iZiI6MTcyMzkwNDU1NCwicGF0aCI6Ii85OTA5Njc2Ny8zMjc1MjEyNTQtNTIyMjI0MzgtZGFkOC00MzM0LWE3NmItMmIwNzQ4MGNiZjAyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE3VDE0MjIzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRjODVlYTIxMTI1Y2U5OTY3MzAxNWYxMDAzNjRjNzE3OWMzMjdlMTc4YjdmNWIyZTk1ZTI2NmM2YjU3OWRiNTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.fka9XuSb8Hel-I_wMSKkd5rvLMNMexzyWS6WG-je2N4)
The text was updated successfully, but these errors were encountered: