On 2025/03/05 at 5:27 AM, Coulomb said:

Does the JK BMS talk a protocol that the inverter or monitoring software understand?

I'm unclear on whether the inverter can operate on SoC% if the inverter is not connected directly to the battery's BMS.

In any case, unfortunately 72.66 and its patched versions do not have the required support for SoC%. Several firmwares after 72.66 no longer have the "presumed good" MPPT logic. Factory firmware version 72.75 (the latest I know of, July 2024) has both. I have not patched 72.75. So I'd say that your best bet is to try 72.75 first. Some people report good MPPT behaviour with the "presumed good" logic, others prefer patched firmware. 72.75 is available here. However, note that the poster reports SoC% as not working. I have no idea why. I'd like to research this, but time is not available at present.

Hi. Thanks for your reply.

I just installed the fw 72.75 and MCU 12.28.

Tomorrow I start with the MPPT logic tests.

The SOC is correctly displayed in Watchpower. I use the Voltronic protocol on the JK and the LIB protocol on the inverter.

NB you need to use the RS485 cable that is supplied with the inverter that has a particular pinout (pin 1 battery side connected to pin 3 inverter side and pin 2 battery side connected to pin 5 inverter side).

Thanks again.

Ps do you know what improvement the fw MCU 12.28 introduced? Thanks.

On 2025/03/11 at 9:30 AM, CarecaIII said:

Ps do you know what improvement the fw MCU 12.28 introduced?

No, sorry. It's fairly old now (Nov 2023).

Don't be tempted to update to 12.17 (Jan 2025), as this is for the Ultra models, which have a very different (graphical) display.

Edited March 13, 20251 yr by Coulomb

Hi friends,
I have an inverter MPP Solar 8KW and i also have trouble sleeping on 90 volts and with with Pylontech battery discharge.

I have 3 Pylontech batteries, 2 US2000 and one US2000C. I installed the US2000C as the master and the rest in cascade.

I notice that the Inverter recognized the Pylontech battery, but it does not discharge from the battery at night. It always charges it up to 53.2V..
I have

Main CPU: 46.05

Secondary CPU:12.13

Can you tell me which firmware is suitable for my inverter.

Thanks for your reply.

Mihai

4 hours ago, misu said:

Can you tell me which firmware is suitable for my inverter.

Yes. Factory firmware version 46.82 has the "presumed good" MPPT logic, so it should work a lot better. Sorry, there is no recent patched firmware for these models.

Hello,

I have a 8kw I non-twin inverter (with detachable display).

Connected to Pylontech BMS via RS485

I am trying to integrate with Raspberry Pi and Home Assistant but whenever I connect any serial on the serial port or an USB to retrieve the data, an error 04 (low batt) or 61 (batt communication failure) appears randomly. Sometimes the error appears right after connecting, sometimes it takes a bit. Sometimes it stays put, sometimes comes and goes. I've tried everything and this is only happening when I connect a new communication to the inverter.

I've seen in other forums/YouTube that this is a common issue that could be fixed updating (this CPU is not able to cope with two communications at the same time, RPi and Pylontech), but I'm not sure. Anyone here that has had this issue fixed? I would also appreciate if you could help me identify my processor on the inverter.

Current firmware:

Main CPU Vers. U1 46.05

Secondary CPU Vers. U2 12.06

Secondary WIFI Vers. U3 88.88

The factory firmware version 46.82 has "supposedly good" MPPT logic and works much better. There is also SOC, but it is visible and adjustable only on the inverter, on the applications it is displayed in volts. The display has also been updated v12.28.

Edited February 13Feb 13 by jevko

On 2025/08/28 at 9:13 PM, franlopez said:

I am trying to integrate with Raspberry Pi and Home Assistant but whenever I connect any serial on the serial port or an USB to retrieve the data,

You might be running into the issue where when sending commands to the USB port, you (sometimes?) have to send a maximum of 8 characters in a single command. So commands with more than 5 characters (so more than 8 when adding the carriage return and two CRC characters) should be split into two write commands one after the other. This might be fixed in later Python libraries.