I hope this will be added to Sunsynk 5kw as well.

6 годин тому Sleeper85 сказав:

Hi,

I noticed the same thing with my Deye SUN-6K-SG03LP1-EU.

I spoke with the Deye service about this and they advised me to add optimizers 😐

But, since the latest firmware version:

HMI: 0000-C369
MAIN: 0-4385-1515

A new “MPPT multi-point scanning” option has appeared.

I haven't tested it yet but I hope it will help to have better behavior.

 

I checked. This option does not work for me.
I highlight a checker. I save the settings.
I am looking at the settings - the option is self-turned off (is not stored).

Edited December 9, 20232 yr by Ed Zozulya

I updated the firmware three weeks ago (Deye SUN-6K-SG03LP1).
The situation with the speed of finding a new mppt point, in my opinion, is not good.

Search by the Deye Inverter   for the second mppt point with partial shading of one panel of a string of six panels:
14:06 - the first attempt
14:09 - second attempt
14:12 - the third attempt
14:14 - the fourth attempt

Edited December 10, 20232 yr by Ed Zozulya

Hello,

 

Where/how did you get this FW update? I wrote to Deye support and they said this:

 

"The firmware has been updated to the latest version"1144" for you, but this feature does not exist,Perhaps what you see (they mean this forum) is not our deye's inverter."

 

Then after asking details and pointing to this forum, they said:

 

"Our latest version of single-phase 6KW inverter is C367，His C369 version may be customized，He is a single-phase version and is not suitable for your three-phase inverter.Your inverter types currently does not have this feature, and I will notify you when it is available"

 

Mine is a 8k 3 phases Deye.

 

Any luck with the MPPT tracking problem? I had my Sunsynk 8kw updated to the latest firmware and was told by support I can now select MPPT Mutipoint tracking, wich I did but I don't see any improvement.

 

 

 

Edited February 19, 20242 yr by JBurger

I find that there is an improvement since my original issue whether or not I tick the option in the firmware, but there is an associated problem now in the other string. I am currently querying this with Sunsynk/Deye.  I was also advised that they had done all they could on the shading and that I should explore optimizers. But in fact they made a sincere effort to address the issue and got 80% of the way there, and mostly resolved my original issue, just that there is a side effect which needs to be addressed still.  My production with partial shading of the one string in the morning changed from this (partial morning shading affecting the purple string):

 

to this after a FW upgrade (see the weird impact on the blue string when the shading recedes on the purple):

 

Sadly I am back to where I started. Maybe with sun lower, maybe the FW changes have been reverted to deal with the unintended consequence on the other string.....

Has anyone had any success with optimizers and willing to share what they did?
Alternatively, has anyone managed to get the DC connection under software control so that the cycling can be automated?

Just wondering if it would make any difference to combine the two strings in parallel on one MPPT.

Or otherwise, would it make any difference to schedule a change with the TOU feature? Say for example, start a 5-minute grid-charge at 08:15 each day. Maybe if you have an automation system, try to swap the work mode to solar-sell and back at that time. Or try a change in the Max Solar Power value to zero, and then back up to your max value.

Just throwing out ideas here. If you don't have an automation setup, if you manually change a setting there and back a minute later, if it works, it might be a workaround that could justify getting an automation assistant.

17 hours ago, zak687 said:

willing to share what they did?

I split my 8S string into 4S2P, at least when 4 panels are in full sun I am getting good power from those 4. Sunsynk needs to adjust the code of their MPPT to look for global maximums power points. Their firmware is lacking.

2 hours ago, iiznh said:

I split my 8S string into 4S2P, at least when 4 panels are in full sun I am getting good power from those 4. Sunsynk needs to adjust the code of their MPPT to look for global maximums power points. Their firmware is lacking.

Is this 4S2P on one MPPT, or did you connect 4S per MPPT? Do you have any graphs maybe showing the difference between those setup ideas? Just have this nagging question in my head of whether 4S2P on one MPPT would resolve the issue, since the MPPT Voltage should hopefully not drop below the shutdown Voltage in the morning when one of the strings gets early shade shortly after starting up.

@GreenFields One MPPT has 5S and the other 4S2P, the voltage shows that it is always above the minimum, there is just very little current when not in full sunshine. The voltage dips mid-day is when it actually produces some real power

Edited June 4, 20241 yr by iiznh

On 2023/06/19 at 11:26 PM, FrancoisSnyman said:

So as a test, I split the one string of 8 modules into two strings of 4 each. 

As a comparative measurement - I attach two screenshots showing the total DC Input Power (i.e. total power produced by both MPPT's).

This one from 2023/06/15 is when all panels were connected in series on one MPPT:

And then for 2023/06/17 when the panels were split into two strings, one on each MPPT:

 

Production increased from 10.9kWh up to 12.9kWh... Same shading on panels, nothing changed as of yet here.

Less voltage on each string.

 

Anyway - thought I would post the update for anyone interested

@FrancoisSnyman will you please post the graphs per mppt? Voltage, Amps and wattage.

17 hours ago, Inverter said:

@FrancoisSnyman will you please post the graphs per mppt? Voltage, Amps and wattage.

What I did not see in any of the replies is that you need say 2 adjacent columns 1/2, 3/4 or 5/6 covered by over 80% shade before the bypass diode conducts. Normal shade over columns gets the panel to conduct but very little. This then throttles the whole series string very badly. 

Hello,

reposting as maybe my comment was missed ^^

 

Where/how did you get this FW update? I wrote to Deye support and they said this:

 

"The firmware has been updated to the latest version"1144" for you, but this feature does not exist,Perhaps what you see (they mean this forum) is not our deye's inverter."

 

Then after asking details and pointing to this forum, they said:

 

"Our latest version of single-phase 6KW inverter is C367，His C369 version may be customized，He is a single-phase version and is not suitable for your three-phase inverter.Your inverter types currently does not have this feature, and I will notify you when it is available"

 

Mine is a 8k 3 phases Deye .

I'm using Deye SUN-12K-SG04LP3 inverter. Connected to the inverter are 30 450W panels (Risen RSM108-10-435-460BNDG) organised in 3 strings 10 panels each.

Currently the two string sitting higher on the roof are connected to PV1 (the inverter has two parallel string inputs). And the lower string is connected to PV2.

The lower string is seeing partial shading of 5 panels. Before 14PM I'm seeing very little production on PV2 - 200W at most. Around 14PM all panels are fully lit and it goes up to 2500W.

I contacted Deye support for some help, they haven't replied yet..

Couple of questions:

1. Is there anything else I can do to improve PV2 production - other than waiting for Deye to fix the MPPT algo?

2. DC optimizers on the shaded panels - are they likely to mitigate this issue?

3. I was thinking to connect the top two string into single string with 20 panels. This should give open circuit voltage around 800V which is within Deye spec. Will this improve production? Is is true that one should maximize the voltage on the string to get optimal performance?

4. When 5 out of 10 panels are shaded the MPPT voltage is around 175V. Does this mean that the inverter will not even try to go in this voltage range to search. Deye manual for 12K says that PV array MPPT voltage range is 200-650V. Does this mean that in shaded conditions the inverter has to chance of setting the MPPT voltage because it's out of the range?

2. Optimizers should help to allow part of the lower string to produce a higher output as long as all 10 are not covered by the same shade AFAIK. 

Good news. I was the initial poster on this thread. I let it lie for a while but decided to see if Deye/Sunsynk managed to sort out their MPPT algorithm which seemed to get bogged down in a less than ideal power point. Manual cycling of the string forced a full rescan and usually the MPPT then found the best power point. Not ideal. I recently updated my 8kW Deye to firmware Main: 6027-1724. Selected "MPPT Multi point scanning" in the "Advanced Function" menu under "System setup" and viola problem solved. In any case for my shading scenario. Much, much better. See below. The partially shaded string (PV1) now gradually improves its power output until it is unshaded and similar to PV2. Been tracking it now for a few weeks. It is not a fluke. I would like to believe that Powerforum and maybe this thread helped to make Deye/Sunsynk aware of the problem which they seemed to have solved. Not sure for their other inverters but it must have been a universal problem.

Edited March 14, 20251 yr by rfl
Font not consistent. Added "Advanced Function" menu under "System setup"

Thank you @rfl for helping me solve the exact problem you have, It works like a charm for me.

I wanted to share this to show the multi-point scanning option at work. Green is the power from my NW roof and blue is the power from my NE roof. NW roof has some shade in the mornings and I've always struggled to get it kickstarted in the morning. With the recent addition of the NE roof and the new firmware option, it's interesting to watch the firmware option at work. Yellow and orange are the voltages and it seems the inverter varies that at times in an attempt to get more power from the panels. There's several points on the graphs where the voltages were varied and the power immediately increased.

PS: the power and voltage values of the NE roof aren't really negative; it was the only way I could (think of to) get 4 strings into 2 graphs.

On 2023/12/09 at 2:16 PM, Sleeper85 said:

I haven't tested it yet but I hope it will help to have better behavior.

 

Did you test already?