-
Notifications
You must be signed in to change notification settings - Fork 67
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
Add additional Pylontech CAN protocol fields #1213
Conversation
|
22550fd
to
4731984
Compare
CAN message simulator (connect Pi GPIO 10 (MOSI) to ESP32 CAN rx input):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new data points are interpreted and added to the live view, but please also publish them to the MQTT broker and add them to HASS auto-discovery.
3d52a4b
to
8fc39e1
Compare
@DerHavey1994 @Snusme83 Die entsprechenden builds findet ihr hier: https://github.com/helgeerbe/OpenDTU-OnBattery/actions/runs/10709343648?pr=1213 Danke vorab. |
@AndreasBoehm läuft! |
Danke @DerHavey1994 fürs testen! Great job @ranma! |
Servus, soll ich noch testen? Kann ich das hier: |
@Snusme83 Genau da wo du gerade bist kannst du das verlinkte build als update hochladen. |
@Snusme83 Ja. |
91cc2fc
to
8ff94e7
Compare
I noticed that these are missing while looking at dissassembly of the Pytes implementation of the protocol. I also found Pylontech sample CAN messages] which match the Pytes implementation [1]: ``` CAN ID – followed by 2 to 8 bytes of data: 0x351 – 14 02 74 0E 74 0E CC 01 – Battery voltage + current limits ^^^^^ discharge cutoff voltage 46.0V 0x355 – 1A 00 64 00 – State of Health (SOH) / State of Charge (SOC) 0x356 – 4e 13 02 03 04 05 – Voltage / Current / Temp 0x359 – 00 00 00 00 0A 50 4E – Protection & Alarm flags ^^^^^ always 0x50 0x59 in Pytes implementation ^^ module count (matches the blog article image) 0x35C – C0 00 – Battery charge request flags ^^ two possible additional flags (bit 3 and bit 4) 0x35E – 50 59 4C 4F 4E 20 20 20 – Manufacturer name (“PYLON “) ^^^^^^^^^^^^^^ Note: Pytes sends a 5-byte message "PYTES" instead padding with spaces ``` The extra charge request flag is "bit4: SOC low" (Seems to be SoC < 10% threshold for Pytes), I haven't bothered adding that as it provides little value. [1] https://www.setfirelabs.com/green-energy/pylontech-can-reading-can-replication
8fc39e1
to
2aa0607
Compare
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
I noticed that these are missing while looking at dissassembly of the Pytes implementation of the protocol. I also found Pylontech sample CAN messages which match the Pytes implementation [1]:
The extra charge request flag is "bit4: SOC low" (Seems to be SoC < 10% threshold for Pytes), I haven't bothered adding that as it provides little value.
[1] https://www.setfirelabs.com/green-energy/pylontech-can-reading-can-replication