As soon as I have it I'll open it up and compare with an older one.
Hankzor JK BMS with screen and power button
- Thread starter upnorthandpersonal
- Start date
As soon as I have it I'll open it up and compare with an older one.
They arrived today, I'll post some pictures this week and also open one up. LCD comes with the cable to connect to the BMS.
Steve_S
Offgrid Cabineer, N.E. Ontario, Canada
I was disappointed with my batch because I ordered mine just before they updated the design to enable the LCD Screen. Mine have the RS485 & CanBus ports and Bluetooth of course. Had I known to wait 2 weeks or so I would have.
hwse
Solar Enthusiast
- Joined
- Jan 2, 2021
- Messages
- 585
That is where I am now. I am building a 2PS4 and a 3P4S and have heard that they will have a 4S JK in a month or so.
Ok, update time. Finally had some time to have a look at the new BMS.
The new one on the right, old one on the left. They're both 100A versions to keep the comparison easier. The port to the right of the GPS/RS485 label is the display port. As Dave Jones would say: "Don't turn it on. Take it apart!"
New one on the right again. The original is hardware version 6.0, the new one 8.0. There have been a few changes, mostly on the other side of the board. The main change on this side of the board is the micro controller. The old version had an original STM32F103; probably due to shortages or because more resources were needed, it is replaced with a GD32F103. This is a pin compatible clone of the STM, it's used on some Bluepill boards and finds its way into many products these days since it's cheaper and actually available, unlike the STM. It also has more RAM/FLASH and can run at higher clock speeds. I'm actually surprised they didn't have the GD32 on there from the beginning. The MOSFETs are still the same: G042N10.
The GD32.
Other side of the board. More profound changes here. For one, the Bluetooth module was changed. Didn't look at the details, but they're both common modules. The chip at the bottom is a YD3082, which is an RS485 transceiver, which is what is driving the display. I'm not sure yet if this shares the same RS485 bus where one connects the RS485 dongle to. I'll find out later. There are also some added digital isolators that weren't there before (an 122U31) - probably to provide better isolation between the power and control side.
The YD3082 RS485 transceiver in the middle to the right.
This is the Display itself. It's very clear and bright, and the power button on the side works fine to turn the BMS on. I somehow wish it could be used to turn the BMS off again, but that's not a deal breaker. Ignore the 6.6V and state of charge, I just connected the BMS to two spare cells and a power supply.
I originally wanted to create a custom enclosure for it, but the handle bar mount can be removed easily, and it looks much better this way.
Of course, I also opened the display:
It's based around a Holtec HT1621 display driver on the right. This thing has a serial interface, and the other chip to the left is a hk32f030, another microcontroller that takes the incoming data and talks to the Holtec chip.
The LCD display itself.
I want to dig in deeper in some of the changes and other aspects of the BMS. For one, I really want to figure out how the power button is implemented, and if this is a software or hardware thing (or both). I don't know when I will have time for this though; now that I have one sitting on my desk I want to get back to the RS485 communication, finishing my Grafana interface and then go to the next step: implement a supervisor which has a full overview of all components and their status, and can make decisions based on this...
The new one on the right, old one on the left. They're both 100A versions to keep the comparison easier. The port to the right of the GPS/RS485 label is the display port. As Dave Jones would say: "Don't turn it on. Take it apart!"
New one on the right again. The original is hardware version 6.0, the new one 8.0. There have been a few changes, mostly on the other side of the board. The main change on this side of the board is the micro controller. The old version had an original STM32F103; probably due to shortages or because more resources were needed, it is replaced with a GD32F103. This is a pin compatible clone of the STM, it's used on some Bluepill boards and finds its way into many products these days since it's cheaper and actually available, unlike the STM. It also has more RAM/FLASH and can run at higher clock speeds. I'm actually surprised they didn't have the GD32 on there from the beginning. The MOSFETs are still the same: G042N10.
The GD32.
Other side of the board. More profound changes here. For one, the Bluetooth module was changed. Didn't look at the details, but they're both common modules. The chip at the bottom is a YD3082, which is an RS485 transceiver, which is what is driving the display. I'm not sure yet if this shares the same RS485 bus where one connects the RS485 dongle to. I'll find out later. There are also some added digital isolators that weren't there before (an 122U31) - probably to provide better isolation between the power and control side.
The YD3082 RS485 transceiver in the middle to the right.
This is the Display itself. It's very clear and bright, and the power button on the side works fine to turn the BMS on. I somehow wish it could be used to turn the BMS off again, but that's not a deal breaker. Ignore the 6.6V and state of charge, I just connected the BMS to two spare cells and a power supply.
I originally wanted to create a custom enclosure for it, but the handle bar mount can be removed easily, and it looks much better this way.
Of course, I also opened the display:
It's based around a Holtec HT1621 display driver on the right. This thing has a serial interface, and the other chip to the left is a hk32f030, another microcontroller that takes the incoming data and talks to the Holtec chip.
The LCD display itself.
I want to dig in deeper in some of the changes and other aspects of the BMS. For one, I really want to figure out how the power button is implemented, and if this is a software or hardware thing (or both). I don't know when I will have time for this though; now that I have one sitting on my desk I want to get back to the RS485 communication, finishing my Grafana interface and then go to the next step: implement a supervisor which has a full overview of all components and their status, and can make decisions based on this...
Last edited:
hwse
Solar Enthusiast
- Joined
- Jan 2, 2021
- Messages
- 585
Thanks for the great writeup.
I cannot find it now but on the a description that I found on the display, it said (if memory is correct) that you could turn the BMS off by "long pressing" the button. I cannot remember the time but I have several other devises that turn off with a 3-5 second press and hold on the button.
I cannot find it now but on the a description that I found on the display, it said (if memory is correct) that you could turn the BMS off by "long pressing" the button. I cannot remember the time but I have several other devises that turn off with a 3-5 second press and hold on the button.
Yeah, I tried that, didn't work.
curiouscarbon
Science Penguin
- Joined
- Jun 29, 2020
- Messages
- 3,024
wonderful write up!
interesting that the G042N10 MOSFET is used here.
thank you for taking time to document these details!
on the JBD 120A 4S that i have, the MOSFET are labeled G013N04. fun to learn which switch is in which BMS. thanks
https://diysolarforum.com/threads/j...-lifepo4-in-series-parallel.19228/post-332656
based on the model number, perhaps Huayi makes the MOSFET in this JK BMS as well.
reference from other BMS
curiouscarbon
Science Penguin
- Joined
- Jun 29, 2020
- Messages
- 3,024
Vdss 100V rating!
Yes, here too:
diysolarforum.com
This one above had the G035N10N - also 100V, but higher max current.
JBD/Overkill vs JK/Heltec BMS
Has anyone done a comparison between the JBD and JK BMS's? They look very similar to me. The JBD seems to use the Xioxiang app, and the JK uses thr ENJpower app. The apps are also VERY similar. I know Overkill is JBD, ans Heltec is JK based. Is the same manufacturer making both? I am not as...
diysolarforum.com
This one above had the G035N10N - also 100V, but higher max current.
mrzed001
Voice of reason
Yes, here too:
JBD/Overkill vs JK/Heltec BMS
Has anyone done a comparison between the JBD and JK BMS's? They look very similar to me. The JBD seems to use the Xioxiang app, and the JK uses thr ENJpower app. The apps are also VERY similar. I know Overkill is JBD, ans Heltec is JK based. Is the same manufacturer making both? I am not as...
This one above had the G035N10N - also 100V, but higher max current.
The MPP Solar inverters have 75V MOSFETs
One other thing I don't like about the screen: it's a (in relative terms) power hog. When active, it consumes 960mW, and when the display if off (but connected) it's 320mW. As someone who designs low power embedded systems, this is unacceptable. I'll probably add a power switch for the screen if I decide to use it, or I might be tempted do design my own screen for this BMS...
Ok, on the power consumption, it seems that after a while the screen draws 320mW in a pulsed pattern, and then some time later drops to 0mW altogether. The button wakes up the screen just fine and once it goes back to sleep it draws 320mW again, starting the pulsed pattern again after a few minutes and then back to 0mW. I guess there is some sleep code that only kicks in after some minutes. I'll add it to the list of further investigations needed...
Edit: Display keeps coming up and draw 320mW after some time, cycling pulsed pattern, etc. Never staying at 0mW... definitely needs a power switch in my opinion.
Edit: Display keeps coming up and draw 320mW after some time, cycling pulsed pattern, etc. Never staying at 0mW... definitely needs a power switch in my opinion.
Last edited:
Steve_S
Offgrid Cabineer, N.E. Ontario, Canada
Sure seems to me you got the Bull by the Horns and in your case that would a Northern Moose Bull ! (with a grumpy tude in winter no less).
Thanks for doing the in-depth detailed look, something that is not all that common.
Everytime I see your avatar, I think of:
Thanks for doing the in-depth detailed look, something that is not all that common.
Everytime I see your avatar, I think of:
I've updated my repo to read the data from the BMS for Grafana display.
github.com
GitHub - PurpleAlien/jk-bms_grafana: Read data from a JK BMS and graph it in Grafana
Read data from a JK BMS and graph it in Grafana. Contribute to PurpleAlien/jk-bms_grafana development by creating an account on GitHub.
github.com
hwse
Solar Enthusiast
- Joined
- Jan 2, 2021
- Messages
- 585
I look at your RS-485 code and my poor brain starts to smoke. I have not needed to do any real programing since collage and that was in Fortran with punch cards.I've updated my repo to read the data from the BMS for Grafana display.
GitHub - PurpleAlien/jk-bms_grafana: Read data from a JK BMS and graph it in Grafana
Read data from a JK BMS and graph it in Grafana. Contribute to PurpleAlien/jk-bms_grafana development by creating an account on GitHub.
I recently installed a bunch of NMEA 2000 electronics on my boat. My understanding was that NMEA 2000 is basically CAN bus with funny connections to make it more "marine". I was hoping that connecting a BMS to an inverter would be as simple as connecting a chart plotter to a wind instrument which basically involves plugging each into the NMEA back bone and answering the questions on the Wizard that pops up.
Looks like it is more involved that that, sigh!
NMEA 2000 (I mostly know it as IEC 61162-3) is essentially plug an play. However, to do that, there is a whole lot of higher level functionality on top of the physical CAN bus and protocol. That RS485 code you see on my github is essentially something that lives right above the hardware, where we take incoming data bytes and decode those bytes according to a protocol description of what byte means what, in what order, how many need to be grouped, etc.
That said, you don't have to connect an inverter to the BMS. They work fine independently. But yes, if you want the BMS to control the inverter, etc. there is more involved unless you go with specific hardware that supports this (like Batrium BMS with Victron hardware).
That said, you don't have to connect an inverter to the BMS. They work fine independently. But yes, if you want the BMS to control the inverter, etc. there is more involved unless you go with specific hardware that supports this (like Batrium BMS with Victron hardware).
HGPilot
New Member
- Joined
- Nov 29, 2021
- Messages
- 33
Serial is fun for sure!
Nice code, will have to try it once I get my hardware.
You seem like a right person to ask, do you know what is the jk bms pinout on rs485 port and same on an LV6548 inverter by any chance?
I heard that JK BMS is talking Pylontech protocol and it should interoperate with MPP's LV6548.
Thanks,
A
