Solder esp8266 directly on seplos 10E display PCB

[itiotdk]

hi i tried to attach an esp on the empty spot on the bluetooth display. the pcb is not correct and seplos is working to fix it and add wifi. but i want to do it my self and use esphome to talk to the bms directly.. but it seems that the comm is not modbus but serial - i get a IM_READY in a terminal connected to the tx and rx. can we translate the protocol from modbus to serial or am i just dreaming.?

[itiotdk]

more info here: https://diysolarforum.com/threads/adding-wifi-esp-to-seplos-display.74588/#post-944930

[itiotdk]

is that replies ? not very good in serial. yet...

[itiotdk]

changed to dummy_receiver: false
and get.

[14:04:49][D][uart_debug:158]: >>> "~20004642E00200FD37\r"
[14:04:51][D][uart_debug:158]: >>> "~200046470000FDA9\r"
[14:04:53][D][uart_debug:158]: >>> "~2000464F0000FD9A\r"
[14:04:55][D][uart_debug:158]: >>> "~200046510000FDAE\r"
[14:04:57][D][uart_debug:158]: >>> "~200046920000FDA9\r"
[14:04:59][D][uart_debug:158]: >>> "~200046930000FDA8\r"

[itiotdk]

seems i soldered the wires wrong. so i get no answers no matter what dummy_receiver is..

[syssi]

The dummy_receiver: true is important if there is no component consuming the uart buffer. You should use this test YAML for testing: https://github.com/syssi/esphome-seplos-bms/blob/main/tests/esp8266-requests.yaml#L37-L62

The log capture from above with >>> outgoing and <<< incoming traffic is the better one. It looks like your BMS did respond with <<< "\nOK\r" and some linebreak to some requests: >>> "~200046510000FDAE\r". In my opinion you are talking the wrong protocol. Because OK\r is neither a valid response of the Seplos/Pylontech plaintext protocol with the ~ premable nor a valid Modbus response.

[itiotdk]

ok. i changed to true. and i get:

[15:50:40][W][component:215]: Components should block for at most 20-30ms.
[15:50:42][D][api.connection:1089]: Home Assistant 2023.12.1 (10.0.0.191): Connected successfully
[15:50:43][D][uart_debug:158]: >>> "~20004642E00200FD37\r"
[15:50:45][D][uart_debug:158]: >>> "~200046470000FDA9\r"
[15:50:45][D][uart_debug:158]: <<< "\r"
[15:50:45][D][uart_debug:158]: <<< "\r"
[15:50:45][D][uart_debug:158]: <<< "\nOK\r"
[15:50:45][D][uart_debug:158]: <<< "\r"
[15:50:46][D][uart_debug:158]: <<< "\n"
[15:50:47][D][uart_debug:158]: >>> "~2000464F0000FD9A\r"
[15:50:49][D][uart_debug:158]: >>> "~200046510000FDAE\r"
[15:50:49][D][uart_debug:158]: <<< "\r"
[15:50:49][D][uart_debug:158]: <<< "\r"
[15:50:49][D][uart_debug:158]: <<< "\nOK\r"
[15:50:49][D][uart_debug:158]: <<< "\r"
[15:50:49][W][component:214]: Component uart took a long time for an operation (0.05 s).
[15:50:49][W][component:215]: Components should block for at most 20-30ms.
[15:50:50][D][uart_debug:158]: <<< "\n"
[15:50:51][D][uart_debug:158]: >>> "~200046920000FDA9\r"
[15:50:51][D][uart_debug:158]: <<< "\r"
[15:50:51][D][uart_debug:158]: <<< "\r"
[15:50:51][D][uart_debug:158]: <<< "\nOK\r"
[15:50:52][D][uart_debug:158]: <<< "\r"
[15:50:52][W][component:214]: Component uart took a long time for an operation (0.05 s).
[15:50:52][W][component:215]: Components should block for at most 20-30ms.
[15:50:52][D][uart_debug:158]: <<< "\n"
[15:50:53][D][uart_debug:158]: >>> "~200046930000FDA8\r"
[15:50:54][D][uart_debug:158]: <<< "\r"
[15:50:54][D][uart_debug:158]: <<< "\r"
[15:50:54][D][uart_debug:158]: <<< "\nOK\r"
[15:50:54][D][uart_debug:158]: <<< "\r"
[15:50:54][D][uart_debug:158]: <<< "\n"
[15:51:03][D][uart_debug:158]: >>> "~20004642E00200FD37\r"

[itiotdk]

i asked about protocols. they send me modbus info... i will look at your link.

[syssi]

Could you provide the MODBUS-ASCII Communication Protocol protocol document? F.e. my mail.

[syssi]

The protocol of the provided description should respond to ~2000464F0000FD9A\r with ~200046000000FDB4\r. OK\r isn't a valid response here too.

[itiotdk]

No it's not the correct doc. We will see if they answer my mail.

[itiotdk]

I've got the Bluetooth protocol from solos. So if the Bluetooth chip is just a bridge we now have the info on the serial data available on the board?

I sent it to your mail.

[itiotdk]

Happy new year

Did you get the information? And was it useful ?