bratpit

Hi
On FTP side there is DSP firmware too. Togather with Display 57.22.I think they are stable.
Here I upload 60.14 DSP firmware.
VM TWIN_60.14.7z

Hi
On FTP side there is DSP firmware too. Togather with Display 57.22.I think they are stable.
Here I upload 60.14 DSP firmware.
VM TWIN_60.14.7z

Hi
This is quick and dirty fix this issue . Automation in SA. Maybe for premature float bug too.

There are a couple differences between fw 60.95 or 60.10 with this 68.13 FW:
MPPT works slightly differently . MPP in 68.13 is achived at higher voltage so there is more power at the same current.This is charts from SA. Temperature outside is nearly the same so conditions is comparable.
60.95


68.13


I should check it by multimeter for sure
In bypass at SBU and Solar only mode 68.13 not charging battery from the grid (was 2.7A in 60.95) but draws 0.7A from battery. It may be positive or negative impact depends what you want to achive.
Cooling is about the same at low load but is less agressive at high load so it may be negative impact in places with hot climate. When charging from sun cooling is the same in both fw.
This is chart load+charging from grid 2.5kW . In opposite in 60.95 fan revs goes to max at about 40oC. Here we have 48oC and revs did not go to max.

Forgive my laziness, I just wanted you to make sure that know, @bratpit, about the x60.96 firmwares, that fix the premature float bug in factory firmware version 60.95. Patched firmware version 860.95 has only the premature float bug fixed, no MPPT changes. But of course you may benefit from the MPPT changes as well.
Thanks again for the generous coffees!
 

Ad.1 I use APL too because keeps 0A charging battery from grid at bypass in SBU and "Solar only".
At UPS it is drawing  2.7A from grid(135W). It's stable 2.7A not cycled. It is 6kW model.
Inverter LCD panel do not show charging battery but BMS and clamp meter yes.
More... inverters grid usage do not measure it so it is big gap between load+battery charging and grid usage if inverter is in bypass at UPS+SBU+Solaronly combo.
Ad2 Yes but is very little noticable for me (noticed it after 2 month of use inverter) so do not bother me at all .I think is noticable more at low SoC of battery.

Mine inverter is not connected to bms. Both  BMS  and inverter are connected to SA.Inverter settings for battery is set tu "USER" 

It happens on grid too.I checked it  at night.
At the begining  for example at 20% of SOC diode is blinking but goes early solid on . 

Maybe mine is the same.
Never goes to CV at 56.2V. Always stops at float at 54.9V.
In the morning  diode blinking (means bulk) but goes to float(stays ON) very early when battery is about 53V-53.6V or so.No matter there is on grid or PV. No logick here claudy or sunny always the same. Mybe it is hardware fault . I checked 5 firmwares and nothing changes.
 
So CV level  practically  not exist in my inverter .
 

No repairs, no errors.
I bought it in SolarPower24 at the beginning 2023.

If you have a setup already running with ESP32 then that's all good. I was just laying out some options with a Raspberry pi if you didn't. I think Meetyg's point is that good quality EEPROM is generally, as you say, in the range of 100,000 writes in a lifetime, but we don't know the quality of the EEPROM used in the machine. Some EEPROM can have as few as 10,000 or less writes in a lifecycle.
EEPROM is writing when sending the commands for change of float voltage in Cagire's case with the automation using the ESP32.

Maybe but Inwerter do not know  difference between LFP and AGM because of "user"  mode.
There is no difference for me between 60.95 and 860.95 so I stay with patched one.
For LFP batteries  no matter if I charge it to 30%, 70% or 99% or discharge to 5% .As long as you stick to flat characteristics (avoid upper and lower  knee) of charge and discharge everething is OK and they like it
So termins "bulk , float" is from the leaden world barelly fit to LFP.
LFP charge to some point or discharge and thats all. 
If inverter allow you set that points more or less precisely (eg. 95% - 5%) there is no need go to  "float".

Ha . It' oposite to mine. Never went to bulk.

For all those that have used my patched VM III and VM IV bugs, my humblest apologies! I included a fix for the premature float bug, thinking that it was a two-word patch, but I misunderstood the logic, and as reported by several users, the patched firmware never goes to float! These are the perils of patching code that you can't test on an actual machine.
The first fixed patched firmware I'm releasing is for factory firmware version 60.95, mainly because user @roadrunner79 sent me excellent graphs detailing exactly what the problem is. This change affects all the variants, so I've numbered the fix for these as x60.96, even though they are based on factory firmware version 60.95. I hope that there is never a factory firmware version 60.96 to get confused with.
If you are using any of the x60.95 patched firmwares, please update to x60.96 at your earliest convenience.
Once I get some feedback that I've correctly fixed this bug, I hope to apply it to other VM III and VM IV patched firmwares.
These are patched firmwares version 860.96, 260.96, 560.96, 160.96, and 960.96, all based on factory firmware version 60.95 for the Axpert VM III Twin 6kW and 4kW, and the Axpert VM IV Twin 6kW and 4kW. These patches implement most of Georg's MPPT "stuck at 90V" patches (here it would be "stuck at 60 V"), and fix the premature float bug. The only parts not applied are for the forward current constant, which doesn't seem to be changed based on solar voltage in any VM firmwares. The version number should display in full when using monitoring software, but will still show as 60.95 on the front panel display. Do not use with any other models, not even older VM III and VM IV models with power ratings like 5 kW or 3 kW, or non-twin models. Use at your own risk.
In the reflash tool, you may have to navigate to the folder with the patched files the first time it is run. Choose the hex file with the minimum MPPT voltage that you want:
860.96: float bug only
260.96: 200V min MPPT
560.96: 150V min MPPT
160.96: 100V min MPPT
960.96: 90V min MPPT
Use the 200 V variant if your PV panels are nearly always well above 200 V. Otherwise, use the 150 V version if your panels are almost always above 150 V. Use the 100 V version if your panels are particularly low in voltage. Try the 90 V version only if you have just 3 panels, the very bare minimum.
You can also of course choose the original factory firmware.
Firmware upload instructions.
 
dsp x60.96 VM III Twin patched.zip

I checked once again patched 60.95 (this time 960 version) and it is the same.
Next I checked only anti premature float bug version (860).
It is free from mptt goes to 0W at current change but:
1. Full SUN no clouds

At the morning bulk phase began and goes till 53.8(9) V. Diode CHG blinking. After that goes to float. Bulk never cross 54V. On inverter it is set 55.2.
2.Some clouds yestarday.

 
Bulk phase ends at 53.6 V.
 
 

I had the same.
Change driver

I had the same.
Change driver

Nope.
I think for 24V voltage is lower than 85V like in NCEP85T16.

Oh. That a good point.Never exited 17.1A in paralell.But in one series got 11.7A once.
Pardon 12A.
 

Yes, it's quite possible that the PV current is limited to a particular value. Alas, the web page and user manual (for the VM IV that I checked) doesn't say what this limit is. Often, the 500 V max PV voltage models are "nominally" 350 V; 6000 W / 350 V = 17.1 A. If true, that means that whenever your Vmp is below  350 V, you won't be getting full power from the solar charge controller. Whenever your Vmp is over 350 V, the solar power should clip to 6000 W.

There is one element that I did not pay attention to.
Temperature. Some days differed by 8 degrees Celsius, unfortunately I don't remember(write) the days from which I took the charts

Here you are:
https://static.trinasolar.com/sites/default/files/EN_Datasheet_Vertex_DE09.pdf

1. I tried to make the conditions comparable, but not check it  by multimeter. So I think difference is valid with the same magnitude of error for both FW. 2. I only checked current by clamp meter at PV IN to measure eficiacy the inverter.Was 19.5A vs. 17.1A(can not checked this and I do not know where it is measured) measured by inverter himself  . So  17.1/19.5=88% at 125-130 V.  what surprises me that I can not go above 17,1 from 11AM to 13 PM (horizontal line) at full sun in parallel panels.At one string current touched 11.5A sometimes. It looks like inverter cut current at this level. 3. Yes I am using SA.    

@Coulomb & @Tarek Yag
This is a little comparison in mptt behavior between 60.95 and 68.04 FW. Clear sky.Max current.
Configuration is 2s4p  2x1600W . The same Trina Solar panels.
60.95
 

68.04
 

As we can see 60.95 works better. Current is near 17A , and voltage about 135V hence more power. 2.2-2.3 kW
The most impact to power in 68.04 is  less voltage at mptt point (minus ~10V) and current too . Result -  2-2.05 kW.
 
PS. I can not go above 17A current in my installation. But each string alone  goes above 10A.
I do not know what couse this.
35 meters of solar cabel 6 mm2 (9 AWG) gives me with this calculator loss about 100W at 20A.
https://www.rapidtables.com/calc/wire/voltage-drop-calculator.html
but 3A less current in parallel vs. single string gives more than 300W potential loss at full sun.
May be inverter mptt efficiency at 130V is so poor.
May be FW cut some current? Inverter specs say 27A max ???
On the other hand parallel gives me better behavior in low light  conditions so battery stays longer..