Closed Pho3niX90 closed 8 months ago
So this can be ignored. Tried the following:
tx_pin: GPIO5 rx_pin: GPIO4
Shortly after I noticed the following picture:
This would then be a confirmation that this specific seplos E10 v2 (rebranded as Apexium Apex) works with the software, baud rate 19200
Could you provide some more details about your BMS model? So you are able to talk to your BMS using this component now?
Yes everything is working as it should
So the BMS in question is branded as a "Apex 48200", it's supplied by Docan/Apexium Apex BMS 48V200A-compressed.pdf
It is actually a Seplos E10 (v2),
Manufacturer Info: CAN:PNG_DYE_Luxp_TBB
Part Model: 1101-JK06
Software Version: 16.7
Protocol Version: 2.0
Perfect! I will add the model to the list of supported devices and will close this issue.
See 4688c849fd9d0a0ae17c6ccc8b0d6b6777516ea6
So just recently purchased the ESP32 and a TTL converted, I set everything up, and ran in debug mode. RJ45 is connected to the first RS485 next to the CAN.
On the converter, I can see the periodic tx, but RX is never triggered.
esp32-example.yaml
and have tried both 19200 and 9600 without success.Here is the debug info:![image](https://github.com/syssi/esphome-seplos-bms/assets/7858187/43f03feb-7f68-49e8-affa-d9c1e9ba7d42)
The converter being used:![image](https://github.com/syssi/esphome-seplos-bms/assets/7858187/fb1ef393-c26b-48bd-9d17-07ba284e33d9)
I do see the following warning about GPIO5, not sure if it's related:![image](https://github.com/syssi/esphome-seplos-bms/assets/7858187/2e2dcdf2-e5e1-45cc-8594-ab07e0d78573)