JK-inverter-BMS issues that have been discussed on the channel in the past: 1. "SOC 100% reset" - it resets when the highest cell reaches a specified voltage - not very good. One idea was to reset when Absorption ends. Another idea was to add a Tail Current setting like the Victron SmartShunt. Another idea was to reset when ALL cells are above a specified voltage (not just the highest). 2. Can you set the Float timer to a very long duration (7 days, 168 hours)? Keep the cells below 100% for a week and then give them an Absorption to balance and reset the SOC to 100%.
I think your "SOC 100% reset" idea would make a very minor effect on the accuracy of SOC calculation in case of a well-balanced battery pack. But it would lead to losing a lot of opportunities to reset the SOC when the pack reaches (almost) full charge for just a short period of time. Which eventually would lead to a less accurate SOC.
@@istvantiricz296 "(almost) full charge for just a short period of time" ... that means it's not fully charged. Therefore SOC should not reset to 100%.
@@danielardelian2 Totally agree, the 100% SOC should be sent only at the end of the charging phase (logic to be determined). This is what I do with my YamBMS application, the soc remains at max 98% until the charging phase is finished, then the 100% soc can be sent.
@@OffGridGarageAustralia Nice. They should include these profiles with the app so that it would be simple even for newbies to select Andy's LFP defaults. :)
@@OffGridGarageAustralia pin 1 is B pin 2 is A for RS 485. But it does not communicate. Can you please upload a video to show how we can establish communication between solax and jk inverter bms.
You and a couple other battery, solar, BMS Ytubers are.... and have been at the forefront for bringing the quality of these products UP to an amazing level so that everyone in the world can benefit from you're work. Industry changing really... Something to be proud of for sure! Thank you for all you do Andy. (Almost up to 100k!) and for good reason... 🤘
Thank you, Andy, For all your work and the brilliant videos. It makes it so much easier for all of us to choose the right products. Just received 2x EEL battery vertical housing (with JK-PB2A16S20P), 2x “Peter Board” + 32 Gobel Power MB31's and lot's of Victron equipment. All based on the info from your videos. Thank you so much!!
Great work Andy getting JK to engage with you again. A feature I'd like to see is the ability to save configurations to an external file, and then upload configurations from an external file. So that you can have your config backed up, as well as making setting up multiple batteries much faster in the configure one, then apply to all others approach. Take care D
We need open source code for this BMS. Im glad JK finally decided to reply to you. Although I've had multiple distributors of the bms contact them and the distributors have not gotten any responses. Makes me very hesitant to use their bms in all my installs.
There is still a very extensive list of Fixes needed - many posted into this thread without any acknowledgement. SOC is still also completely botched. The "only" person they talked to is Andy for Appeasemernt & Pacification purposes (to save face) which is exactly what this Vid is.
I have a huge amount of respect for Andy and his efforts. But like you said. It's probably not going to get JK to actually change their poor behavior. When it comes to customer support.
Correct. It won't change their overall approach towards their customers nor will they fix all the problems this BMS still has. I think JK is still the best shot we have at the moment. If anyone has a path forward or knows any alternatives to the JK BMS, I'm all for it.
@OffGridGarageAustralia I think we all got too excited when jk first released this bms. And seemed to be working with the community. But in reality. I don't know of any main BMS manufacturers that are any better. In that regards. I'm waiting patiently to see if they fix the 100% soc. As that is a make it or break it issue for me.
Thank you very much for the firmware Andy. Just to let you know that we can still reach DIY Eve batteries with JK with 15KW under 1650 Euros in Europe.
Andy, There are 2 major issues which need fixing. 1. Cell voltage jumping issue. Where cell voltage is erratic when used with inverter. 2. Soc 100% issue. This setting is ruined in inverter Bms. It used to work well in older black model. Soc has become very inaccurate now. I have emailed you with videos & proofs. Pls check. Also JK does not reply to me, which is concerning.
100% soc charging cut out is a big issue for the AIO inverters. Intrested to see how this is addressed in the next video. Also, i would really like to see. The heater control logic with its own set points. Right now, it will turn on at charge UTP and of at charge UTPR. Which results in a constant cycling. Between charging and heating.
BMS does not register Amperage in/out above 0.3A and often times not until 0.5A This obviously causes serious SOC drift which is made worse with multiple packs on a bank. Within 24 hrs there can be as much as 20% drift between identical packs with identical BMS'.
You cant imagine how happy I am Andy! 3x JK bms + 3x Luyuan diy Box + 3 sets of MB31 on the way!! :D Feels like Christmas already in hot summer Netherlands! jahwohl! 15.30 is available for some days already from the jk site ;)
RCV Time Bug in V15.30 Hi Andy, thank you for your great support and the results you can achieve with JK. I have found a major bug in the current firmware version. The BMS no longer applies the RCV time parameter. After the RCV time has expired, the BMS does not switch to the RFV cell voltage. Accordingly, the charging voltage (CVL) in the GX device remains set to 55.2 V throughout the day (RCVx16). This means that my 2 batteries are charged at 55.2 V for approx. 7 hours a day. Andi, you may not have enough amps outside to be able to check this. Can someone from the community check in the VRM portal whether my observation can be confirmed?
Hello, I can confirm that. There are still enough amps out there in Germany.😎 After the update to V15.30 everything is going well so far. But now I have the same problem that the float mode no longer works.
Andy to be fair JK is only talking to you and not their customers. This is causing community concern in the forums because they aren't communicating to anyone else. Did they shed any light on their behavior? It's really causing people to second guess further purchases.
Well done, great result. As a recent convert to JK I do have one observation that it would be nice to address: Most programable BMS have a pack over voltage disconnect as well as a cell over voltage disconnect the JK doesn't seem to have this and everything is done on a cell voltage basis. As I often use the frankenstein approach due to my source of cells this can be a problem. I would normally have a pack charge disconnect of 3.5vpc (56v) and a cell over voltage disconnect of 3.65vpc this gives best balancing performance as it enables the pack to continue charging while the high cell(s) is / are being brought down. If the cell over voltage is set to 3.5v this causes a pack charge disconnect while the other cells may be in a relatively low state of charge and the balancing at this level doesn't last long before the 3.5v cell is down with the others however it is still well out of balance with the result that it never really comes back into balance. This is the situation with the JK BMS and i have to set the cell disconnect voltage a lot higher than 3.5v to get good balancing yet, when balanced, I want to keep it at a pack disconnect of 56v which means I have to constantly change the settings. As this is for propulsion packs on boats they can spend some time at a full level and i prefer this to be 56v rather than around 58v. So, in summary, I think it would be good to have a pack disconnect independent of cell over voltage disconnect. This would then also make it suitable for use in hybrid systems which have an increasing following for those retrofitting lfp to boats with lead acid charging equipment and where the balancing effort is important due to the limited time in normal use that it is available for.
BMS cannot disable T3 & T4 if BMS is used in 8S Config and generates a persistent ERROR if the sensors are not present. (could be auto-config based on # of cells or with a switch.)
Fantastic Andy and community!! This is giving me the incentive to keep buying. Love the part where the battery ID is shown when using multiples. Awesome Andy all 👍
I have the JK Inverter BMS installed, it gives a temperature reading for the MOS but it gives "NA" as the temperature for Battery T1 T2 T3 and T4 . I have tried disabling and re-enabling the temperature sensor via the bluetooth app.
One issue for me with the Jk inverter BMS and Luxpower inverter, is the fact that once the BMS reports 100% it sends a flag to stop charging. This is with 15.27 and latest updates on the 6000xp.
@@Stefanfj The battery may display 100% but not have completed the charging phase (wrong soc). Some inverters stop charging when the battery reaches 100%. I corrected this problem in my YamBMS application, during the charging phase the soc peaks at 98% maximum. As soon as the battery is fully charged the soc 100% can be sent. So I perform a slight manipulation at the end of charging.
@@OpenSolarEnergy if the BMS sends the 100% SoC, but isn't finished charging, that's incorrect BMS behaviour. If an inverter continues to increase the voltage after getting 100% SoC from the BMS, that's incorrect inverter behaviour - it should not attempt to overcharge a lithium battery.
@@Stefanfj Yes I totally agree with you, this is bad behavior of the BMS, it should send the SOC 100% only at the end of the charging phase (logic to be determined) before switching to Float.
I spent the entire afternoon today working on the update to 15.30. I just couldn't get it done. The upload bar kept staying at 0, and nothing else happened. After a few hours, I discovered that the problem was that I had the firmware in my GDrive folder. Once I placed it in a local folder, it worked immediately.
I really appreciate your efforts to help JK creating a good firmware for all of us. But in my oppinion double power button press should be bluetooth pairig. I want to be able to use bluetooth any time. But the BMS is still vulnerable when bluetooth is on.
I am pleased that JK is talking to Andy again. I wrote to many people and in particular Gobel Power and YIXIANG. The guys a YIXIANG were very helpful and did try to find out why JK had gone to ground. I am not sure if it was my efforts and the efforts of YIXIANG that encouraged them to take up communications with Andy again, but I am very pleased that they have done that, as are many others. It does look like they are still not dealing with the community as they are still not responding to my emails. One can only hope that this might change.
Thanks for your work with JK! I'm going to test the BMS with SMA (Sunny Island 6.0H-13). According to their marketing material it should work, but we'll see.
This is fantastic news, its great that JK are now working with you again, hopefully you can get all the issues ironed out. Any chance you can get the battery box manufactures to fit Class T fuses? By the way, you now have over 94,100 subscribers, and over 15.6 million views.
Thank you for your feedback. I don't think call T will come as standard in these boxes. I quite like the breakers Gobel and Jaki are using. They can both cope with a very high current.
ja! ja! ja! ja! sag niemals neeeeeey! Weihnachten und Ostern können also doch auf einen Tag fallen! 🎉🎉🎉 Thank you for your effort, and Thank you JK for listening to us!
Hello Andy can you make a part 3 again of all the parameter settings and all functions of jk bms, a lot has change in the updates, just hoping you could do it again. Thanks!
I was going to send you a message shortly. This success was due to your contribution as well. I've forwarded the document you sent me a while back to the right channels. So, thank you very much for your help and assistance as well. We will soon have an import/export function for the settings. That will make our life a lot easier.
Question, have you managed to get cheap shipping from Gobel power? Batterys x16 280 ah batterys $1400 aud, shipping to New zealand $3200 !! Seriously $4600 total
Thanks for your support! 🙏 Put everything in your shopping cart and get in contact with Gobelpower to negotiate shipping. If it is still too high, let them know and buy elsewhere. We have a few options now...
Superb work Andy! Loving it.❤ One thing i would love and is not yet fixed is the BMS consumption showing in the VRM which is missing data atm. Are you still working with JK on a version 15.31 where this issue and maybe more will be fixed? Im expecting an EEL standing JK case any day now. So these improvements are right on time for me!🎉🎉🎉
@@SayWhaaaaaaaaaaaaaaaaaaaaaaat if a single cell hits RCV the BMS sends 100% signal to inverter. Basically your battery pack as a whole is never fully charged. There are also major SOC% drift issues.
@@OffGridGarageAustralia JK should send the SOC 100% only at the end of the charge phase (logic to be determined) before switching to Float, but, in the case of an unbalanced battery it should also introduce protections to prevent max_cell_v from hitting OVP... and all this should be easily and clearly configurable... This is still a lot of things to develop for JK, maybe too many things... This is what we have done in the YamBMS application.
It's about time JK realised the resource they have with you doing real world R&D testing for them. Pity more companies don't recognise the community they sell into and the experience that exists.
I bought 200A-2A version months ago, but waiting on Gobel cells (landed now) after wrong first shipment.(Redirected after wrong terminals detected). I'll buy 2 more JK now things are back on track. Thanks JK.
SOC 100% will report that Pack is FULL when only 1 cells reached set Trigger Point, For many devices like Voltronic, Victron etc, that terminate charging which is NOT Correct and other packs in Bank will also stop charging as a result. This ends Absorb/Bulk, and Float thereby effectively terminating Balancing & Levelling of cells & packs. THE FIX should be to set 100% SOC Value and trigger FLOAT once reached. Other options are possible. Another SOC 100% Error. Often the BMS will report 100% SOC even when NO CELL has reached the 100% SOC voltage as set ! This is likely a result of Bad coulomb counting and poor math within the firmware.
I thought Victron was not affected by this "100% charging-terminate" and would continue charging anyway? Are you sure that this is also the case with Victron?
It's great to see this happening... Now they need to create a way to change lost passwords... Maybe they give the backdoor then have you load an update to eliminate that backdoor while instituting a way to go to their site and change it after that.
@OffGridGarageAustralia Thanks for your work Andy. Tested the 15.30 on a parallel pack setup. New features showing up in venus os. Still what i have now experienced is that the float mode does not work anymore. Its staying on high voltage forever. Am I the only one?
Question: Has it been suggested to have the ability to export to file setings of the Master battery?, then import the saved setting into battery-2, battery-2, ect
Did they also fix the heater function? In the non inverter sytle the heater doesnt turn on until it hits the low temp disconnect. Need it to turn on sooner so it doesnt disconnect.
I found a serious bug in firmware versions V15.30 (and V15.32), which concerns parallel use. The point is that the slave battery constantly falls off the inverter and at these moments the inverter changes its key parameters of limiting the charge and discharge current, the charge percentage etc. - all this is set as if we have only one battery. This does not last long, about 10 seconds, but it affects the logic of the inverter. It is as if we are constantly pulling out the cable connecting two batteries via RS485 for 10 seconds. My inverter is DEYE, but I think this is not so important. Now I have solved the problem by returning to V15.27. It is a pity that I cannot attach screenshots and photos here. I think this is related to the fix in V15.30 "Adjust the alarm mechanism in parallel mode" that you talked about earlier in another video. One thing was fixed - another was broken ((.
hi Andy From the start of the firmware 15.30 I have constantly I have excess voltage alarm and Overload L1 at least 6 times a day !!!!!! Thank you for any effort since the beginning to remind you of the V14.01 nothing to work !!!!!
@Andy. Got a V15 BMS and updated to this 15.30 sotware, from your off grid garage site. Thanks. So have communication to PC, OK. Using the blue RS485 to USB adapter. I noticed you connected to CAN on the Cerbo. Did you try connecting it to Raspberry Pi by RS485 or CAN? I have 2 problems with it. Can't get it to connect by RS485 to Raspberry Pi. (maybe need to buy a CAN Hat, if that would work?). - as that would help to diagnose what is going on with the other issue: Using the Dry 1 Trigger as battery cell under voltage, setting number 5. Trigger value 3100, Release value 3120. To turn off inverter running AirCon at night. SNADI via a timer relay to give a 4 second pulse to stop the inverter. First time, last night, it turned off about 1am, and again while i was checking it, after restarting inverter, because all cells were 3.2x. Later it turned off again. Early in the morning all cells still 3.2x so restarted the inverter again. Have had 1 cell being lower, (but not recently, after increasing float voltage to 3.325). 24v system, now at 8:30am getting 15A in, pack voltage 26.73. 72% - but SOC is approximate, as only on 2 days, and 0 cycles. Can you please try communication with raspberry Pi? I might try the Dry 2 trigger! Thanks again
@Andy. Would be great if you can test the CAN on your Raspberry Pi Hat. If it works, i will buy a Hat. I think you said JK was still working on the RS485 for Victron. ps, i changed the Dry Trigger 1 value to 3000, Release 3050, and it seems better. It did cut out my inverter again 2nd night on 3100 when cells were all 3.2x. Not sure yet what min cell voltage it actually works on.
How about the last bullet point in the release notes? Where you able to test this too already? "7.Added the ability to count discharge energy and charge energy." Maybe it makes the graphs and data in the VRM portal a bit closer to reality 😅 as it is currently not even close (have not updated to .30 yet and using the system parallel to grid, only ACin connected yet)
HI Thanks again Andy, I just want to know if anyone else is having issues with the 15.3 firmware and a HWV14.2 in the network. I have 2 x HW15 with firm 15.3, working as expected, but the V14 hardware with firm 14.20 is dropping on and off the RS485 network consistently about every 10 seconds. It was fine prior to the HW 15 firmware upgrade.
Hi Andy. Great news, thanks. Unfortunately they did not solve the 2nd relay issue which I had asked them to solve. In my hardware version V15A the 2nd relay does not work. Never, not on any of the settings. Relay #1 works fine as it should. This is on all my 8 bmsses. Maybe if you were to ask them to include this fix in the next version, that would be great. I also tested V15.30, and it has not been solved. If I load V14.20 (!) on my bms with hardware version V15A, then the relay #2 works (!), but relay #1 doesn't work anymore. Anyway, the hardware of the relays seem to be fine, only the firmware isn't. Did you actually test the 2nd relay function ?? Keep up the good work, and thanks again, Mario from Netherlands
@@OffGridGarageAustralia hi Andy, thanks for your reply. Indeed, none of my 2nd relays are working. Regardless how I configure them. I tested with the system failure function, and with the overtemperature function. None work. For relay #1 everything works. The guy from JK in the support mentioned something as that early bmsses have slightly different hardware, so it would require dedicated firmware. But already for weeks now, they don't answer me anymore. They must be tired of me adking about the status every now and then. Besides that, I also found a flaw in the hardware design around the relays; sometimes also the relay #1 doesn't switch. It is due to a poor hardware design. The relays are 12V types, but they are activated only by a poor 8.7V and as the relay datasheet it requires minimum 9V to switch. So this leads to very weak switching of the relays. I have made a change in the hardware, by replacing 2 resistors that drive the opto couplers for the relays. I have also told this to JK, and probably they don't like me anymore. I made a video about it on my youtube channel @mariohoogenboom It is in dutch language, but you will get the hang of it if you are intested. It is called Zelfbouw thuisbatterij deel 5. Anyway, after the modification the relays switch very well at 10.5V, but relays #2 still do not switch at all. While if I load fw V14.20 it gets reversed; in that case relay#1 doesn't work anymore, and relay#2 works all of a sudden. But as my hardware is V15A, JK should be able to make a fw that will drive both relays properly. I just hope that they have the intention to solve this for these early V15A versions....
@@mariohoogenboom Hi mario, Can you also send this software to other members? I'm still working with the latest 15.17 and can't find the later versions.... Ps ik kom ook uit nederland😉 Thanks,
@@jeroenwiedijk2566 Hi Jeroen, JK has just informed me that this version is specific for my hardware. Appearently, I have an early V15 hardware version with a problem on the 2nd relay. JK also advises me to not update the fw in future, because this fix only exists in this fw version. Maybe you have also seen my latest video on my youtube channel that also shows a hardware flaw in the bms. Anyway, if you have the same problem, then this fw could help. If you would send your mail address to me, I will send you the fw.
I just received 2 Yixiang DIY Battery Boxes and am very happy that a lot of the issues are solved now. Thanks for all your work. Do you know when this release wil be official available? (I know that you have a link)
amazing work, Andy, thank you for pushing fixes any chance JK would consider best practices from UI of PACE BMS software (grouping of the parameters, using tale current in addition to absorption timer for SOC determination, etc.)?
They have the parameters in a certain order which they think makes sense from a customer perspective. Customers have to start with the highest value first (OVP) then work their way down until OVPR. Makes kind of sense but I also would like to have a different grouping. Let's see...
That's excellent news Andy. The Bluetooth fix is 👌 I'd also like to know if the fixes are working for SMA inverters.
4 หลายเดือนก่อน +2
Put the zero and one together to make a hillbilly nine.. Some of these added functions would be nice for the older non inverter BMS or an inverter BMS with more than 16 sense lines for oddballs like me with 17 cell batteries.. I enjoy every video even if they have nothing to do with my hardware, thanks..
Thank for your feedback. The older version (BD series) cannot be upgraded unfortunately. I think they are working on a 24s version of this BMS. I'll check it...
100% SOC is triggered when 1st cell reaches setpoint and cuts off Charging with connected Inverters (Make/Model experiencing this) SOC Drift Correction & resets must be addressed and lower resolution for Amperage in/out needs improvement to show at "least" 0.1 accuracy.
I think it's the biggest issue from all JK PB issues that like 95% inverters cuts off charging because of what you described and do not respecting requested absorption charge time and requested float charge time.
What news do you expect? I was in contact with the Seplos engineer a while back and we discussed some ideas to move forward. They wanted to discuss internally. I never heard back though, so obviously these new suggestions didn't go through the approval...
ANDY can you pls summarise a list of HW ver Nos to avoid. Ive lost track and over in diy solar power there have been some horrendous stories of bricking and countless hours of frustration, no response from JK etc when trying to perform FW updates.
Hi Andy, I've been following you for a long time. Congratulations! I have a piece of advice! I own both Seplos and JK as BMS and I think it would be useful to integrate the total voltages and consequently also the total alarms of the Seplos also in the JK! I hope you can talk to coach JK because that would be the top! I wish you a good day! See you soon! Sorry if the text is strange but I'm using the translator (I'm writing to you from Italy) and I also have a TH-cam channel. 😊
Hi Andy Congratulations for all you do I am a happy owner of BMS jk with firmware 15.17. Why when I update it the bluetooth no longer works? I have tried several times with both fw 15.30 and fw 15.32
Andy, tell JK to stop investing time on the pc app and rather focus on their mobile app. The only thing missing from mobile is firmware updates via bluetooth. This would give them more time to focus on the issues. Ps. Thanks for being the voice for the entire community 🎉
Hello Andy, thanks for the great work, The history calculation is correct in version 15.30! Since I installed the version, consumption has shot up by a factor of ten in the portal? Can someone recreate this? Or am I making a mistake?
Hi Andy, is it possible to implement the warning/protection/alarm notification also with the Solarman App? This app is used from Deye, Sofar and other big inverter manufacturers
You have to tell me if there is a message on the screen of your inverter if one battery goes OVP. Not sure how well such a message would forward to a third party app. I would expect, if the inverter shows a warning, that the Solarman app will display this as well.
Tak!
Thank you very much for your support 🙏
Vielen Dank für deine Arbeit!
Thank you very much!
JK-inverter-BMS issues that have been discussed on the channel in the past:
1. "SOC 100% reset" - it resets when the highest cell reaches a specified voltage - not very good.
One idea was to reset when Absorption ends.
Another idea was to add a Tail Current setting like the Victron SmartShunt.
Another idea was to reset when ALL cells are above a specified voltage (not just the highest).
2. Can you set the Float timer to a very long duration (7 days, 168 hours)?
Keep the cells below 100% for a week and then give them an Absorption to balance and reset the SOC to 100%.
I think your "SOC 100% reset" idea would make a very minor effect on the accuracy of SOC calculation in case of a well-balanced battery pack. But it would lead to losing a lot of opportunities to reset the SOC when the pack reaches (almost) full charge for just a short period of time. Which eventually would lead to a less accurate SOC.
@@istvantiricz296 "(almost) full charge for just a short period of time" ... that means it's not fully charged. Therefore SOC should not reset to 100%.
@@danielardelian2 Totally agree, the 100% SOC should be sent only at the end of the charging phase (logic to be determined). This is what I do with my YamBMS application, the soc remains at max 98% until the charging phase is finished, then the 100% soc can be sent.
I hate that. Why on earth would they do that?
Great work Andy! Please let JK put all your default settings under the lifepo4 button. Safe everybody a lot of time
Thank you. JK will have an import/export function soon, so it will be very easy to import "Andy's JK Default' 😉
@@OffGridGarageAustralia Nice! Andy's default, I like it!😎
@@OffGridGarageAustralia Nice. They should include these profiles with the app so that it would be simple even for newbies to select Andy's LFP defaults. :)
@@OffGridGarageAustraliamaybe they add Andy-button?
@@OffGridGarageAustralia pin 1 is B pin 2 is A for RS 485. But it does not communicate. Can you please upload a video to show how we can establish communication between solax and jk inverter bms.
You and a couple other battery, solar, BMS Ytubers are.... and have been at the forefront for bringing the quality of these products UP to an amazing level so that everyone in the world can benefit from you're work. Industry changing really...
Something to be proud of for sure!
Thank you for all you do Andy. (Almost up to 100k!) and for good reason... 🤘
JK got lucky to have FREE R&D team such like you.
This is and has been the normal for most of the electronics industry worldwide for many decades now.. Consumers are the mass beta testers..
I'm happy to do it if we all benefit from the outcome.
Thank you, Andy, For all your work and the brilliant videos. It makes it so much easier for all of us to choose the right products. Just received 2x EEL battery vertical housing (with JK-PB2A16S20P), 2x “Peter Board” + 32 Gobel Power MB31's and lot's of Victron equipment. All based on the info from your videos. Thank you so much!!
hi there, where did you buy the peter boards from? i cant seem to find them!
Well done Jikong, Andy, and mostly this community!!!
Thanks Andy, What a great result and you mentioned in the comments "JK will have an import/export function soon" It just keep getting better 👍
Great work Andy getting JK to engage with you again. A feature I'd like to see is the ability to save configurations to an external file, and then upload configurations from an external file. So that you can have your config backed up, as well as making setting up multiple batteries much faster in the configure one, then apply to all others approach. Take care D
It is already approved and the backups will implement it
DEYE/Sunsynk still uses a Force Request Charge to charge from GRID. Parameters are not settable on BMS. Protocol Implementation is incomplete.
And Victron also uses a can id for forced charging, I implemented it in YamBMS for Victron, PYLON and LuxPower.
15.30 has a RCV/RFV bug - RFV ist not set after timer expired in victron system. Batteries are kept at RCV-level only. :(
Danke!😅
Thank you very much, my friend! 🙏
Andy, you made my day! Danke daß Du so hartnäckig drangeblieben bist!🎉
Iss doch klar!
When will the SOC issue be addressed? Thank you in advance
Yea! SOC issue solving requires a lot HW modifications, I think.
I'll have this in my next video.
We need open source code for this BMS.
Im glad JK finally decided to reply to you. Although I've had multiple distributors of the bms contact them and the distributors have not gotten any responses.
Makes me very hesitant to use their bms in all my installs.
There is still a very extensive list of Fixes needed - many posted into this thread without any acknowledgement. SOC is still also completely botched.
The "only" person they talked to is Andy for Appeasemernt & Pacification purposes (to save face) which is exactly what this Vid is.
I have a huge amount of respect for Andy and his efforts. But like you said. It's probably not going to get JK to actually change their poor behavior. When it comes to customer support.
Correct. It won't change their overall approach towards their customers nor will they fix all the problems this BMS still has. I think JK is still the best shot we have at the moment.
If anyone has a path forward or knows any alternatives to the JK BMS, I'm all for it.
@OffGridGarageAustralia
I think we all got too excited when jk first released this bms.
And seemed to be working with the community.
But in reality. I don't know of any main BMS manufacturers that are any better. In that regards.
I'm waiting patiently to see if they fix the 100% soc.
As that is a make it or break it issue for me.
@@SunInLithium are suggesting that JK BMS is premium level?
Thank you very much for the firmware Andy. Just to let you know that we can still reach DIY Eve batteries with JK with 15KW under 1650 Euros in Europe.
15kWh for 1650€? Wow!
Could you share your experiences on which seller/platform might be the cheapest/best for Europe?
@@leumel900 ще дешевше, 1200 евро за 16кВт, купуй на НКОН як не резидент Европи, наприклад шо ти з України.
@@leumel900 i recently had a quote of 1750 euro for eve mb31 , jk bms, QSO battery box, wheels and the optional long thicker cables.
Takk!
Thank you for your support!
Andy,
There are 2 major issues which need fixing.
1. Cell voltage jumping issue. Where cell voltage is erratic when used with inverter.
2. Soc 100% issue. This setting is ruined in inverter Bms. It used to work well in older black model.
Soc has become very inaccurate now.
I have emailed you with videos & proofs. Pls check.
Also JK does not reply to me, which is concerning.
We group of 50 members facing the same issues please help us by reporting these issues to jk software team
100% soc charging cut out is a big issue for the AIO inverters.
Intrested to see how this is addressed in the next video.
Also, i would really like to see. The heater control logic with its own set points.
Right now, it will turn on at charge UTP and of at charge UTPR. Which results in a constant cycling. Between charging and heating.
Danke!
Danke Dir!
BMS does not register Amperage in/out above 0.3A and often times not until 0.5A This obviously causes serious SOC drift which is made worse with multiple packs on a bank. Within 24 hrs there can be as much as 20% drift between identical packs with identical BMS'.
Wonderful. I have 5 of the v14s and am awaiting the new firmware.
Yes, me too😄
You cant imagine how happy I am Andy! 3x JK bms + 3x Luyuan diy Box + 3 sets of MB31 on the way!! :D Feels like Christmas already in hot summer Netherlands! jahwohl! 15.30 is available for some days already from the jk site ;)
Hello landgenoot :)
@@firefly2472ook al!😂
Hier in Leeuwarden ook aan de klus met 16 MB31 cellen 😊
Groetjes uit Den Haag.. ook 16 celletjes en een Multiplus 5000
De grap is die 280 cellen passen exact in een Ikea kastje 😂
Hello from hoofddorp, 16 cells 280ah. Victron multiplus-ii 5000.😅
thanks Andy you are absolutely brilliant
Thanks for the update sir👍
But SoC issue is still present.. please help us with that also 🙏
Coming in the next video...
@@OffGridGarageAustralia thanks 👍
Fantastic work Andy!!, thanks also to JK for a listening ear and direct approach.
RCV Time Bug in V15.30
Hi Andy, thank you for your great support and the results you can achieve with JK.
I have found a major bug in the current firmware version.
The BMS no longer applies the RCV time parameter. After the RCV time has expired, the BMS does not switch to the RFV cell voltage. Accordingly, the charging voltage (CVL) in the GX device remains set to 55.2 V throughout the day (RCVx16). This means that my 2 batteries are charged at 55.2 V for approx. 7 hours a day. Andi, you may not have enough amps outside to be able to check this. Can someone from the community check in the VRM portal whether my observation can be confirmed?
I have experienced the same!
I created a small flow in Node Red to emulate the correct behavior as a workaround to set DVCC max volt
I have The same Bug :(
@OffGridGarageAustralia Hi Andy, the RCV time bug is confirmed. Can you please add this issue to your list of requirements for JK?
Hello,
I can confirm that. There are still enough amps out there in Germany.😎
After the update to V15.30 everything is going well so far.
But now I have the same problem that the float mode no longer works.
Great work andy! Nice to see JK is wanting to work with you again. Keep it up!
Andy to be fair JK is only talking to you and not their customers. This is causing community concern in the forums because they aren't communicating to anyone else. Did they shed any light on their behavior? It's really causing people to second guess further purchases.
Yes, I know, I flagged this with the management but haven't heard back how they want to address that.
@@OffGridGarageAustraliaThank you, we all appreciate the time you've spent on this.
@@OffGridGarageAustralia
Maybe that's also a good thing, if everyone is shouting you can't hear anything.....
If JK had a better documentation and download section (in English!) on their webside, it would solve 99% of all issues / questions the customers have.
Well done, great result. As a recent convert to JK I do have one observation that it would be nice to address: Most programable BMS have a pack over voltage disconnect as well as a cell over voltage disconnect the JK doesn't seem to have this and everything is done on a cell voltage basis. As I often use the frankenstein approach due to my source of cells this can be a problem. I would normally have a pack charge disconnect of 3.5vpc (56v) and a cell over voltage disconnect of 3.65vpc this gives best balancing performance as it enables the pack to continue charging while the high cell(s) is / are being brought down. If the cell over voltage is set to 3.5v this causes a pack charge disconnect while the other cells may be in a relatively low state of charge and the balancing at this level doesn't last long before the 3.5v cell is down with the others however it is still well out of balance with the result that it never really comes back into balance. This is the situation with the JK BMS and i have to set the cell disconnect voltage a lot higher than 3.5v to get good balancing yet, when balanced, I want to keep it at a pack disconnect of 56v which means I have to constantly change the settings. As this is for propulsion packs on boats they can spend some time at a full level and i prefer this to be 56v rather than around 58v. So, in summary, I think it would be good to have a pack disconnect independent of cell over voltage disconnect. This would then also make it suitable for use in hybrid systems which have an increasing following for those retrofitting lfp to boats with lead acid charging equipment and where the balancing effort is important due to the limited time in normal use that it is available for.
BMS cannot disable T3 & T4 if BMS is used in 8S Config and generates a persistent ERROR if the sensors are not present.
(could be auto-config based on # of cells or with a switch.)
Fantastic Andy and community!! This is giving me the incentive to keep buying. Love the part where the battery ID is shown when using multiples. Awesome Andy all 👍
Excellent, awaiting the V14.30 update patiently
I have the JK Inverter BMS installed, it gives a temperature reading for the MOS but it gives "NA" as the temperature for Battery T1 T2 T3 and T4 . I have tried disabling and re-enabling the temperature sensor via the bluetooth app.
One issue for me with the Jk inverter BMS and Luxpower inverter, is the fact that once the BMS reports 100% it sends a flag to stop charging. This is with 15.27 and latest updates on the 6000xp.
Isn't that exactly what should happen, though? if the battery is full then you shouldn't be charging anymore?
@@Stefanfj The battery may display 100% but not have completed the charging phase (wrong soc). Some inverters stop charging when the battery reaches 100%. I corrected this problem in my YamBMS application, during the charging phase the soc peaks at 98% maximum. As soon as the battery is fully charged the soc 100% can be sent. So I perform a slight manipulation at the end of charging.
@@OpenSolarEnergy if the BMS sends the 100% SoC, but isn't finished charging, that's incorrect BMS behaviour.
If an inverter continues to increase the voltage after getting 100% SoC from the BMS, that's incorrect inverter behaviour - it should not attempt to overcharge a lithium battery.
@@Stefanfj Yes I totally agree with you, this is bad behavior of the BMS, it should send the SOC 100% only at the end of the charging phase (logic to be determined) before switching to Float.
That's great! Keep moving forward. One issue at at time. Goed bezig man!
Perfekt vielen Dank für dein Einsatz
Bau mit JK „Das BMS“!!!
Thanks, Paul.
Heya, so nice you have a contact with JK again and so good to see JK inplomented all the idees from the form
yaaaaayyyyy! we really had an impact! thanks a lot Andy for the voice of the community!! 🎉🎉🎉😁😁
My pleasure!!
Thank you Andy for your work with JK
I spent the entire afternoon today working on the update to 15.30. I just couldn't get it done. The upload bar kept staying at 0, and nothing else happened. After a few hours, I discovered that the problem was that I had the firmware in my GDrive folder. Once I placed it in a local folder, it worked immediately.
I really appreciate your efforts to help JK creating a good firmware for all of us. But in my oppinion double power button press should be bluetooth pairig. I want to be able to use bluetooth any time. But the BMS is still vulnerable when bluetooth is on.
Pairing is automatically when connecting via Bluetooth. I understand what you mean though. Let me pitch that idea to them...
Thank you Andy. I ordered and waiting for the JK inverter bms 2A200A version.
I am pleased that JK is talking to Andy again.
I wrote to many people and in particular Gobel Power and YIXIANG.
The guys a YIXIANG were very helpful and did try to find out why JK had gone to ground.
I am not sure if it was my efforts and the efforts of YIXIANG that encouraged them to take up communications with Andy again, but I am very pleased that they have done that, as are many others.
It does look like they are still not dealing with the community as they are still not responding to my emails. One can only hope that this might change.
Thanks for your work with JK! I'm going to test the BMS with SMA (Sunny Island 6.0H-13). According to their marketing material it should work, but we'll see.
This is fantastic news, its great that JK are now working with you again, hopefully you can get all the issues ironed out. Any chance you can get the battery box manufactures to fit Class T fuses? By the way, you now have over 94,100 subscribers, and over 15.6 million views.
Thank you for your feedback. I don't think call T will come as standard in these boxes. I quite like the breakers Gobel and Jaki are using. They can both cope with a very high current.
The question is, can these brakes disrupt the current even if there is a huge spark? Class-T has sand inside which fills the gab between the contacts.
ja! ja! ja! ja! sag niemals neeeeeey! Weihnachten und Ostern können also doch auf einen Tag fallen! 🎉🎉🎉
Thank you for your effort, and Thank you JK for listening to us!
Thank you.
Hello Andy can you make a part 3 again of all the parameter settings and all functions of jk bms, a lot has change in the updates, just hoping you could do it again. Thanks!
Can they implement your prefered LFP settings as a default? That would be amazing ;)
Thanks for all the effort and improvements! So great!!!
I was going to send you a message shortly. This success was due to your contribution as well. I've forwarded the document you sent me a while back to the right channels.
So, thank you very much for your help and assistance as well.
We will soon have an import/export function for the settings. That will make our life a lot easier.
@@OffGridGarageAustralia Amazing! I'm just glad that you have to power to move them into the right direction ☺
Question, have you managed to get cheap shipping from Gobel power? Batterys x16 280 ah batterys $1400 aud, shipping to New zealand $3200 !! Seriously $4600 total
Thanks for your support! 🙏
Put everything in your shopping cart and get in contact with Gobelpower to negotiate shipping. If it is still too high, let them know and buy elsewhere. We have a few options now...
Superb work Andy! Loving it.❤
One thing i would love and is not yet fixed is the BMS consumption showing in the VRM which is missing data atm. Are you still working with JK on a version 15.31 where this issue and maybe more will be fixed?
Im expecting an EEL standing JK case any day now. So these improvements are right on time for me!🎉🎉🎉
Heard the 100% SOC issue is not addressed yet. Frustrating.
what is the issue if you can tell?
I'll address this in the next video.
@@SayWhaaaaaaaaaaaaaaaaaaaaaaat if a single cell hits RCV the BMS sends 100% signal to inverter. Basically your battery pack as a whole is never fully charged. There are also major SOC% drift issues.
@@OffGridGarageAustralia JK should send the SOC 100% only at the end of the charge phase (logic to be determined) before switching to Float, but, in the case of an unbalanced battery it should also introduce protections to prevent max_cell_v from hitting OVP... and all this should be easily and clearly configurable... This is still a lot of things to develop for JK, maybe too many things... This is what we have done in the YamBMS application.
@@OffGridGarageAustralia you did not address the known 100% SOC issue in your latest video. You only talked about drift.
94.1k moving forward good job. 😊
We are getting close!
Best wishes from Hamburg, Germany. Well done. Great job delivered with the community tackling the issues. 😂❤❤❤❤
It's about time JK realised the resource they have with you doing real world R&D testing for them. Pity more companies don't recognise the community they sell into and the experience that exists.
I bought 200A-2A version months ago, but waiting on Gobel cells (landed now) after wrong first shipment.(Redirected after wrong terminals detected). I'll buy 2 more JK now things are back on track. Thanks JK.
SOC 100% will report that Pack is FULL when only 1 cells reached set Trigger Point, For many devices like Voltronic, Victron etc, that terminate charging which is NOT Correct and other packs in Bank will also stop charging as a result. This ends Absorb/Bulk, and Float thereby effectively terminating Balancing & Levelling of cells & packs. THE FIX should be to set 100% SOC Value and trigger FLOAT once reached. Other options are possible.
Another SOC 100% Error. Often the BMS will report 100% SOC even when NO CELL has reached the 100% SOC voltage as set ! This is likely a result of Bad coulomb counting and poor math within the firmware.
I thought Victron was not affected by this "100% charging-terminate" and would continue charging anyway? Are you sure that this is also the case with Victron?
Andy, is it possible that JK ads the Cell Voltages from all Batteries in the Victron VRM Console like SerielBattery?
It's great to see this happening... Now they need to create a way to change lost passwords... Maybe they give the backdoor then have you load an update to eliminate that backdoor while instituting a way to go to their site and change it after that.
@OffGridGarageAustralia
Thanks for your work Andy.
Tested the 15.30 on a parallel pack setup. New features showing up in venus os. Still what i have now experienced is that the float mode does not work anymore. Its staying on high voltage forever. Am I the only one?
Great work. Just orderd a Jk bms , lets see if it matches my main requierement. Set and Forget
How to reset current and voltage calibration?
Hey JK, thanks for the great work with Andy. Not really his fault that he is German.
Hahaha, great!
Question: Has it been suggested to have the ability to export to file setings of the Master battery?, then import the saved setting into battery-2, battery-2, ect
JK told me to try version 15.30 on the 14v BMS. Have not had a chance yet but....
It will not work. V14 is different hardware and needs different firmware. They are working on it.
@@OffGridGarageAustralia Thank you. I asked her three times to make sure this was for V14. Three times she said yes. Thank you for the clarity.
Would be nice for this firmware to also be added to their 12 volt BMS units for which I have 4, eliminating the need for Peter boards...
Did they also fix the heater function? In the non inverter sytle the heater doesnt turn on until it hits the low temp disconnect. Need it to turn on sooner so it doesnt disconnect.
I found a serious bug in firmware versions V15.30 (and V15.32), which concerns parallel use. The point is that the slave battery constantly falls off the inverter and at these moments the inverter changes its key parameters of limiting the charge and discharge current, the charge percentage etc. - all this is set as if we have only one battery. This does not last long, about 10 seconds, but it affects the logic of the inverter. It is as if we are constantly pulling out the cable connecting two batteries via RS485 for 10 seconds. My inverter is DEYE, but I think this is not so important. Now I have solved the problem by returning to V15.27. It is a pity that I cannot attach screenshots and photos here.
I think this is related to the fix in V15.30 "Adjust the alarm mechanism in parallel mode" that you talked about earlier in another video. One thing was fixed - another was broken ((.
hi Andy From the start of the firmware 15.30 I have constantly I have excess voltage alarm and Overload L1 at least 6 times a day !!!!!! Thank you for any effort since the beginning to remind you of the V14.01 nothing to work !!!!!
@Andy. Got a V15 BMS and updated to this 15.30 sotware, from your off grid garage site. Thanks. So have communication to PC, OK. Using the blue RS485 to USB adapter. I noticed you connected to CAN on the Cerbo. Did you try connecting it to Raspberry Pi by RS485 or CAN? I have 2 problems with it. Can't get it to connect by RS485 to Raspberry Pi. (maybe need to buy a CAN Hat, if that would work?). - as that would help to diagnose what is going on with the other issue: Using the Dry 1 Trigger as battery cell under voltage, setting number 5. Trigger value 3100, Release value 3120. To turn off inverter running AirCon at night. SNADI via a timer relay to give a 4 second pulse to stop the inverter. First time, last night, it turned off about 1am, and again while i was checking it, after restarting inverter, because all cells were 3.2x. Later it turned off again. Early in the morning all cells still 3.2x so restarted the inverter again. Have had 1 cell being lower, (but not recently, after increasing float voltage to 3.325). 24v system, now at 8:30am getting 15A in, pack voltage 26.73. 72% - but SOC is approximate, as only on 2 days, and 0 cycles. Can you please try communication with raspberry Pi? I might try the Dry 2 trigger! Thanks again
what is setting Dry ARM intermittent? it is default OFF
Had a persistent Temp Sensor Abnormal warning, since connection, using just 8S balance wiring. Added the 2 other sets of wires, OK now.
@Andy. Would be great if you can test the CAN on your Raspberry Pi Hat. If it works, i will buy a Hat. I think you said JK was still working on the RS485 for Victron. ps, i changed the Dry Trigger 1 value to 3000, Release 3050, and it seems better. It did cut out my inverter again 2nd night on 3100 when cells were all 3.2x. Not sure yet what min cell voltage it actually works on.
How about the last bullet point in the release notes? Where you able to test this too already?
"7.Added the ability to count discharge energy and charge energy."
Maybe it makes the graphs and data in the VRM portal a bit closer to reality 😅 as it is currently not even close (have not updated to .30 yet and using the system parallel to grid, only ACin connected yet)
I will address the SOC problem in the next video.
@@OffGridGarageAustralia Thank you very much. Your time and efforts are really appreciated!!
PC-APP should also be able to run on Linux / Mac. LINUX more likely preferred
Thanks Andy you are the best clean energy engineer 🎉
HI Thanks again Andy, I just want to know if anyone else is having issues with the 15.3 firmware and a HWV14.2 in the network. I have 2 x HW15 with firm 15.3, working as expected, but the V14 hardware with firm 14.20 is dropping on and off the RS485 network consistently about every 10 seconds. It was fine prior to the HW 15 firmware upgrade.
@ Andy Float-Voltage Bug in FW15.30 ist auch im Pylon-Protokoll enthalten (also nicht nur Victron) :( Grüße aus Austria
Hi. What is about the feature of save/restore settings. Is there a plan this feature will include into the pc software or app?
It's in the make...
Excellent video, excellent results
Thank you very much!
Hi Andy. Great news, thanks. Unfortunately they did not solve the 2nd relay issue which I had asked them to solve. In my hardware version V15A the 2nd relay does not work. Never, not on any of the settings. Relay #1 works fine as it should.
This is on all my 8 bmsses.
Maybe if you were to ask them to include this fix in the next version, that would be great.
I also tested V15.30, and it has not been solved. If I load V14.20 (!) on my bms with hardware version V15A, then the relay #2 works (!), but relay #1 doesn't work anymore. Anyway, the hardware of the relays seem to be fine, only the firmware isn't.
Did you actually test the 2nd relay function ??
Keep up the good work, and thanks again,
Mario from Netherlands
Hi Mario, yes, I tested 3 of my V15 BMS and both relays are working.
Are yours not working at all, so regardless if OVP, OT or SOC used?
@@OffGridGarageAustralia hi Andy, thanks for your reply. Indeed, none of my 2nd relays are working. Regardless how I configure them. I tested with the system failure function, and with the overtemperature function. None work. For relay #1 everything works.
The guy from JK in the support mentioned something as that early bmsses have slightly different hardware, so it would require dedicated firmware. But already for weeks now, they don't answer me anymore. They must be tired of me adking about the status every now and then.
Besides that, I also found a flaw in the hardware design around the relays; sometimes also the relay #1 doesn't switch. It is due to a poor hardware design. The relays are 12V types, but they are activated only by a poor 8.7V and as the relay datasheet it requires minimum 9V to switch. So this leads to very weak switching of the relays. I have made a change in the hardware, by replacing 2 resistors that drive the opto couplers for the relays. I have also told this to JK, and probably they don't like me anymore.
I made a video about it on my youtube channel @mariohoogenboom
It is in dutch language, but you will get the hang of it if you are intested. It is called Zelfbouw thuisbatterij deel 5.
Anyway, after the modification the relays switch very well at 10.5V, but relays #2 still do not switch at all. While if I load fw V14.20 it gets reversed; in that case relay#1 doesn't work anymore, and relay#2 works all of a sudden.
But as my hardware is V15A, JK should be able to make a fw that will drive both relays properly. I just hope that they have the intention to solve this for these early V15A versions....
Hello Andy
Great news from my side for a change ! JK has sent me new FW V15.32 that solved the 2nd relay issue on my 8 bmsses. Problem solved !
@@mariohoogenboom
Hi mario,
Can you also send this software to other members?
I'm still working with the latest 15.17 and can't find the later versions....
Ps ik kom ook uit nederland😉
Thanks,
@@jeroenwiedijk2566 Hi Jeroen, JK has just informed me that this version is specific for my hardware. Appearently, I have an early V15 hardware version with a problem on the 2nd relay. JK also advises me to not update the fw in future, because this fix only exists in this fw version. Maybe you have also seen my latest video on my youtube channel that also shows a hardware flaw in the bms. Anyway, if you have the same problem, then this fw could help. If you would send your mail address to me, I will send you the fw.
I just received 2 Yixiang DIY Battery Boxes and am very happy that a lot of the issues are solved now. Thanks for all your work. Do you know when this release wil be official available? (I know that you have a link)
amazing work, Andy, thank you for pushing fixes
any chance JK would consider best practices from UI of PACE BMS software (grouping of the parameters, using tale current in addition to absorption timer for SOC determination, etc.)?
They have the parameters in a certain order which they think makes sense from a customer perspective. Customers have to start with the highest value first (OVP) then work their way down until OVPR. Makes kind of sense but I also would like to have a different grouping. Let's see...
Power button light should blink slowly when the bt is active.
Save or export on the table with the software engineers?
Yes, coming soon!
@@OffGridGarageAustralia Sweet!
That's excellent news Andy. The Bluetooth fix is 👌
I'd also like to know if the fixes are working for SMA inverters.
Put the zero and one together to make a hillbilly nine.. Some of these added functions would be nice for the older non inverter BMS or an inverter BMS with more than 16 sense lines for oddballs like me with 17 cell batteries.. I enjoy every video even if they have nothing to do with my hardware, thanks..
Thank for your feedback. The older version (BD series) cannot be upgraded unfortunately.
I think they are working on a 24s version of this BMS. I'll check it...
Well done Andy
Thank you JK!
100% SOC is triggered when 1st cell reaches setpoint and cuts off Charging with connected Inverters (Make/Model experiencing this)
SOC Drift Correction & resets must be addressed and lower resolution for Amperage in/out needs improvement to show at "least" 0.1 accuracy.
I think it's the biggest issue from all JK PB issues that like 95% inverters cuts off charging because of what you described and do not respecting requested absorption charge time and requested float charge time.
Hello Andy. Nice news, but what about news for the Seplos 3.0 BMS?
What news do you expect?
I was in contact with the Seplos engineer a while back and we discussed some ideas to move forward. They wanted to discuss internally. I never heard back though, so obviously these new suggestions didn't go through the approval...
Andy, how about an upgrade firmware from the app feature? That would be a really handy feature.
ANDY can you pls summarise a list of HW ver Nos to avoid. Ive lost track and over in diy solar power there have been some horrendous stories of bricking and countless hours of frustration, no response from JK etc when trying to perform FW updates.
Hi Andy, I've been following you for a long time. Congratulations! I have a piece of advice! I own both Seplos and JK as BMS and I think it would be useful to integrate the total voltages and consequently also the total alarms of the Seplos also in the JK!
I hope you can talk to coach JK because that would be the top! I wish you a good day! See you soon! Sorry if the text is strange but I'm using the translator (I'm writing to you from Italy) and I also have a TH-cam channel. 😊
Hi Andy Congratulations for all you do I am a happy owner of BMS jk with firmware 15.17. Why when I update it the bluetooth no longer works? I have tried several times with both fw 15.30 and fw 15.32
Awesome work
Andy, tell JK to stop investing time on the pc app and rather focus on their mobile app. The only thing missing from mobile is firmware updates via bluetooth. This would give them more time to focus on the issues.
Ps. Thanks for being the voice for the entire community 🎉
Hello Andy, thanks for the great work,
The history calculation is correct in version 15.30! Since I installed the version, consumption has shot up by a factor of ten in the portal? Can someone recreate this? Or am I making a mistake?
Hi Andy, is it possible to implement the warning/protection/alarm notification also with the Solarman App?
This app is used from Deye, Sofar and other big inverter manufacturers
You have to tell me if there is a message on the screen of your inverter if one battery goes OVP. Not sure how well such a message would forward to a third party app. I would expect, if the inverter shows a warning, that the Solarman app will display this as well.
Gobel also didn't honour your coupon code for me in the past. However cells arrived no problem and are great quality.
Moin Andi, löppt👍, good job JK.
Thank you.
is it possibile to enter the jkbms on android app without entering location?