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-08-15 12:39] – replace venus-device with GX device guy_stewart | ess:ess_mode_2_and_3 [2020-02-17 13:52] – [1.3 - Mode 3] changed mode 3 CANbus battery information (DCL ignored) boekel | ||
---|---|---|---|
Line 29: | Line 29: | ||
* 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 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 256: | Line 260: | ||
* 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 are used, and from which point the communication is sent to the inverter, there are several factors involved in the response time: the Color Control GX, ModbusTCP, MK3 microprocessor, | + | |
- | + | ||
- | The (now deprecated) Hub-4 Assistant had no rate limiter. | + | |
- | The ESS Assistant has a rate limiter. In the currently latest version | + | There are multiple factors that determine |
- | Background: late 2016, we copied the Hub-4 Assistant, | + | - Latency and communication speed of all components in the communication chain: ModbusTCP or MQTT, GX Device, MK3 microprocessor, |
+ | - Rate limiting imposed by the used Country Grid code. Code "Other" | ||
+ | | ||
===== 6. Further examples for external control ===== | ===== 6. Further examples for external control ===== |
ess/ess_mode_2_and_3.txt · Last modified: 2023-02-14 15:25 by mvader