-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DVCC: Also control AC chargers and inverters #736
Comments
Assigning Martin, because there is a question about the Phoenix Smart IP43 Charger. It supports these vregs already:
But it does not currently support receiving VE_REG_LINK_VSENSE, VE_REG_LINK_TSENSE, and VE_REG_LINK_BATTERY_CURRENT (SVS, STS and SCS) from both VE.Smart networking and VE.Direct. If this is to be added as well, firmware work will be required. |
Hey @izak , Martin wont have time for this anytime soon. Pls start with a different charger model: the Skylla IP65 |
When you receive DCL=0, switch off inverters by setting /Mode=4. When manual switch is used, the inverter disappears from dbus. Hence we cannot accidentally turn an inverter on that was manually off. For Inverter-RS, simply copy DischargeCurrent across. Firmware already switches off. victronenergy/venus#736
Only allow DVCC to turn an inverter on, if it was previously turned off by DVCC. If inverter was soft-turned off manually, leave it off. victronenergy/venus#736
When you receive DCL=0, switch off inverters by setting /Mode=4. When manual switch is used, the inverter disappears from dbus. Hence we cannot accidentally turn an inverter on that was manually off. For Inverter-RS, simply copy DischargeCurrent across. Firmware already switches off. victronenergy/venus#736
Only allow DVCC to turn an inverter on, if it was previously turned off by DVCC. If inverter was soft-turned off manually, leave it off. victronenergy/venus#736
….74 & v2.75 Add full DVCC support for Inverter RS, including CVL, CCL, SVS, STS and SCS. Closes victronenergy/venus#803 Implement logic for ActiveAcIn in systemcalc so it can move out of the GUI Fix problem where grid meter reading disappears from GUI when Multi is off Fix hubtype indication Turning off a Multi in an ESS system would cause hubtype to change to Hub-1 Overview would change and Critical Loads block would disappear when turning off Multi. victronenergy/venus#806 Improve System State display In system without a Multi but w* dbus-generator v1.4.0 & v1.4.1 Update to python3 Fix unit tests broken since Venus 2.70.ith a managed battery, show when discharge is allowed/disallowed by battery Support for Lynx Smart BMS (Backported to 2.72~2 as patch) Stop all chargers when CCL=0 (charge current limit) is received. Switch off inverters when DCL=0 (discharge current limit) is received from a managed battery For Inverter RS, copy the the DCL to the inverter. Firmware 1.04 switches off inverter. For other inverters (not Multis), switch the inverter off by setting Mode to Off. victronenergy/venus#736 Fix possible crash when non-ascii character used in battery measurement name No actual cases found, part of a wider unicode cleanup Clean up BMS selection where there is another battery monitor in the system Since Venus 2.30, it is possible to set the battery monitor to a BMV, but still use the charge parameters from a BMS in the system. This hidden functionality is not shown anywhere, so instead remove it and make it simpler. victronenergy/venus#783 Force DVCC settings for pylontech batteries Set this as the documentation already advises: DVCC=on, SVS=off, STS=off. victronenergy/venus#784 Upgrade to Python3
For inverter control, this is now implemented such that systemcalc controls Phoenix VE.Direct Inverter via their normal on/off switch. And for that to properly work, Venus OS keeps state: ie it doesn’t switch an inverter on if it was first off. Which is not good enough. Its needs taking out. This whole issue came up for the Inverter RS, not for these Phoenix VE.Direct Inverters. So also no need to now add them in in a non proper manner. Control for Phoenix Inverters needs to be removed, including its keeping state. While keeping the Inverter RS part in. And then leave it like that: Phoenix Inverters with VE.Direct port are simply not supported at the moment. And then some day we can make it properly, including a fw change of the PHoenix Inverter VE.Direct; but not now since that team has other prios. |
This is much better done in firmware in future. For now we support only InverterRS. This reverts d872937. This partially reverts d47c0e3. victronenergy/venus#736
Remove DVCC support for Phoenix inverters (note: Inverter RS is still supported) It is better implemented as Link Vregs in firmware. victronenergy/venus#736 Add venus version and build date/time to dbus/mqtt For use in html5 app Closes victronenergy/venus#838 Add support for fuel cell devices This adds support for accounting of DC power, or using a fuel cell as a voltage measuring service. Add AC-input summary for UIs (GUI, VRM) so they know what inputs are available, used, and where to find data for it. victronenergy/venus#843
Some investigation today: It doesn't look as if the Skylla IP65 supports VE_REG_LINK_NETWORK_MODE, and writing to VE_REG_LINK_VSET is not supported. The charger has firmware |
@izak what is the status on this? Iirc you worked on it with Martin for the Phoenix IP43 charger rev 2, connected via VE.Direct? (and the rev1 model won't get this due to hardware limitations). Basically, what I want to know is what has changed between v2.73 and v2.80-now. And what will then remain to be done later. Also for changelog and documentation. |
I started working on it and found that basically none of our chargers supported the VREGs required for this. Martin then added them for the Phoenix IP43 charger. He also made changes to systemcalc to test it, but I have yet to look at his changes and possibly incorporate them. What needs a bit more thought is prioritising solar over AC chargers, something I don't think has been done. |
This is implemented in vedirect-interface v3.67, included in venus 2.80~27. |
removed from v2.90 milestone; its not finished, and not important enough to delay v2.90 any further either. |
When will this be integrated? Currently the Multiplus II is not following DCL=0 or CCL=0 but still charging/discharging the battery even though forbidden by the battery. It could drive battery into overvoltage or undervoltage. DCL=0 and DCL=0 must be followed under all circumstances. . Also Modbus register 38 is not working like documented. |
Also interested in this functionality as I have a Phoenix Smart Charger (VE.Direct HW Rev 2) that I would very much like to get under DVCC control. I am willing to help code and/or test, with some guidance, if it would speed things along. Cheers |
Todo list
Limitations
The text was updated successfully, but these errors were encountered: