March 9, 20233 yr 8 hours ago, jgdt said: it successfully connects That is excellent news, so the adapter works finally! 9 hours ago, jgdt said: So this brings me back to my original question can the master battery talk CAN to inverter and RS485 to USB/PC at the same time? That's a very good question, I have not seen anyone with this working yet, I've not tried as my inverter doesn't support CAN and I only have 1 battery so DIP addressing wouldn't be an issue. I think you are correct that the software is seeing the slave as pack1 because DIP 1 is on. There are files on the seplos google drive for DIP settings for CAN and RS485 and comparing them it looks like DIP 5-8 on the master are used to set the CAN address (or number of batteries) and DIP1-4 are used to set up the RS485 addresses. The RS485 doc shows that with multiple batteries DIP1 needs to be set on the master and DIP2 on the slave which is why it is seeing your slave as the master in the software because it has DIP1 on from the CAN setting and it can't see your master because it has no (or incorrect) DIP setting for RS485 because DIP1-4 are all down. I assume that it sees DIP1 as master then it looks for the next address for the slave which should be DIP2 up. So after scratching my head for a while I think the best would be to try the following DIP settings to satisfy the CAN addressing requirement and also the RS485 addressing requirements to get them to work at the same time: Master: DIP1 on (set as master for RS485) and DIP5 on (set as master of 2 batteries for CAN) Slave: DIP2 on (set as slave for RS485) [no need for CAN setting, it will speak RS485 to the master] 9 hours ago, Antonio de Sa said: Just be careful, from what is posted above you are overcharging your battery to the point that the BMS cut out all charging. This is something I noticed before on someone else's setup. It seems that with comms the BMS requests a charge voltage of +57V and the BMS is set to protect at 57.75V. I really don't know why it is set so high because I easily charge my battery at 56V. 9 hours ago, jgdt said: On my inverter (SunSynk) the max charge/discharge rates are set to lower than what the BMS advertises and when SOC hits 98% the BMS lowers the charge rate to 10A and the inverter does comply then it carries on slower charging until 100% at which point the BMS signals max charge rate as 0A. Yeah the bms controls the current request nicely, but unfortunately it requests a high voltage, so it's possible it might hit that just for a short time at the top of charge and also by then the amps will be low anyway, so maybe not much damage, but I don't like seeing a red error message. You can pull up the history which should give you some decent info to be able to see what was going on and what voltages were reached. 9 hours ago, jgdt said: Guess it will only be cleared after a while. It will clear after it reaches 53.5V again.
March 9, 20233 yr 9 hours ago, jgdt said: Hang on before you try what I've written above... I think it might be even simpler. Just click on Pack1 on the rhs to deselect it and it will probably display the info for Pack0.
March 10, 20233 yr 9 hours ago, jumper said: Master: DIP1 on (set as master for RS485) and DIP5 on (set as master of 2 batteries for CAN) Slave: DIP2 on (set as slave for RS485) [no need for CAN setting, it will speak RS485 to the master] I'll maybe try this over weekend, if I feel brave enough. Is this risky at all, especially if DIP1+DIP5 is an invalid combination on BMS? Has anyone caused themselves problems before based on odd dips? 9 hours ago, jumper said: It seems that with comms the BMS requests a charge voltage of +57V and the BMS is set to protect at 57.75V. I really don't know why it is set so high because I easily charge my battery at 56V. Mmmh, looking at the LiBMS page on inverter and the "V-Charge-BMS" parameter on my graphs, it seems that BMS always request a charge voltage of 57.8V. Not sure why and where it gets this from. Guess I need to load the parameters of Pack1 from Battery Monitor, as it should be coming from the BMS, right? On inverter the battery type is set to Lithium and then the voltage related settings don't apply, but even if it did I don't see a 57.8V on inverter's battery setup. 9 hours ago, jumper said: Just click on Pack1 on the rhs to deselect it and it will probably display the info for Pack0. Did not work in my case, unfortunately. Edited March 10, 20233 yr by jgdt
March 10, 20233 yr 3 minutes ago, jgdt said: I'll maybe try this over weekend, if I feel brave enough. Is this risky at all, especially if DIP1+DIP5 is an invalid combination on BMS? Has anyone caused themselves problems before based on odd dips? You shouldn't physically break anything with invalid DIP settings, they are just there to set up the unique addresses on the network for communication. If the settings are invalid then the batteries might not see each other or conflict with each other, but you can just revert back without issues. First try what I wrote after that with deselecting Pack1 and see if that works without changing any DIPs.
March 10, 20233 yr 8 minutes ago, jumper said: First try what I wrote after that with deselecting Pack1 and see if that works without changing any DIPs. Thanks. This did not work in my case, unfortunately. Thanks for explaining the risk (or rather no risk) involved with changing the dips.
March 10, 20233 yr 9 minutes ago, jgdt said: Mmmh, looking at the LiBMS page on inverter and the "V-Charge-BMS" parameter on my graphs, it seems that BMS always request a charge voltage of 57.8V. Not sure why and where it gets this from. Guess I need to load the parameters of Pack1 from Battery Monitor, as it should be coming from the BMS, right? On inverter the battery type is set to Lithium and then the voltage related settings don't apply, but even if it did I don't see a 57.8V on inverter's battery setup. This is what concerns me with automatic battery comms, there are strange things going on. I have seen high voltage requests like this before (I think it was on a luxpower) and I have been waiting for voltronic to add shoto support so I could test it myself, but I'm still waiting. One would expect that the manufacturer would know best how to charge their batteries, but I don't like to see the battery shutting off charging with red errors, hitting overvoltage protection. 16 minutes ago, jgdt said: as it should be coming from the BMS, right? Yeah the BMS will be telling it these settings, but I don't think I've seen any settings related to this in the BMS parameters, I'll have another look.
March 10, 20233 yr 55 minutes ago, jgdt said: This did not work in my case, unfortunately. Bummer, that would have been so easy =D I've had a look at the BMS settings and I can't see anything related to charge voltages, amps or settings for the inverter, but I think I know what might be going on... I don't think it's the BMS telling the inverter what to do, I think the inverter requests certain parameters from the BMS for charging and I think it is querying the wrong parameter. The only parameter close to 57.8V is parameter 14 "Total_voltage overvoltage protection" which is set to 57.75V. I think they are pulling this value and using it for the charge voltage instead of something like parameter 11 "Total pressure and high pressure recovery" which is set to 56V (charge voltage I use). If this is the case then I think it is Sunsynk that needs to update their firmware to query the correct parameter, not Shoto or Seplos. Edit: on second thought it might be the implementation of the pylontech protocol on the BMS that gives the incorrect value when given the command for the charge voltage... I don't know for sure. Edited March 10, 20233 yr by jumper
March 10, 20233 yr 4 minutes ago, jumper said: Bummer, that would have been so easy =D I've had a look at the BMS settings and I can't see anything related to charge voltages, amps or settings for the inverter, but I think I know what might be going on... I don't think it's the BMS telling the inverter what to do, I think the inverter requests certain parameters from the BMS for charging and I think it is querying the wrong parameter. The only parameter close to 57.8V is parameter 14 "Total_voltage overvoltage protection" which is set to 57.75V. I think they are pulling this value and using it for the charge voltage instead of something like parameter 11 "Total pressure and high pressure recovery" which is set to 56V (charge voltage I use). If this is the case then I think it is Sunsynk that needs to update their firmware to query the correct parameter, not Shoto or Seplos. @jumper I don't know if you agree with me, but I would recommend @jgdt to disconnect the coms and run it on inverter voltage settings until this issue is resolved, if he keeps charging the battery to that level he will most definitely sooner or later have bigger problems.
March 10, 20233 yr Ah man this sounds scary. Its gonna take a while if I indeed need to get SunSynk to do a firmware change. I doubt that this is fixed in their latest firmware. I'm running the 2nd latest one. And then if they change something what else are they gonna break? According to the inverter graphs the battery voltages reaches this 57.8V when it reaches 99% SOC just before it clicks over to 100%. I guess technically its 57.75 but gets rounded to 57.8V See screenshot the battery voltages peaks at 99% SOC, at which point I guess the BMS cutout kicks in. When I approach SunSynk should I ask them to make a change in line with the battery spec's charge voltage which is 54.0-56.4? So probably more like 56.4V.
March 10, 20233 yr 10 minutes ago, jgdt said: Ah man this sounds scary. Its gonna take a while if I indeed need to get SunSynk to do a firmware change. I doubt that this is fixed in their latest firmware. I'm running the 2nd latest one. And then if they change something what else are they gonna break? According to the inverter graphs the battery voltages reaches this 57.8V when it reaches 99% SOC just before it clicks over to 100%. I guess technically its 57.75 but gets rounded to 57.8V See screenshot the battery voltages peaks at 99% SOC, at which point I guess the BMS cutout kicks in. When I approach SunSynk should I ask them to make a change in line with the battery spec's charge voltage which is 54.0-56.4? So probably more like 56.4V. @jgdt Until such time if I was you, I would run the system without coms, I don't know the Sunsynk inverter, but I'm pretty sure that you should be able to run it on battery type Lithium and be able set the charge and float voltages. if that is possible set to charge at 56.4 and float at 54. At the present settings you are shortening the life span of your batteries.
March 10, 20233 yr 14 minutes ago, Antonio de Sa said: if that is possible set to charge at 56.4 and float at 54 This is what the battery settings look like on inverter (on the app the voltage settings are not shown at all). There's three voltage settings: Float, Absorption, Equalization. I can set float to 54.0, but what does the other two voltage settings mean and what should they be set to to get a effective charge rate of 56.4V? Whether they will take affect is another question. Ofcourse the charge voltage indicated on inverter's LiBMS page is probably still gonna show 57.8V. Hopefully the inverter uses the manually set 56.4V and not the errournous 57.8V from BMS.
March 10, 20233 yr 19 minutes ago, jgdt said: This is what the battery settings look like on inverter (on the app the voltage settings are not shown at all). There's three voltage settings: Float, Absorption, Equalization. I can set float to 54.0, but what does the other two voltage settings mean and what should they be set to to get a effective charge rate of 56.4V? Whether they will take affect is another question. Ofcourse the charge voltage indicated on inverter's LiBMS page is probably still gonna show 57.8V. Hopefully the inverter uses the manually set 56.4V and not the errournous 57.8V from BMS. @jgdt Sorry I'm not familiar with SunSynk inverters, Maybe contact them and ask what you must do to run your system without battery BMS coms, until such time they fix that bug. I personally run my system without BMS coms, I like to control my battery using voltage settings, that way I know that I'm looking after my battery to the best of the OEM recommendations.
March 10, 20233 yr FIY, I've opened this on the sunsynk forum so long (but its known that the tech support themselves don't comment too often there) : https://www.sunsynk.org/forum/techical-support/inverter-battery-charge-voltage-too-high To @jumper and @Antonio de Sa : a very big thank you for all your support and help here, appreciated it!
March 10, 20233 yr I know this thread is drifting off topic, which was just about the cable and establishing comms, sorry. But, I've proved @jumpertheory on where my inverter is getting the high charge voltage from. I've dropped the overvoltage value in the BMS using Battery Monitor to 56.9V and the inverter followed this and is now showing 56.9V as the charge voltage on the LiBMS page. I'll see tomorrow what happens at charging end, but most hopefully it will charge with 56.9V, then cutout at 56.9V and still throw the error. If this is the case I'll drop it further down to 56.4V to stay in check with the battery's spec. Then my batteries will charge at a more reasonable voltage of 56.4V, but it will still throw errors at the end, but then at least we can ignore the error a bit. For further reference : https://www.sunsynk.org/forum/techical-support/inverter-battery-charge-voltage-too-high/dl-977cc6ff-2a89-4c5e-9c62-2ed7f4314e37?postId=640b073f6122ae00126b84a6 PS: I had to change the setting on both batteries before the inverter followed it. To get a hold of master battery I pulled the CAN cable and flipped the DIP switch from 5 to off. Battery Monitor then picked up this battery (but of course then it couldn't get hold of slave battery, but I updated the value there first). Afterwards I restored the dip switch and the CAN cable and all was okay again (at least seems that way). Edited March 10, 20233 yr by jgdt Added PS on how I got a hold of master battery to change setting
March 10, 20233 yr Adding to previous comment, if this "work-around" does not pan out or causes other issues then I'll have to follow @Antonio de Sa advice of falling back to voltage based settings and not rely Inverter/BMS interaction. At least until SunSynk has somehow resolved this.
March 10, 20233 yr 25 minutes ago, jgdt said: Adding to previous comment, if this "work-around" does not pan out or causes other issues then I'll have to follow @Antonio de Sa advice of falling back to voltage based settings and not rely Inverter/BMS interaction. At least until SunSynk has somehow resolved this. @jgdt I just wonder. How many similar systems are out there that the owners are not monitoring things like you do, slowly killing they batteries?
March 11, 20233 yr On 2023/03/10 at 3:17 PM, jgdt said: I've dropped the overvoltage value in the BMS using Battery Monitor to 56.9V and the inverter followed this and is now showing 56.9V as the charge voltage on the LiBMS page. Thanks for testing that, it's very helpful to know. So either sunsynk is calling the wrong variable or the bms is sending the wrong variable value when being asked for the charge voltage or maybe seplos is ok with those short spikes in voltage although they are not necessary to fully charge to 100% SOC. On 2023/03/10 at 9:15 AM, Antonio de Sa said: @jumper I don't know if you agree with me, but I would recommend @jgdt to disconnect the coms and run it on inverter voltage settings until this issue is resolved, if he keeps charging the battery to that level he will most definitely sooner or later have bigger problems. Generally I would say yes, but the sunsynk runs so much off SOC he will lose a lot of that functionality. There is another "Charging overvoltage protection" which is set to 63V, so either it is set that high because it never gets hit due to the total overvoltage protection being triggered first or shoto reckons their batteries can handle 57.8V. On 2023/03/10 at 4:23 PM, Antonio de Sa said: @jgdt I just wonder. How many similar systems are out there that the owners are not monitoring things like you do, slowly killing they batteries? I suspect all systems running CAN comms are doing this as I've seen it on another inverter setup. @jgdtI would suggest also contacting the supplier of the battery to see if they will tell you officially that it's ok to be charging to the overvoltage protection. I will bet they are completely unaware of the situation.
March 12, 20233 yr Please note that the "overcharging" sub thread herein has been continued under : Thanks again for all the help in getting comms going between BMS and PC
March 13, 20233 yr Followup question relating to Battery Monitor software. Sometimes at the end of charge the cells start flashing different shades of orange and beige almost (see screenshot). What does this mean? This is typically after the monomer high voltage alarms has kicked in (after V3.5V). Is this perhaps an indication of cell balancing/equalization kicking in? What's the trigger points on Shoto/SeplosBMS for balancing to kick in?
March 14, 20233 yr 15 hours ago, jgdt said: Followup question relating to Battery Monitor software. Sometimes at the end of charge the cells start flashing different shades of orange and beige almost (see screenshot). What does this mean? This is typically after the monomer high voltage alarms has kicked in (after V3.5V). Is this perhaps an indication of cell balancing/equalization kicking in? What's the trigger points on Shoto/SeplosBMS for balancing to kick in? Yeah, that is cell balancing and it only triggers if the cell is over 3.5V (param 8 ) and there is a difference of 50mV (param 62) between the highest and lowest cell and will stop when the difference reaches 30mV (param 63) or 100% SOC is reached. Edited March 14, 20233 yr by jumper
March 14, 20233 yr Would have been nice if Battery Monitor had graphs built in. But, at least one can save the 'Real-time' readings to a CSV/Excel file, when clicking the 'Real time' toggle on toolbar (saved to folder \RealTimeRecord). Has anybody pulled in these files successfully in some kind of graphing library? I tried a few online ones, but they are lacking functionality. Currently setting up a local Grafana stack with CSV plugin, but haven't had success yet.
June 12, 20233 yr Hello, Can someone please tell me where I can download PBMODBUS tools? I am unable to get PBMS Tools to work with my AM-5 battery. Thanks.
June 13, 20233 yr Does anyone on here have a Shoto SDC10-Box5 connected to PC via Seplos Battery management software? I am looking for the parameter file for those batteries
June 16, 20232 yr On 2022/12/17 at 8:33 PM, jumper said: I'm just going to put some screenshots of all the default BMS settings here for reference and for anyone interested who doesn't have comms set up... THANK you for this, been looking everywhere
August 9, 20232 yr On 2023/01/12 at 5:04 PM, geert said: hello guys, Someone know the administrator password for PMODBUSTOOS (I guess it is the same as for the PBMSTOOLS) ? This Pmodbustoos is the only software that works, I cannot make the Pbmstools to work, it times out on the "serial port" - same cable, same com-port I use the USB to RS485 adapter. Can you help me share the software PmodbusToos Mail: [email protected]
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.