JK BMS RS485/UART

[gfjardim]

Is there any plans to add JK BMS serial communication to this app?

[ai-republic]

Sure, will be the next to be implemented :)

[ai-republic]

@gfjardim I have implemented the initial JK BMS RS485 support. If you could test it and see if it reads the SOC correctly I could go forward to implement the rest

[gfjardim]

Hi @ai-republic, saw that but can’t communicate with my Deye inverter using a Canable USB adapter.

Have you ever used such device?

[ai-republic]

So you saw that it reads the SOC correctly, right? That would be perfect and I would go forward implementing the rest of the protocol.
How do you use the Canable USB adapter? Have you flashed it with the Candlelight firmware?

[DezR]

Just a quick question.
For the JK 'RS485' interface to work with a PI RS485/CAN HAT, I'm assuming that you'll need the JK TTL to RS485 adapter.

Is it possible to connect directly from the JK 'RS485' interface to the PI RXD and TXD pins (not using the HAT RS485 interface)?

[ai-republic]

Yes, you can do that. You can use the PI's serial IO pins 6 (GND), 8 (TX) and 10 (RX) as seen here:

[DezR]

Thank you for your help.

One problem I've been having though, is that no matter what port or ID I enter for the BMS (JK_RS485), it always seems to be stuck at trying to open it.
An example is if I use /dev/ttyAMA0:

2024-03-14 14:11:12.950 | INFO | main | core.BMSListProducer:87 | Intialized BMS #0[JK_RS485] on port /dev/ttyAMA0
2024-03-14 14:11:12.951 | INFO | main | verter.BmsToInverter:157 | Starting BMS receiver...
2024-03-14 14:11:12.953 | INFO | Thread-2 | verter.BmsToInverter:164 | Reading BMS #0 JK_RS485 on /dev/ttyAMA0...
2024-03-14 14:11:12.955 | INFO | Thread-2 | stoinverter.core.BMS:120 | ---------------------------------> Thread 19
2024-03-14 14:11:12.956 | INFO | Thread-2 | toinverter.core.Port:101 | Opening /dev/ttyAMA0 ...

For direct connection between Pi TXD and RXD with TTL, I've tried serial0, AMA0, AMA10, ttyS0, 0x000 etc
Through the 485/CAN hat (single Waveshare) , I've tried ttySC0, ttySC1 and the ones above with no luck.
I've also tried swapping Tx and Rx around, and another BMS with no luck either.

[ai-republic]

Your PI probably needs to be properly configured:
The serial port of Raspberry Pi is often used to access the shell. However, in some condition you just want to use it to communicate with UART peripherals. You can disable shell and kernel messages on the serial connection via Raspberry Pi configuration tool:

sudo raspi-config

Select Advanced Options -> Serial -> to disable shell and kernel messages on the serial connection. Then edit the /boot/config.txt file and append:

enable_uart=1

And you will need to set the baud rate to 9600 baud (for now everytime you start your PI):

stty -F /dev/ttyAMA0 9600

If you ever have the port still open you can close the using process by calling:

fuser -k /dev/ttyAMA0

[DezR]

Thanks.
Unfortunately, I'd already done these things (except adding enable_uart=1).

I have a Pi5 running Bookworm and thought dtparam=uart0=on was enough to enable the port, but still added enable_uart=1 without luck.

ls -la /dev/serial* shows

lrwxrwxrwx 1 root root 8 Mar 14 14:17 /dev/serial0 -> ttyAMA10
lrwxrwxrwx 1 root root 5 Mar 14 14:17 /dev/serial1 -> ttyS0

I tried with these at first and also tried after removing the RS485/CAN Hat unsuccessfully.
Edit: I also tried disabled bluetooth and linked serial0 to ttyAMA0 (instead of ttyAMA10) using sudo ln -sf /dev/ttyAMA0 /dev/serial0

I'll keep trying some other different things, but think I'm almost at the end of everything i know to try.

[ai-republic]

Hmm, could you try using your RS485/CAN hat again? And can you tell me which hat exactly that is? Then I could try and figure out the installation on that and guide you through that. I guess you'll need the CAN anyway later to connect your Goodwe inverter.

I just got my PI 5 a few day ago but haven't had the chance to run any tests on it :)

[DezR]

I don't seem to have any issues with CAN.
Running candump can0 on the Pi, I believe I can see the expected frames for each battery profile selected on the inverter, ie;
BYD I receive can0 308 [8] 47 57 35 30 34 38 45 53
Pylon I receive can0 305 [8] 00 00 00 00 00 00 00 00

The RS485/CAN Hat I'm using is Waveshare RS485/CAN HAT
I basically just followed their instructions at RS485/CAN HAT usage to setup

One thing with this Hat is that it needs a riser so the tracks and through-hole soldered leads of its PCB clear the Pi 5 heatsink.

Pi 5 seems to have some obscure differences to earlier types. It's been a bit of a learning adventure :)

[ai-republic]

Ok, good I have the same for testing. So you did the following:

sudo raspi-config

go to Interface Options -> SPI enable

sudo nano /boot/config.txt

and add the lines depending on the oscillator (the silver oval shaped component) if it says 12MHz:

dtparam=spi=on
dtoverlay=mcp2515-can0,oscillator=12000000,interrupt=25,spimaxfrequency=2000000

or 8MHz:

dtparam=spi=on
dtoverlay=mcp2515-can0,oscillator=8000000,interrupt=25,spimaxfrequency=1000000

then

ip addr | grep "can"

-> should see can0

sudo modprobe can
sudo modprobe can_raw
lsmod | grep "can"

-> should see can and can_raw

ifconfig -a

-> you should see can0

[DezR]

Yep, basically that, however...instead of

ip addr | grep "can"
sudo modprobe can
sudo modprobe can_raw
lsmod | grep "can"

I just used
sudo ip link set can0 up type can bitrate 500000
sudo ifconfig can0 txqueuelen 65536
then with ifconfig I could see the interface and start receiving frames from the inverter.

[ai-republic]

ok, yeah that's the CAN related setup that seems to work properly.
ATM we'll need to figure out your RS485 and that is basically configuring to enable the SPI and making sure the dtparam=spi=on is configured in the /boot/config.txt.
Then your port should be /dev/ttyS0

[ai-republic]

I will install my PI 5 today and see if I run into any problems?
Did you install the Python libraries when following the Waveshare Wiki? They are not needed. I don't know if installing python-serial might make any configuration changes to your PI

[DezR]

Thank you, good luck with it. :)
I guess a lot of people will eventually be moving to the Pi 5.

I'll also keep playing around as well to hopefully get it working. Your BMS solution has a lot of good potential.

Edit: Sorry I missed that question about python libraries. I didn't install them.

[ai-republic]

Thanks! I will reply in an hour ago when Raspian is installed and the WS RS485-CAN-Hat is configured and tested

[ai-republic]

So, I do seem to have the same problem with the PI 5 and the Waveshare RS485-CAN-HAT.
I've contacted Waveshare and submitted a ticket, so I need to wait for an answer.
I have not yet tested to go straight to the GPIO pins, but will test that tomorrow morning.

[DezR]

Thanks for the update.

I removed the Waveshare RS485/CAN HAT completely and still had the same problem, however didn't try every config variation with it removed.
I'll try with the HAT removed again, but with more different configs and see how it goes.

[ai-republic]

@DezR
I've tested the PI 5 with the UART Pins 14 (TX) and 15 (RX) and they work as long as you have run raspi-config, go to Interface Options -> Serial Port and turn off login via serial (first mask - NO) and then enable serial port hardware (second mask - YES) .
The port device is then: /dev/ttyAMA0

[DezR]

Thanks for testing this.
I'd already set the interface config this way, but checked again and still set correctly.
Unfortunately still stuck at INFO | Thread-2 | toinverter.core.Port:101 | Opening /dev/ttyAMA0 ... when physically connected to the JK BMS port.

I've also tried setting the rate at 115200, 9600 etc with no luck, also ttyAMA10 and ttyS0
I think I have a TTL-USB adapter around somewhere. I'll try to see if I can at least eliminate the Pi as being the problem.

The BMS(s) connect fine when I try with a ESP32 board (using this emulator ) and can see all of the battery and cell info.

It might be possible I have a dodgy Pi.

[ai-republic]

I connected it like this including the yellow cable (goes to GPIO15) next to the red (GPIO14):

Although connecting it like this I got to read messages too but I think the sending did not work. I will try that tomorrow...

[DezR]

Yep, that's the same way I've been connecting mine, and then directly to the JK TTL/RS485 port.

[ai-republic]

Ok, that's strange. And when the JK is connected and running cat /dev/ttyAMA0 outputs nothing I guess.
And I presumed you checked that the JK BMS is also running and not switched off or idle right?

Well, all I could think of is to try to flash a new Raspian OS and only do the serial settings to definitly to verify its really the pins.

[DezR]

Yes, that is correct. There is no output running cat /dev/ttyAMA0 and the BMS is definitely functional and running.
It is a very weird problem.

I'll try another Raspbian OS a bit later today when I get home. Thank you for the suggestion.

[DezR]

I tried with another microsd and fresh installation of bookworm.
Unfortunately it still has the same problem.

The weirdest thing is that i can connect a jumper between pins 8 and 10 and get minicom to work correctly, just not connect to the BMS. Even when trying 4 different BD4A17S4P's

Maybe my Pi 5 is cursed and I should get a Pi 4 :)

[DezR]

I haven't yet, but will order the connector and definitely try it.
Apparently it's just a 1.0mm 3-pin JST ‘SH’ connector.

Hopefully it will get here in a few days. :)

[ai-republic]

Maybe just wait for the debug/serial port connector.It's strange. Maybe the port on the BMS is not working?On 18/3/24, 17:40 DezR ***@***.***> wrote: I tried with another microsd and fresh installation of bookworm. Unfortunately it still has the same problem. The weirdest thing is that i can connect a jumper between pins 8 and 10 and get minicom to work correctly, just not connect to the BMS. Even when trying 4 different BD4A17S4P's Maybe my Pi 5 is cursed and I should get a Pi 4 :) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[DezR]

Weirder still, yesterday I hooked the Pi5 (and RS485/CAN Hat) up to a RS485-USB adapter connected to a PC.
I ran Minicom on both, however could only receive on the PC from the Pi5, not get it to receive.

Tried again without the RS485/CAN hat and a loopback on pins 8 and 10.......and no Rx this time....
It seems the Pi5 I have has a flakey UART or something has burnt out.

I now have a new Pi4 arriving tomorrow :) , so this should fix some problems.
I'll still try to get the Pi5 working, but will probably use it for something else.

[ai-republic]

Sorry to hear that.
But I also have the problem with the Waveshare RS485/CAN hat on my Pi 5.
Pi 3B and 4B work like a charm. I'm still waiting for another reply from Waveshare...

[kommando828]

If you google Bookworm and UART there are lot of posts saying its broken in late 23.

This was one issue

raspberrypi/linux#5667

Which was fixed sept 7th 23 but did not make it into the main release until Nov 6th.

So maybe go back to Bullseye to see if it works.

[DezR]

Thanks.
It's certainly worth trying.

Edit: Bullseye doesn't run on a Pi 5

[ai-republic]

@DezR
I got a reply from Waveshare and this is what they say:

"The serial port configuration of Raspberry Pi 5 and Raspberry Pi 4 is different,

Please refer to the following steps to configure the serial port:

Edit the config.txt file

sudo nano /boot/config.txt

Add the following and statement at the end

dtoverlay=disable-bt

After restarting, ttyS0 can be seen"

I have not yet tested it but might do later today if I have time.

[DezR]

Thank you for the update.
I'd already done this and can see ttyS0 as per here , however no luck in connecting to it.

I finally got the JK ttl-rs485 adapter, re-attached the CAN Hat and also also tried everything again. Unfortunately no go.
As you've said, I'll try through the debug port when the connector arrives.

There still seems to be some bugs with Bookworm and the Pi 5.

I've no problem getting a Pi 4 and trying it.
One definite advantage anyway is the the Pi 4 uses less power and has been around long enough for most bugs to be fixed :)

[ai-republic]

Yeah, didn't work on my PI 5 either. Contacted Waveshare again ;)

[DezR]

Hey Torsten,
It looks like with a Pi 4, it can connect to the JK BMS (using the RS485/CAN hat) and appears that it is receiving as expected;

2024-03-23 07:32:16.563 | DEBUG | Thread-2 | s485.JSerialCommPort:116 | Send: Buffer (HEX): [0x4E, 0x57, 0x00, 0x13, 0x00, 0x00, 0x00, 0x00, 0x06, 0x03, 0x00, 0x79, 0x00, 0x00, 0x00, 0x00, 0x68, 0x00, 0x00, 0x01, 0xA2]

2024-03-23 07:32:16.576 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01]

2024-03-23 07:32:16.576 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x79, 0x30, 0x01, 0x0B, 0xBA]

2024-03-23 07:32:16.576 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x02, 0x0B]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAB, 0x03]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBA, 0x04]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBA]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x05, 0x0B]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAB]

2024-03-23 07:32:16.577 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x06]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B, 0xAA]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x07]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBA]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x08]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAA, 0x09]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBC]

2024-03-23 07:32:16.578 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0A]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAA]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBC, 0x0C]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBC]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0D]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.579 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA9]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0E]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B, 0xA9]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0F]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBC]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x10, 0x0B]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAA, 0x80]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x1B]

2024-03-23 07:32:16.580 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x81]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x17]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x82]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x17]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x83]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x12]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB7]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x84]

2024-03-23 07:32:16.581 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x85]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x02]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x86]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x02]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x87]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x07]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x89]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.582 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x7B, 0x8A]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x10]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x8B]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x8C]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x07]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x8E]

2024-03-23 07:32:16.583 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x16]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x80, 0x8F]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x10]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x40]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x90]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0E, 0x10]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x91]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0D]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xDE, 0x92]

2024-03-23 07:32:16.584 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x05]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x93]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0A]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x28]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x94]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0A]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x5A]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x95, 0x00]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x05]

2024-03-23 07:32:16.585 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x96]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x2C]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x97]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x1E]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x98]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x2C]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x99]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x1E]

2024-03-23 07:32:16.586 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x9A]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x1E]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x9B]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB8]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x9C]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x0A]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x9D]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01, 0x9E]

2024-03-23 07:32:16.587 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x64]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x9F]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x50]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA0]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x64]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA1]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.588 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x64]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA2, 0x00]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x14]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA3]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x46]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA4]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x46]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA5, 0xFF]

2024-03-23 07:32:16.589 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xEC]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA6]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xFF, 0xF6]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA7]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xFF]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xEC]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA8]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xFF]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xF6]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA9]

2024-03-23 07:32:16.590 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x10, 0xAA]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x1E]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAB]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01, 0xAC]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01, 0xAD]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x03]

2024-03-23 07:32:16.591 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB1]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAE]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01, 0xAF]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB0]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0A, 0xB1, 0x14]

2024-03-23 07:32:16.592 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB2, 0x31]

2024-03-23 07:32:16.593 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x32]

2024-03-23 07:32:16.593 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x33, 0x34]

2024-03-23 07:32:16.593 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x35]

2024-03-23 07:32:16.593 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x36, 0x00]

2024-03-23 07:32:16.593 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00]

2024-03-23 07:32:16.593 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00]

2024-03-23 07:32:16.594 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB3, 0x00, 0xB4, 0x49, 0x6E]

2024-03-23 07:32:16.595 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x70, 0x75, 0x74, 0x20, 0x55, 0x73, 0xB5, 0x32, 0x33, 0x31, 0x32, 0xB6]

2024-03-23 07:32:16.595 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00, 0xFA, 0xD5]

2024-03-23 07:32:16.596 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB7, 0x31, 0x31, 0x2E, 0x58]

2024-03-23 07:32:16.596 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x57, 0x5F, 0x53, 0x31]

2024-03-23 07:32:16.596 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x31, 0x2E, 0x32, 0x38]

2024-03-23 07:32:16.596 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x38, 0x5F]

2024-03-23 07:32:16.597 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x5F, 0xB8, 0x00]

2024-03-23 07:32:16.597 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB9]

2024-03-23 07:32:16.597 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00]

2024-03-23 07:32:16.597 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x11]

2024-03-23 07:32:16.597 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xBA]

2024-03-23 07:32:16.597 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x49]

2024-03-23 07:32:16.598 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x6E, 0x70, 0x75, 0x74]

2024-03-23 07:32:16.598 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x20, 0x55, 0x73, 0x65, 0x72]

2024-03-23 07:32:16.598 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x64, 0x61, 0x30]

2024-03-23 07:32:16.598 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x30]

2024-03-23 07:32:16.599 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x30, 0x00]

2024-03-23 07:32:16.599 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00]

2024-03-23 07:32:16.599 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00, 0x00, 0x00, 0x00]

2024-03-23 07:32:16.599 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0xC0, 0x01]

2024-03-23 07:32:16.600 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00, 0x00]

2024-03-23 07:32:16.600 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x68]

2024-03-23 07:32:16.600 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00]

2024-03-23 07:32:16.600 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x52, 0x93]

2024-03-23 07:32:16.685 | DEBUG | Thread-2 | s485.JSerialCommPort:106 | Next frame: Buffer (HEX): [null]

2024-03-23 07:32:16.686 | DEBUG | Thread-2 | .JKBmsRS485Processor:122 | No bytes received: 11 times!
2024-03-23 07:32:16.687 | ERROR | Thread-2 | .JKBmsRS485Processor:145 | Error sending frame: Buffer (HEX): [0x4E, 0x57, 0x00, 0x13, 0x00, 0x00, 0x00, 0x00, 0x06, 0x03, 0x00, 0x79, 0x00, 0x00, 0x00, 0x00, 0x68, 0x00, 0x00, 0x01, 0xA2]

2024-03-23 07:32:16.688 | DEBUG | Thread-2 | s485.JSerialCommPort:116 | Send: Buffer (HEX): [0x4E, 0x57, 0x00, 0x13, 0x00, 0x00, 0x00, 0x00, 0x06, 0x03, 0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x68, 0x00, 0x00, 0x01, 0xA9]

2024-03-23 07:32:16.701 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01]

2024-03-23 07:32:16.702 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x79, 0x30, 0x01, 0x0B, 0xBA, 0x02]

2024-03-23 07:32:16.703 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B, 0xAB, 0x03, 0x0B, 0xBA, 0x04, 0x0B, 0xBA, 0x05, 0x0B, 0xAB]

2024-03-23 07:32:16.703 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x06, 0x0B, 0xAB, 0x07, 0x0B, 0xBC, 0x08]

2024-03-23 07:32:16.704 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B, 0xAA, 0x09, 0x0B, 0xBC, 0x0A, 0x0B, 0xAA, 0x0B]

2024-03-23 07:32:16.705 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x0B, 0xBC, 0x0C, 0x0B, 0xBC, 0x0D, 0x0B, 0xA9, 0x0E, 0x0B]

2024-03-23 07:32:16.706 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xA9, 0x0F, 0x0B, 0xBC, 0x10, 0x0B, 0xAA, 0x80]

2024-03-23 07:32:16.706 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x1B, 0x81, 0x00, 0x17]

2024-03-23 07:32:16.707 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x82, 0x00, 0x17, 0x83, 0x12, 0xB7, 0x84]

2024-03-23 07:32:16.707 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00, 0x85, 0x02, 0x86, 0x02, 0x87, 0x00, 0x07]

2024-03-23 07:32:16.708 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x89, 0x00, 0x00, 0x00, 0x7B, 0x8A, 0x00]

2024-03-23 07:32:16.709 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x10, 0x8B, 0x00, 0x00, 0x8C, 0x00, 0x07, 0x8E, 0x16]

2024-03-23 07:32:16.710 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x80, 0x8F, 0x10, 0x40, 0x90, 0x0E, 0x10, 0x91, 0x0D]

2024-03-23 07:32:16.710 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xDE, 0x92, 0x00, 0x05, 0x93, 0x0A, 0x28]

2024-03-23 07:32:16.711 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x94, 0x0A, 0x5A, 0x95, 0x00, 0x05, 0x96]

2024-03-23 07:32:16.711 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x01, 0x2C, 0x97, 0x00, 0x1E]

2024-03-23 07:32:16.712 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x98, 0x01, 0x2C, 0x99, 0x00, 0x1E, 0x9A]

2024-03-23 07:32:16.712 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x1E, 0x9B, 0x0B, 0xB8, 0x9C, 0x00, 0x0A]

2024-03-23 07:32:16.717 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x9D, 0x01, 0x9E, 0x00, 0x64, 0x9F, 0x00, 0x50, 0xA0, 0x00, 0x64, 0xA1, 0x00, 0x64, 0xA2, 0x00, 0x14, 0xA3, 0x00, 0x46, 0xA4, 0x00, 0x46, 0xA5, 0xFF, 0xEC, 0xA6, 0xFF, 0xF6, 0xA7, 0xFF, 0xEC, 0xA8, 0xFF, 0xF6, 0xA9, 0x10, 0xAA, 0x00, 0x00, 0x00, 0x1E, 0xAB, 0x01, 0xAC, 0x01]

2024-03-23 07:32:16.717 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xAD, 0x03, 0xB1, 0xAE, 0x01, 0xAF, 0x00]

2024-03-23 07:32:16.718 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0xB0, 0x00, 0x0A, 0xB1, 0x14, 0xB2, 0x31]

2024-03-23 07:32:16.718 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x32, 0x33, 0x34, 0x35, 0x36, 0x00]

2024-03-23 07:32:16.719 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00, 0x00, 0xB3, 0x00, 0xB4, 0x49]

2024-03-23 07:32:16.719 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x6E, 0x70, 0x75, 0x74, 0x20]

2024-03-23 07:32:16.722 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x55, 0x73, 0xB5, 0x32, 0x33, 0x31, 0x32, 0xB6, 0x00, 0x00, 0xFA, 0xD5, 0xB7, 0x31, 0x31, 0x2E, 0x58, 0x57, 0x5F, 0x53, 0x31, 0x31, 0x2E, 0x32, 0x38, 0x38, 0x5F, 0x5F, 0xB8, 0x00, 0xB9, 0x00]

2024-03-23 07:32:16.723 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x00, 0x00, 0x11, 0xBA, 0x49, 0x6E, 0x70]

2024-03-23 07:32:16.723 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x75, 0x74, 0x20, 0x55, 0x73, 0x65, 0x72]

2024-03-23 07:32:16.726 | DEBUG | Thread-4 | s485.JSerialCommPort:157 | Received: Buffer (HEX): [0x64, 0x61, 0x30, 0x30, 0x30, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xC0, 0x01, 0x00, 0x00, 0x00, 0x00, 0x68, 0x00, 0x00, 0x52, 0x96]

2024-03-23 07:32:16.809 | DEBUG | Thread-2 | s485.JSerialCommPort:106 | Next frame: Buffer (HEX): [null]

2024-03-23 07:32:16.809 | DEBUG | Thread-2 | .JKBmsRS485Processor:122 | No bytes received: 12 times!
2024-03-23 07:32:16.810 | ERROR | Thread-2 | .JKBmsRS485Processor:145 | Error sending frame: Buffer (HEX): [0x4E, 0x57, 0x00, 0x13, 0x00, 0x00, 0x00, 0x00, 0x06, 0x03, 0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x68, 0x00, 0x00, 0x01, 0xA9]

Is it expected that there is the error (in bold) that increments the error counter between frames?

So far looking a lot better than with the Pi 5 :)

[ai-republic]

Great! You're receiving data now. But something is not right with the implementation because its not finding any valid frames. I will go through your log and find out what the problem is.

I have starting to figure out the returned data. Its different than expected but I can change the code.

Oh, and next time please just attach the log, otherwise the thread gets to overloaded and everything is hard to find ;)

[DezR]

No problem, I will next time.

Sorry, I wasn't sure if you wanted the 42MB file attached or just part. :)

[ai-republic]

Ok, could you please do a Clean install and test again. I hope that now the binding can process the JK response data properly.

If the log file is too big, then just attach a file with the relevant part from the start or the end (but at least including one complete BMS reading cycle)

[DezR]

No problem, done.

Let me know of anything you want to try.

BMS-to-Inverter.log

[ai-republic]

Hmm OK, there is still something wrong with the data processing.I'll do a test case tomorrow. Then I have more time ;)

[ai-republic]

Ok, ready to test again :)
I've fixed the data processing now and also wrote a test based on the data I got from you.

[DezR]

Thanks :)
I've attached the log file after trying with 2 different BMS.
BMS-to-Inverter.log

[ai-republic]

Thanks for the log. I fixed the queue initializing so now we should get a result.

[DezR]

Here's the log from that.
I wish i knew more about coding to help more with this.
BMS-to-Inverter.log

[ai-republic]

No problem, its always step-by-step since I don't have the hardware (JK) to test on.

But its good - we are already getting valid data.
I fixed the exception and added debug logging to log the data being processed.

Could you please update the application and attach the log again?

[ai-republic]

Ok, great we're getting all the values. I noticed some units were off, but have fixed them, and also the cell voltages.

According to the received data the SOC is actually 0 (zero). Is that correct?
And could you compare the values we get to the values in the BMS just to see if we're not mingling some values. (There a a few JK RS485 specs out there which look generally very similar, but they have their little differences - some were translated from chinese some published by sellers). So let's see that we get these values figured out all correctly.

[DezR]

That's great!
Yeah, SOC shows as 0 on the JK app as well, so that's right.
When the BMS stops discharging and hits the low cell limit, they show 0 SOC and shutdown until they sense a charge current.

Aside from the cell voltages as you've said, most look good. I'll go through them and compare to get the right values.

[DezR]

The actual battery rated capacity should be 30Ah, however that might be a weird figure that the BMS is providing as I have the Cycle Capacity showing 137Ah on the JK app.

The Charge MOS should =ON, Discharge and Balance are correct.

The Cell max voltage limit should be 3.6V instead of 0.36V and Cell min voltage limit should be 2.6V instead of 0.26 V

CellDiff should be ~0.2V instead of 0V, however the BMS(s) I have do have an inbuilt 0.4A balancer, so CellDiff will constantly change.

Aside from those, it is looking really good :)
For my application i'll have 10 batteries (10 JK BMS's.....all the same model) in parallel, each with a unique serial/RS485 address, so might be a bit of challenge aggregating this for the inverter.

[ai-republic]

Great, I think I've got all the values correct now, also added cells with min/max voltages and their number and cell difference.
Could please update, recheck and attach the log file?

[DezR]

Sure thing.
The cell voltages are still incorrect.
The BMS alarm [BMS #1:levelOneCellVoltageTooHigh] is incorrect. Is this coming from the BMS system log?

Everything else looks good.
BMS-to-Inverter.log

[ai-republic]

The cell voltages are now fixed also min/max.
The BMS alarm is implemented according to the first spec. The other spec seems to be the one that fits says (for the same bit) Unit undervoltage alarm so I guess that might be correct.

[DezR]

No worries, thanks.
I'll be able to try this again tomorrow morning.

Hopefully the sun will be out so it can be tried while charging, discharging and balancing :)

[DezR]

This is looking really good. :)
The "Cell Low" and "Cell High" seem to be swapped, but probably doesn't matter if only used to calc "Cell-diff".
Unfortunately very overcast and raining again, but I had a power supply I could use to put some charge back into the batteries and keep the BMS alive.

I need to get more JK TTL-RS485 adapters for the other 9 BMS's to get a RS485 bus working and add those.

Also once the sun is back out or the batteries charged, check how the inverter is responding.
BMS-to-Inverter.log

[ai-republic]

Ah yes, the min/max cell voltages were only swapped in the log. Fixed that.
So, next will be to correlate the alarms to the propper specification :)

[ai-republic]

I changed the alarms now to support all the general alarms and protection notifications

[DezR]

That's great :)
I'll try it out in a few hours and post and attach a log file.

I'm just reverse engineering the JK TTL-RS485 adapter to be able to use something far cheaper, quicker and easier to get, then will try to get all 10 BMS's hooked up in parallel. It's basically just a DC-DC converter and MAX485 clone.

[DezR]

The serial side is looking good.
I'll start trying different battery profiles on the inverter to try and get one working.
BMS-to-Inverter.log

[ai-republic]

I also fixed the exception in the SMA inverter binding

[DezR]

I'll try it out.
The inverter I have is relatively new, but supposed to be compatible with a bunch of different battery manufacturers and one of the newest LV hybrid inverters that are approved for grid connection here in Australia.

I'll switch over to here while trying it out.

I think you've nailed JK BMS compatibility now :)