Everything posted by Kalaharipro
-
DC Current PV behavior
It is grid tied - PV first, then battery, then Escom. The panels are cleaned every 3 months or so - and in summer with rain most poop is also washed away. As I mentioned in the first post this scenario suddenly appeared in April after running perfectly for 908 days. Browsing through all the days since then there doesn't seem to be a 100% fixed pattern. Most days it occurs, sometimes for an hour then lines up with Pv 1 and then maybe drop again, today for example the drop was until the batteries were fully charged - ie the PV production "need" dropped. It sits mostly at a 600-700W drop in production, but sometimes it's 200-300w. Its never been more than 700w So its a bit random, when it does happen it is normally around 09:00 till batteries are full, and then after that it mostly tracks PV1, but not always - and not nearly as closely as what the Slave does. Slave is almost a carbon copy on PV1 and 2 - not at all the case on Master And as mentioned, nothing changed that I am aware of - not software or hardware, or any settings. Not sure if Deye has remote access and could have updates software etc?
-
DC Current PV behavior
-
DC Current PV behavior
I managed to get two photos earlier today of the inverters in action. Master - PV2 shows the lower Watts created MASTER SLAVE The above was taken around 09:40 - graph below MASTER SLAVE
-
DC Current PV behavior
Ok thanks will go that route - but its a Deye unit, so will call them
-
DC Current PV behavior
So since day 1 Slave has always run hotter than Master - so the slides below are inline with normal behavior as far as temperature goes. I don't see any correlation between the AC/DC temp and the drop in PV power 10 August MASTER Peak temperature DC 66 AC 55 SLAVE Peak temperature DC 95 AC 56
-
DC Current PV behavior
Thank you for the feedback so far. At one stage I thought it might be heat related, ie when it gets to a certain surface temp it looses some efficiency (which is generally true but then all panels becomes less efficient), but I started to watch that closely and even in that there was no consistency. It seems as if PV2 on Master struggle to keep the "load" consistently, but then again on some days it does. Could it be a loose connection that does it? Yesterday for example it was freezing cold with rain till around 14:00, then it was mostly fun sunshine. See how it "keeps up" in the cloudy and rainy weather, then totally fall back when the sun comes out, but at around 15:20 it then suddenly starts to track the PV1 almost to the tee.
-
DC Current PV behavior
Good day First disclaimer, I am an enduser and not technically proficient on solar at all. So if what I am trying to explain makes no sense then please forgive me. I have two 5kw Deye single phase inverters, setup as master and slave, with that I have 24 x 455w panels, and 5 x 5kw batteries The system has been running for 1029 days and for the first 908 days the behavior described below did not occur Each inverter has 12 panels linked to it, and standing in front of them looking at their live performance the load is (up to date 908) equally balanced - PV/Grid/Load/Batteries. So the one does not work harder or perform better than the other. Then on 10 April this year the PV produced, suddenly started to show a difference, with the Master producing less - on ave around 700-800w, at times I did not do anything physically to the system, or to software, or to any setting - it just happened by itself as far as I can see. And also the all 24 panels are on the same level and angle, with zero shade on them during the day, so a shadow of a tree is not the issue I am not sure if I am looking at the correct stat, but going through the different options on the software I saw that on DC Current PV I could see the difference. I have no idea how the physical setup was done, but as explained both inverters have 12 panels, and somehow the "stats" see it as DC Current PV1 and DC Current PV2 for both inverters (so 4 sets of data for the 24 panels) So up to 10 April all PV DC stats were "perfectly aligned" on stats for both inverters - se below what I am trying to say Master Slave Master on 10 April Since then this has always been the case, with DC PV2 on the Master producing less (red line). Looking through all the days it seems to start in line with PV1, then drop off somewhere for a couple of hours and then catches up again by producing the same. Most days its not inline with PV1 - especially if you compare to how closely PV1 and 2 follows each other on the slave Here for example are the stats for this week Master Slave So the question is twofold. What is causing it to make me loose generating capacity of around 700-800w most days on Master for a couple of hours, and secondly how do I fix it?
-
Deye sometimes "dynamically" creates its own minimum SOC
Thanks for the feedback. I do not see that specific indication on mine (picture 4), but either way the explanation you give make sense thanks.
-
Deye sometimes "dynamically" creates its own minimum SOC
Good day Let me start off by saying I have a workaround for this issue, but surely it must be a glitch? Not that I am at all qualified in the field of PV, so my comments and deductions might be silly to the experts on this forum. In my limited technical understanding the setup of my solar system is as follows. 20x455w panels 2x5kw Deye inverters 5x5kw Greenrich batteries Setup to feed house 100% at all times - so nothing in the house excluded from getting electricity off the inverters. Only when battery and PV can't supply demand if would use Eskom My system is big enough to take me off grid about 85% of the time, which means my batteries are fully charged through the PV about 85% of the time. I like to run my system in a way to allow me absolutely minimum Escom dependancy, which obviously also equals very low Escom cost. Typically I will set all of my daytime zones to run down to 20% if need be, and only then start to use Escom if PV is not enough to handle the load at the time. So what I have noticed a few times now, and the first time it took me a good week to get the workaround going, is that if the batteries do not charge to 100% for more than 3 days in a row, then it starts to "ignore" my 20% setting. This typically happens when we have the type of weather currently in Gauteng where you have a number of days in a row where it rains and/or there is thick cloud cover. So what would happen is it would start to add 1%-2% a day (when it does not charge to 100%) to the 20% minimum and then starts to use Escom power. Just to be clear, it does not change the actual setting on the device, it just "dynamically" start to do its own thing and creates its own minimum. For example the first time this happened I had a week or so where I could not get enough sun to charge to a 100% SOC minimum set to 20% From about day 3 onwards this happens (I am fairly sure this does not happen in the first two days, but could be wrong) Day Setting Escom usage starts 2 20% 22% 3 20% 23.5% 4 20% 26% And so it increased daily up to around 31%, even though the minimum was set at 20% And then I got a full sunshine day, the system went back up to 100% and from there on the issue was resolved again. This has happened 3 times now in the last year or so, and there are two ways of "fixing" it, either you charge the batteries to 100% via Escom, or you let the sun take it back to 100% - both takes the issue away. So it seems as if the "self regulating" minimum appears after around 3 days of no full charge, and disappears as soon as the batteries have had a full charge. But as soon as we have not had full sunshine (like for the least couple of days) it does its own thing again. Maybe the system should work like this? Not sure if anybody else has had the same experience.
-
Power from grid higher than setting
Agree fully. I suppose they get away with it because the system does function, and unless you really look into the detail of what is happening then most wont pick it up. I now for the first time have a true view of actual usage and my stats makes sense, compared to the meter stats. Even before all of this started there was a miss match between what the stats said I used as "Power Purchased" compared to what the actual meter reading was. I thought the stats were just incorrect (indicated 30-40% of actual usage), but now the "Power Purchased" stats align 100% with what the meter says.
-
Power from grid higher than setting
UPDATE - Resolved So this is very early days but it seems as if the solution was the adding of a CT device on the DB board/inverter. In my limited technical understanding the setup of my solar system is as follows. 20x455w panels 2x5kw Deye inverters 5x5kw Greenrich batteries Setup to feed house 100% at all times - so nothing in the house excluded from getting electricity off the inverters. Only when battery and PV can't supply demand if would use Eskom Worked perfect until the whole situation on this topic started happening. First it was the roughly 300w per hour it pulled from Eskom, even though the setting was at 10w. And then in the last 2 weeks I went totally belly up and randomly used Eskom power - although the system did not show it - between 17kw and 30kw a day on meter which was not reflecting on system. So the simple solution was - install a CT on the board, and now everything works 100% as it should. I have almost zero movement on my Eskom meter, and the system does as it should. For the first time my "Power Purchased" stat is also accurate - used to show around 30-40% of what the meter showed I used. After a bit of Googling it seems as if it is not uncommon practise to run a solar system without a CT. In my case, for whatever reason, it is actually very necessary.
-
Power from grid higher than setting
Thanks for all the responses, so let me explain in another very simplistic way what is happening here. I am not technical at all, so apologies if I frustrate you. So during autumn to spring my system is big enough to give me a 100% off the grid experience - I can literally disconnect Eskom power and not have a moment without electricity. Last year during the same period I went through 157 days of zero need for Eskom, but due to the importance of the trickle feed I obviously did attract some usage - something to the tune of 150w/h*24 = around 3-4 units a day. Post the master being replaced that suddenly jumped to double that, and now in the last 10 days it jumped to 17 units a day - with still zero actual need for Eskom power, and zero change to any setting (that I am aware of) The stats are also not reflective of what is really happening. The power usage patterns in my house has not changed but yet the stats for Grid usage, as well as Consumption in the house has dropped by between 700w and 1kw/h - as per the stats. So having read my meter this morning compared to 10 days ago, I used 170 units of Eskom power. That is nowhere to be found on the stats and on the active displays, but the house is using it. So I am still using around 37-42 kwh per day, but the inverter stats recons its only 23-30. In short my total usage per day has remained unchanged, but the stats shows differently - and Eskom is smiling. Whatever is causing that to happen I have no clue, and that applies to Deye as well as my installer. So from the stats there are only 2 things that is factually visible - on 21 May at 13:30 my issue of 300w-350w trickle feed (original issue after replacement) suddenly went away and become 0-2w trickle feed, at the very same time my illustrated usage fell by 700w-1kwh. It looks as if the PV and battery stats remained accurate.
-
Power from grid higher than setting
Thanks, that's a bit too technical for me though. I am limited to operating the touch screen - but thanks anyway!
-
Power from grid higher than setting
So I have set it to load first - it was on battery first. Also took 2 pictures just now of some settings - as well as what the dials are showing. Notice no usage in house - totally wrong, many things running, should be around 2kw+. Both investors shows the same - zero for house
-
Power from grid higher than setting
I am in the East of Pretoria, close to Centurion
-
Power from grid higher than setting
Thank you. The system has been in for almost 2 years. Up to the Master been replaced in Jan, it worked perfectly. I am not aware of any system changes or setting changes, I never touch those myself. So from original installation to replacement of unit I ave about 3units a day (on whatever the settings was), then when unit was replaced it went up to around 8 (with supplier checking on three different occasions that the settings where the same as before). The suddenly 10 days ago (without me being aware of anybody changing anything - definitely not on site) the stats went crazy for actual usage as well as grid power, with me now using 17 units a day. Below is a graph on the day it happened For example it is not possible for me to use less than 700w at night as I have a oxygen unit running 24/7 for my mom that draws 620W So it might very well be setting related, but I have not changed anything and those who have had a look recon all are set correctly - hence my request for some expert to come have a look
-
Power from grid higher than setting
The original issue started as per the very first post in this thread Morning So 4 months later I still do not have a solution from the installer or the supplier. Unfortunately the situation has moved backwards - without me doing anything. The stats are showing I take zero power (0-1W) off the grid, that my consumption is around 1kw/h lower than actual - and yet I am using around 17units a day from ESKOM. That is with zero need to do so as my batteries(25kw) are more than sufficient to cary me thought the night and typically end up around 50-60% left when the sun starts to do its thing again. Fully charged again by 13:00/14:00 most days So my situation has changed from (and it is supposed to be 1-2 for trickle feed) 8 units a day tot 17 units a day - without having to use any ESKOM power. Not sure if one are allowed to ask it in this forum, but where can I get hold of an EXPERT that can come and have a look at the system. I am in desperate need of somebody who is truly knowledgable on Deye invertors and the correct setup for a Master/Slave hybrid system? Regards Jacques
-
Power from grid higher than setting
So took these pictures - not sure if they hold any clues. I have no idea what all the abbreviations mean. First one is the master, showing the 10W it is set at. Second the slave, also set at 10W but using 250W plus non-stop from the grid.
-
Power from grid higher than setting
Ok so I tried what I think you asked. Untick the solar having to use Eskom if the battery is to low compared to setting - for a specific time slot Did it and the load from Eskom remained unchanged - so even though I told it not to make use of Eskom it still took load. Then I did it the other way round, put the battery at 100% from grid for the time slot, but unticked the box, so it should not use Eskom? Again it did not consider the unticked state and started charging the battery. With "use grid" unticked and thus not supposed to add to battery - even if just trickle Still used Eskom Then with battery supposed to charge from Eskom to 100% (but set not to use Eskom) Not sure if this is what you suggested. Just another comment I forget before. The load of 300w (varies between (120and 300W - mostly above 250W) only comes from the slave - the master shows zero to 1W
-
Power from grid higher than setting
Good day First off I am not an installer, nor competent on solar in any form or shape - so please excuse any nonsensical remarks or questions. So the background as follows: I have 2 x 5kw Deye inverters, setup as slave and master Both were set before to draw 10W from grid at all times This worked out to be around 30 w of continuous usage if the need for higher consumption from grid was not there The master got damaged and replaced and since then: With the settings as before on 10W for both machines it now continuously draws around 300W, when no Eskom load is needed I have changed this to 0W, 30W, 50W - it makes no difference, it stills draws 300W I have checked every single setting I can find on both master and slave - and they all mirror each other Below the two setting (I think) which talks back to how much is drawn from grid when no Eskom load is needed Master Slave Current load if no power is needed from Eskom So the problem is that my installer does not seem to have an answer, Deye neither. We have confirmed that both run on the same version of firmware as well. My concern is that I have a very big installation and manage to be off-grid 80%+ of the time, however with this 300W continuous draw I now end up with something like (300W*20hours*30days) 180KW a month of Eskom power I am not in need of. And we did test the slave in isolation as well - it then draws no more than 30W I hope this makes some sort of sense? Any suggestions please? Regards Jacques
-
SOC stats crazy after additional battery was added
Software was updated and the SOC seems to be accurate again. So it seems as if different firmware/software (even though it is the same battery type) caused the issue. As mentioned before I could clearly see that the additional battery was adding the extra capacity, the SOC was just all over the place.
-
SOC stats crazy after additional battery was added
I got hold of the installer. He spoke to the suppliers eventually and they asked him to update the battery software/firmware - if that makes sense. I will give feedback on the result once the update has been done.
-
SOC stats crazy after additional battery was added
Thanks I'll do that. I do not think any of the settings were changed - and all the readings prior to the additional battery worked perfectly. The 5th battery was connected to the other 4 and then the stats started going in the wrong direction.
-
SOC stats crazy after additional battery was added
Ok thanks, that makes sense then
-
SOC stats crazy after additional battery was added
Thanks for the response. Just a quick question on the charge discharge. Seeing that my installation is under warranty I don't want to change anything myself. Is there a risk of anything breaking or causing fire/failure issues as the current settings? Or are the paramaters just set extremely wide and the system can't get there in any event - so no need to change from a risk perspective?