ZS1SCI

He quoted twice, rails and IBR truncated brackets, no where did he communicate the problem(non OEM compliance) with the cheaper solution.
We asked for a cheaper quote which he provided.

Hi there so if we look at the following illustrations

then the next page


That would mean the only correct installation method for these panels, is the long frame as per 1st image mid left.
All other options are not supported.
This is going to be a fun conversation...

Thanks for everyone's inputs so far !
Nou moet ek gaan baklei met n bra :/

Eish

Interesting discussion about the "Rules"

Moer hom!
But in all honesty, this installer doesn't seem to care about right, wrong or OEM specifications. Tell him to replace or get reported.

Hi, I think it might just be easier to make the new rails higher on one side than lift the IBR roof as a whole.

Want to give vinegar a try on the spots? Wet a rag full of vinegar see if it helps?

Fire would probably result if MC4 connectors are touching the roof. Water would probably the damage the panels but I don't see it starting a fire.
Yes, draining clips is a plaster on a broken leg. Fix the panels at 10 degrees or more.
Yes, have the panels replaced.

Those panels are cooked , why would you rub them with vinegar haha ? water and dirt is under the glass layer . Solar panels have a anti reflective layer that is not acid /detergent friendly btw . Those panels need to be replaced and the new ones need middle support IMO.

Hi ZS1SCI! Thank you for the information provided on the forum. Currently I am monitoring my battery using Canalyst - II, Home Assistant via Inter CAN bus and PCS CAN bus, I also connected a NEEY balancer. Everything works fine. All that remains is to install Grafana. Thanks.

I finally got the battery monitoring working in Home Assistant. I used two ESP 32 to collect data. One runs on the Inter CAN bus, and the other on the PCS CAN bus.

Good morning
I've finally managed to get the batteries in a more stable state:
The wacky behavior was noticed after Deye did a remote firmware update on my batteries, which changed the charging voltage on the BMS from 57.6 to 58.4V.
Which I erroneously assumed was the culprit of this misbehavior:


The batteries would go into an alarm state when overvoltage was reach for a cell and then drop down to a certain voltage and repeat the same cycle.
After unplugging the CAN cable this routine would stop

The following is over the last two days, set the battery mode to AGM and the voltage settings according to battery manual.

Then after Deye sent be the software and firmware to flash locally, the same happened when I let the inverter and battery talk via CAN. 

So I went back to my solar assistant graphs and recalled that I had changed a default setting called Disable Float Charge some time back, it made my battery go through these 10 hours charge and discharge cycles(which I thought strange at the time), but not disabling float charge has seem to remedy the over voltage issue experience.
The effect of which was just exacerbated by the new firmware which upped the Charging voltage.

So what I have learned now with these batteries and the Deye inverter, this floating charge should not be on.

Cells are happy now.

Thank you for listening to my Ted-Talk.
Have a nice day

Hi @Muttley @IggyP . Its a known issue with that card. Here is a link to the fix
https://github.com/AmoebeLabs/flex-horseshoe-card/issues/88#issuecomment-2145334978

Hi @ZS1SCI
I have a question for you regarding the communication with the battery and the LVESS program. Are you using CANalyst-II for this ?  
 

 
Like the predecessors in the topic I cannot read the voltages of the individual cells. Of course I am connected to interCan however the IDs I get are quite different to yours. The battery software is AA56 2008 I wonder where to look for the problem ....

EDIT: Perhaps there is something interesting in the LVESS logs?  

I have already installed the 3rd module MCP2515. But unfortunately I have not received data from the IN port. I don't know how to deal with this((((

Hi. I also could not get cell voltage data via mcp2515 and interCAN. But after I connected to the batteries via LVESS using CANalist II and interCAN, I started receiving data via mcp2515 too. I think that some command is needed to start the necessary registers. I also tried connecting via two tja1050 boards, but in this case only interCAN worked for me, and pcs did not work with this connection.

Hello @ZS1SCI,
I just registered on this forum to thank you for the amazing job that you have been doing!
Could you please give me a graphic of SOC vs BMS voltage for these batteries? Basically I just need see their voltage during one cycle of charging/discharging.

You probably forgot to say in the description that there should be a module like TJA1050 or SN65HVD230 between the ESP and the Battery?
Link https://esphome.io/components/canbus/esp32_can.html

Hello,
I just received from DEYE two SE-G5.1 PRO B batteries.
These are new models with quick connectors like the Pylontech batteries. For testing, I use the YAML code with a MCP2515 and I receive the PCS information on Home Asistant. For now I can't receive the information on the RJ45 IN and OUT ports. For these ports I use a CAN SN65HVD230 adapter.
I am working on the problem with European friends who know HA, ESPHOME, ESP32 / S3 etc.
Concerning these batteries which seem different inside to those in the photos of this post there is a large resistance of 12 ohms / 100W.
which is connected to the BMS at the level, it seems, of the "balancing" part.
Is it a single resistance for balancing, or a resistance which serves as a heating element?

Have you tried to use equalization function? ( which is basically for AGM but you can used it for lithium if you modified the voltage ) so this feature will allow charging voltage without current so it could Triger balancing for enough time 

What inverter are you running it with? 
Im using ESP in the middle to alter the message for charge voltage. 

 
We can downgrade if we had 2004 fw.
Deye didn't want to provide the old binary as it was too buggy...
2004 had 57.6V charge voltage request 
The behaviour of the BMS is to set soc to 100% when any cell hits 3.6V and then switch off the charge mosfet until 99% soc is hit, then allowing charging again. 
 
With 58.4V this is sped up quite a bit and imbalanced cells reach this quickly whilst others are still 3.44V.
With charge mosfet off after this there is no equalization time. 
Anyways it's not like the balancer is up to the task, I'm adding a Neeeeeeeeey 4th generation balancer to each of my packs to fix the imbalance and void the warranty 😁
Anyways good luck deciding 

This was at 55.2V charge voltage request

What inverter are you running it with? 
Im using ESP in the middle to alter the message for charge voltage. 

 
We can downgrade if we had 2004 fw.
Deye didn't want to provide the old binary as it was too buggy...
2004 had 57.6V charge voltage request 
The behaviour of the BMS is to set soc to 100% when any cell hits 3.6V and then switch off the charge mosfet until 99% soc is hit, then allowing charging again. 
 
With 58.4V this is sped up quite a bit and imbalanced cells reach this quickly whilst others are still 3.44V.
With charge mosfet off after this there is no equalization time. 
Anyways it's not like the balancer is up to the task, I'm adding a Neeeeeeeeey 4th generation balancer to each of my packs to fix the imbalance and void the warranty 😁
Anyways good luck deciding 

This was at 55.2V charge voltage request