Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Youda last won the day on March 13 2021

Youda had the most liked content!

Profile Information

  • Location

Recent Profile Visitors

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

Youda's Achievements

  1. Yes, PIP-5048MK and Axpert King are the same machines. RS485 cable for one of them will work with the other too.
  2. Yeah, the current 3-phase hybrid inverters from almost every manufacturer now are using HV batteries (where allowed voltage range is typically 200V to 400V DC). LV, aka 48V DC batteries are being used for 1-phase inverters mainly. Speaking of Pylontech, their HV and LV batteries are talking different protocols. Therefore, BatteryView version intended for US2000/3000 is incompatible with H48050 of Force H2. If you want to try it out, I have a BatteryView version for HV batteries as well. It works with H48050 (aka PowerCube-X1), but I don't know whether is will work with Force-H2 too. Anyway, RS232-to-USB coverter, together with a correctly wired communication cable is a must, of course.
  3. https://www.mppsolar.com/v3/download/
  4. In my opinion, the best hybrid mode is "Grid Tie with Backup II". Eastron meter is needed in order to get this mode to work correctly. In this mode, the inverter blends Grid+PV+battery power together. It allways try to compensate grid to zero: If there's too much PV power, the inverter lowers it's output in order to reach zero export. If there's a huge load on the backup or AC side, the inverter uses PV first, then battery, then the grid. You can also limit the amount of Power (watts) that will be pulled from the battery. If there's a need for more power than this limit, the remaining watts will be pulled from the grid. Logic: If you have some loads connected to the AC IN side of the inverter, these load will benefit from the PV, Battery and the Grid too. Once the grid is down, these load will go down too. They are not backed up. These load can be huge, there's virtually no limit on Amps. Whatever is connected between the grid and the Eastron meter, will NOT benefit from PV, nor from the battery. If you have some loads connected to the AC OUT side of the inverter, these loads will benefit from PV, Battery, Grid. These loads will be backed up even if the grid goes down. These loads have a current limit of approx 21A. For a shame, this mode does not work with NetMetering because it aims at 0 export. If you have an excess power generation, fully charged batteries and small AC loads, the inverter will lower it's output. If you want to use NetMetering, the best mode is "Grid Tie with Backup I" In this mode Eastron meter must NOT be installed. The logic is very same like in the previous mode, but with two exceptions: All the loads in the house will benefit from PV+GRID, no matter where they are connected. If you have excess PV generation, all of it will be fed to the grid. In most of the countries, there's a limit of roughly 3700W set in the inverter's configuration. Feeding the battery to the grid By default, feeding the battery to the grid is disabled in all the modes. However, if you really want to, you can manually tick "allow grid feed-in" + "allow feed-in battery to the grid". Then the inverter will send all the excess PV generation to the grid, up to a defined limit (normally 3700W). And if there's not enough PV, it will discharge the battery to the grid too. Again, up to a total limit of 3700W by default. For a shame, it's not possible to control battery discharge based on the SoC. It simply discharges the battery up to a point where the low-voltage threshold kicks in.
  5. Yeah, I know that it might sound strange but I'd like to stay objective whenever comes to judging something (or someone). Some other people are not able to criticize a product if they just spent a huge amount of money on it. For example, a Mercedes owner rarely tells you that there's something bad on the car and that if he had a second chance he would go for a Bentley instead. Also, some people are recommending a product just because they don't want to be only ones who's using it. Even if they know that the product is a bit sh*tty. The case with my InfiniSolars is that I'm okay with them. I know how to manage these machines in my setup, I know how to remotely read operational values and execute commands. But there's a lot of drawbacks and painpoints too and it took me a while to found out. Based on the experience that I've made I have to say that for almost every use case there's a better product available. For example, Axpert is much more efficient and way cheaper for the offgrid solutions. GoodWe is more efficient, more compatible, more intelligent as a hybrid. Victron has much bigger scalability, frequent firmware updates and has a complete ecosystem of devices for automation, monitoring and other accessories. So, yes, I'm happy with my inverters too, but if I will build another house in my life, I will choose a different hardware. Not sure what exactly, but at least I know what features I want and what pitfalls to beware of
  6. This is pretty normal, like @plonkster explained. If happens once a while then it's okay. But, if that happens everyday, then it means that the real capacity of the cells is much lower than what's hardcoded in the BMS FW. Everyday jump from 90% to 100% is okay. Everyday jump from 76% to 100% is not.
  7. Hi guys, based on the fact that many forum users are trying to understand how to use Pylontech batteries efficiently, I've extracted some of the internal configuration values. It's from a stack of 8xUS3000. What instantly catched my eye are especially these values. So I added a couple of my comments and thougths: Total Num : 8 //Number of maximum daisy-chained bricks supported by the firmware. Present Num : 8 //Number of actually daisy-chained (RS485) bricks. Shut time : 72.0 H //If the brick is not charged/discharged for 3 days, it will auto-power off. Balance Volt : 30 mV Balance Start : 3360 mV //Looks like the BMS is able start balancing cells at this voltage it's not //a static top-balancing, as I know that the BMS chip is able to stop balancing //at a much higher voltage, if all the cells are at roughly the same voltage level. Recommend chg voltage : 53250 mV //This is what inverters like Axpert are reading //from the BMS and using as CC. Over VoltageR : 51000 mV //Strange, that this is triggered at 51V, given //the recommended CC=53.2V. High VoltageR : 52500 mV High Voltage : 53900 mV //Just 650mV of margin between recommended CC=53.2V and alarm. Over Voltage : 54000 mV //Just 750mV of margin between recommended CC=53.2V and panic. A complete list goes here. Please note that the column "Battery" means actually a CELL while the column "Power" means a single US3000 BRICK: Protect Attribution --------------------------------- Item Battery Power Over Voltage : 3700 54000 mV Over VoltageR : 3600 51000 mV High Voltage : 3650 53900 mV High VoltageR : 3500 52500 mV Low Voltage : 3050 46000 mV Low VoltageR : 3100 47000 mV Under Voltage : 2900 44500 mV Under VoltageR : 3250 49000 mV Sleep Voltage : 2500 38000 mV Charging OT : 61000 61000 mC Charging OTR : 55000 55000 mC Charging HT : 59000 59000 mC Charging HTR : 55000 55000 mC Charging LT : -9000 -9000 mC Charging LTR : -5000 -5000 mC Charging UT : -11000 -11000 mC Charging UTR : -5000 -5000 mC Discharging OT : 61000 61000 mC Discharging OTR : 55000 55000 mC Discharging HT : 59000 59000 mC Discharging HTR : 55000 55000 mC Discharging LT : -9000 -9000 mC Discharging LTR : -5000 -5000 mC Discharging UT : -11000 -11000 mC Discharging UTR : -5000 -5000 mC Charging OC : 102000 mA Charging OC Alarm : 50000 mA Charging OC AlarmR : 40000 mA Discharging OC : -100000 mA Discharging OC Alarm : -50000 mA Discharging OC AlarmR : -45000 mA OC Delay : 15000 mS OC Release : 60000 mS Charging OC2 : 200000 mA Discharging OC2 : -200000 mA OC2 Delay : 100 mS OC2 Release : 60000 mS Discharging SC : -400000 mA SC Delay : 0 mS SC Release : 60000 mS Charging Max Cur : 10000 mA Balance Start : 3360 mV Balance Volt : 30 mV Shut time : 72.0 H BUV/PUV time : 2400 S Sleep ctrl state : OFF Sleep every day StartTime : 20:00 EndTime : 08:00 HwSleepInfo HwSleepStatus : OFF HwSleepTime : 6 S HwWakeupTime : 60 S Data Save every day StartTime : 00:00 EndTime : 23:59 Save Interval : 1800 S Power System Information --------------------------------- System is idle Total Num : 8 Present Num : 8 Sleep Num : 0 System Volt : 49381 mV System Curr : -367 mA System RC : 352367 mAH System FCC : 585266 mAH System SOC : 60 % System SOH : 99 % Highest voltage : 3294 mV Average voltage : 3292 mV Lowest voltage : 3290 mV Highest temperature : 23000 mC Average temperature : 21875 mC Lowest temperature : 21000 mC Recommend chg voltage : 53250 mV Recommend dsg voltage : 47000 mV Recommend chg current : 296000 mA Recommend dsg current : -296000 mA Hope this helps all the young scientists that are developing their own monitoring and control solution for the batteries and inverters Youda
  8. The download is in my LAB thread, link to LAB is in my signature. There is a long post with pictures and the actual file is attached at the end. More than 200users dowloaded it already, you can make it too
  9. Trust me, it's not possible for LiFePo4. With some other Liion yes, but not here. The only way to determine the correct SoC is counting in/out amphours. So Victron BMV700, shunt, coloumbmeter. And since BMS already has this circuit implemented, the most obvious way is to communicate with the BMS. But don't worry. I would say that within 5yrs this feature (custom top-bottom charge/discharge based on the true SoC and BMS communication) will make it to the inverters In the meantime, you have to code your own middleware, if you want this.
  10. For a shame, it's not that simple. The SoC/Voltage curve of the LiFePO4 batteries is so flat that there's almost the same voltage anywhere in the range of 20-80% SoC. Even in the 80-100% range you cannot say what's the SoC based on the voltage. It's like behaving like 80%...80%... and now suddenly 99% and 100%. Technically, the feasible way is when the inverter actively talks to the battery BMS and once the BMS reports 90% SOC the inverter should stop charging it. But, like I said before, I don't know any inverter that is able to use such a rule. For the high-voltage batteries (200-400V) the common practice is that the inverter charges to 90%, then stops charging. For example SolaX X3 Hybrid operates like that. But in the 48V world, if you want to have this feature, you have to implement your own monitoring solution that will communicate with the battery via CAN or RS485 and then instruct the inverter to start/stop charging. It's doable even in my current homebrew monitoring, but I'm too lazy to code it...
  11. @Rclegg just check the whole thread you will notice the reason for that short period: @Pren mismatched DoD and SoC in his description. In reality, he's using just 1.4kWh out of 2xUS3000 and then he's switching to grid. Basically treating 7kWh of lithium like 7kWh of lead-acid
  12. Personally, I'm cycling my US3000 stack between 100% SoC and 40%SoC. Once discharged to 40% SoC, my system automatically switches to the grid. Since manufacturer's specs allow cycling between 100% and 10%, I have a lot of margin here. BTW: Technically, it would be better to cycle these between 40% SoC and 90% SoC daily, while allowing a full charge (100%SoC) only once a week, to let BMS reset amphours counter and balance the cells. But as far as I know, no inverter on the market has ability to set such a complex rule.
  13. Are you sure that you are not confusing DoD with the SoC? 80%DoD means that there's roughly just 20% of energy left in the battery. Such a deep everyday cycling cannot be called "wasting of a potential" as consuming that last remaining 1.4kWh won't make any change but it will kill the batteries for sure. In the US3000 BMS the 9%SoC is hardcoded as a lower limit. Once you discharge US3000 to this limit it will auto-shutdown and log an error to its NVRAM.
  • Create New...