Jump to content
Thank you for the great forum, Safe Driving over the weekend. Sincerely Jason


  • Content Count

  • Joined

  • Last visited

  • Days Won


SiliconKid last won the day on March 4

SiliconKid had the most liked content!


About SiliconKid

  • Birthday 16/02/1974

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi I only have a single inverter so I don't have hands-on experience with configuring inverters in parallel, but I do recall that the dipswitch settings are different if you are running multiple inverters in parallel. Have you deployed the firmware upgrades to both inverters? You say you did not get a comms cable with the inverters, but it's not clear from your post if you have deployed the firmware updates yet or not. If not, you need to get that done. You are not going to get your system to work correctly until you upgrade the firmware. If you need the firmware let me know I will email or PM you the details and a link to download it. Allan
  2. What Mahone says makes sense to me. Essentially when the battery reaches full charge the inverter shuts off input from PV, for both charging and direct supply to load. It then allows the battery SOC to drop to around 95%, at which point it enables PV input again. That is pretty much the same behaviour I see on mine with mains supply only (I have no PV). Apparently they do that to protect the battery from over charging, and they aren't allowing it to drop below 95% because they don't want it to ever have a lower SOC than that if the mains supply suddenly drops completely (load shedding) and you need your batteries at as close to max capacity as possible, immediately. So that's all good and well and makes some sense, but I still find the approach interesting because I'm not entirely sure why stopping the battery from charging needs to also result in your PV no longer supplying the load directly. I think that's because the load is ALWAYS supplied via the battery, I don't think there is a full bypass mode where the inverter can take the input from the PV and pass it straight to the load, which means that when they cutoff the PV input to the battery, they also effectively stop the PV from supplying the load in any way. And then there is the issue of your inverter randomly going into Standby mode, which still hasn't been explained. Given that you've had that happen in the middle of the night when the PV is clearly not involved, that would still seem so be a completely separate issue that is not related to PV. It would be interesting to know all the official reasons why those inverters decide to go into Standby mode. What is the set of conditions that trigger Standby mode? I wonder if Mahone can give you that set of conditions so we can better understand what is triggering Standby, because I suspect that going into Standby mode is actually a symptom of something else.
  3. Hi Glad to hear you came right. I'm a little confused as to how my original post was not clear on this though. In my original post I noted this: It turns out, the Growatt does NOT communicate via the CAN port. It communicates via the RS485 port that is positioned below the CAN port on the master battery. And in addition to that, it requires a 9600 baud rate, which you can set using the 4 small white dipswitches on the master battery. For the Growatt you must set those dipswitches to: 1 0 0 0 (ON OFF OFF OFF) When connected to the CAN port and put into Li (L02) mode, the Growatt inverter faults and gives an error 20 and an error 04 constantly. When connected to the RS485 port with the dipswitches set to 1000, comms is immediately established and it works as intended. That seems to clearly state that you must NOT connect the cable to the CAN port and need to connect it to the RS485 port, in bold and red Were you speed reading maybe?
  4. OK, well what I can tell you is that even the batteries with BMS and comms capability built in have given our community a lot of issues connecting to various inverters, even when they are supposed to be compatible. And the reason for that is that each BMS has its own protocol that has to be explicitly supported by the inverter firmware, and each BMS also has its own cable pinout for communicating with it. So if you don't have an inverter that natively supports your batteries the only reasonable way I can think of to get that working is to ignore the BMS and just put your inverter into User mode, configure it manually, and use good old voltage monitoring. That seems to be what most of the installers in SA do most of the time anyway, even when they are installing new Li batteries like the PylonTech, with BMS and comms, which shouldn't require User mode. You should be able to get it all working well enough that way if you configure the inverter correctly for the spec of those batteries. I don't think you will win if you try to retro fit some kind of comms to the BMS purely because you would also need a firmware update for your inverter that supports a mode for that specific BMS protocol, which I'm guessing is not going to be possible to get? Or does your inverter already have an Li profile for that specific make and model of battery?
  5. Hi Are those batteries Lithium batteries? I'm guessing no. Given that your batteries have no BMS (Battery Management System) built in, and are probably not Lithium, the easiest thing for you to do is simply run your inverter in User mode and manually configure your voltages etc. As you can see from my various posts I prefer using a BMS when it's available and built in, but in your case where your batteries have no BMS at all it makes sense to just hook them up old school without any comms and let your inverter rely on voltage monitoring in User mode.
  6. Of course they did. The standard answer to all problems when Li batteries are involved apparently.
  7. It really is starting to sound like one of the pieces of hardware involved is faulty somehow, and I'm inclined to think it's the battery given your reports to date.
  8. Interesting that @Digital Clouds is showing 002.003 and mine is currently on 002.001. Not quite sure how he's running a more recent version than me unless the firmware updates I was sent actually revert that revision number to a lower number than the one that is currently on the shipping units coming out of the factory. And I also just want to re-iterate that BOTH firmware updates are necessary for everything to work correctly as far as we can tell.
  9. When you have BMS comms working properly the charge rate settings, and several others, are no longer configurable. The BMS takes over and decides what's best. Again, that's the whole point. Inversion of control. You don't manually set things, the BMS takes control. The 2 settings related to charging current, in particular, are no longer settings, they are now actually real time display values simply showing you how many amps your batteries are drawing at any given point in time. It always amuses me that people are so conditioned to setting everything manually that when the BMS takes over and locks settings down and auto configures values they get confused, and still try to override it
  10. Excellent! So how does everybody else get those firmware updates now? I've got several people wanting to buy Dyness but they refuse to commit unless Dyness will make the firmware available. That nonsense that they won't supply firmware to end users needs to stop. That is not viable in South Africa, the firmware needs to be freely available so people can sort the problems out themselves, we can't rely on installers and suppliers here unfortunately.
  11. Firmware Update FAIL - Recovery Procedure It finally happened, inevitably, and one of our team has run into the dreaded firmware update failure and been left with a non responsive inverter. This is unfortunately the risk you take any time you upgrade firmware on anything, but it's also what makes it all so thrilling. In this particular case, Growatt are clearly aware of the fact that their firmware updater software doesn't always work ... shall we say ... to optimal effect. If you look at the very last page of the PDF file that I provided in the firmware pack (That Growatt sent me) that I've been giving everyone (yes, that same PDF file you ignored and didn't bother to read ... because who needs manuals right?), you will find this gem: NOTE:Sometimes updating may fail, you may close the inverter by disconnect battery break and closeISP tool and disconnect USB line. Confirm the inverter is not power by battery or PV or utility.Then you connect USB line again, and open ISP tool do the same step as above, after you pressFlash button, you let the inverter power on. Wait for several minutes the update will go on. As you can see, failure to launch is not entirely unexpected, and there is a recovery procedure that will (hopefully), save your inverter. PDF attached for those too lazy to go find it on their hard drive. Update SOP for MHP5000_20200102 GRT.pdf
  12. Once again, good feedback. And thanks for doing the firmware updates and eliminating that as the cause. So now we have confirmation on dips and cable and we know that any inverter firmware we currently have access to is not the cause. It would be nice if someone else could confirm your findings because that will tell us if the problem is specific to you and your specific equipment or not. It is looking more and more like this is a battery firmware problem related to holding the comms channel open though, sadly.
  • Create New...