48 minutes ago, Smokey said:

I currently have 1 x Kodak OG Plus 5.48 with 2 x Kodak FL5.2 batteries

my issue started in March 2022, when I bought 4 c ESS 2500 bat's
the OG will NOT communicate when more that two batteries are connected
it will only charge & discharge the 1st two batteries
( just displays the 69 error)

Segen, the supplier, then suggested I use 2 x FRL5.2 batteries - that solved the problem
well, didint solve it, they just side stepped the issue

now I want to connect two more FL5.2 batteries - same issue, only sees the 1st two
this after I received an email from Segen at the time, confirming the OG5.48 will handle up to 12 Fl5.2 batteries in parallel
 

I run the same firmware version as a mate of mine, using his Mecer ( essentially the same Axpert King engine)

so it looks like the flaw is with the Kodak and Segen couldn't care less

 

Hi @Smokey, I am sorry for your upheaval, and I am surprised  because I have got good support from Segen so far.

So lets ask @SEGEN SOLAR to respond to you, I am sure they will tell us what route to take.

 

I am running 3 x US3000C batteries on my Kodak King inverter. It also shows warning 69 when batteries are fully charge but keeps working without any issues. As soon as the BMS asks for current/charge from the inverter the warning 69 disappears. 

52 minutes ago, Jacques Ester said:

I am running 3 x US3000C batteries on my Kodak King inverter. It also shows warning 69 when batteries are fully charge but keeps working without any issues. As soon as the BMS asks for current/charge from the inverter the warning 69 disappears. 

same here

when using RS485 to BAT - all good now errors
BUT
it does not drain the 3rd and 4th battery

If I do a load test, the Wh I can draw, only adds up to two batteries
the result concludes that only two batteries are used to supply power

No such issues with my system. All 3 Batteries are draining and charging together.

6 hours ago, Smokey said:

I run the same firmware version as a mate of mine, using his Mecer ( essentially the same Axpert King engine)

so it looks like the flaw is with the Kodak

The Kodak, Mecer, and all other legitimate Voltronic inverters are made the same in the same factory, just with different paint and stickers.

What version of display (U2) firmware are you running?

U2 -> 02.70

U1 -> 71.97

02.70 isn't too old. You could however try updating to display firmware version 02.81 for Axpert King and VM III.

Hello!

I have Voltronic Axpert VM-III 4000 Twin and battery Felicitysolar LPBF24200-M (LiFePO4, Pylontech compatible). The inverter works; it regularly gives 230VAC to AC OUT, but warning 69 occurs occasionally. Main firmware is v60.05, and MCU firmware is v25.08.

I see that many of you write here that it is nothing dangerous, but that it is just a warning that the battery is full. However, that warning is irritating and I wish it wasn't there... How to solve this? Thanks in advance...

40 minutes ago, Mika said:

Hello!

I have Voltronic Axpert VM-III 4000 Twin and battery Felicitysolar LPBF24200-M (LiFePO4, Pylontech compatible). The inverter works; it regularly gives 230VAC to AC OUT, but warning 69 occurs occasionally. Main firmware is v60.05, and MCU firmware is v25.08.

I see that many of you write here that it is nothing dangerous, but that it is just a warning that the battery is full. However, that warning is irritating and I wish it wasn't there... How to solve this? Thanks in advance...

Answer from Tommy Wu -Voltronic, (...but I'm not sure that's exactly the case...)

Dear Sir,

69⚠    Charging the battery status is not allowed

 If, after successful communication between the inverter and the battery, charging the battery state is not allowed, the code 69 is displayed to stop charging the battery.  Lithium battery communication is abnormal, please check the battery setting type and communication protocol.

Tommy Wu, [email protected]

Edited November 24, 2025Nov 24 by Mika
...but I'm not sure that's exactly the case...

On 2025/11/24 at 8:14 PM, Mika said:

However, that warning is irritating and I wish it wasn't there... How to solve this?

The later display firmwares relented and removed the warning altogether.

The latest available 25.xx display firmware is 25.16: