-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help for P16S100A, looks like PACE #19
Comments
|
Thanks a lot for your reply, i'll gather all information and come back to you as soon as possible |
The Modbus seems to need a configurated address to work, I use AddressNo. 1. (switch 1 set ON) |
Ok thanks for your reply, I will set both to address 1. No time this evening but will try tomorrow morning |
Ok lots of stuff came up but I did some stuff this morning: Question in advance: anyone knows how I can get pbmstools to communicate on address 0x01? |
I use pbmstools with interface RS232. RS485 is the monitoring interface for me. With homeassistant and esphome, i can also change the parameter (but not all) |
This sounds like good progress. You have to change the address at the YAML to |
FYI! The modbus-address 0x00 is a broadcast address and is not a valid slave-address |
I can't see to make it work. I checked the yaml in my home/esphome-pace-bms folder and it already had 0x01 defined
I see rx and tx blinking on the conversion board irregularly so there seems to be communication that also stops when plugin in the single rs485 port |
I also dont see any value in all the mqtt topics so I'm afraid its not being decoded |
Do you mean by Slave address the battery pack address?? I only have one battery pack |
The responses aren't valid Modbus frames. It looks like Seplos/Pylon responses. This reason could be one of the following options
|
This issue (#17) is about to the same problem. |
Thanks for your quick reply
Do you know by any chance if the seplos/pylon method also needs to be on pack 1? I tried that but only with dip 0 I'll check issue 17 now! Thanks a lot |
Ok thanks again, I will try that tomorrow morning and let you know |
I'm a bit in doubt what to do next. With whatever version of pbmstools I tried yesterday I cannot change the inverter setting. Most versions only work with pack 1-xx. |
Could you provide a screenshot of the |
... and you now the special secret password (123456) for changing settings? |
I'll make tomorrow |
Yups have that. Is a specific password for other settings and one for inverter protocol |
Look at andy's video canal: offgrid-garage |
I sent a message to the company i bought the battery from, didn't got an answer yet, will ask them again |
On the last picture, you have to click <Read> under Inverter protocol to show selected protocols BTW: First you have generaly click <Read> before you can write any parameters, Pace expect complete filled parameterfield to update its parameter. |
Hi Thomas, When pushing read it gives an error, when filling in all field or some fields it gives the same error. Tried all different options. Error is: "Command error" |
@syssi Sebastian, I saw your mention "It looks like some BMS firmware versions doesn't support Modbus. In best case there will be a different firmware version." |
I got all cable the day before going on holiday and all three of them didnt work out of the box |
I got it working with the following cable: SOK SK48V100 Battery RS232 serial communicatrion Prolific USB RS232 to RJ11 6P6C |
May I know which PBMSTool Version you used? Is it online somewhere available? My versions does not allow me to change the protocols.... Thanks! |
So sorry I just read your reply now; I ended up keeping using the rs232 cable because it works reliably and i had a usb-port left :) |
Hello,
I have read the topic/issue "Add PACE BMS support #1" and tried with the default "esp32-example.yaml" but can't get communication to work. My MQTT is working as i can see in the MQTT explorer. I got my battery in error with all experiments (luckily solved now) so I'm a bit more carefull now.
When i readout the pack with pbmstools i can only make connection with the version "Gobel_PC-BMS_Tools_HS2.0.3_Win32", i use rs485 on the parralel port. dip switch is set to 0, the dedicated rs485 next to can isnt working, other dipswitch settings are not working
However I see that address 0x01 is setup in the yaml. Do I need to change the pack dipswitch or change the yaml?
Also I use and only have the "esp32doit-devkit-v1" which i setup in yaml as:
is this correct? I see in the topic "Add PCA BMS support" only 8266 mentioned and a different board.
Also in your documentation you say to use orange/orange-white for B/A, however with pbmstools i can only communicate with brown/brown-white as B/A
I'm using a Joyvoit Suns Energy battery pack BW5KW: https://www.alibaba.com/product-detail/Energy-Power-wall-5-3-2kw_1600330104517.html
Using the pbmstools i get the VER readout: P16S100A-21468-1.00
Searching on google I think this is a PACE BMS, it also look like one, I can confirm it has 100A and 16 cells
Also I'm using the following RS485 3.3-5V module: https://a.aliexpress.com/_mt820MY
Is changing the address setting enough to make this work, and if so do I have to change the dipswitch on the pack or the setting in the yaml?
Sorry for all questions, I'm not experienced with ESP but would really like this to work
Greetings Maikel
The text was updated successfully, but these errors were encountered: