Here you can see the voltage once again. Depending on the number of PV modules 4 to 10, the voltage rises to a certain value (as can be seen from the characteristic curves of the modules). The gaps in the morning and evening are probably due to the fact that the electronics are already active, but the minimum current has not yet been reached. Therefore, no usable power is generated. Does anyone have a better explanation?

The changes are already producing significantly more power!

The comparable PV fields are greyed out. Green is Georg594 firmware. Brown and orange are the latest version from Coulomb and red is the original firmware.

The question is whether the control behaviour should be improved (more quiet)?

Period	PV1 I1	PV1 I3	PV1 I4	PV1 I5	PV2 I1	PV2 I3	PV2 I4
2022 12-22	0,53	0,61	0,30	0,44	0,24	0,76	0,36
2022 12-21	0,97	1,01	0,74	0,96	0,42	1,19	0,87
2022 12-20	0,92	0,93	0,69	0,88	0,38	1,09	0,76

Edited December 22, 20223 yr by Volker

With the latest firmware, the two MPPTs always regulate in exactly the opposite direction. In the original it is only sometimes like this. The control steps comes from the algorithm, they are necessary. Could it be that the steps are sometimes too large? The step size seems to be adjusted. When I also look at the curve of the original firmware (red), it doesn't always look sensible how the controller behaves. Is that why Georg has removed parts of it?

1 hour ago, Volker said:

I think the latest firmware flutters too much and this causes losses. Surely the last change should have prevented it?

On re-reading my code, I see that I'm comparing a solar reference with 175 V, not the actual panel voltage reading. The reference is what the firmware is aiming for, which roughly tracks the actual panel voltage, but it's not the same thing. I would not expect the reference to dip down below 175 V very often, so I'm not totally convinced that fixing this will stop the jitter.

It's nearly 3am here, so I can't do anything about it now, and I haven't even finished looking over all your graphs. Thanks for all that detail, it's really helpful!

7 hours ago, ClauBebe said:

can you please tell me what processor I have and if I can flash your firmware, thanks

Yes, you have 56.xx, so you can use the patched firmware with versions y56.05, where y is 1-4 so far.

But note that I've found a bug in 456.05, and we're still comparing Georg's and my approaches, so it's probably worth waiting for the dust to settle.

30 minutes ago, Volker said:

With the latest firmware, the two MPPTs always regulate in exactly the opposite direction. In the original it is only sometimes like this.

When they are in opposite directions, I assume that's because you would have too much PV power if you had them both go up. With the original firmware, the power is so low that this never becomes an issue (you always want as much power as possible). If you had larger loads or your battery could take more current (or it's allocated more current by the master, not totally sure how that works), then presumably the steps would be in the same direction. The steps themselves are due to changes in available solar power, presumably.

I've just realised another possible reason for the jitter. In the previous patched version, when the MPPT reference voltage was set to max (450V), the direction was set to 0, meaning that we expect the PV power to increase as the PV voltage is reduced (we are above the MPPT voltage). This makes sense.

But in this patched version, when we set the MPPT to a middling voltage (200 V), we do this because the PV voltage is low (below 175.0 V), so the direction should really be set to 1,meaning that we expect the PV power to increase with increasing voltage (we are still below the MPPT voltage). This might occasionally not be correct, in which case we'll get the occasional glitch, can't be helped, but in the common case where the MPPT voltage will be over 200 V, the assumption will be correct, so the PV voltage won't go in the wrong direction most of the time. Fortunately, this is a trivial change.

I came across this while commenting the many many firmwares that I have now, attempting to check for a difference between MPPT1 and MPPT2. I strongly suspect that there is none, and the differences in behaviour are due to other factors, but I may as well finish that commenting and comparing, just to be sure. Who knows, it might even shake out more bugs, in either the patched code or the original factory firmware.

9 hours ago, Coulomb said:

Who knows, it might even shake out more bugs, in either the patched code...

I think it has. I should be doing the resets after an adjustment cycle, when the accumulated power is set to zero, so the next cycle, you'll get a clean measurement of the difference between 175 V and 200 V. As it is, it's basing its direction on the last measurement when it was bumbling down at below 175 V, and the measured power was likely decreasing. This change is also pretty easy, and should result in better smoothness. I should split the patch into two separate pieces as well, one for MPPT1 and one for MPPT2, since in theory they might get out of sync with their counters.

This next patched firmware should be a good improvement. A good thing too, as I'm running out of patch version numbers: 65 605 representing version 656.05 would be > 65 535, so that won't fit into an unsigned 16 bit variable. So 556.05 has to be the last patched version. No more bugs! 🙂. Of course, I can resort to a different numbering scheme.

[ Edit: Sigh. Had wrong firmware version number to patch. ]

Edited December 23, 20223 yr by Coulomb

19 hours ago, Coulomb said:

Yes, you have 56.xx, so you can use the patched firmware with versions y56.05, where y is 1-4 so far.

But note that I've found a bug in 456.05, and we're still comparing Georg's and my approaches, so it's probably worth waiting for the dust to settle.

I will waiting from the next patched firmware from you or Georege ! TX !!

Edited December 23, 20223 yr by ClauBebe

1 hour ago, ClauBebe said:

 

 

@ClauBebe, I assume that this is with factory firmware version 56.02 or so? With or without the plug removed?

25 minutes ago, Coulomb said:

@ClauBebe, I assume that this is with factory firmware version 56.02 or so? With or without the plug removed?

Yes, factory default firmware version 56.02 and unplug on grid with full house load 

Were is the spike i reset the mppt manually on both 

 

Edited December 23, 20223 yr by ClauBebe

3 minutes ago, ClauBebe said:

Yes, factory default firmware version 56.02 and unplug on grid with full house load

Hopefully all my distractions are gone now. I think that the new patched firmware, with resets every 5 minutes instead of  1 minute, should do it. Edit: Probably with the plug removed as well, but we'll see.

Edited December 23, 20223 yr by Coulomb

9 minutes ago, Coulomb said:

Hopefully all my distractions are gone now. I think that the new patched firmware, with resets every 5 minutes instead of  1 minute, should do it. Edit: Probably with the plug removed as well, but we'll see.

I can't wait to test it, TX for the hard work!!

My setup is 2 string on 375w * 10 pic's Canadian Solar and 25Kw li ion battery Nissan Leaf with Orion Jr 2 BMS and Victron Smart Shut for monitor the pack in solar assistant 

Edited December 23, 20223 yr by ClauBebe

12 minutes ago, ClauBebe said:

I can't wait to test it, TX for the hard work!!

My setup is 2 string on 375w * 10 pic's Canadian Solar and 25Kw li ion battery Nissan Leaf with Orion Jr 2 BMS and Victron Smart Shut for monitor the pack in solar assistant 

Man, i love your install, that extra lcd display on the Max is beauty😍

Hi there, I have a Kodak OG 10 inverter, a rebranded Expert I presume. Do you have any new firmware for my unit as I can not connect to my BMS on my batteries via RS485, standard pinouts, 3-->8 and 5-->7..

Here with a screen shot of my device details. as you can see, no battery info  

by the way, all Kodak firmware files can be found here: https://365segen.sharepoint.com/sites/SegenFirmwareControlCentre/Shared Documents/Forms/AllItems.aspx?ga=1&id=%2Fsites%2FSegenFirmwareControlCentre%2FShared Documents%2FKODAK&viewid=67638a2a-c217-436b-9e6e-fc0ae45f8824

I see when downloaded, it states Axpert.. so Kodak is a rebrand. 

1 hour ago, VanWykAC said:

by the way, all Kodak firmware files can be found here: https://365segen.sharepoint.com/sites/SegenFirmwareControlCentre/Shared Documents/Forms/AllItems.aspx?ga=1&id=%2Fsites%2FSegenFirmwareControlCentre%2FShared Documents%2FKODAK&viewid=67638a2a-c217-436b-9e6e-fc0ae45f8824

I see when downloaded, it states Axpert.. so Kodak is a rebrand. 

Hi, you don't have the 90v  bug on your inverer ?? Can you upload here the firmware?

1 hour ago, VanWykAC said:

Do you have any new firmware for my unit as I can not connect to my BMS on my batteries via RS485, standard pinouts, 3-->8 and 5-->7..

Your firmware is newer than what we're patching, which is 56.05.

I don't have any 30.xx display firmware, which would be what you would need. But I'm 99.9% sure that firmware won't fix the problem with the battery information. What battery do you have?

I have the Deichmann YL-R48100 by TheSunPays, rebranded Yilink

I see in this video there is a configuration option 14 where you can enable 3rd party control protocol. My Kodak OG10 does not have option 14  

 

 

Here is patched firmware version 556.05 for the Axpert Max II 10kW with the older '2809 DSP processor.

It implements:

* Fixes the premature float bug.

* Displays as version 556.05; I think I messed up the version number for what was supposed to be 456.05.

* Implements Georg's current threshold patch, 0.50 A -> 0.05 A.

* No longer stops setting the direction flag when the current is low; I decided it would make no difference.

* Every 5 minutes now (was 1 minute), it checks each MPPT voltage. If below 175.0 V, the MPPT (1 and 2) is "reset" by changing the direction flag to 1 (was to 0 in 456.05) and sets the MPPT voltage threshold to 200.0 V. Setting the flag to 1 should hopefuly fix the "glitchiness" of the PV voltage.

* MPPT1 and MPPT2 are handled in separate patches now, in case they get out of sync, which could have been another source of glitchiness.

* Fixed the bug where I was testing the solar voltage reference against 175.0V, instead of the latest actual voltage measurement.

Use at your own risk.

OG-10 DSP Reflash_556.05 patched.zip

Edited December 23, 20223 yr by Coulomb

I did some more tests today. As it was very cloudy and dark again, I was able to switch off the PV fields without any risk. Everything is already really good - but there is still room for (small) improvement...

The fluctuations have nothing to do with the solar irradiation, as I can see from the other fields. At the moment there is no sun either - there is only very dim light through a thick grey cloud layer. This guarantees that the fields are illuminated more evenly.

The power is absolutely low - I am already happy about 1.xx KW... Peak power would be 23.5 kW. Charging power and DC load are designed for 60 kW (2 x 300 mm² busbars for 50VDC).

I have a suggestion for the assembler code, but for now I will test the last version 556.05.

8 hours ago, VanWykAC said:

My Kodak OG10 does not have option 14  

His is an Infini V IV, which looks the same as an Axpert MKS IV, and very similar to an Axpert VM IV. The Infinis have different settings, and even equivalent settings like battery type are merely in a different order. Just use setting 05 (battery type) on an Axpert; the last setting option should be protocol LIC, just after SOL and LIb. I believe that all OG10s should have this option.

Hi, I flash ultimate firmware 556.05 and this is the grafic on dark night. I can wait to see in the light condition

 

Edited December 24, 20223 yr by ClauBebe