Glad everyone is taking this up with them. @charlvnk@charlvnk who is the local importer? 

Guys also keep in mind that as soon as you set 05 to Li the BMS takes over and your bulk/float charge and also setting 02 and 11(I think) . 02 and 11 control the current for charging and this also gets managed by the BMS and will fluctuate as the BMS sees fit. 

Edited April 13, 20206 yr by Tsa

Hi Tsa,

I only have an e-mail address - don't know if anyone is actually receiving these mails on that account, because I haven't received anything back from them yet.  But then I haven't asked them anything yet - just copied them in the mails to Mahone.

It's this one, from their website growatt.co.za :

[email protected]

Cell: +27 83 468 9783

Hi all

Any Feedback from them ? Just been the sound of crickets here.

5 hours ago, willietes said:

Any Feedback from them ? Just been the sound of crickets here.

Same here. Nothing on the missing data issue from Mahone. I am however again leaning to the fact that mine appears when my batteries get to 99/100% charge then start their self discharge down to 95%. It's seems to happen mostly in this cycle that I lose data and then re-appears some time later. Usually around 89%. 

I have also highlighted another issue to Mahone where my setting 13 (back to battery) is set @ 50%, but even with SOC at 80%+ and PV drops utility kicks in and wants to charge the batteries. So as if it ignores the setting 13 value when PV is no longer available. While PV is active it works perfectly and stops dedicating the PV power to the batteries and then shares PV between battery charging and load. 

On 2020/04/20 at 1:23 PM, Tsa said:

Same here. Nothing on the missing data issue from Mahone. I am however again leaning to the fact that mine appears when my batteries get to 99/100% charge then start their self discharge down to 95%. It's seems to happen mostly in this cycle that I lose data and then re-appears some time later. Usually around 89%. 

I have also highlighted another issue to Mahone where my setting 13 (back to battery) is set @ 50%, but even with SOC at 80%+ and PV drops utility kicks in and wants to charge the batteries. So as if it ignores the setting 13 value when PV is no longer available. While PV is active it works perfectly and stops dedicating the PV power to the batteries and then shares 

Agreed. I grow tired of the slow movement to resolve our issues. 

 

I wish I could get the source and compiler of their firmware and do the code fixes myself.

Hi all 

 

Any of you having issues with MPPT freezing or something ? It would be 1pm in the day, cloudless skys and next thing the PV disengages and runs on battery. 

Then suddenly it pops back. 

 

Seems like their firmware update is extremely shoddy

@willietes @charlvnk Where does one get the PVKeeper software and what do you run it on? Windows? Pi? 

Thanks

Hi @tsa I got PV keeper from the cd I got with my inverter

 

9 minutes ago, willietes said:

Hi @tsa I got PV keeper from the cd I got with my inverter

Thanks will have a look. You just run it on a laptop connected to the inverter then? 

Just had another AC trip at 15:45!!!! Have emailed Mahone and the Dyness contacts all in one now. Time they start talking too each other. 

5 hours ago, Tsa said:

Thanks will have a look. You just run it on a laptop connected to the inverter then? 

Just had another AC trip at 15:45!!!! Have emailed Mahone and the Dyness contacts all in one now. Time they start talking too each other. 

Yebo and you just leave it on.

 

Guys 

 

Awesome news!

I am now working with Growatt to get this datalogging issue right - so far so good.

I will let you know once the firmware is ready for release.

7 minutes ago, willietes said:

Guys 

 

Awesome news!

I am now working with Growatt to get this datalogging issue right - so far so good.

I will let you know once the firmware is ready for release.

Nice! That is awesome news! Thanks for your involvement! 

Do you think this could also relate to the tripping/reset issues we have been seeing? 

1 hour ago, Tsa said:

Nice! That is awesome news! Thanks for your involvement! 

Do you think this could also relate to the tripping/r0eset issues we have been seeing? 

I believe so. When I set to us2 (special Usermode for Lithium) setting my trips disappeared unless my load was greater than battery capacity. That was the only time I could get it to trip in 4 days

8 minutes ago, willietes said:

I believe so. When I set to us2 (special Usermode for Lithium) setting my trips disappeared unless my load was greater than battery capacity. That was the only time I could get it to trip in 4 days

Yip same here. After the last round of trips, I changed to US2 as well and havent had a trip of missing data for the last 2 weeks since doing that. 

Have you been able to see what in the firmware is causing the trips/missing data issue? Loss of comms? Anything related to the auto discharge cycle? 

While you at it, sommer update the FW so is also gets the SOH and cycles of each battery 😝

loooollll 

3 minutes ago, Tsa said:

Yip same here. After the last round of trips, I changed to US2 as well and havent had a trip of missing data for the last 2 weeks since doing that. 

Have you been able to see what in the firmware is causing the trips/missing data issue? Loss of comms? Anything related to the auto discharge cycle? 

While you at it, sommer update the FW so is also gets the SOH and cycles of each battery 😝

loooollll Since I now have the open channel, I will add that to their todo list 🙂 I am already running the test firmware but have been asked not to share yet.

But so far so good EVERYTHING works with the BMS so far. 

 

Thanks is great news! Thanks for the update. 

@willietes Out of interest, post the new FW, does the BOF setting stop the buttons from beeping when you press them now?  I am sure I could silence them with that setting in my original FW, but Mahone thinks I'm crazy. 

Hi guys 

been following this trend to see if we can get to a point of resolving the bms issue. Been working on this for a while now but I keep on getting back to fw. If you look at the firmware they send it is actually older then the fw on the inverter. So it is about time fw gets updated. 
Thank you @willietes for your time to help with this. Can you please send us an inbox with new firmware or email address to contact you as soon as the fw is ready?

regards

On 2020/05/20 at 11:56 AM, Tsa said:

@willietes Out of interest, post the new FW, does the BOF setting stop the buttons from beeping when you press them now?  I am sure I could silence them with that setting in my original FW, but Mahone thinks I'm crazy. 

YEs. Works perfect. Update - Software update is working well. 

19 hours ago, Solar-Jake said:

Hi guys 

been following this trend to see if we can get to a point of resolving the bms issue. Been working on this for a while now but I keep on getting back to fw. If you look at the firmware they send it is actually older then the fw on the inverter. So it is about time fw gets updated. 
Thank you @willietes for your time to help with this. Can you please send us an inbox with new firmware or email address to contact you as soon as the fw is ready?

regards

Will do. The agreement with growatt is I do not give it out until they allow me and I get to work with them.

Nice relationship

Thanks 

Got that firmware already this morning, that is only for the Dyness batteries. 
 

the other software I have is for bms. I have the settings for Shoto and then the Pylontec settings. 
 

There is a couple of things regarding the bms and LI settings I don’t like but will probably get answers in time. 

Hi @willietes 

Do you know if the FW update for missing data issue is available publicly as yet? 

Thanks!

Hi, I have not installed my inverter yet, hopefully tomorrow. It's been lying in my house for almost a month..

Wandering if the missing data issue is resolved?

No idea. Feedback from @willietes was that all the problems are sorted in his initial tests, but he has since disappeared  

I queried with Mahone on the missing data. 

He sent me a FW update which I deployed but the problem still remains.