Waveshare RS4845 to Wifi Converter - MQTT connection got hex number evaluation?

Hardware
1

Hello, today I have a question and hope someone can help me. I bought an RS485 to WiFi converter for my home storage system and set it up for testing. According to the battery’s datasheet, the RS485 cables were connected to the converter.

https://www.waveshare.com/wiki/RS485_TO_WIFI/ETH

I then set up an MQTT connection and, after a bit of searching, found out that dip6 (or maybe dip5) needs to be on for my battery. Now I can see data in the MQTT Explorer via the converter. But it’s just a hex number, I think. This needs to be interpreted, but I don’t know how do or what I’m doing wrong. Ultimately, the battery data is hidden behind it somehow.

image
image2513×1002 488 KB

Unfortunately, I can’t find much information online about the waveshare component and how to configure it. You might have to change something there and the data would then be delivered to MQTT in a different format. I’m not really sure, and I’ve been experimenting for a few days now.

If anything is unclear or more information is needed, I’ll be happy to provide it.

2

I got these batteries through a friend because he’s now powering his Victron system with even larger batteries. So I got two 5.12kWh storage units; I couldn’t say no.

[[Papool 48v 100Ah / identical to pylontech 100ah 48 V]](https://de.aliexpress.com/item/1005003764117272.html?spm=a2g0o.productlist.main.17.41ecw9lQw9lQ8F&algo_pvid=eec4e16b-1064-44f8-8ef6-9247ac4d26f7&algo_exp_id=eec4e16b-1064-44f8-8ef6-9247ac4d26f7-8&pdp_ext_f={"order"%3A"12"%2C"ev al%22%3A%221%22%7D&pdp_npi=4%40dis%21EUR%211520.96%21775.69%21%21%211612.21%21822.23%21%40210384b217427664122656570e5fd c%2112000046080827491%21sea%21DE%213411042977%21X&curPageLogUid=MReynQ0QDdMA&utparam-url=scene%3Asearch%7Cquery_from%3A)

With Waveshare RS485 to Wifi I get data from the Battery. That’s obviously working correctly. I’ve set the baud rate, etc.

I’m currently calculating the battery values ​​based on what’s being charged and discharged. I factor in losses, and that works quite well. I read the battery voltage via the inverter and can use it to perform emergency shutdowns. So I have all the important data, but over time, the values ​​will always shift slightly, and I won’t be running down to the basement every two weeks or so to correct them.

The BMS must have something to do with DR; in any case, it’s shown on the battery display and the program (USB serial) also references it.

So I tested all versions of BMS Pace last night, but unfortunately without success. New MQTT values ​​were generated, just not filled in.

BMS Pace – Python Data Retrieval

So I kept searching and came across DR Switcher, with great hope. The title already lists the protocol that’s also listed in the USB program, “Protocol DR-1363.”

DR-JC03-RS485-Switcher

I fed the script from chatgpt with one of my HEX numbers today, but the resulting values ​​don’t really match, except for the temperatures. So I’m not sure if it makes sense to install it on the Raspberry Pi now.

In any case, I learned that the HEX number is converted by the script and apparently a counter-request occurs beforehand, but I didn’t really understand that.

I found what I was looking for here in an English forum; others have the same problem.

I also need a solution for how to convert the HEX number using a script to the DR-1363 protocol. But unfortunately, I lack the knowledge to implement it on my own.

My last attempt yesterday was to create a local server to read the data with Scrape. Since I open the program in the browser, that would also be an option. Then a PC would always have to be connected, albeit via USB, to retrieve the data. That’s not so nice, and Scrape always requires an http address.

Oh, and then there are DIP switches 1-6. If dip 1 is on and the others are off, I can connect to the PC. If dip 6 is on and the others are off, I can retrieve the data via Waveshare.

Maybe thats helps to understand my Problem better.