SoC mode set to charge battery actually discharges it

[averter]

Hello,

Today I've tried to charge the battery during night using the new remote control functionality, specifically SoC mode 3. The controls were set to charge up to 75% in a maximum time of 3000s and a maximum power of 1000W

Next I've started the mode, and as you can see in the above picture the actual values seem to be correct.

However, what actually happened is that the inverter started sending 3000W from the battery to the grid...

My guess is that the remote control timeout of 3000s is mixed up with the control charge/discharge power, which then is set at 3000W, and the SoC target might be mixed with one of the other variables set at 0 (Power/Energy Target or Duration time) and therefore it tries to reach a fully discharged state.

[averter]

@saidlm
This is the registers table

and your builder where you add each of the control settings is shown below

        Domoticz.Debug("Starting ModBus Remote Control.")
        
        builder = BinaryPayloadBuilder(byteorder=Endian.BIG, wordorder=Endian.LITTLE)
        modes = (0, 1, 2, 3, 7)
        mode = modes[int(int(self.__RC_SETTINGS['Mode'])/10)]
        
        builder.reset()
        builder.add_16bit_uint(mode)                                            # Remote Control Mode
        builder.add_16bit_uint(1)                                               # TargetSet type = SET
        builder.add_32bit_int(int(self.__RC_SETTINGS['PowerTarget']))           # Target Active Power
        builder.add_32bit_int(0)                                                # Target Reactive Power
        builder.add_16bit_uint(int(self.__RC_SETTINGS['DurationTime']))         # Time of Duration
        builder.add_16bit_uint(int(self.__RC_SETTINGS['SOCTarget']))            # Target SOC
        builder.add_32bit_uint(int(self.__RC_SETTINGS['EnergyTarget']))         # Target Energy
        builder.add_32bit_int(int(self.__RC_SETTINGS['ChargerPower']))          # Charge / Discharge Power
        builder.add_16bit_uint(int(self.__RC_SETTINGS['TimeOut']))              # Remote Control Timeout

        payload = builder.to_registers()

and although the number of bits seems right the order does not match the above table at all. For example, Target Energy should come before the Target SOC, and all of the bits of "actual" values below the mode are not accounted for.

[saidlm]

Hi,
there are two different range of registers for writing and reading. The writing uses mod-bus function 0x10 - Write multiple register.

The reading of current state of the inverter is done via mod-bus function 0x04 - Read input register. It is the part you have mentioned above. Domoticz shows you real actual values which were read from the inverter. There are two reason for that. a) It is to allow you to check that it uses exactly what you want. b) If there is another master device which makes any changes you can see the real state of the inverter.

Strange thing is that it looks ok. You can see in Input registers exactly what you set in Multiple register up. There is no automation logic in the plugin. My idea is to create just interface to Inverter and let user to do their automation in event scripts. I have just reviewed builder and decoder as well and I haven't found any problem there. There is only small issue with type int vs uint for reading Target SoC from inverter but it can't influence the behavior of the inverter.

Martin

[saidlm]

I am just running the test and it seems to me it is working properly.

M.

[averter]

@saidlm Just to make sure that we followed the same steps, you:

1. Set the target soc, the charge/discharge power and the control timeout
2. set mode 3 (soc) in the control mode switch
3. and turned the mode on using the trigger
   Right?

[saidlm]

Yes, right.

M.

BTW. What is the version of your inverter software?

[averter]

I hope this is the info you're after:

DSP: 2.07
ARM: 2.03

[averter]

@saidlm
I've tried to charge the battery again, this time setting different values for the variables, to see if I could get it to work as it should

but exactly the same happened. The battery started discharging at 3000W into the grid (despite the now 600s in remote control timeout (a coincidence)).
Do you think that it might be due to the version of the inverter's firmware?
The debug log is also not helpful. Are there any variables worth adding to the log so that we can understand what's wrong?
Any other things worth testing?
I really want to get this functionality of the plugin working before winter, for obvious reasons :-)

[averter]

Yess, it's probably because of the inverter's firmware version... Version 3.29 of the protocol document was the latest version that I could find, and the registers look quite different than the ones you've shown above. Strangely, they don't provide a table relating to the inverter's firmware version.
Solax-Hybrid X1&X3-G3 ModbusTCP&RTU V3.29- English.pdf

[saidlm]

It looks to me for different model. I have G4 and the plugin is written for G4. The documents which I have uploaded to doc folder are also for G4. V3.24 is the latest one which I have found.

[saidlm]

Back to the software version which I am running on it. My Internal code is now 43 09 42. It includes versions v1.43 is for DSP and 1.42 is for ARM. I hope it is the last version. It was updated by my supplier about 10 day ago.

BTW. I have found this link: https://app.box.com/s/3nvo7ic523fhojf8uuto105q9a8dgk9n/folder/79352264617
There is collection of different software for Solax devices. Honestly speaking I am not about to test it. I would like to be sure that the version which I am running is the official one.

Martin

[averter]

From my side the firmware version are DSP: 2.07, ARM: 2.03 and the internal code is 26 04 24 03.
Before the update which version were you running? I'm a bit confused with the DSP/ARM version numbers, since mine are higher than yours, and my inverter was installed in May 2024 and I have never updated the firmware (head scratching). Like yours, it's a G4, X1 Hybrid model.
Ahh, so the link you shared it's unofficial (reverse engineered) firmware? If so I think it's a very useful resource, although I am also not very inclined to use it unless others have tested it extensively.

[averter]

The v3.24 document is quite clear in how the versions are structured (table below)

However the v3.29 and v3.28 which I was also able to find online don't provide such table. So I can't find ANY document that specifies the registers for the firmware version (2.07/2.03 DSP/ARM) that is installed in my inverter :-(. Worst case scenario I'll have to contact Solax directly for this information... Before doing this, do you know if there is a collection of solax modbus registers documentation for different versions, similar to what you mentioned before for the firmware of solax devices? Thanks.

[saidlm]

Honestly speaking I don't know exactly what is software version. According to information from the link software version is 1.4X now. The same information I have from my supplier. And it corresponds with internal codes.
The versions which you are talking about are something different I guess. I am not sure but I guess it is HW version of the board.

Martin

[saidlm]

I have look for changelogs etc. I have also asked my supplier for that but have no success :-(. The answer is that they are not allowed to share this kind of information.
Only what I have from Solax/my supplier is list of Mod-Bus registers v 3.21. Everything else has been found somewhere on the Internet.

Martin

[averter]

@saidlm Cheers. I've contacted solax regarding this issue and will let you know if they send me anything useful. If it is a version-related problem I can always update the firmware to the latest version, which hopefully will be 1.4X as yours.
Off-topic: Besides mode 3 "SOC mode", I am also interested in mode 7 "Self-consume - Charge Only mode" to charge my EV rather than the battery during night in Winter. Since when in this mode the battery cannot be discharged and can only be charged with PV, this mode will effectively pull energy from the grid to charge the EV.

In the remote control this is labelled as "Charge Only" I believe. I will test to see if there is any difference relatively to mode 3, although it is unlikely...