MultiSIBControl - Issue with Charge Current Limitation (MCHGCnnn) – Commands momentarily ignored

Hello,

I am using MultiSIBControl to manage my Axpert Max II Duplex 11KW inverter in conjunction with Pylontech batteries. Communication between the software and the inverter generally works (receiving (ACK confirmation in the console), but I am encountering issues with the implementation of SOC-dependent charge current limitation.

The control objective is to achieve a gentle, stepped charging of the Pylontechs in the upper range (Hysteresis 80% to 90% SOC) while keeping the AC charging permanently deactivated.

1. My Setup

• Inverter: Axpert Max II Duplex 11KW  ; Main CPU Firmware Version 00063.04 ; Secondary CPU Firmeware Version 00022.21

• Battery: Pylontech (BMS communication active, but AC charging deactivated via Menu 16 set to "SOL")

• MultiSIBControl Version: 1.9 (Assumed)

  2. Implemented Control Logic (Stepped Charging)

  I have set up a precise, non-overlapping chain of rules to control the total charge current:

  SOC Range	Rule Title	Action Command	Action Repeat Strategy
  < 80%	Lade_volle_Leistu_80_Prozent	MCHGC090	Execute once
  85\% to < 86\%	Lade_drossel_85_Prozent	MCHGC045	Execute once
  89\% to < 90\%	Lade_drossel_89_Prozent	MCHGC025	Execute once
  >= 90\%	Lade_stop_90_Prozent	MCHGC000	Repeat every 1 minute

3. Observed Problem: Momentary Charging/Flickering

The issue affects both the 0A Stop Rule and the Throttling Rules:

1. On Charge Stop (SOC≥90%):

   • MCHGC000 is sent, and the charge current briefly drops to 0A (ACK confirmation received).

   • Within < 60 seconds (before the next repeat command arrives), the inverter ignores the 0A command and increases the charge current to an internal default value (approx. 50A or more).

   • Since charging resumes, the condition SOC≥90% remains fulfilled. The MCHGC000 command is sent again after 1 minute, the current drops to 0A, and the cycle immediately repeats (flickering).

2. During Throttling (85% to 90%):

   • The throttling commands (e.g., MCHGC045 at 85%) are also only implemented very briefly.

   • Shortly after sending the 45A command, the charging jumps back to the internal default value (approx. 50A), undermining the fine-tuned throttling.

4. My Question

Is there a recommended "aggressive strategy" in MultiSIBControl for this known issue (overriding of external MCHGCnnn commands by the internal firmware/BMS logic)?

Should a Mode Change command (e.g., PSB) be used in the Lade_stop_90_Prozent rule to inhibit the WR's charging function at a higher level, thereby resolving the flickering? If so, which mode commands are recommended for "Stop Charging" (at ≥90%) and "Re-enable Charging" (at SOC<80%)?

Thank you in advance for your support.

Rafa