ess:ess_mode_2_and_3
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ess:ess_mode_2_and_3 [2019-01-21 11:10] – [DISQUS] ictbeheer | ess:ess_mode_2_and_3 [2020-02-17 09:55] – [1.3 - Mode 3] iburger | ||
---|---|---|---|
Line 26: | Line 26: | ||
Necessary Victron equipment: | Necessary Victron equipment: | ||
* Multi or Quattro inverter/ | * Multi or Quattro inverter/ | ||
- | * [[venus-os: | + | * [[venus-os: |
* Note that there is no AC sensor necessary, since the inverter/ | * Note that there is no AC sensor necessary, since the inverter/ | ||
- | Available control points include the switch (on, charger-only, | + | Available control points include the switch (on, charger-only, |
+ | |||
+ | === Mode 3 with a managed battery === | ||
+ | When using Mode 3 with a managed battery, please note that the maximum discharge current sent by the battery will be ignored. The implemented control loop should take care of discharge limits communicated by the battery. | ||
+ | |||
+ | The exception to the above rule is a zero discharge limit. If a managed battery requests a zero discharge limit, the Multi will stop discharging the battery. | ||
+ | * If grid power is available, the Multi will go into passthru. | ||
+ | * If grid power is not available, the Multi will switch off. | ||
+ | |||
+ | The maximum charge current sent by a managed battery is however always heeded and cannot be overruled by the setpoint. | ||
- | Similar to Mode 2, there are various ways to access those control points. | ||
===== 2. Mode 2 in detail ===== | ===== 2. Mode 2 in detail ===== | ||
Line 64: | Line 72: | ||
For more information, | For more information, | ||
- | MQTT is available both on the local broker on the [[venus-os: | + | MQTT is available both on the local broker on the [[venus-os: |
=== C) Running your own scripts on the CCGX === | === C) Running your own scripts on the CCGX === | ||
Line 256: | Line 264: | ||
* As an alternative to running the control loop externally, using ModbusTCP, it is also possible to run code on the CCGX itself and update the AcPowerSetpoint via D-Bus. We have one customer that is running a MQTT client on the CCGX, written in Python, that gets the control-loop output as updates from a MQTT broker. And the Python script sends them to the Multi, using D-Bus service com.victronenergy.vebus.ttyO1, | * As an alternative to running the control loop externally, using ModbusTCP, it is also possible to run code on the CCGX itself and update the AcPowerSetpoint via D-Bus. We have one customer that is running a MQTT client on the CCGX, written in Python, that gets the control-loop output as updates from a MQTT broker. And the Python script sends them to the Multi, using D-Bus service com.victronenergy.vebus.ttyO1, | ||
- | ===== 5. Response times ===== | + | ===== 5. Response times and ramp speed ===== |
- | Depending on which components | + | There are multiple |
- | The (now deprecated) Hub-4 Assistant | + | |
- | + | - Rate limiting imposed by the used Country Grid code. Code " | |
- | The ESS Assistant | + | - Hard coded rate limiting in the inverter/ |
- | + | ||
- | Background: late 2016, we copied the Hub-4 Assistant, and named the copy "ESS Assistant" | + | |
===== 6. Further examples for external control ===== | ===== 6. Further examples for external control ===== | ||
Line 322: | Line 328: | ||
* Set register 39 to 0 | * Set register 39 to 0 | ||
* Set register 37 to -1000 | * Set register 37 to -1000 | ||
+ | |||
+ | ===== DISQUS ===== | ||
+ | ~~DISQUS~~ | ||
ess/ess_mode_2_and_3.txt · Last modified: 2023-02-14 15:25 by mvader