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 revision | ||
| ess:ess_mode_2_and_3 [2020-02-10 16:00] – [5. Response times and ramp speed] mvader | ess:ess_mode_2_and_3 [2024-10-14 15:20] (current) – [2.1 Available control points] iburger | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| The here described functionality builds on top of the normal standalone operation, see [[ess: | The here described functionality builds on top of the normal standalone operation, see [[ess: | ||
| + | WARNING & DISCLAIMER: whilst publically available, Victron Energy does not offer support in professional customers or end-users that implement features using the here documented functionality, | ||
| ===== 1. Overview of ESS operating modes ===== | ===== 1. Overview of ESS operating modes ===== | ||
| ==== 1.1 - Mode 1 ==== | ==== 1.1 - Mode 1 ==== | ||
| - | The system runs automatically, | + | The system runs automatically, |
| ==== 1.2 - Mode 2 ==== | ==== 1.2 - Mode 2 ==== | ||
| Line 29: | Line 30: | ||
| * 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 37: | Line 42: | ||
| ==== 2.1 Available control points ==== | ==== 2.1 Available control points ==== | ||
| - | === a) Grid power setpoint - Modbus-TCP register | + | Please note that the power setpoint register changed in Venus 3.50. Prior to Venus 3.50, the power setpoint would be written to register 2700 or 2703 instead. While this is still supported, it is recommended that future implementations use the 32-bit setting at registers 2716 and 2717 to avoid constantly logging the new setpoint to VRM, and wearing the flash on the GX-device with repeated writes. |
| + | |||
| + | === a) Grid power setpoint - Modbus-TCP register | ||
| + | For venus versions before 3.50, use register 2700 instead. | ||
| * Positive: take power from grid. | * Positive: take power from grid. | ||
| * Negative: send power to grid. | * Negative: send power to grid. | ||
| - | * Default: | + | * Default: |
| - | * This register has range -32768W to 32767W (scale factor=1). | + | * Note that register |
| - | === b) Enable/ | + | === b) Enable/ |
| * 0: disable charging. This setting may be used for time shifting. For example by disabling charging the battery when feeding back to the grid is profitable, and leaving battery capacity for later. | * 0: disable charging. This setting may be used for time shifting. For example by disabling charging the battery when feeding back to the grid is profitable, and leaving battery capacity for later. | ||
| * 100: unlimited charging. Battery, VEConfigure settings, and BMS permitting. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | * 100: unlimited charging. Battery, VEConfigure settings, and BMS permitting. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | ||
| - | Note that this setting has a higher priority than the //Grid power setpoint//. | + | Notes: |
| + | * This setting is deprecated and only works when DVCC is disabled. It is retained for backwards compatibility only. Use register 2705 instead to control battery charging. | ||
| + | * This setting has a higher priority than the //Grid power setpoint//. | ||
| - | === c) Enable/ | + | === c) Enable/ |
| * 0: disable inverter | * 0: disable inverter | ||
| * 100: enabled inverter. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | * 100: enabled inverter. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | ||
| - | Note that this settings has a higher priority than the //Grid power setpoint//. | + | Notes: |
| + | * This setting is deprecated and only works when DVCC is disabled. It is retained for backwards compatibility only. Use register 2704 instead to control battery discharge. | ||
| + | * This settings has a higher priority than the //Grid power setpoint//. | ||
| + | |||
| + | === d) Maximum inverter power - Modbus-TCP register 2704 === | ||
| + | * -1: No limit | ||
| + | * Any positive number: Maximum power in Watt that the Multi will feed to the loads. | ||
| + | |||
| + | === e) DVCC maximum system charge current - Modbus-TCP register 2705 === | ||
| + | * -1: No limit. Solar Chargers and the Multi will charge to their full capacity or individual configured limits. | ||
| + | * Any positive number: Maximum combined current in Ampere for battery charging. This limits the solar chargers and the multi, and takes loads into account. Solar chargers take priority over the Multi. | ||
| + | |||
| + | === f) Maximum system grid feed-in - Modbus-TCP register 2706 === | ||
| + | * -1: No limit. If feeding in excess PV is enabled, all of it will be fed in. See registers 2707 and 2708 below. | ||
| + | * Any positive number: Maximum power in 100 Watt units to feed into the grid. | ||
| + | |||
| + | === g) Feed excess DC-coupled PV into the grid - Modbus-TCP register 2707 === | ||
| + | * 0: Excess DC-coupled PV is not fed into the grid. | ||
| + | * 1: Excess DC-coupled PV is fed into the grid | ||
| + | |||
| + | === h) Feed excess AC-coupled PV into the grid - Modbus-TCP register 2708 === | ||
| + | Please note that for historical reasons this register is inverted compared to 2707. | ||
| + | * 0: Excess AC-coupled PV is fed into the grid | ||
| + | * 1: Excess AC-coupled PV is not fed into the grid. | ||
| + | === i) Grid limiting status - Modbus-TCP register 2709 === | ||
| + | When feed-in of excess AC-coupled PV is disabled, or when a limit is set in register 2706, limiting will be active. | ||
| + | * 0: Feed-in of excess power is not limited in any way. | ||
| + | * 1: Feed-in of excess power is limited in some way, either register 2707 is set to 0, or register 2706 is set to a positive number. | ||
| ==== 2.2 Accessing the control points ==== | ==== 2.2 Accessing the control points ==== | ||
| Line 64: | Line 102: | ||
| 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 GX device |
| Start reading [[open_source: | Start reading [[open_source: | ||
| Line 73: | Line 111: | ||
| * com.victronenergy.settings / | * com.victronenergy.settings / | ||
| * com.victronenergy.settings / | * com.victronenergy.settings / | ||
| + | * com.victronenergy.settings / | ||
| + | * com.victronenergy.settings / | ||
| + | * com.victronenergy.settings / | ||
| + | * com.victronenergy.settings / | ||
| + | * com.victronenergy.settings / | ||
| + | * com.victronenergy.hub4 / | ||
| - | Note that the paths are represented as percentage, but should be used as on/off switch (0: off, | + | Note that the MaxChargePercentage and MaxDischargePercentage |
| 100: on). | 100: on). | ||
| Line 114: | Line 158: | ||
| * When both Charge and Feed-in is disabled, the Multi will go into Passthru. | * When both Charge and Feed-in is disabled, the Multi will go into Passthru. | ||
| - | ==== 3.3 Running software on the CCGX and using DBus paths ==== | + | === d) Disable overvoltage Feed-in - Modbus-TCP register 65 === |
| + | Overvoltage feed-in can be used to feed excess DC-tied PV into the grid. Note that DVCC needs to be enabled to properly use this feature. | ||
| + | * 0: Feed overvoltage into the grid. | ||
| + | * 1: Do not Feed overvoltage into the grid. | ||
| - | When controlling the Multi using software running on the CCGX, you should set // | + | === e) Maximum Feed-in power due to overvoltage - Modbus-TCP register 66 to 68 === |
| + | When overvoltage feed-in is enabled, these registers can be used to limit how much power is fed in. To disable the limit, write a large number to the register. | ||
| + | * Register 66: Overvoltage feed-in limit for L1 | ||
| + | * Register 67: Overvoltage feed-in limit for L2 | ||
| + | * Register 68: Overvoltage feed-in limit for L3 | ||
| + | |||
| + | === f) Power Setpoints acts as limit - Modbus-TCP register 71 === | ||
| + | When this register is set to 1, the Multi will feed in overvoltage up to the value in registers 37, 40 and 41. This is useful when powering loads with excess DC-coupled PV, while still keeping the batteries fully charged. The Power setpoints are then set to match the loads as normal, but the Multi will feed in only excess PV and not energy from the batteries. | ||
| + | |||
| + | === g) Overvoltage offset - Modbus-TCP register 72 === | ||
| + | When feeding excess DC-coupled PV to loads or into the grid, the Multi has two possible settings. It can either add a 1V offset to the solar charger charge voltage, or a 100mV offset. These values are for a 12V setup, and must be multiplied by 2 or 4 for a 24V or 48V setup respectively. | ||
| + | |||
| + | The larger 1V setting is a legacy setting and is now discouraged. When using ESS mode 3 with the overvoltage feed-in feature, it is recommended that you set this register to 1, which will use the lower 100mV offset. | ||
| + | ==== 3.3 Running software on the GX device and using DBus paths ==== | ||
| + | |||
| + | When controlling the Multi using software running on the GX device, you should set // | ||
| === a) Grid Power Setpoints - / | === a) Grid Power Setpoints - / | ||
| Line 141: | Line 203: | ||
| * When set to -400W, it will feed 400W back through its input. This energy will be taken from the battery. If there is also a 200W AC load connected to AC output the total energy taken from the battery will be 600W. The batteries will always be discharged when the setpoint is negative. | * When set to -400W, it will feed 400W back through its input. This energy will be taken from the battery. If there is also a 200W AC load connected to AC output the total energy taken from the battery will be 600W. The batteries will always be discharged when the setpoint is negative. | ||
| * When set to 400W, it will take 400W from the AC input. When the load on the output is lower than 400W, it will charge the battery with the difference. When the load on the AC output is higher, it will discharge the battery with the difference. So with a positive setpoint charge/ | * When set to 400W, it will take 400W from the AC input. When the load on the output is lower than 400W, it will charge the battery with the difference. When the load on the AC output is higher, it will discharge the battery with the difference. So with a positive setpoint charge/ | ||
| - | * **Important note**: The above examples describe operation from the point of view of the CCGX. When communicating directly with the ESS assistant (see further on) you should bear in mind that the CCGX inverts the setpoint: Positive becomes negative and vice versa. | + | * **Important note**: The above examples describe operation from the point of view of the GX device. When communicating directly with the ESS assistant (see further on) you should bear in mind that the GX device |
| * Note that it will always remain within battery and maximum inverter power limits: when the battery is full or when the maximum charge current as configured in VEConfigure is already met, it will not draw more power, and when instructed to discharge with 10000 watt while it only has a 2500W inverter capacity, it will discharge with 2500W until the battery is empty. | * Note that it will always remain within battery and maximum inverter power limits: when the battery is full or when the maximum charge current as configured in VEConfigure is already met, it will not draw more power, and when instructed to discharge with 10000 watt while it only has a 2500W inverter capacity, it will discharge with 2500W until the battery is empty. | ||
| * To force the Multi to Inverter Mode, set the switch to Inverter-only. Note that when you do that, there will be no grid assist. On an overload the Inverter will switch off and signal an overload alarm instead of switching back to the grid. | * To force the Multi to Inverter Mode, set the switch to Inverter-only. Note that when you do that, there will be no grid assist. On an overload the Inverter will switch off and signal an overload alarm instead of switching back to the grid. | ||
| Line 154: | Line 216: | ||
| * Note that there are various ramp-up and ramp-down restrictions, | * Note that there are various ramp-up and ramp-down restrictions, | ||
| * The ' | * The ' | ||
| - | * If your system contains a ESS compatible AC-Sensor which is set up as grid meter, the CCGX will automatically enter mode 1 and start updating the AC power setpoint continuously. You can disable this behavior by setting // | + | * If your system contains a ESS compatible AC-Sensor which is set up as grid meter, the GX device |
| - | ==== 3.6 Using the MK3 directly instead of via CCGX ==== | + | ==== 3.6 Using the MK3 directly instead of via GX device |
| === 3.6.1 Introduction === | === 3.6.1 Introduction === | ||
| - | In this setup, it is not necessary to use a CCGX for the control interface. Instead an MK3 is used. We have both MK2-RS232 and an MK3-USB available, see the pricelist. | + | In this setup, it is not necessary to use a GX device |
| The MK3-USB has replaced the MK2-USB. There are no differences in the protocol. | The MK3-USB has replaced the MK2-USB. There are no differences in the protocol. | ||
| - | A direct connection to the VE.Bus RS485, without MK3 or CCGX, is not possible. | + | A direct connection to the VE.Bus RS485, without MK3 or GX device, is not possible. |
| Note that, as also indicated on the Data Communication whitepaper, the MK2/3 protocol is not an easy protocol. That is unfortunate, | Note that, as also indicated on the Data Communication whitepaper, the MK2/3 protocol is not an easy protocol. That is unfortunate, | ||
| Line 219: | Line 281: | ||
| (Length, 0xFF, ‘W’, 0x85, Lo(ValueA), Hi(ValueA), Lo(ValueB)*, | (Length, 0xFF, ‘W’, 0x85, Lo(ValueA), Hi(ValueA), Lo(ValueB)*, | ||
| - | ValueA is the contents of RAMID 128. In this example it is 0x0032 which indicates | + | ValueA is the contents of RAMID 128. In this example it is 0x0032 which indicates |
| //*) Please note that you will get an extra ValueB. This is a feature of newer Multi firmware versions. Because the IDs range from 0..255 the Hi(ID) field would always be 0. | //*) Please note that you will get an extra ValueB. This is a feature of newer Multi firmware versions. Because the IDs range from 0..255 the Hi(ID) field would always be 0. | ||
| Line 254: | Line 316: | ||
| * when you do not want to discharge, set the switch to charger-only. Note that when the switch is set to charger-only, | * when you do not want to discharge, set the switch to charger-only. Note that when the switch is set to charger-only, | ||
| * when you do not want to charge, disable charging via the disable-charge flag. | * when you do not want to charge, disable charging via the disable-charge flag. | ||
| - | * 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 GX device |
| ===== 5. Response times and ramp speed ===== | ===== 5. Response times and ramp speed ===== | ||
| Line 321: | Line 383: | ||
| * Set register 37 to -1000 | * Set register 37 to -1000 | ||
| - | ===== DISQUS ===== | + | |
| - | ~~DISQUS~~ | + | |
ess/ess_mode_2_and_3.1581346829.txt.gz · Last modified: 2020-02-10 16:00 by mvader