diyers230ah
New Member
As per the manual
See the table from the manual.
Master id = 0 (0000 dipswitch)
Slave id = 2 (0100 disswitch)
Correct ser?
As per the manual
See the table from the manual.
I did ser Master id = 0, but in contrary the PC app still functioning and is able to modify settings. Also, UART2 Prtocol was still fixed to 017 RS485 Protocol 17. Even if i changed the id = 1, 2 3 etc the UART is always at 017 greyed out.ModbusID is selected via dip-switches.
For the master battery, I reserve the Modbus ID 0 (for running) and 1 (for PC app settings)
Modbus ID = 0. Other values = slaves.
When the Modbus ID is 0, the PC app will not function to modify the settings.
My second battery has the Modbus ID = 2.
If the Modbus ID is different from 0 => slave battery => UART2 protocol is fixed to 015 for communications between batteries).
You use the UART 2 (the two ports on the right, NOT close to the can) to connect the batteries.
Tried Slave id = 1, UART2 Protocol changed to 000 - 4G GPS Remote module protocol.ModbusID is selected via dip-switches.
For the master battery, I reserve the Modbus ID 0 (for running) and 1 (for PC app settings)
Modbus ID = 0. Other values = slaves.
When the Modbus ID is 0, the PC app will not function to modify the settings.
My second battery has the Modbus ID = 2.
If the Modbus ID is different from 0 => slave battery => UART2 protocol is fixed to 015 for communications between batteries).
You use the UART 2 (the two ports on the right, NOT close to the can) to connect the batteries.
I have the same problem with the UART 2 settings.
JKBMS V19 with Firmware V19.10
PC SW 3.2.0 @ RS485-1
Good BMS at ID0000(Master)
View attachment 323017
Good BMS at ID0001(Slave)
View attachment 323018
Bad BMS at ID0000(Master)
View attachment 323016
Bad BMS at ID0001(Slave)
View attachment 323015
As you can see the "broken" BMS shows in slave mode the wrong protocol and cant be operated as slave.
In master mode the protocol seems ok and the BMS can be used as Master
Seem like a firmware BUG.
On the PC Software and Android App the settings of UART 2 are greyed out and can not be changed by user.
Any ideas? Is there any way to do some kind of "factory" reset?
Things I tried:
- Downgrading FW to 19.05 and back to 19.10
Hello, I had the same problem with 4 jk bms v19, 3 worked perfectly, 1 stuck on master mode, regardless of dip switch setting, all with firmware 19.10. The problem was solved by forced update to firmware 19.16, after the update all 4 jk bms v19 work perfectly. Try a firmware update to 19.16 version. Download from here: https://diysolarforum.com/threads/jk-bms-v19-firmware-versions.108167/post-1614661Hello
I have just build my last battery (for now). In total i have 4, in Yixiang V.2 enclosures, with JK inverter BMS V.19. I have updated to firmware 19.10, The first tree went fine, and communication was working from start. Today i had so many problems with the fourth pack. First it interrupted all the communication on the RS485-2 ports. After fidelling a lot with it changed cables and so on, I saw that UART 2 ( The one that is chosen by the bms it self) was set to 1 JK BMS 485 on the 2 slaves that worked but on battery 4 (adress 3) it was set to the 4g protocol. Then I set UART 1 to protocol 1 JK BMS 485 and connected Battery 4 (adress 3) RS485 -1 to Battery 3 (adress 2) RS485-2. The made the pack work! Not the intended connection, but it confirmed my theory about UART 2 protocol being wrong)
Any ideas?
Regards Tommy
The solution is above, try installing firmware version 19.16. It worked for me!I am having the same problem. My uart2 setting seems to be locked to no. 16 when device id set to 0. If ID is set to 1, then I can change the Uart2 setting. What is the solution?
was you able to fix it? one of mine is also 000 instead of 001Tried Slave id = 1, UART2 Protocol changed to 000 - 4G GPS Remote module protocol.
But still cannot communicate to Master w/c was at id = 0, UART2 Protocol = 017.
What a headache. Im so stress already and my battery still cannot use in parallel![]()
Did is solve your problem?Thank you! Will try soon![]()
Did you try a forced update?I also have UART2 not working as slave (DIP other than 0) on 3 x JK BMS pb2a16s20p (locked on 000 - 4G... ) "fireware" 19.16 and 19.18 not helped. As I only have 3, i connect them in paralell from the master UART2_1 -> Slave1_UART1, master UART2_2 -> Slave2_UART1, Master CAN to Inverter. JK support not answering anymore.... Initially, I got a reply from them a month ago, that they will send me a firmware the next day that will solve the issue, but never got anything after.... It is unbelievable, that they can ignore customers in this manner.
Forced update to 19.10. No luck. The reset button doesn't reset s...t. I went a litle crazy and intrerrupted the firmware update process (pulled the cable at 49%) and after that I reflashed. Every setting was reset to factory, EXCEPT the read only UART2 value....still on 000-4G....Did you try a forced update?
The solution for me was update to 19.16. Export the settings from a good bms and import them to the bad one.Forced update to 19.10. No luck. The reset button doesn't reset s...t. I went a litle crazy and intrerrupted the firmware update process (pulled the cable at 49%) and after that I reflashed. Every setting was reset to factory, EXCEPT the read only UART2 value....still on 000-4G...
tried already, not working.The solution for me was update to 19.16. Export the settings from a good bms and import them to the bad one.