The solution I proposed above is great if it is to always keep the AC input current limit at the same value (and this value being lower than the minimum configurable value when Power Assist is enabled). But it is an impractical solution if you need to change the configured limit, because you will need to do it through VE Configure, enabling or disabling PowerAssist, inserting or removing the assistants and changing the AC load value in the assistants that causes the AC input to be ignored. A better, much more practical solution would be to automate all of this through Node Red, configuring everything according to the current limit set by the console. I tried to do this, but I encountered a difficulty: when Power Assist is enabled, and a current limit value is entered through the console that is lower than the minimum acceptable value when Power Assist is enabled, the value entered is automatically replaced by the minimum value, and I cannot get the value that was entered in Node Red to be able to disable Power Assist. I talked about this in this other post, let’s see if a solution appears for this.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Way to disable AC charging | 35 | 978 | 14 January 2025 | |
48v Multiplus-II input current limit from AC: arbitrary minimum threshold? | 2 | 311 | 13 June 2025 | |
Node-RED flow to set low current limit on AC input | 0 | 45 | 26 June 2025 | |
MultiPlus II dynamic charge current limit based on AC load (with no ESS] | 15 | 507 | 1 March 2025 | |
Exactly how BoostFactor works? | 24 | 654 | 9 May 2025 |