July 17, 20232 yr Trying to get coms working between the Axpert King (Kodak version) and a 3.6kwh Greenrich battery installed off-grid in a cabin. Have the right cable and the hexagon flashes suggesting coms is working. Watchpower app reflects the BMS data as read by the inverter if I set it to Pylon or Lithium B, but the issue is that if I set it to Pylontech, the charge voltage is preset (? in the firmware) to 57v. If I set it to User settings, the SoC calculation is way off and very confusing. We had an issue that when the battery is fully charged or close to fully charged after a few hours of sun, the inverter fans spin up and down every few seconds trying to charge then stopping, repeatedly, sometimes for a few hours. This also happens when the user settings have the bulk and float voltages at 57v or 57.4v which the installer was told were the right voltages for the battery. Later discussion with Elyhill who supply the battery suggest the bulk should be 56v and the float 55v. I finally had a chance to connect a serial cable and monitor with PBMS tools and could see that the stopping and starting when close to full charge were due to overvoltage protection kicking in from the battery BMS when the charge voltage was at 57v (pylontech setting) or higher (on the user setting). Using 56v and 55v as above and the spinning up and down stopped. So now having to chose between wildly inaccurate SoC (user settings) or voltage too high (Pylontech settings). Are the voltages supposed to be this high on the in-built programs, or is it something weird with our inverter? Is there a way to change the inbuilt voltage settings for one of the existing Lithium protocols to be lower, or another way to support SoC from the BMS coms while still being able to lower the voltages?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.